Checkout.com MCP server
Give your AI assistant 7 tools it can call in Checkout.com, over one server URL.
Checkout.com is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.
- Tools
- 7
- Works with
- Any MCP client
- Auth
- API key
- License
- MIT, open source
- Updated
- August 2026
About the Checkout.com MCP server
Connect Checkout.com once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Checkout.com and 760+ other apps over a single connection, on our cloud or a self-hosted install.
Tools
Checkout.com tools your AI can run
Once connected, your assistant can call any of these Checkout.com actions by asking in plain language.
Create Customer
Store a customer's details in a customer object to reuse in future payments. You can link payment instruments and set a default instrument.
6 fields
Update Customer
Update existing customer or their metadata.
7 fields
Create Payment Link
Create a Payment Link to accept and process payment details.
35 fields
Create Payment
Process and manage payments from various sources including card payments and payouts.
50 fields
Refund a Payment
Issue a refund (full or partial) for a captured payment. Supports split refunds, line items, and bank account destinations.
32 fields
Get Payment Details
Check transaction amount and status before refunding.
2 fields
Get Payment Actions
Build full transaction lifecycles for audit logs.
2 fields
Triggers
Checkout.com events your agent can watch
These start a run the moment something happens in Checkout.com, so work gets picked up on its own.
Payment Events
Trigger order fulfillment when payment is approved.
1 field
Dispute Events
Notify operations upon dispute opening or resolution.
1 field
Checkout.com MCP, answered.
No. That is the point of it. One Activepieces server exposes Checkout.com alongside every other piece you connect, so your client keeps a single connection.