Can an AI agent use Checkout.com?
Checkout.com is a payments company whose API handles card payments, refunds, disputes, 3D Secure, stored customer cards and webhook workflows.
Rank among the 246 products we drove
- Time to get in
- tied #42
- 4minutes
- Getting in on its own
- Core work done
- tied #85
- 60%
- 6 of 10 core tasks
- Steps on its own
- tied #86
- 2/ 5
- Find to Leave, no person
Yes. Our agent signed up for Checkout.com on its own in a browser with an email and password, got an API key and used its API. It also has an MCP server. No CLI found.
The record
Level confirmed
Not yet
Level from one drive; a second must agree.
- Got in by
- Sign-up in a browser4 minutes
- Got as far as
- Use: 6 of 10 core tasksA person has to buy
Connects by
MCP, API, SDK
Agent payments
None found
On its own · 412 doc pages read
Docs it can act on: llms.txt, an OpenAPI and an MCP server.
On its own · 4 minutes
Sign-up in a browser.
Partly · 6 of 10 core tasks
Did: take a test card payment and read it back; capture, partly refund and cancel test payments. 4 not done, among them: create a hosted payment page or payment link.
Stopped
Needs a person to buy. These add-ons are not switched on for a self-serve account.
Partly
Nothing to cancel. Its account stays.
- On its own
- Partly
- Stopped
To reach L4: Do 80% of the core work (now 60%) and delete its account, so its keys and login stop working.
See how it ranks among payment APIs for agents.
Own Checkout.com? 9 things to fix. Get your findings, free
Checked 18 Nov 2026: MCP server asks for a sign-in, sign-up page, llms.txt and OpenAPI unchanged since the check before.
Find
How an agent connects
MCP, API, OpenAPI, SDK and llms.txt found.
MCP server
Listed, not testedOfficial server. Remote MCP (beta), 9 tools when driven documented, OAuth with allowlisted clients. Sign‑in needed to see its tools.
9 tools mapped in our drive, none of them called
API
76 of 236 testedREST, 236 operations, OpenAPI 3.0.1, per-account base URL.
236 operations mapped in our drive
OpenAPI
YesA machine-readable description of the API.
CLI
None foundSDK
Listed, not testedBack-end SDKs: Go, Java, .NET, Node.js, PHP, Python, Ruby (GitHub).
35 methods mapped in our drive, none of them called
llms.txt
YesAgent payments
None foundThe checkout wasn't reached.
Docs
In partCovers getting started, auth, error codes and code examples.
Describes each operation only in part: completeness 74 of 100.
5 of 10 documented ways to do the core work were tried, and 5 of them worked.
412 of 1,810 pages read
Get in
Getting in
Our agent tried 2 of 3 ways in; 1 worked without a person.
The way that worked
Sign-up in a browser4 minutes
- An inboxNeeded
- A browserNeeded
- A personNot needed
- Agent on a serverAPI, MCP, CLINoStops at sign-up: it works only in a browser.
- Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does 6 of its 10 core tasks, then stops: the rest needs a paid plan. It can't delete its account.
- Signed agentKnown to CloudflareYesThe site opens.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Sign-up in a browser | Worked | |
| Sign-in for apps (OAuth) | Stopped | The consent page needs an account |
| Added by an admin | Not tried | Needs a person's account |
- CrawlersThe robots.txt on identity-sandbox.checkout.com asks crawlers to stay off sign-up. Nothing to fix.
Use
What an agent can do with Checkout.com
6 of 10 core tasks done, and 10 of 28 others.
Core tasks
- done there
- tried, not done
- offered, not tried
| Task | Result | Through |
|---|---|---|
| Accept an online card payment | Done | API: done thereMCP: offered, not tried |
| Embed the Flow checkout in a website | Done | API: done there |
| Capture an authorized payment | Done | API: done there |
| Refund a payment | Done | API: done there |
| Screen payments with fraud risk rules | Done | Web app: done there |
| Respond to a dispute with evidence | Done | API: done there |
| Pay out to a bank account or card | Paid plan | API: tried, not done |
| Issue a virtual or physical card | Paid plan | API: tried, not done |
| Create a Hosted Payments Page sessionA new account gets an empty 401 until the feature is enabled. | Blocked | API: tried, not done |
| Create a payment link | Blocked | API: tried, not done |
Surface audit: 287 documented operations: 82 run, 197 blocked by sandbox or plan limits and 8 left out because they spend money or reach real people. Of the 82 run, 72 passed and 10 didn't; 12 behaved differently from the docs. By surface, 76 on the API and 6 elsewhere, such as sign-in and webhooks.
Holds up
80of 100
- Reliability94
- Handles mistakes67
The mean of the two, 80.5, with a half rounded to the even number.
Docs match
82of 100
- Docs accuracy85
- Docs completeness74
Docs accuracy counts 70%, completeness 30%.
Surface tested
26of 100
72 of 279 passed: the 287 documented operations less the 8 that spend money or reach real people
What it can't do, and why
- Create a hosted payment page or payment link A new account gets an empty 401 until the feature is enabled.
- Pay out, issue cards, onboard sub-accounts or use FX These add-ons are not switched on for a self-serve account.
- Create or revoke API keys without a browser Keys can only be made and deleted in the dashboard.
- Use the MCP server It refused our client with 'client_id not permitted'.
- Buy a plan Pricing is set per merchant through sales.
- Delete the account No close option was found in the dashboard, API or docs.
10 of 28 other tasks done
- Void an authorized paymentDone
- Search and list paymentsDone
- Create a customerDone
- Look up a customerDone
- Save a customer's payment instrumentDone
- Set up a webhook through a notification workflowDone
- Read entity balancesDone
- Run a standalone 3D Secure authenticationDone
- Test payments with sandbox test cardsDone
- Get available payment methodsDone
- Download a payment or financial reportPartly
- Transfer funds between sub-accountsBlocked
- Onboard a sub-entityBlocked
- Verify a customer's identityBlocked
- Screen a person against AML databasesBlocked
- Provision a network tokenBlocked
- Get updated card credentialsBlocked
- Set spending controls on an issued cardBlocked
- Simulate a card authorization in the sandboxBlocked
- Get FX ratesBlocked
- Create a delegated payment token for agentic commerceBlocked
- Send a test webhook eventNot tried
- Invite a Dashboard userNot tried
- Set a Dashboard user's permissionsNot tried
- Configure single sign-on for the DashboardNot tried
- Turn on multi-factor authenticationNot tried
- Brand the hosted payment page and payment linksA new account gets an empty 401 until the feature is enabled.Not tried
- Read user activity in the DashboardNot tried
Needs a paid plan
- Read entity balancespaid
- Get FX ratespaid
- Set spending controls on an issued cardpaid
- Simulate a card authorization in the sandboxpaid
- Transfer funds between sub-accountspaid
- Onboard a sub-entitypaid
- Verify a customer's identitypaid
- Screen a person against AML databasespaid
- Provision a network tokenpaid
- Get updated card credentialspaid
- Create a delegated payment token for agentic commercepaid
The drive used the free plan.
Tips for agent builders
- Find your account's base URL under Developers > Overview ({prefix}.api.sandbox.checkout.com). The generic api.sandbox.checkout.com host answers 403 base_url_invalid.
- Some operations live on other hosts given in the OpenAPI servers per path, for example balances.sandbox.checkout.com for GET /balances/{entity}.
- When creating a secret key, choose Customise > Select all scopes. 3DS sessions need an OAuth token from an access key pair: POST {prefix}.access.sandbox.checkout.com/connect/token.
- A 202 on a refund does not mean it was approved. Read GET /payments/{id}/actions: a fresh account's first refund can come back declined with 50003 'Balance reservation insufficient funds'.
- Send Cko-Idempotency-Key on every create. Without it, identical POST /payments calls make duplicate payments.
- Disputes appear about 3 minutes after a payment that uses a dispute scenario amount with expiry 01/2099 (Disputes testing page).
- The 3DS simulator password is shown on its own page as a hint (Checkout1!).
Pay
Paying
Ways to pay checked 3 Nov 2026.
- ResultStopped. Needs a person to buy. These add-ons are not switched on for a self-serve account.
Leave
Leaving
- ResultPartly. Nothing to cancel. Its account stays.
- Its accountNot on its own: blocked. The sandbox account stays and the login still works. Every key was revoked and refused afterwards; the customers, instruments, workflows, secrets and risk rules were deleted. Dashboard Settings shows no close or delete option, the OpenAPI has no operation for it and no docs page on closing an account was found.
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
Loads on the newest check; 14 of 14 days
llms.txt,
Found on the newest check; 14 of 14 days
MCP server,
Asks for a sign-in on the newest check; 14 of 14 days
OpenAPI,
Found on the newest check; 14 of 14 days
Compare
How Checkout.com compares
In Payments
None of the 10 products we drove in Payments is higher; 4 others share L3. As of 6 Nov 2026.
| Product | Level | Find to leave |
|---|---|---|
| GoCardless | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| Stripe | L3 | Find: On its own, Get in: On its own, Use: Partly, Pay: Not tried, Leave: On its own. |
| Lemon Squeezy | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| Mollie | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| PayPal | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| Polar | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| Nevermined | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| Checkout.com (this page) | L3 | Find: On its own, Get in: On its own, Use: Partly, Pay: Stopped, Leave: Partly. |
| Crossmint | L3 | Find: On its own, Get in: On its own, Use: Partly, Pay: Partly, Leave: Partly. |
| Square | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
For the team behind Checkout.com
Agents get stuck at Pay
9 things to fix for agents: 5 small and 4 medium
One fix can cover several findings.
Agent blockers: 6 foundAgent surfaces: 30 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at checkout.com.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UsePartly
- PayBlocks agents
- LeavePartly
Or claim Checkout.com to see where each issue is, read your safety findings with their fixes and ask for a free drive after a fix.
Want Checkout.com driven every month? See Watch
On our standard
Best or ahead on 5 of 27 criteria, behind on 7. Each against the products we measured on it.
- Pages fit one fetchAhead of 8 of 9 others (payments products), 1 the same.
- A way in with no personAhead of 5 of 9 others (payments products), 4 the same.
- Answers sized for an agentTied for the best result 3 of 6 others (payments products) the same, 3 lower.
- Docs an agent can navigateLevel with 5 of 9 others (payments products), 4 lower.
- One way to page through listsBehind 4 of 5 others (payments products), 1 the same.
- No person in the buy pathBehind 115 of 138 others (every product), 23 the same.
- A path written for agentsBehind 8 of 9 others (payments products), 1 the same.
- Fast to the first callThe lowest result All 8 others (payments products) higher.
All 27 criteria
- Spend an agent can see and capAhead of 4 of 7 others (payments products), 2 the same, 1 higher.
- Every way in works for an agentLevel with 6 of 9 others (payments products), 3 lower.
- The best way in is built for agentsAhead of 5 of 9 others (payments products), 2 the same, 2 higher.
- Export before leavingIn the middle 4 of 9 others (payments products) lower, 4 the same, 1 higher.
- Retried payments charge once, with a receiptIn the middle 2 of 5 others (payments products) lower, 2 the same, 1 higher.
- Errors a program can readLevel with 5 of 8 others (payments products), 2 lower, 1 higher.
- Errors say what to do nextLevel with 7 of 8 others (payments products), 1 lower.
- llms.txt that worksLevel with 6 of 9 others (payments products), 2 lower, 1 higher.
- A request id on every answerIn the middle 3 of 9 others (payments products) lower, 4 the same, 2 higher.
- Terms allow an agent's accountThe same as all 9 others (payments products).
- Versions an agent can pinThe same as all 5 others (payments products).
- Real status codesThe same as all 9 others (payments products).
- An agent payment rail on the coreThe same as all 9 others (payments products).
- A plan an agent can buy by APIThe same as all 7 others (payments products).
- Delete by API, checkedThe same as all 4 others (payments products).
- WebMCP tools on the web appThe same as all 9 others (payments products).
- Sign-in for agents acting for a personTied for the lowest result 4 of 8 others (payments products) the same, 4 higher.
- Limits known before they hitBehind 3 of 5 others (payments products), 2 the same.
- Prices an agent can readBehind 4 of 5 others (payments products), 1 the same.
Where Checkout.com fits
- Category
- Tasks
- Topics
- MCP serversFind step
- Docs and llms.txtFind step
- MCP sign-inGet in step
- Sign-upGet in step
- Card checkoutPay step
- Delete the accountLeave step
- Rivals
History
Level by drive
One drive so far, on 3 Nov 2026.
One drive so far.
Read more on this step
Pay is where our agent stopped at Checkout.com.
- Finding · 18 Nov 2026How far does an AI agent get in a card checkout?Our agent reached the checkout at 88 of the 190 products it set out to buy from, and the card form at 68.Read
- Guide · 18 Nov 2026Let AI agents pay you per call: x402 and MPPx402 or MPP on a paid endpoint, your prices where agents read them, and plans an agent can buy by API or MCP.Read
- Guide · 9 Nov 2026Agent experience (AX): what it is, measured at 246 productsAs of 9 Nov 2026: Agent experience (AX) is whether an AI agent can find, get into, use and pay for a product on its own. We drove 246 products to measure it.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
Found an error? Tell us on this page or read how corrections work.
Questions people ask about Checkout.com
- Can an AI agent create a Checkout.com account on its own?
- Yes, in a browser, without a person. Sandbox account through the web form at checkout.com/get-test-account in the browser (name, job title, company, email, country, processing volume; our agent answered). No CAPTCHA. There is no documented sign-up API.
- Does Checkout.com have an MCP server, and can an agent connect to it?
- Yes. Checkout.com has an official MCP server. The server is hosted, lists 9 tools and signs an agent in with OAuth. A new agent can get in on its own: in the drive of 3 Nov 2026, our agent signed up, verified and got its key without a person.
- How does an AI agent get a Checkout.com API key?
- In the drive of 3 Nov 2026, our agent got its Checkout.com API key in a browser, without a person. Keys are created only in the Dashboard (Developers > Keys), which the agent did itself in its own browser: a secret key with chosen scopes, a public key and an access key pair. No API or CLI creates keys. All keys were deleted in the Dashboard at the end and were refused afterwards.
- Can an AI agent delete its Checkout.com account?
- Not on its own: blocked. The sandbox account stays and the login still works. Every key was revoked and refused afterwards; the customers, instruments, workflows, secrets and risk rules were deleted. Dashboard Settings shows no close or delete option, the OpenAPI has no operation for it and no docs page on closing an account was found.
- Can an AI agent pay for Checkout.com?
- No. A person has to buy: a sales call.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “Checkout.com: AI agent test drive”, 3 November 2026, https://agentdrives.com/tools/checkout. CC BY 4.0.
AgentDrives. (2026, November 3). Checkout.com: AI agent test drive. https://agentdrives.com/tools/checkout
@misc{agentdrives_checkout_2026,
author = {{AgentDrives}},
title = {Checkout.com: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/checkout},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
We check it against the drive and correct the page, with the date.