Checkout.com
Checkout.com is a global payment processor offering card acquiring, alternative payments, fraud, and connected accounts via a single API. Direct integrations with Visa, Mastercard, and APMs.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Checkout.com the way a machine reads it — 28 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Checkout.com scores 41.6/100 (thin), with a separate agent-readiness read of 56/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Checkout.com
Each block below is one kind of artifact we hold for Checkout.com. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Checkout.com Payments API
Process card and alternative payment methods with full lifecycle support including authorization, capture, void, refund.
Checkout.com Payouts API
Send payouts to cards, bank accounts and wallets.
Checkout.com Payment Sessions & Flow API
Hosted Flow component and payment sessions for SCA-ready payment workflows.
Checkout.com Payment Links & Hosted Payments API
Generate shareable payment links and hosted payment pages.
Checkout.com Issuing API
Issue physical and virtual cards with spending controls.
Checkout.com Tokenization & Instruments API
Tokenize and store payment credentials as instruments.
Checkout.com Disputes & Risk API
Manage chargebacks, disputes, AML screening and identity verification.
Checkout.com Forex API
Foreign exchange rate services for multi-currency processing.
Checkout.com Apple Pay & Google Pay API
Provision and process payments through Apple Pay and Google Pay.
Checkout.com Network Tokens API
Provision and manage network tokens for higher authorization rates.
Checkout.com Transfers & Balances API
Move funds between balances and entities on the platform.
Checkout.com Reporting & Financial Actions API
Transaction reporting, reconciliation, and financial action exports.
Checkout.com Customers API
The Customers API from Checkout.com — 2 operation(s) for customers.
Checkout.com Instruments API
The Instruments API from Checkout.com — 2 operation(s) for instruments.
Checkout.com Payments API
The Payments API from Checkout.com — 5 operation(s) for payments.
Checkout.com Tokens API
The Tokens API from Checkout.com — 2 operation(s) for tokens.
Checkout.com Workflows API
The Workflows API from Checkout.com — 2 operation(s) for workflows.
Scroll within the panel for all 17 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Checkout.com API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Checkout.com GraphQL API
Checkout.com is a global payments platform offering card acquiring, alternative payment methods, and embedded finance. The API covers payments, payouts, sessions, instruments, d...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Checkout Com Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Checkout Com Finops
FINOPSSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Checkout.com — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/checkout-com · machine-readable index on apis.io