Checkout.com MCP. Handle payments, refunds, and vaults from conversation.
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 handles your entire payment lifecycle: request payments, capture funds, process refunds, and manage card instruments. Connect this MCP to any AI client to automate complex financial workflows directly from natural conversation.
You'll handle everything from voiding transactions to auditing detailed billing history without switching dashboards.
What your AI agents can do
Capture payment
Locks an authorized transaction, converting it into settled funds and finalizing the sale.
Create instrument
Generates and securely stores new card payment details in the vault for later use.
Delete instrument
Permanently removes a specific payment instrument record from the vault.
Converts an authorized payment into settled limits, completing the sale and securing the funds.
Initiates refunds or cancels authorizations (voids) for payments that didn't go through.
Creates, reads, modifies, and deletes payment instruments (cards) in a secure vault.
Retrieves detailed logs showing every step taken on an account or payment to diagnose failures.
Identifies customer records and prepares them for a new payment flow within the gateway.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Checkout.com Payment MCP (10 Tools)
These ten tools let you programmatically control every aspect of payment processing, including fund capture, instrument management, and detailed transaction auditing.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Checkout.com on Vinkius019d756ecapture payment
Locks an authorized transaction, converting it into settled funds and finalizing the sale.
019d756ecreate instrument
Generates and securely stores new card payment details in the vault for later use.
019d756edelete instrument
Permanently removes a specific payment instrument record from the vault.
019d756eget instrument
Identifies and retrieves active card records currently stored in the vault.
019d756eget payment actions
Lists structured rules and state changes attached to a gateway transaction.
019d756eget payment details
Extracts key properties about an active billing record to understand its current status.
019d756erefund payment
Sends money back to the original card network for a specific payment.
019d756erequest payment
Finds necessary customer records within the system to initiate a new payment request.
019d756eupdate instrument
Modifies existing stored card details, like changing the billing address or holder name.
019d756evoid payment
Cancels an authorized transaction, dropping limits before final settlement.
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,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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
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.
Sifting Through Payments is a Nightmare
Right now, if you need to figure out why a payment failed or track down the details of an old refund, you're bouncing between three different dashboards. You copy a transaction ID from one screen, jump into another system to check its status, and then open a third place just to view the audit log. It's slow, it involves too many clicks, and frankly, it’s exhausting.
With this MCP, you tell your agent exactly what you need—like 'Show me every action on payment pay_456.' You get a single, structured response that tells you everything: who authorized it, when the funds were captured, and why any failures happened. It cuts out all the jumping around.
Vaulting Instruments with Checkout.com
Manual processes force teams to treat card data as an external resource. You might copy a customer's last four digits into a CRM, then paste it somewhere else for billing, creating messy, unverified records that are hard to audit and risky to manage.
This MCP gives you the ability to programmatically manage instruments using `create_instrument`. The data lives in Checkout.com's secure vault, accessible by your agent only when needed. You don't store it; you reference it.
What you can do with this MCP connector
This connector lets you run the full spectrum of payment operations through your agent. Need to process a sale, but only after verifying details? You can request funds and then later capture them when inventory clears—all in one conversation. If an order gets canceled, you don't have to manually navigate refund portals; tell your agent to issue a refund directly.
Beyond basic transactions, you manage payment instruments, securely creating or updating card records, which is crucial for subscription services. The system also tracks every action taken on a payment, giving you a full audit log of successes and failures. Because handling money means accuracy is non-negotiable, Vinkius gives you complete visibility into everything your agent does through its AI Analytics layer, tracking exactly what data flowed when executing these calls.
You finally have one place to manage the entire flow—from initial authorization requests to final reconciliation reporting.
019d756e-9a1b-70b3-9ec7-3704563b91d3 
How Checkout.com MCP Works
- 1 Subscribe to this MCP and provide your Checkout.com Secret API Key, selecting either Sandbox or Live environment.
- 2 Connect your preferred AI client (Claude, Cursor, etc.) to the Vinkius platform using that single credential set.
- 3 Tell your agent what you need—for example, 'Refund payment pay_123 for $50.00'—and execute the command conversationally.
The bottom line is: you connect once to Vinkius and use this MCP to manage payments across all your client apps.
Who Is Checkout.com MCP For?
E-commerce operations managers, finance analysts, and senior developers. You're the one who gets stuck at 2 AM trying to reconcile a failed batch of refunds or needs to test complex payment flows without touching production credentials.
You use this MCP to audit specific transaction histories and verify that every refund processed matches the expected amount for month-end reconciliation.
You test new payment features in sandbox mode, using your agent to provision card instruments or simulate complex failure scenarios before deployment.
When a customer calls about a billing issue, you use this MCP to look up the full history of their payments and guide them through the resolution process instantly.
What Changes When You Connect
- Automate full payment cycles: Start by using
request_paymentto identify a customer, then usecapture_paymentwhen the goods ship. It handles the entire state transition without you lifting a finger. - Maintain security while working: You don't have to store sensitive card data yourself. Use
create_instrumentandget_instrumentto provision and retrieve records in the secure vault. - Diagnose failures instantly: If something goes wrong, calling
get_payment_actionsgives you a detailed log of every rule change or state transition that happened during the transaction. - Handle complex reversals: Instead of manual clicks, use
refund_paymentto process money back directly. You can also proactively callvoid_paymentif an order needs canceling before capture. - Keep your data clean: Use
delete_instrumentwhen a card is retired or compromised, ensuring that obsolete records are permanently vaporized and removed from the vault.
Real-World Use Cases
The Refund Trail
A customer calls claiming they were double-charged. Instead of searching multiple dashboards, your agent uses get_payment_details to pull up all billing data and then executes a refund via refund_payment, providing the customer with immediate proof.
The Subscription Update
A user's credit card expires. You use your agent to first run get_instrument to find their existing record, then call update_instrument to plug in the new details and keep billing uninterrupted.
The Failed Batch
You need to process 50 payments, but a few fail. Your agent runs through all transactions, using get_payment_actions on each failure to identify if the issue was insufficient funds or an invalid card.
The Failed Test
A developer needs to test a payment flow but doesn't want to commit real money. They use void_payment in sandbox mode, simulating failure and proving the logic works without any actual financial impact.
The Tradeoffs
Trying to refund an unknown ID
The user tries to call a refund function with a payment ID they only vaguely remember, leading to a failure because the required source data isn't available.
→
Always first use get_payment_details or get_payment_actions to confirm the full details and status of the payment before attempting any reversal using refund_payment.
Manually managing card data
A developer writes code to handle card storage, leading them to store raw PCI data locally and risking a massive compliance failure.
→
Use the secure vault functions like create_instrument or update_instrument. The system handles the sensitive storage, so you never have to worry about keeping keys on disk.
Assuming authorization equals capture
A developer calls a payment request and assumes the money is safe. They later find out the funds were only authorized but not finalized.
→
Remember that authorization is temporary. You must explicitly call capture_payment to lock in those limits and make the transaction final.
When It Fits, When It Doesn't
Use this MCP if your core problem involves managing state transitions across the payment lifecycle: from initial request, through authorization, to capture, and finally to refund or void. It's mandatory when you need to audit why a payment failed or when you must programmatically manage stored card instruments. Don't use it if all you need is simple data retrieval—a generic database connector might suffice. But if the data relates to money movement, settlement status, or vaulting, this MCP provides the necessary depth and control.
When building complex payment flows that cross systems (e.g., calling a billing API after capturing funds), remember the power of Vinkius. You can chain multiple different MCPs together with your agent—like combining this Checkout.com flow with an inventory MCP—to build automations that span platforms, all through one single connection.
Common Questions About Checkout.com MCP
How do I process a refund with the refund_payment tool? +
You tell your agent to run refund_payment and provide the payment ID and the exact amount. The system will dispatch an automated validation check and initiate the money transfer back to the originating card network.
Can I see what happened when a payment failed using get_payment_actions? +
Yes, get_payment_actions enumerates all attached structured rules. It gives you a detailed record of every status change or failure code that occurred on the transaction.
What is the difference between void_payment and refund_payment? +
Voiding (void_payment) cancels an authorization before funds are settled. A refund (refund_payment) moves hard money back after a payment has already successfully captured.
How do I save a customer's card details for later use? +
You must use the create_instrument tool to provision and securely store the card data in the vault. You then reference this instrument ID whenever you need to charge them again.
When I use `create_instrument`, how are my sensitive card details kept secure? +
Your credentials pass through a zero-trust proxy and never sit on a disk. Vinkius runs the tool inside an isolated sandbox, enforcing 34+ security rules for every call.
What information can I get from `get_payment_details` for reconciliation? +
It performs structural extraction of properties that drive active billing logic. You get detailed records on the payment's status, authorization history, and associated fees.
If my `capture_payment` call fails, what should I check first? +
First, check the specific transaction details using get_payment_actions. This tool shows if the failure was due to insufficient funds or a gateway block during settlement.
What is the right sequence for processing a payment when I only have customer IDs? Should I use `request_payment`? +
Yes, you must start with request_payment. This identifies bounded CRM records within the Checkout.com Gateway before you can proceed to capture or refund any funds.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.