Integration

Checkout.com integration

Enterprise payment gateway and unified commerce platform. Process card payments, alternative payment methods, and payouts; manage customers and stored payment instruments; create payment links and Hosted Payments Pages; handle disputes; configure webhook workflows; and query balances. Built for global merchants needing high-throughput, multi-currency processing with built-in 3D Secure, risk management, and reconciliation.

Connect Checkout.com How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Checkout.com.Built from the 30 Checkout.com tools below, on the connection you add once.

Common Checkout.com use cases

GDPR erasure
support lookups
chargeback defense
reconciliation
subscription onboarding
invoicing
card removal
saved-card UI
webhook audit
checkout flows

What you can do with Checkout.com

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Customer, 4 operations

create_customerCreate customerPOSTCreates a Checkout.com customer record.
delete_customerDelete customerDELETEDeletes a Checkout.com customer and detaches their stored instruments.
get_customerGet customerGETRetrieves a Checkout.com customer with their attached payment instruments.
update_customerUpdate customerPATCHUpdates a Checkout.com customer's profile fields and default instrument.

Instrument, 4 operations

create_instrumentCreate instrumentPOSTCreates a stored payment instrument (token-backed card or bank account) attached to a customer.
delete_instrumentDelete instrumentDELETEDeletes a stored Checkout.com instrument.
get_instrumentGet instrumentGETRetrieves a stored Checkout.com payment instrument.
update_instrumentUpdate instrumentPATCHUpdates a Checkout.com instrument (expiry, holder details, linked customer, metadata).

Dispute, 2 operations

accept_disputeAccept disputePOSTAccepts a Checkout.com dispute, conceding the chargeback without submitting evidence.
get_disputeGet disputeGETRetrieves a Checkout.com dispute with full details and accepted evidence types.

Dispute evidence, 2 operations

provide_dispute_evidenceProvide dispute evidencePUTStages the evidence fields for a Checkout.com dispute (idempotent), before locking and submitting them to the issuer.
submit_dispute_evidenceSubmit dispute evidencePOSTSubmits the staged evidence package for a Checkout.com dispute, locking it for issuer review.

Payment, 2 operations

get_paymentGet paymentGETRetrieves a Checkout.com payment by ID with full status, source, and action history links.
request_paymentRequest paymentPOSTSends a Checkout.com payment or payout - authorize a card, charge an alternative payment method, or push funds to a destination.

Payment link, 2 operations

create_payment_linkCreate payment linkPOSTCreates a hosted Checkout.com Payment Link the customer can open in a browser to complete payment.
get_payment_linkGet payment linkGETRetrieves a Checkout.com Payment Link with its current status and any associated payment.

Workflow, 2 operations

create_workflowCreate workflowPOSTCreates a Checkout.com notification workflow that fires webhooks on matching payment/dispute events.
delete_workflowDelete workflowDELETEDeletes a Checkout.com notification workflow.

Authorization, 1 operation

increment_authorizationIncrement authorizationPOSTIncrements the authorized amount on an existing Checkout.com payment.

Balances, 1 operation

get_balancesGet balancesGETRetrieves Checkout.com account balances for an entity, broken down by currency.

Capture, 1 operation

capture_paymentCapture paymentPOSTCaptures funds from a previously authorized Checkout.com payment, in full or in part.

Disputes, 1 operation

list_disputesList disputesGETLists Checkout.com disputes (chargebacks) filtered by status, payment, ARN, MID, or date range.

Hosted payment, 1 operation

create_hosted_paymentCreate hosted paymentPOSTCreates a Checkout.com Hosted Payments Page session for redirect-based card collection.

Payment actions, 1 operation

get_payment_actionsGet payment actionsGETLists all actions performed on a Checkout.com payment (authorize, capture, refund, void, reversal).

Payment methods, 1 operation

list_payment_methodsList payment methodsGETLists Checkout.com payment methods available for a given buyer context (country, currency, amount).

Payments, 1 operation

search_paymentsSearch paymentsPOSTSearches Checkout.com payments using a structured field:'value' query and date range with pagination.

Refund, 1 operation

refund_paymentRefund paymentPOSTRefunds a captured Checkout.com payment, in full or in part.

Reports, 1 operation

list_reportsList reportsGETLists Checkout.com reconciliation and financial reports generated for the account.

Void, 1 operation

void_paymentVoid paymentPOSTVoids an authorized but not-yet-captured Checkout.com payment.

Workflows, 1 operation

list_workflowsList workflowsGETLists all Checkout.com notification workflows on the account.

Checkout.com API rate limits

100 requests per second

100 RPS for GET and 100 RPS for POST/PUT/DELETE separately

These are the limits Checkout.com documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Checkout.com documentation for current values.

Use Checkout.com from Claude Code, Cursor or Codex

Connect Checkout.com in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Checkout.com operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Checkout.com

Create your workspace
Sign up free. Nothing to install.
Connect Checkout.com once
Add your Checkout.com connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Checkout.com integration FAQ

What can you do with the Checkout.com integration?

LiveContext exposes 30 operations on Checkout.com, covering customer, instrument, dispute and dispute evidence. Common uses include GDPR erasure, support lookups and chargeback defense.

What are the Checkout.com API rate limits?

Checkout.com documents 100 requests per second. 100 RPS for GET and 100 RPS for POST/PUT/DELETE separately Limits are set by Checkout.com and can depend on your plan.