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.

checkout.comPayments

Driven 3 Nov 2026

Evidence sha256 6b5e5b48JSONMarkdownFeedCite

L3

Does the work

  1. L0
  2. L1
  3. L2
  4. L3
  5. L4
  6. L5

Rank among the 246 products we drove

Holds up
tied #45
80/ 100
Reliability under errors
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

  1. Find

    On its own · 412 doc pages read

    Docs it can act on: llms.txt, an OpenAPI and an MCP server.

  2. Get in

    On its own · 4 minutes

    Sign-up in a browser.

  3. Use

    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.

  4. PayFirst stop

    Stopped

    Needs a person to buy. These add-ons are not switched on for a self-serve account.

  5. Leave

    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.

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 tested

    Official server. Remote MCP (beta), 9 tools when driven documented, OAuth with allowlisted clients. Sign‑in needed to see its tools.

    mcp.checkout.com/mcp

    9 tools mapped in our drive, none of them called

  • API

    76 of 236 tested

    REST, 236 operations, OpenAPI 3.0.1, per-account base URL.

    236 operations mapped in our drive

  • OpenAPI

    Yes

    A machine-readable description of the API.

  • CLI

    None found
  • SDK

    Listed, not tested

    Back-end SDKs: Go, Java, .NET, Node.js, PHP, Python, Ruby (GitHub).

    35 methods mapped in our drive, none of them called

  • llms.txt

    Yes
  • Agent payments

    None found

    The checkout wasn't reached.

  • Docs

    In part

    Covers 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.

    api-reference.checkout.com

    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

Every way in and what happened
Way inWhat happenedWhy
Sign-up in a browserWorked
Sign-in for apps (OAuth)StoppedThe consent page needs an account
Added by an adminNot triedNeeds 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
Core tasks of Checkout.com: the result and the surfaces they went through
TaskResultThrough
Accept an online card paymentDoneAPI: done thereMCP: offered, not tried
Embed the Flow checkout in a websiteDoneAPI: done there
Capture an authorized paymentDoneAPI: done there
Refund a paymentDoneAPI: done there
Screen payments with fraud risk rulesDoneWeb app: done there
Respond to a dispute with evidenceDoneAPI: done there
Pay out to a bank account or cardPaid planAPI: tried, not done
Issue a virtual or physical cardPaid planAPI: tried, not done
Create a Hosted Payments Page sessionA new account gets an empty 401 until the feature is enabled.BlockedAPI: tried, not done
Create a payment linkBlockedAPI: 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

From this drive

7 tips
  • 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.

The products we drove in Payments, in the directory's order, with Checkout.com
ProductLevelFind to leave
GoCardlessL3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.
StripeL3Find: On its own, Get in: On its own, Use: Partly, Pay: Not tried, Leave: On its own.
Lemon SqueezyL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
MollieL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
PayPalL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
PolarL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
NeverminedL3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.
Checkout.com (this page)L3Find: On its own, Get in: On its own, Use: Partly, Pay: Stopped, Leave: Partly.
CrossmintL3Find: On its own, Get in: On its own, Use: Partly, Pay: Partly, Leave: Partly.
SquareL1Find: 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.

  1. FindClear
  2. Get inClear
  3. UsePartly
  4. PayBlocks agents
  5. 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.

All 27 criteria
How each criterion is graded

Where Checkout.com fits

History

Level by drive

One drive so far, on 3 Nov 2026.

Source: our drives of Checkout.com. As of 3 Nov 2026.

One drive so far.

Read more on this step

Pay is where our agent stopped at Checkout.com.

Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.

Found an error? 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
Plain
AgentDrives, “Checkout.com: AI agent test drive”, 3 November 2026, https://agentdrives.com/tools/checkout. CC BY 4.0.
APA
AgentDrives. (2026, November 3). Checkout.com: AI agent test drive. https://agentdrives.com/tools/checkout
BibTeX
@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.