{
 "categories": [
  "payments",
  "developer-tools"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-27",
   "fact": "homepage",
   "note": "Checkout.com presents a payments network for pay-ins, payouts, acquiring, and fraud tools.",
   "source": "https://www.checkout.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "license",
   "note": "The commercial site offers a test account and sales contact. No permanent free processing plan was stated on the homepage.",
   "source": "https://www.checkout.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.api.exists",
   "note": "Checkout.com documents API calls authenticated with public and secret API keys, including a payments request.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.api.kinds[0]",
   "note": "The example is an HTTPS POST of JSON to https://{prefix}.api.sandbox.checkout.com/payments/.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.api.auth[0]",
   "note": "Send the API key in the Authorization header with the Bearer prefix. Secret keys are for server-to-server calls and can access most APIs. Public keys are limited to client-side calls such as tokenization.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.api.coverage",
   "note": "Secret keys can be scoped to one API or to the APIs the merchant selects, including a payments example. This page does not inventory payouts, disputes, or issuing.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.mcp.first_party",
   "note": "Checkout.com documents a Beta MCP server at https://mcp.checkout.com and https://checkout.mcp.sbox.cko.tech, with Dashboard sign-in.",
   "source": "https://www.checkout.com/docs/developer-resources/checkout-com-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.data_access.export[0]",
   "note": "The documented payments request uses a JSON body. The MCP setup guide says the server can query payment status from the account.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.data_access.import[0]",
   "note": "The payments example POSTs a JSON body with source, amount, currency, and reference.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.rpa.ui_stack[0]",
   "note": "Checkout.com is operated from a web Dashboard. The MCP guide requires a Dashboard account to sign in.",
   "source": "https://www.checkout.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened a plain-text index of the Checkout.com documentation.",
   "source": "https://www.checkout.com/docs/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "verdict.scores.api",
   "note": "Bearer secret keys access most APIs, can be scoped per API, and the page shows a live payments POST.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "verdict.scores.mcp",
   "note": "The setup guide, last updated 23 September 2026, labels the server Beta and describes docs search, payment status, voids, and payment links under the signed-in user's permissions.",
   "source": "https://www.checkout.com/docs/developer-resources/checkout-com-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "freshness.watch[0].url",
   "note": "Opened the Checkout.com MCP setup guide, including both environment URLs and the Beta label.",
   "source": "https://www.checkout.com/docs/developer-resources/checkout-com-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "freshness.watch[1].url",
   "note": "Opened the API keys guide, including Bearer authentication and the payments example.",
   "source": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-27",
   "fact": "freshness.watch[2].url",
   "note": "Opened the Checkout.com MCP README, which documents https://mcp.checkout.com and names refund among the payment actions.",
   "source": "https://github.com/checkout/checkout-mcp",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-27",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://www.checkout.com/docs/developer-resources/checkout-com-mcp-server"
   },
   {
    "type": "docs",
    "url": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys"
   },
   {
    "type": "docs",
    "url": "https://github.com/checkout/checkout-mcp"
   }
  ]
 },
 "homepage": "https://www.checkout.com/",
 "id": "checkout-com",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "bearer"
   ],
   "coverage": "partial",
   "docs": "https://www.checkout.com/docs/developer-resources/api/manage-api-keys/api-keys",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": [
    "json"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Checkout.com's REST API and hosted MCP server cover payment calls and docs lookup without browser control of the Dashboard, apart from the MCP sign-in.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Checkout.com",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "stripe",
   "adyen",
   "mollie",
   "paypal"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Checkout.com",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 6,
   "overall": 7,
   "rpa": null
  },
  "summary": "Checkout.com is automatable today through its payments REST API. This record is the Checkout.com payments platform. Stripe, Adyen, Mollie, and PayPal are separate products. Secret API keys are for server-to-server calls and can access most Checkout.com APIs. Public API keys are for a limited client-side set, including tokenization. Both are sent as Authorization: Bearer. The keys page shows a sandbox payments POST to https://{prefix}.api.sandbox.checkout.com/payments/. Keys are created in the Dashboard by an Admin, a Developer, or a custom role with key permissions. Checkout.com also hosts an MCP server, marked Beta in the setup guide last updated 23 September 2026. Production is https://mcp.checkout.com and sandbox is https://checkout.mcp.sbox.cko.tech. Sign-in is Dashboard OAuth. The agent inherits that user's permissions. The setup guide describes documentation search, payment-status queries, voids, and payment links. The Checkout.com repository README also names refunds. Connector catalogs and the event-notification reference were not opened for this record. https://www.checkout.com/docs/llms.txt is a documentation index. Computer-use viability is unassessed. The API scores 7 and is the best path. MCP scores 6 because the official server is useful and still labeled Beta, with a narrower action set than the payments API.\n"
 }
}