Checkout.com MCP. Manage payments, refunds, and card instruments via natural language.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Checkout.com MCP Server lets you manage all global payments directly from your AI agent. Use the server to request, capture, void, and refund payments.
You can also vault and manage payment cards (instruments) and audit all associated actions using natural conversation.
What your AI agents can do
Capture payment
Converts an authorized transaction into settled funds, completing the payment process.
Create instrument
Creates a new payment card record and stores it in the secure Checkout.com Vault.
Delete instrument
Permanently removes a payment card record from the Vault.
Initiate payment requests, capture authorized funds, or send refunds/voids without switching dashboards.
Create, read, update, and delete payment cards (instruments) in the secure Vault, keeping them ready for future use.
Retrieve detailed payment actions and structural properties to understand exactly what happened with a transaction.
Look up specific payment details and activity logs to resolve billing or reconciliation questions.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Checkout.com MCP Server: 10 Tools for Payments & Vaults
Use these 10 tools to handle every stage of payment processing, from initiating a payment request to voiding or refunding funds, all through your AI agent.
019d756ecapture payment
Converts an authorized transaction into settled funds, completing the payment process.
019d756ecreate instrument
Creates a new payment card record and stores it in the secure Checkout.com Vault.
019d756edelete instrument
Permanently removes a payment card record from the Vault.
019d756eget instrument
Retrieves the details of a specific payment card from the Vault.
019d756eget payment actions
Lists every recorded action taken on a payment, showing authorization successes and failures.
019d756eget payment details
Extracts specific properties and data points from a payment record.
019d756erefund payment
Sends money back to the original card or bank account associated with the payment.
019d756erequest payment
Starts a payment transaction, identifying the necessary customer and billing records.
019d756eupdate instrument
Modifies the details of an existing payment card record in the Vault.
019d756evoid payment
Cancels a pending payment before funds are captured, often used to prevent gateway fees.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Checkout.com, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're running your whole global payments stack right from your AI client. The Checkout.com MCP Server lets you manage everything—requests, captures, refunds, and voids—without ever leaving your conversation window. You can also handle payment cards, or 'instruments,' and check the history of every action.
Process Fund Movements
- You can start a payment transaction using
request_payment, which identifies the customer and billing records needed. To finish the deal, youcapture_paymentconverts an authorized transaction into settled funds. You can undo a pending payment before capturing it withvoid_payment, which keeps you from getting hit with gateway fees. Need to send money back? Yourefund_paymentsends cash back to the original card or bank account. - Manage Payment Instruments
You control the secure Checkout.com Vault, handling payment cards (instruments) directly. Use create_instrument to save a new card record. You can also pull up details for a specific card using get_instrument, modify existing card details with update_instrument, or wipe a card record completely using delete_instrument.
Audit Transaction Status
- Need to know what went down with a payment?
get_payment_actionslists every single recorded action on a payment, showing you if authorizations succeeded or failed. To dig deeper into the payment itself,get_payment_detailsextracts specific properties and data points from the record.
Track Payment History
- You can look up specific payment details and activity logs by using
get_payment_detailsto resolve billing or reconciliation questions.
How Checkout.com MCP Works
- 1 Subscribe to the server and provide your Checkout.com Secret API Key. Choose the environment (Sandbox or Live).
- 2 Your AI client sends a command (e.g., 'Refund payment pay_123 for $50.00').
- 3 The server executes the corresponding tool, handles the API calls, and returns the final status and results to your client.
The bottom line is, you talk to your agent, and the agent handles the complex payment logic behind the scenes.
Who Is Checkout.com MCP For?
The e-commerce operations manager who needs to process refunds and voids instantly, without logging into a dedicated dashboard. Also, developers testing payment flows in a sandbox environment, and finance analysts who need to audit payment actions for reconciliation.
Handles customer refunds and voids instantly via chat, eliminating the need to jump between tabs or specialized dashboard views.
Tests full payment flows in the sandbox environment, debugging instrument vaulting logic using natural language.
Audits payment actions and verifies capture statuses for monthly reconciliation reports.
What Changes When You Connect
- Process refunds and voids without context switching. The server lets you handle these actions directly, eliminating the need to jump between dashboard views.
- Maintain a secure, centralized card vault. Use
create_instrument,update_instrument, anddelete_instrumentto manage card data without leaving your AI agent. - Instantly debug payment failures. Use
get_payment_actionsto see a full log of every attempt, pinpointing exactly where the authorization failed. - Streamline reconciliation. Query
get_payment_detailsandget_payment_actionsto pull specific, auditable payment statuses for finance reports. - Complete the full payment cycle. Start with
request_paymentand finalize withcapture_payment—all in one conversation. - Minimize financial risk. Use
void_paymentto drop limits when a transaction is canceled, avoiding potential gateway fees.
Real-World Use Cases
Customer needs a refund.
A customer service agent receives a request for a refund on payment pay_123. Instead of navigating to the billing portal, the agent asks their AI agent to run refund_payment for $50.00. The agent executes the tool and confirms the refund status immediately.
Developer needs to test a purchase flow.
A developer needs to validate a new checkout flow. They ask their agent to first create_instrument for a test card, then request_payment, and finally capture_payment in the sandbox. The agent guides them through the full, traceable cycle.
Finance team must reconcile a batch of payments.
The finance team runs a query asking the agent to list all payment actions for a specific date range using get_payment_actions. This pulls a structured list of success/fail codes, allowing for fast, accurate reconciliation.
Ops team must cancel a pending order.
An order is canceled before payment capture. The ops team asks the agent to run void_payment on the initial request, ensuring no funds are trapped and avoiding unnecessary gateway fees.
The Tradeoffs
Only checking payment status.
The developer tries to manually look up a payment ID using only a simple text prompt, which might fail if the payment details are complex or require specific fields.
→
To get a complete picture, use get_payment_details to pull structured properties, or use get_payment_actions to see the full history of attempts and status changes.
Forgetting to void payments.
A user cancels an order, but forgets to call a function to release the held funds, leading to unnecessary gateway fees and potential financial discrepancies.
→
Always run void_payment when an order is canceled before capture. This drops the limits and keeps your transaction clean.
Trying to manage cards manually.
A user attempts to update a card's expiry date or holder name by editing a record in a web interface, which might not reflect the latest vault logic.
→
Use update_instrument with the specific instrument ID. This guarantees the change is recorded and traceable in the official Checkout.com Vault.
When It Fits, When It Doesn't
Use this server if your primary job is managing the entire lifecycle of money. You need to move funds, store card data, or audit complex transaction sequences. You must use it if you need to go beyond simple 'check status' queries, because tools like void_payment and capture_payment change the state of money. Don't use it if you only need to verify if a payment record exists. For that, basic database lookups might suffice. But if you need to know why it failed, or if you need to actively change the state (like refunding or voiding), this server is essential. The core difference is active state change vs. passive data reading.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Checkout.com. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Handling payments shouldn't require jumping between five different dashboards.
Today, processing a simple refund means opening the billing portal, finding the transaction ID, navigating to the refund section, entering the amount, and submitting. If you need to check the payment's full history afterward, you have to copy the ID and paste it into a separate audit log.
With this MCP server, you tell your agent: 'Refund payment pay_123 for $50.00'. The agent handles the entire sequence, calling `refund_payment`, and confirms the success—all in the chat. It’s the full process, zero context switches.
Checkout.com MCP Server: Control payment captures and voids.
Without this server, canceling a payment involves complex, multi-step forms to ensure the held limits are released. Furthermore, you need to verify if the cancellation avoids certain gateway fees, requiring manual checks against service agreements.
Now, you simply instruct your agent to `void_payment` on the initial request. It executes the tool, guaranteeing the limits drop cleanly. You control the transaction state from the command line, period.
Common Questions About Checkout.com MCP
How do I refund a payment using the refund_payment tool? +
You send a command specifying the payment ID and the amount. The agent executes refund_payment and sends confirmation that the money transfer was initiated at the gateway.
What is the difference between void_payment and refund_payment? +
A void cancels a pending payment before funds move, dropping limits. A refund moves hard cash back to the card after the funds have already moved.
How do I manage payment cards with the create_instrument tool? +
Use create_instrument to generate a new payment card record and bind it to the Vault. You can then use get_instrument to check its details later.
Can I check if a payment failed using get_payment_actions? +
Yes. get_payment_actions enumerates every structured rule and event attached to a payment, letting you see the specific failure code and why the authorization failed.
What kind of data can I retrieve using the get_payment_details tool? +
You get structured billing data. This tool extracts properties that drive active billing logic, letting you understand exactly what a payment record contains.
How do I list all my saved payment instruments with the get_instrument tool? +
The tool identifies active payment arrays within the Vault. You'll get a list of all stored cards and payment methods you can use for future transactions.
Can I track payment activity history using the get_payment_actions tool? +
Yes, this tool enumerates all attached structured rules. You can track the full lifecycle of a payment, seeing every authorization attempt and status change.
What happens when I need to void a payment using the void_payment tool? +
The tool drops limits before a capture closes, preventing heavy gateway fees. This lets you inspect the internal arrays without completing the transaction.
Can my agent help me debug why a payment failed? +
Yes. Ask your agent to get payment actions for a specific ID. It returns a detailed trace of everything that happened at the gateway level, identifying exactly why an authorization fell through, from CVV checks to insufficient funds.
Is it safe to manage card instruments via the AI agent? +
Absolutely. The server uses Checkout.com's native Vault logic. Sensitive PANs are wrapped safely, and your API keys are encrypted at rest. The agent only interacts with tokens or vaulted IDs, maintaining high security standards.
Can I test this in sandbox before going live? +
Yes. Simply choose the 'Sandbox' environment during setup and use your sandbox secret key (sk_sbox_...). This allows you to simulate transactions and vaulting logic without processing real money.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Blink Payment
Manage payments, customers, and paylinks seamlessly using Blink Payment with AI Agents.
Kraken
Get real-time cryptocurrency prices, OHLC data, order books and trades from Kraken exchange.
BILL (Bill.com)
Manage financial operations via BILL — list vendors, customers, bills, and invoices directly from any AI agent.
You might also like
Restful Booker
Manage hotel bookings via the Restful Booker API—create, retrieve, update, and delete reservations directly from your AI agent.
GrowthBook
Manage feature flags and experiments via GrowthBook — control environments, toggle features, and organize projects directly from your AI agent.
ScreenshotOne
Capture website screenshots — audit visual content and generate PDFs via AI.