Adyen vs Checkout.com

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Adyen
   Adyen✓fullprobed10/10

   Adyen has a live, probed llms.txt (HTTP 200) plus markdown-renderable docs pages (append .md), a documented full-docs ZIP mirror explicitly for feeding AI agents/code assistants, and an OpenAPI spec repo positioned as LLM context — this is direct, independently-probed confirmation of agent-oriented docs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.adyen.com/online-payments.md --- title: "Online payments" description: "Accept payments with cards, …”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”
   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”

   proof ↗⚑ flag

   Checkout.com✓fullprobed8/10

   Checkout.com hosts a live llms.txt at both www.checkout.com/llms.txt and docs.checkout.com/llms.txt, confirmed via probe returning HTTP 200 with structured content, plus multiple docs entries derived from that file listing agent-readable summaries of products/APIs. This directly satisfies pointing an agent at llms.txt. missing for 10: independent third-party confirmation of an agent successfully consuming the file end-to-end, and a docs.md/markdown mirror (docs.md returned 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.checkout.com/llms.txt # Checkout.com: High-performance global payments platform for enterprise and s…”
   • [claimed-docs] “Unified Payments API: Connect to all payment methods through a single API integration.”
   • [claimed-docs] “Request a payment using a token, a network token, a payment instrument, or the full card details.”
   • [claimed-docs] “Use your Checkout Business Account to efficiently manage your funds across our product suite.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.checkout.com/docs.md”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Checkout.com
   Adyen~partialclaimed6/10

   Adyen's core integration is a server-to-server REST API (docs-1, docs-2) that can be called entirely headlessly with no UI dependency, supports idempotency keys for safe automated retries (adyen-docs-4, adyen-docs-25), and provides a dedicated test environment with test credentials explicitly meant for pre-production integration testing (adyen-docs-6, adyen-docs-18). Scoped, multiple API credentials support automated/service-account style access (adyen-docs-26, adyen-supp-api-credential-scoping). However, there is no explicit CI/CD pipeline documentation, no CLI/SDK testing harness, and the MCP server is documented as running locally via npx rather than as a CI-oriented headless service. Missing for 10: explicit CI/CD integration guides, automated test-suite/SDK tooling, and confirmation of non-interactive credential provisioning for pipelines.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Your server makes three Checkout API requests: /paymentMethods, /payments, and /payments/details.”
   • [claimed-docs] “To submit a request for idempotent processing, send a request with the `idempotency-key:` in the header.”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”
   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials.”
   • [claimed-docs] “You can also create multiple API credentials to improve security and control access.”
   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”

   proof ↗⚑ flag

   Checkout.com~partialclaimed7/10

   Checkout.com is API-first with SDKs (e.g. Node.js), OAuth2 client-credentials auth, idempotent retries, webhooks, and a full sandbox/test-account environment with test cards — all of which support scripted, headless use in CI/test pipelines. However there is no dedicated CLI or explicit CI/CD pipeline documentation/tutorials for automation. Missing for 10: dedicated CLI tool, explicit CI/CD integration guide or example pipeline.

   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”
   • [claimed-docs] “Two documented server-side authentication forms — "Access keys (OAuth 2.0)" (client-credentials flow) and "Secret keys" — plus public keys f…”
   • [claimed-docs] “A dedicated test-account environment with per-scenario testing docs: payments testing, test cards, disputes testing, fraud-detection testing…”
   • [github] “The official Node.js SDK for Checkout.com payment gateway.”
   • [claimed-docs] “Test cards”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Checkout.com
   Adyen✓fullprobed8/10

   Adyen documents and ships an official MCP server (github.com/Adyen/adyen-mcp) that lets LLM clients call Checkout, payment links, modifications, and Management API tools via natural language, with clear setup (npx install), scoped API-key auth, and role-based permissions. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice (only vendor docs and a live-probe confirming the doc page exists, no community usage reports) and clarity on production-readiness given its 'Alpha' status.

   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “MCP access rides on Adyen's standard scoped credentials: "To authenticate the requests you will make using the MCP, generate an API key. Mak…”

   proof ↗⚑ flag

   Checkout.com✓fullprobed9/10

   Checkout.com documents an official, hosted MCP server (sandbox and production endpoints, OAuth via Dashboard account) with concrete setup instructions (e.g., adding it to Claude Code) and documented capabilities like querying payments, issuing refunds, managing payment links, and knowledge-base search — directly fulfilling the story. Missing for 10: independent/third-party corroboration of real-world usage beyond vendor docs, and it's explicitly marked Beta.

   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”
   • [claimed-docs] “The Checkout.com Model Context Protocol (MCP) Server enables you to search through our knowledge base and manage payment operations directly…”
   • [probe] “official MCP server documented at https://www.checkout.com/docs/developer-resources/checkout-com-mcp-server”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Adyen—none0/10

   Evidence covers an MCP server, OpenAPI specs, docs tooling, and agentic-commerce protocols, but there is no mention of an official Adyen CLI for AI-native workflows anywhere in the pack.

   ⚑ flag

   Checkout.com—none0/10

   Evidence shows SDKs (Node.js), a Dashboard, an MCP server, and agentic-commerce protocol integrations, but no mention of an official CLI tool for developers. Payment platforms commonly ship CLIs (e.g., for testing webhooks, managing keys), so the axis applies, but no such capability is documented anywhere in this evidence pack.

   • [github] “The official Node.js SDK for Checkout.com payment gateway.”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.checkout.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.checkout.com/openapi.json, https://www.checkout.com/swagger.json, https://www.checkout.c…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Adyen✓fullprobed9/10

   Adyen ships extensive documented public REST APIs (Checkout, Management, Platforms, Payouts, Agentic Commerce, etc.), an OpenAPI spec repo as 'single source of truth' for client generation, idempotency keys, scoped API credentials, webhooks, and machine-readable docs (llms.txt, .md pages, full docs mirror) explicitly aimed at AI tooling. Probes independently confirm llms.txt and .md doc endpoints return 200. Missing for 10: a live discoverable OpenAPI/swagger endpoint directly under docs.adyen.com (probe found 404s on standard paths) and independent third-party corroboration of API usability beyond vendor docs.

   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”
   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.adyen.com/online-payments.md --- title: "Online payments" description: "Accept payments with cards, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

   proof ↗⚑ flag

   Checkout.com✓fullprobed9/10

   Checkout.com documents a comprehensive public REST/Unified Payments API with OAuth2/API-key auth, idempotency, rate limits, webhooks, SDKs (Node.js), and a full testing sandbox, plus explicit agentic-commerce integrations (ChatGPT, Google AI) and an official MCP server for AI-agent operation — strongly supporting AI-native programmatic control. Missing for 10: a discoverable OpenAPI/swagger spec (probe found 404s) and independent third-party corroboration beyond vendor docs.

   • [claimed-docs] “Unified Payments API: Connect to all payment methods through a single API integration.”
   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”
   • [claimed-docs] “Two documented server-side authentication forms — "Access keys (OAuth 2.0)" (client-credentials flow) and "Secret keys" — plus public keys f…”
   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “A dedicated test-account environment with per-scenario testing docs: payments testing, test cards, disputes testing, fraud-detection testing…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”
   • [claimed-docs] “"With agentic commerce, your customers can discover and pay for products through an AI chat interface, instead of visiting your website. The…”
   • [github] “The official Node.js SDK for Checkout.com payment gateway.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.checkout.com/openapi.json, https://www.checkout.com/swagger.json, https://www.checkout.c…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Adyen
   Adyen✓fullclaimed8/10

   Adyen documents scoped, role-based API credentials (roles define exactly what a credential can do, e.g. limiting to initiating vs capturing payments, per-merchant-account scoping) and explicitly recommends creating multiple credentials for finer-grained access control — and the MCP server docs instruct assigning a dedicated API credential with only the specific roles needed for agent use, plus a --tools flag to limit which MCP tools are exposed. This directly supports least-privilege credential issuance for an AI agent. missing for 10: no independent/hands-on verification of least-privilege enforcement in practice, and no explicit per-agent short-lived/ephemeral credential mechanism beyond static role-scoped API keys.

   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”
   • [claimed-docs] “MCP access rides on Adyen's standard scoped credentials: "To authenticate the requests you will make using the MCP, generate an API key. Mak…”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “You can also create multiple API credentials to improve security and control access.”

   proof ↗⚑ flag

   Checkout.com~partialclaimed5/10

   Checkout.com documents OAuth 2.0 client-credentials flow and 'access keys' alongside secret keys, letting integrations obtain scoped, non-static credentials per processing channel — a real least-privilege mechanism. However, the MCP server (the actual agent-facing surface) authenticates via a full Dashboard account login rather than a dedicated scoped/agent-specific credential, so there's no documented way to mint a narrowly-scoped key specifically for an autonomous agent. Missing for 10: explicit agent-scoped OAuth scopes/roles for the MCP server, granular permission docs tied to agent use cases, and independent confirmation that access-key scopes can be limited to agent-safe operations only.

   • [claimed-docs] “Two documented server-side authentication forms — "Access keys (OAuth 2.0)" (client-credentials flow) and "Secret keys" — plus public keys f…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Adyen~partialprobed6/10

   Adyen documents official SDKs for web/iOS/Android/React Native/Flutter and a public OpenAPI spec repo as the 'single source of truth' usable to generate client libraries, which supports SDK-based building; however, the OpenAPI/spec endpoint probes returned 404s and there's no independent/hands-on corroboration of SDK quality or completeness for AI-native workflows specifically. missing for 10: independent verification of official SDK repos/quality, working OpenAPI spec endpoint (probe returned 404s), hands-on developer confirmation of SDK-based agentic integration.

   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

   proof ↗⚑ flag

   Checkout.com~partialprobed6/10

   Checkout.com documents an official Node.js SDK on GitHub, a native Mobile SDK for iOS/Android, plugins for ecommerce platforms, and machine-readable docs (llms.txt) plus an MCP server that let AI agents build against its API. However, evidence only names one language SDK explicitly and no broader SDK catalog (e.g., Python, PHP, Java, .NET) or independent hands-on validation is shown. Missing for 10: multi-language official SDK coverage, independent/community corroboration of SDK quality, and a public OpenAPI spec (probes show openapi.json 404).

   • [github] “The official Node.js SDK for Checkout.com payment gateway.”
   • [claimed-docs] “Mobile SDK: Build native mobile checkout experiences for iOS and Android.”
   • [claimed-docs] “Plugins: Integrate Checkout.com into existing ecommerce platforms via pre-built plugins.”
   • [claimed-docs] “Unified Payments API: Connect to all payment methods through a single API integration.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.checkout.com/llms.txt # Checkout.com: High-performance global payments platform for enterprise and s…”
   • [claimed-docs] “The Checkout.com Model Context Protocol (MCP) Server enables you to search through our knowledge base and manage payment operations directly…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Checkout.com
   Adyen✓fullclaimed8/10

   Adyen provides first-party webhook subscriptions to avoid polling, with event logs visible in the Customer Area, and MCP tools to list/get/test webhooks, plus agentic-commerce flows that explicitly send webhook payment outcomes to merchant servers — showing webhooks are usable both directly and via AI-native/agent tooling. missing for 10: no independent/hands-on developer confirmation of webhook subscription setup via API or MCP, and no detail on webhook event types/payload schema management through natural-language/agentic tooling.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Google Agentic Commerce integration: "Use this integration for processing Google Pay payments through Adyen, when Google agents (Google AI M…”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed9/10

   Checkout.com has robust, well-documented webhooks: event notifications with HMAC signature verification, configuration via Dashboard or API, resending webhooks, and integration with Amazon EventBridge for event streaming — directly enabling programmatic/agentic subscription to payment lifecycle events. Missing for 10: independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “Receive webhooks”
   • [claimed-docs] “Resend webhooks”
   • [claimed-docs] “Manage webhooks in the Dashboard”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Adyen
   Adyen~partialclaimed6/10

   Adyen Uplift is documented as an AI layer that analyzes payment data and 'gives you recommendations that are tailored for your business' to optimize conversion, risk, and cost, and risk management includes ML-powered fraud detection using global transaction data. This matches the spirit of AI-generated insights/suggestions from account data, but it's narrowly scoped to payment-funnel optimization and fraud, not a general-purpose 'insights' feature across reporting/dashboards, and there's no independent/hands-on corroboration of how these suggestions surface in the UI. Missing for 10: broader AI-generated insights across reporting/analytics (not just Uplift/fraud), and third-party or hands-on evidence of the insights UX.

   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”
   • [claimed-docs] “Adyen Uplift helps you strike a balance between conversion, risk and cost. You get recommendations that are tailored for your business”
   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”

   proof ↗⚑ flag

   Checkout.com~partialclaimed3/10

   Checkout.com references a general 'AI-driven solution' to optimize payment acceptance rates and mentions 'advanced analytics' on transaction-level data, which gestures at AI working on the merchant's own data, but there is no documented dashboard AI-insights/copilot feature that surfaces suggestions or narrative insights to the user. Missing for 10: a named in-product AI insights/analytics feature, evidence of generated recommendations shown to users, and any hands-on/independent corroboration beyond marketing copy.

   • [claimed-docs] “Automatically optimize payments to increase your acceptance rate with our powerful AI-driven solution.”
   • [claimed-docs] “Transaction-level data you can use to do more. Go beyond approvals and declines and experience our advanced analytics.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Adyen
   Adyen~partialclaimed5/10

   Adyen supports several background/event-driven automations — webhooks that eliminate manual polling for async status changes, Uplift's AI-driven payment-funnel optimization experiments that can be started/evaluated/stopped autonomously, and risk-management rules/ML fraud detection that run continuously — but these are fixed platform features rather than a general-purpose mechanism for an AI-native user to author custom autonomous background automations. Missing for 10: a user-configurable automation/workflow builder or scheduler that an AI-native user can set up to run arbitrary agentic tasks unattended, and independent evidence of such automations running reliably in production.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”
   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed4/10

   Checkout.com offers building blocks that support background automation — webhooks trigger server-side actions on payment lifecycle events, and the MCP server lets an AI agent query statuses, issue refunds, and manage payment links — plus agentic commerce protocols (ChatGPT, Google AI) letting an AI complete transactions on a user's behalf. However, none of this constitutes a dedicated 'set up an automation that runs autonomously in the background' capability (e.g., scheduled jobs, persistent agent workflows); the MCP server is described as an IDE-session tool, not an unattended background process. Missing for 10: a documented scheduler/background-job or persistent autonomous-agent workflow feature, and independent evidence of such automations running unattended.

   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “"With agentic commerce, your customers can discover and pay for products through an AI chat interface, instead of visiting your website. The…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Adyen—none0/10

   Adyen documents an MCP server (for external LLM clients to call Adyen's APIs) and 'Uplift' (automated AI-driven payment optimization), but no evidence of a built-in AI assistant/copilot inside the Adyen product itself that a user can converse with or delegate tasks to interactively.

   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”

   proof ↗⚑ flag

   Checkout.com—none0/10

   Checkout.com offers an MCP server so external AI agents/IDEs can query its API, and supports agentic-commerce protocols so third-party AI agents (ChatGPT, Google AI) can transact with merchants — but there is no evidence of a built-in AI assistant embedded inside the Checkout.com product/dashboard itself that a user can delegate tasks to. The MCP 'Guide tool' and AI-driven acceptance optimization are external-agent or backend features, not an in-product assistant.

   • [claimed-docs] “The Checkout.com Model Context Protocol (MCP) Server enables you to search through our knowledge base and manage payment operations directly…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “"With agentic commerce, your customers can discover and pay for products through an AI chat interface, instead of visiting your website. The…”
   • [claimed-docs] “Automatically optimize payments to increase your acceptance rate with our powerful AI-driven solution.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Checkout.com
   Adyen~partialprobed7/10

   Adyen ships an official MCP server (adyen-mcp) that explicitly lets users 'use natural language with your chosen LLM client' to interact with Adyen APIs (create sessions, payment links, refunds, management API), with documented scoped-credential setup — a genuine natural-language operation surface for AI-native users. However, the MCP server is explicitly marked 'Alpha', runs only locally via npx, and only exposes a documented subset of tools rather than full product coverage. Missing for 10: production-grade/GA status, independent hands-on validation of the NL interface actually working reliably, and broader coverage beyond the documented tool subset.

   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “MCP access rides on Adyen's standard scoped credentials: "To authenticate the requests you will make using the MCP, generate an API key. Mak…”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server”

   proof ↗⚑ flag

   Checkout.com✓fullprobed8/10

   Checkout.com ships an official MCP Server that lets users query payment statuses, issue refunds, void payments, and manage payment links via natural-language requests to an AI agent, plus guided onboarding through a 'Guide tool' — directly matching the story. This is corroborated by concrete endpoint/setup details (OAuth, sandbox/production URLs, `claude mcp add` command) rather than just marketing copy. Missing for 10: independent/hands-on user reports of the NL commands working (server is labeled Beta) and no evidence beyond vendor docs of reliability at scale.

   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”
   • [claimed-docs] “The Checkout.com Model Context Protocol (MCP) Server enables you to search through our knowledge base and manage payment operations directly…”
   • [probe] “official MCP server documented at https://www.checkout.com/docs/developer-resources/checkout-com-mcp-server”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Adyen—none0/10

   The evidence describes OpenAPI specs (usable to generate Postman collections or client libraries), markdown-rendered docs, and an MCP server for natural-language API access, but there is no evidence of an actual interactive API reference/console embedded in Adyen's docs where a user can run live example requests. A probe for a standard OpenAPI/Swagger endpoint also returned 404s, and no 'try it' console or embedded runnable code examples are documented.

   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”

   proof ↗⚑ flag

   Checkout.com—none0/10

   The evidence pack shows extensive documentation pages, an llms.txt feed, and an MCP server for AI agents, but no evidence of an interactive API reference with runnable/live code examples (e.g., a 'try it' console or embedded sandbox). The OpenAPI probe explicitly found all candidate spec paths returning 404, suggesting no machine-readable spec is exposed for such tooling.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.checkout.com/openapi.json, https://www.checkout.com/swagger.json, https://www.checkout.c…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.checkout.com/docs.md”
   • [claimed-docs] “Request a payment using a token, a network token, a payment instrument, or the full card details.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Adyen
   Adyen✓fullprobed8/10

   Adyen documents a dedicated OpenAPI specification repository (github.com/Adyen/adyen-openapi) covering 'every public API Adyen offers' as the 'single source of truth,' explicitly positioned for machine consumption (client-library generation, Postman collections, and LLM/agent context). This is reinforced by llms.txt, markdown-renderable docs, and a full docs mirror ZIP for AI tooling. missing for 10: independent/hands-on confirmation that the OpenAPI repo is current and complete, and a direct in-docs discoverable openapi.json endpoint (probe found only 404s for openapi.json-style paths on the docs domain itself).

   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

   proof ↗⚑ flag

   Checkout.com—none0/10

   The evidence pack shows an llms.txt (LLM-friendly documentation index) but explicit probes for OpenAPI/Swagger specs at common paths (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no other citation references a downloadable OpenAPI or equivalent machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.checkout.com/openapi.json, https://www.checkout.com/swagger.json, https://www.checkout.c…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.checkout.com/llms.txt # Checkout.com: High-performance global payments platform for enterprise and s…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.checkout.com/docs.md”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Adyen✓fullclaimed8/10

   Adyen documents a dedicated test environment for the full integration (client- and server-side) using test credentials before going live, and this test environment is explicitly wired into AI-native workflows via the Adyen MCP server which runs with `--env=TEST` (or LIVE with a live prefix), letting an AI agent exercise Checkout, payment links, and modification tools against sandbox data. Missing for 10: no independent/hands-on confirmation that sandbox test data is fully isolated from production, and no detail on seeding/resetting sandbox state for repeatable AI-driven test runs.

   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com documents a dedicated sandbox/test-account environment (test cards, disputes testing, fraud/payouts testing, and a public 'get test account' signup) separate from production, and the MCP server itself is explicitly split into a sandbox endpoint (checkout.mcp.sbox.cko.tech) versus production (mcp.checkout.com), letting AI-native integrations test agentic operations without touching live data. Missing for 10: independent/hands-on confirmation that the sandbox fully mirrors production behavior and more detail on data isolation guarantees.

   • [claimed-docs] “A dedicated test-account environment with per-scenario testing docs: payments testing, test cards, disputes testing, fraud-detection testing…”
   • [claimed-docs] “Test cards”
   • [claimed-docs] “Disputes testing”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Adyen—none0/10

   The evidence pack covers API idempotency, webhooks, credentials, OpenAPI specs, and agentic commerce integrations, but contains no documentation of API versioning scheme or a deprecation policy for older API versions. Versioning/deprecation policy is a standard and fair axis for a payments API platform, so absence of evidence yields 'none'.

   ⚑ flag

   Checkout.com—none0/10

   The evidence pack covers idempotency, rate limits, auth, webhooks, and testing, but contains no mention of API version headers, a changelog, or a documented deprecation/sunset policy; probes for an OpenAPI spec even returned 404s, suggesting no discoverable versioning artifact.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Adyen
   Adyen~partialclaimed6/10

   Adyen documents concrete bulk operations in its agentic Product Feed API — batch ingest of up to 200 items per call and batch delete of up to 200 products per call — which is genuine 'many items at once' functionality for AI-platform inventory sync. However, evidence of bulk operations elsewhere in the platform (e.g., bulk payouts, bulk refunds/modifications, bulk reporting exports, or MCP tools operating on many resources at once) is absent; the MCP tool list is single-item oriented (create one session, one payment link, one refund). Missing for 10: bulk support evidenced across other core domains (payments, payouts, platforms/onboarding) and bulk-capable MCP tools, not just the product feed.

   • [claimed-docs] “You can upload batches of information about your inventory to Adyen, and we will synchronize it with AI platforms.”
   • [claimed-docs] “The Adyen Product Feed API is "a centralized product knowledge hub that synchronizes your inventory with AI platforms" via asynchronous batc…”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”

   proof ↗⚑ flag

   Checkout.com—none0/10

   The evidence pack covers single-resource operations (payments, refunds, payment links, webhooks) and idempotent retries for individual requests, but there is no documentation of a batch/bulk API, bulk refund/payout endpoints, or MCP tooling that operates across many items at once. Reconciliation and reporting are read-only aggregate views, not bulk write operations.

   ⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Adyen
   Adyen~partialclaimed5/10

   Adyen documents a genuine rules mechanism — the risk management rule builder lets you 'create, backtest, and label custom rules' that automatically trigger block/allow/review actions on each transaction event (adyen-docs-20, adyen-docs-28, adyen-docs-48), and webhooks notify on async status-change events (adyen-docs-3/17). This satisfies the core 'rule triggers action on event' pattern, but only within the fraud/risk-decisioning domain, not as a general-purpose automation/workflow engine, and there's no evidence of AI-native rule authoring (e.g., via the MCP server or natural language) for these rules. Missing for 10: general cross-domain event-action automation beyond fraud rules, AI/LLM-driven rule creation or triggering, and independent evidence of real-world use of the rule builder.

   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”
   • [claimed-docs] “Each payment goes through a risk evaluation. The risk evaluation reaches a decision that results in an action to block, allow, or review the…”
   • [claimed-docs] “You can detect, monitor, and mitigate fraud using Protect, Adyen's risk management system.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”

   proof ↗⚑ flag

   Checkout.com~partialclaimed4/10

   Checkout.com supports webhooks that notify external systems on payment lifecycle events, and documented 'risk rules and lists' that automatically trigger fraud-prevention actions based on transaction conditions — both are forms of event-triggered automation. However, there is no evidence of a general-purpose, user-defined rules/automation engine (e.g., 'if X event then Y action' workflow builder) spanning arbitrary events beyond fraud, so it only partially satisfies the story. Missing for 10: a native no-code/low-code rules engine for arbitrary event-triggered actions, documented conditional logic builder, and evidence of automation beyond fraud rules and webhook delivery.

   • [claimed-docs] “Create risk rules and lists”
   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “Receive webhooks”
   • [claimed-docs] “Retrieve fraud reports”

   proof ↗⚑ flag

Ai billing ops

1. ai-native userHave an agent monitor failed payments via API and webhooks and drive retries and dunning outreach

   weight 3 · round to Adyen
   Adyen~partialclaimed5/10

   Adyen provides the raw building blocks an agent could use—webhooks for status changes (adyen-docs-3/17/45), refusal-reason detail on failed payments (adyen-docs-7), idempotent retries (adyen-docs-4/25), and an MCP server exposing webhook list/get/test and payment tools (adyen-supp-mcp-tools)—but there is no documented dunning/subscription-retry feature, automated outreach mechanism, or agent workflow specifically for failed-payment recovery. Missing for 10: native dunning/retry orchestration, recurring-billing failed-payment workflow, and evidence of an agent actually driving retries/outreach rather than just monitoring raw webhook/API data.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed4/10

   Checkout.com provides the raw building blocks an agent could use — webhooks for payment lifecycle events (including failures), idempotent retry-safe API endpoints, and an MCP server that can query payment statuses and manage payment operations from an AI agent — but there is no documented dunning/retry-campaign feature or subscription-billing failed-payment workflow (no mention of automatic retry scheduling, dunning emails, or a 'monitor failed payments and drive outreach' capability). missing for 10: dedicated dunning/retry-campaign automation, evidence of subscription/recurring billing failure handling, and any documented agent workflow specifically for failed-payment monitoring/outreach.

   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”
   • [claimed-docs] “Receive webhooks”
   • [claimed-docs] “Resend webhooks”

   proof ↗⚑ flag

2. ai-native userHave an agent provision a new product, price, and payment link via the API in a single session

   weight 3 · round to Checkout.com
   Adyen—none0/10

   Adyen's API and MCP server cover payments, payment links, checkout sessions, and payouts, but there is no evidence of any 'product' or 'price' resource concept (billing/catalog objects like Stripe's Products/Prices) that an agent could provision alongside a payment link — Adyen is a payments processor, not a billing/invoicing product catalog system. The only 'product' references are to inventory feeds for agentic commerce (syncing existing catalog to AI platforms), not creating new products/prices via API. missing for 10: evidence of a Products/Prices API or equivalent billing object model, evidence of a single-session workflow that creates a product+price+payment link together, any documentation of provisioning billing entities (not just payment links) via API or MCP.

   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Offer payment links.”
   • [claimed-docs] “The Adyen Product Feed API is "a centralized product knowledge hub that synchronizes your inventory with AI platforms" via asynchronous batc…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed4/10

   Checkout.com documents API-driven Payment Link creation (docs-19/56) and an MCP server that can be used from an AI-assisted IDE to 'create and manage payment links' (cko-supp-mcp-server), so an agent could plausibly create a payment link in one session via API/MCP. However, there is no evidence of a discrete 'product' or 'price' catalog object/API (unlike a full product-catalog model) — Checkout.com's docs only reference amount/currency fields on payment links, not reusable Product/Price entities. missing for 10: a documented Products API and Prices API (or catalog object model) that an agent could provision alongside a payment link, and any hands-on/independent confirmation of an agent completing product+price+link creation end-to-end in one session.

   • [claimed-docs] “Create a Payment Link”
   • [claimed-docs] “Create a Payment Link - Docs”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”

   proof ↗⚑ flag

Subscriptions

1. finance-ops userAutomatically retry failed subscription payments with smart dunning and recovery emails

   weight 2 · round drawn
   Adyen—none0/10

   The evidence pack covers payments, payouts, webhooks, idempotency, risk management, platforms/marketplace payouts, and agentic commerce, but contains no mention of subscription billing, dunning management, automatic retry logic for failed recurring payments, or recovery emails. This is a plausible axis for a payments platform, but nothing in the docs or community evidence shows Adyen offering smart dunning/recovery workflows.

   ⚑ flag

   Checkout.com—none0/10

   The evidence pack shows Checkout.com as a payments/acquiring platform with API idempotency (for network retries, not subscription dunning), webhooks, refunds, and platforms/marketplace features, but there is no documented subscription billing product, dunning logic, automatic retry scheduling for failed recurring payments, or recovery email capability. This axis is plausible for a payments platform, but no evidence supports it being delivered.

   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”
   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “The Platforms solution enables marketplaces, payment facilitators (Payfacs), and other platform-based businesses to onboard sub-entities and…”

   proof ↗⚑ flag

2. developerSet up recurring subscription billing with plans, trials, upgrades, and proration

   weight 3 · round drawn
   Adyen—none0/10

   Adyen's evidence pack covers payments, payouts, platforms, risk, reporting, and agentic commerce, but there is no mention of subscription/recurring billing constructs like plans, trial periods, upgrades/downgrades, or proration—these are the domain of a billing/subscription-management layer (e.g. Adyen has separate tooling or partners for this) not documented here.

   ⚑ flag

   Checkout.com—none0/10

   Checkout.com is a payments/acquiring platform (payment processing, links, hosted pages, platforms/marketplaces, issuing) but the evidence pack contains no mention of subscription/recurring billing objects such as plans, trial periods, proration, or plan upgrades/downgrades — these are billing-engine concepts (like Stripe Billing/Chargebee) not documented here.

   ⚑ flag

Card acceptance

1. founderAccept an online card payment within a day of signing up

   weight 3 · round to Checkout.com
   Adyen!disputedcontradicted4/10

   Adyen's docs describe a fast technical integration (single /sessions call, test-then-go-live flow, no setup fees) that could suggest same-day acceptance, but independent community reports concretely contradict a founder's ability to just sign up and start accepting payments quickly: Adyen reportedly refuses small clients ('under the million'), requires large reserves for subscription businesses, and one user describes a multi-hundred-hour integration effort before abandoning it. These are hands-on, specific counter-examples, not generic skepticism, so the 'within a day' claim is disputed rather than simply partial. Missing for 10: any evidence of Adyen actually onboarding a small/new founder-level merchant same-day, or a rebuttal to the reserve/minimum-volume gating reports.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Pay per transaction, with no setup or monthly fees.”
   • [community] “Adyen refuses small clients, under the million :/”
   • [community] “One of the bigger drawbacks of Adyen vs Stripe... they require a crazy reserve (in the millions) if your model is subscription based, to be …”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”
   • [community] “Adyen's pricing model looks much more attractive on paper, but the integration complexity and minimum processing volumes usually keep early-…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com explicitly markets a Hosted Payment Page you can get 'fully branded... in less than a day' and offers self-serve test accounts, payment links, and low-code Flow for fast integration, suggesting a founder could technically wire up a checkout quickly. However, the pricing model is explicitly sales-led with 'no self-serve rate card' and merchants must 'get in touch with our team' to create a plan, implying an onboarding/underwriting step before going live with real payments that isn't addressed in the evidence. Missing for 10: evidence of self-serve signup-to-live-payment flow without sales contact, KYC/merchant approval timelines, and confirmation that a brand-new account can process a live card charge within 24 hours.

   • [claimed-docs] “Get a fully branded checkout page in less than a day. No heavy lifting or confusing compliance. Just one integration, and you're ready to ta…”
   • [claimed-docs] “A dedicated test-account environment with per-scenario testing docs: payments testing, test cards, disputes testing, fraud-detection testing…”
   • [claimed-docs] “Pricing is sales-led and unpublished: a tailored "Fully Flat-Rate" plan ("We price based on your business profile and risk category, nothing…”
   • [claimed-docs] “Create a Payment Link”
   • [claimed-docs] “Flow is a clever bit of code that helps you boost conversions, stay compliant, and enter new markets fast. Accept payments using customizabl…”

   proof ↗⚑ flag

Checkout surfaces

1. developerEmbed customizable payment components directly in my own site or app instead of redirecting to a hosted page

   weight 3 · round to Adyen
   Adyen✓fullcommunity8/10

   Adyen's Web/mobile Drop-in and Components let developers embed sessions-based payment UI directly in their own site/app (web, iOS, Android, React Native, Flutter) with customizable styling and localization, rather than redirecting to a hosted page. This is a core, well-documented capability with sample flows (create session, mount Components) and cross-platform SDK support. Missing for 10: independent hands-on confirmation of embedding ease (community feedback is mixed/critical on integration complexity), and no detailed code-level customization examples in the pack.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [claimed-docs] “Customize the styling of your checkout.”
   • [claimed-docs] “Customize the styling of your checkout. Present your payment form in the local language of your shoppers with our localization support.”
   • [claimed-docs] “With the client key, you have: A single key for all your allowed origins in an environment.”
   • [community] “I implemented Adyen for a company I was consulting for. I liked it. Their integration was not as terrible as many here make it seem. It allo…”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed7/10

   Checkout.com's Flow product is explicitly documented as embeddable, customizable payment components in a single integration rather than a redirect ('Accept payments using customizable components – all through one simple integration'), alongside Mobile SDKs for native embedded checkout. missing for 10: hands-on/independent verification of the embedded component customization (theming depth, framework support), and a code sample showing actual component embedding rather than marketing copy.

   • [claimed-docs] “Flow is a clever bit of code that helps you boost conversions, stay compliant, and enter new markets fast. Accept payments using customizabl…”
   • [claimed-docs] “Get started with low-code Flow”
   • [claimed-docs] “Take charge of your mobile checkout with Flow for Mobile. Available via iOS and Android Mobile SDKs.”
   • [claimed-docs] “Mobile SDK: Build native mobile checkout experiences for iOS and Android.”

   proof ↗⚑ flag

2. developerRedirect customers to a vendor-hosted, conversion-optimized checkout page without building my own payment UI

   weight 3 · round to Checkout.com
   Adyen~partialclaimed6/10

   Adyen explicitly offers hosted 'payment links' that developers can generate and redirect customers to without building payment UI (adyen-docs-24), and the MCP tool surface confirms this as a first-class API capability (create/get/expire payment links) (adyen-supp-mcp-tools). However, Adyen's primary integration path emphasized in the docs is the Sessions/Components client-side flow which requires building or embedding UI (adyen-docs-1), and there is no detailed documentation on conversion-optimization specifics of the hosted page itself. Missing for 10: dedicated documentation describing the hosted checkout page's design/conversion features, independent evidence of its effectiveness, and clarity on it being the recommended 'no-code UI' path rather than a secondary option.

   • [claimed-docs] “Offer payment links.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com documents a dedicated Hosted Payments Page product ('Get a fully branded checkout page in less than a day... one integration') with low-code deployment and customization docs, plus a related Payment Links option for no-code hosted checkout flows. This directly matches the story of redirecting to a vendor-hosted, conversion-optimized checkout page without building custom payment UI. Missing for 10: independent/third-party conversion benchmarks or hands-on merchant testimonials validating the 'conversion-optimized' claim beyond vendor copy.

   • [claimed-docs] “Get a fully branded checkout page in less than a day. No heavy lifting or confusing compliance. Just one integration, and you're ready to ta…”
   • [claimed-docs] “Customize your Hosted Payments Page”
   • [claimed-docs] “Hosted Payment Page: Deploy a pre-built, low-code payment page integration.”
   • [claimed-docs] “Create a Payment Link”
   • [claimed-docs] “Send secure Payment Links over email, SMS, social, and more – without any need for coding – and open up more revenue opportunities, no matte…”
   • [claimed-docs] “Flow is a clever bit of code that helps you boost conversions, stay compliant, and enter new markets fast. Accept payments using customizabl…”

   proof ↗⚑ flag

No code selling

1. founderCreate a shareable payment link from the dashboard with no code and start selling immediately

   weight 2 · round to Checkout.com
   Adyen!disputedcontradicted4/10

   Adyen's docs confirm a payment-links feature exists ("Offer payment links" - adyen-docs-24) and a Customer Area dashboard for managing transactions (adyen-docs-16), but there is no evidence of a self-serve, no-code flow a founder can use to instantly start selling. Community reports concretely contradict the 'start immediately' premise for founders: Adyen is described as refusing small clients ('Adyen refuses small clients, under the million' - adyen-comm-1) and requiring underwriting/minimum volumes that keep early-stage startups away ('integration complexity and minimum processing volumes usually keep early-stage startups on Stripe' - adyen-comm-11), unlike a turnkey signup-and-sell experience. missing for 10: documented self-serve onboarding flow for small merchants, step-by-step dashboard payment-link creation, evidence that a founder can go live without a sales/underwriting process.

   • [claimed-docs] “Offer payment links.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [community] “Adyen refuses small clients, under the million :/”
   • [community] “Adyen's pricing model looks much more attractive on paper, but the integration complexity and minimum processing volumes usually keep early-…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com explicitly documents no-code Payment Links that can be sent via email/SMS/social to accept payments without coding (checkout-com-docs-5, -19, -41, -56), which directly matches the story. However, the account/pricing evidence indicates a sales-led, KYC-gated onboarding model rather than instant self-serve signup ('get in touch with our team' — cko-supp-pricing), undercutting the 'start selling immediately' claim for a new founder. Missing for 10: evidence of an instant self-serve dashboard signup (no sales call) and independent/hands-on confirmation that a first-time user can generate a link within minutes.

   • [claimed-docs] “Payment Links: Accept payments on any channel using shareable payment links.”
   • [claimed-docs] “Create a Payment Link”
   • [claimed-docs] “Send secure Payment Links over email, SMS, social, and more – without any need for coding – and open up more revenue opportunities, no matte…”
   • [claimed-docs] “Create a Payment Link - Docs”
   • [claimed-docs] “Pricing is sales-led and unpublished: a tailored "Fully Flat-Rate" plan ("We price based on your business profile and risk category, nothing…”

   proof ↗⚑ flag

Payment methods

1. founderOffer digital wallets and local payment methods (Apple Pay, Google Pay, bank redirects, BNPL) from the same integration

   weight 2 · round drawn
   Adyen✓fullcommunity8/10

   Adyen docs explicitly promise 'one integration' covering all preferred payment methods (wallets, local methods, BNPL) via a single Checkout API/sessions flow, with community corroboration that it supports native local methods like iDEAL and Sofort. Missing for 10: an explicit itemized list of Apple Pay/Google Pay/BNPL support and independent hands-on confirmation of wallet/BNPL specifically (only general local-method corroboration exists), plus some community friction reports on integration complexity.

   • [claimed-docs] “Offer your customers all their preferred payment methods with a single integration.”
   • [claimed-docs] “One integration Offer your customers all their preferred payment methods with a single integration.”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Your server makes three Checkout API requests: /paymentMethods, /payments, and /payments/details.”
   • [community] “I implemented Adyen for a company I was consulting for. I liked it. Their integration was not as terrible as many here make it seem. It allo…”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com documents a unified payments API and Flow/Hosted Payment Page integrations that give access to digital wallets, local payment methods, and global card schemes via a single integration (checkout-com-docs-45, checkout-com-docs-2, checkout-com-docs-38, checkout-com-docs-43), explicitly covering local currencies and regional payment strategies. Missing for 10: no explicit line-item confirmation of BNPL providers or bank redirect method names, and no independent/hands-on corroboration of wallet coverage breadth.

   • [claimed-docs] “Get instant access to all the local payment methods, digital wallets, and global card schemes you need for smarter regional strategies and h…”
   • [claimed-docs] “Unified Payments API: Connect to all payment methods through a single API integration.”
   • [claimed-docs] “Flow is a clever bit of code that helps you boost conversions, stay compliant, and enter new markets fast. Accept payments using customizabl…”
   • [claimed-docs] “Take complete control of the entire payment lifecycle from a single API. Upgrade, expand, and adapt your payment experiences with a flexible…”
   • [claimed-docs] “Accept payments like a local business globally. Get paid in local currencies, settle funds fast, and gain valuable insights.”
   • [claimed-docs] “Process worldwide in 150+ currencies. Plus domestic coverage in 45+ countries and counting.”

   proof ↗⚑ flag

Pci compliance

1. developerKeep my systems out of most of PCI DSS scope because card data is tokenized and never touches my servers

   weight 2 · round to Checkout.com
   Adyen~partialclaimed5/10

   Adyen's Checkout API/sessions flow shows card data handled client-side and passed via Adyen's hosted fields/client key rather than touching the merchant's server (adyen-docs-1, adyen-docs-44), which implies the tokenization pattern developers rely on for reduced PCI scope. However, none of the evidence explicitly discusses PCI DSS, SAQ levels, or scope-reduction guidance, so the compliance benefit is only inferable from the technical integration pattern, not documented directly. missing for 10: explicit PCI DSS scope-reduction documentation, SAQ-A eligibility guidance, independent compliance certification evidence.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “With the client key, you have: A single key for all your allowed origins in an environment.”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com offers hosted payment pages, Flow, mobile SDKs, and payment links that are explicitly marketed as reducing compliance burden ('no confusing compliance'), and also supports tokens/network tokens/payment instruments as an alternative to raw card data, all of which are standard mechanisms for keeping card data off merchant servers and reducing PCI scope. However, no evidence explicitly names PCI DSS, SAQ levels, or describes tokenization architecture/vaulting in detail, and the API also documents accepting 'full card details' directly, meaning scope reduction depends on which integration path a developer chooses. Missing for 10: explicit PCI DSS compliance/SAQ-A scope-reduction documentation, dedicated tokenization/vaulting API docs, and independent confirmation of scope-reduction claims.

   • [claimed-docs] “Request a payment using a token, a network token, a payment instrument, or the full card details.”
   • [claimed-docs] “Flow is a clever bit of code that helps you boost conversions, stay compliant, and enter new markets fast. Accept payments using customizabl…”
   • [claimed-docs] “Get a fully branded checkout page in less than a day. No heavy lifting or confusing compliance. Just one integration, and you're ready to ta…”
   • [claimed-docs] “Take charge of your mobile checkout with Flow for Mobile. Available via iOS and Android Mobile SDKs.”
   • [claimed-docs] “Send secure Payment Links over email, SMS, social, and more – without any need for coding – and open up more revenue opportunities, no matte…”
   • [claimed-docs] “Customize your Hosted Payments Page”

   proof ↗⚑ flag

Integration reliability

1. developerSafely retry any API request using idempotency keys so network failures never create duplicate charges

   weight 2 · round to Checkout.com
   Adyen✓fullclaimed8/10

   Adyen explicitly documents idempotency-key headers for retrying API requests without duplicate side-effects (adyen-docs-4, adyen-docs-25), directly matching the story. Missing for 10: independent/hands-on developer confirmation of idempotency behavior in production and detail on key expiration/edge cases.

   • [claimed-docs] “To submit a request for idempotent processing, send a request with the `idempotency-key:` in the header.”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed9/10

   Checkout.com's docs explicitly document idempotency support via the Cko-Idempotency-Key header across payments, authorizations, captures, refunds, cancellations, voids, and transfers endpoints, caching results of 2xx responses to safely retry without duplicate charges, with a configurable idempotency window. Missing for 10: independent/hands-on developer corroboration of real-world retry behavior beyond vendor docs.

   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”
   • [claimed-docs] “Occasionally, you may need to retry a request due to a disrupted API call. For example, if you encounter a network error or timeout.”
   • [claimed-docs] “Idempotency - Docs”

   proof ↗⚑ flag

2. developerRely on signed webhook deliveries with automatic retries, event logs, and replay to keep my system consistent with payment state

   weight 3 · round to Checkout.com
   Adyen~partialclaimed4/10

   Adyen documents webhook event logs in the Customer Area (adyen-docs-45) and general webhook mechanics to avoid polling (adyen-docs-3/17), plus an MCP tool to 'test' webhooks (adyen-supp-mcp-tools) that hints at replay tooling. However, the evidence pack never explicitly documents HMAC/signature verification for webhook payloads, an automatic retry policy for failed webhook deliveries, or a dedicated replay mechanism. Missing for 10: explicit signed-webhook (HMAC) verification docs, documented automatic retry/backoff schedule for webhook delivery, and a concrete replay/redeliver feature beyond the vague MCP 'test' tool.

   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “To submit a request for idempotent processing, send a request with the `idempotency-key:` in the header.”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com documents HMAC-signed webhooks, dashboard/API-based webhook configuration, and a dedicated 'Resend webhooks' capability for replay, satisfying the signing and replay parts of the story. However, evidence does not confirm automatic system-driven retries of failed webhook deliveries (only manual resend) or a dedicated event log/audit trail view for webhook history. Missing for 10: documented automatic retry policy for undelivered webhooks, explicit event log/audit UI, independent confirmation of retry behavior.

   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “Receive webhooks”
   • [claimed-docs] “Resend webhooks”
   • [claimed-docs] “Manage webhooks in the Dashboard”

   proof ↗⚑ flag

Onboarding dx

1. developerIntegrate a working payment flow from the docs alone in under a day, with copy-paste examples in my language

   weight 2 · round to Checkout.com
   Adyen!disputedcontradicted4/10

   Adyen's docs describe a clear-looking integration path (single /sessions call or paymentMethods/payments/payments/details flow, testing, webhooks) and multi-platform SDK support (web, iOS, Android, React Native, Flutter), but no evidence pack item actually shows copy-paste code samples per language, and independent hands-on reports directly contradict the 'under a day' claim: one integrator says 'after hundreds of hours invested, we ditched Adyen' and another states 'Stripe beats Adyen on ease of integration... hands down,' while a third calls it 'much more bare metal' than turnkey competitors. A counter-report says the integration 'was not as terrible as many here make it seem,' so the picture is mixed rather than uniformly negative. missing for 10: actual copy-paste language-specific code samples in the evidence, a documented time-to-first-payment benchmark, and independent confirmation that integration is fast rather than the reported multi-hundred-hour effort.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Your server makes three Checkout API requests: /paymentMethods, /payments, and /payments/details.”
   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”
   • [community] “I implemented Adyen for a company I was consulting for. I liked it. Their integration was not as terrible as many here make it seem. It allo…”
   • [community] “Adyen is much more 'bare metal.' Think more like a modern Authorize.net. Nobody comes close to Stripe's turnkey developer-friendliness.”
   • [community] “Adyen's pricing model looks much more attractive on paper, but the integration complexity and minimum processing volumes usually keep early-…”

   proof ↗⚑ flag

   Checkout.com~partialprobed5/10

   Checkout.com's docs support several low-code paths (Hosted Payment Page explicitly marketed as 'less than a day', Flow, Payment Links, plugins) and there's a Unified Payments API plus a public Node.js SDK on GitHub, suggesting a developer could get a basic flow running quickly. However, the pack shows only one language SDK (Node.js) with no evidence of multi-language copy-paste snippets in the docs themselves, and openapi/reference-doc probes returned 404s, weakening confidence that a full in-docs multi-language integration experience exists. missing for 10: multi-language code samples embedded in docs, other official SDKs (Python/Java/PHP/Ruby), independent hands-on confirmation of 'under a day' integration.

   • [claimed-docs] “Get a fully branded checkout page in less than a day. No heavy lifting or confusing compliance. Just one integration, and you're ready to ta…”
   • [claimed-docs] “Flow is a clever bit of code that helps you boost conversions, stay compliant, and enter new markets fast. Accept payments using customizabl…”
   • [claimed-docs] “Take complete control of the entire payment lifecycle from a single API. Upgrade, expand, and adapt your payment experiences with a flexible…”
   • [github] “The official Node.js SDK for Checkout.com payment gateway.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.checkout.com/openapi.json, https://www.checkout.com/swagger.json, https://www.checkout.c…”
   • [claimed-docs] “Customize your Hosted Payments Page”

   proof ↗⚑ flag

Sandbox fidelity

1. developerBuild and test the entire payment flow in a sandbox or test mode that mirrors production, with test cards for every scenario including declines and disputes

   weight 3 · round to Checkout.com
   Adyen~partialcommunity6/10

   Adyen documents a dedicated test environment with test credentials for exercising different transaction types (adyen-docs-18), recommends testing the full client+server integration before going live (adyen-docs-6), and documents refusal reasons/result codes for simulating declines (adyen-docs-7). However, the pack lacks explicit documentation of test cards for disputes/chargebacks specifically, or a catalog of scenario-specific test cards, and community evidence notes real-world integration friction (adyen-comm-9) though not specifically about sandbox fidelity. Missing for 10: explicit dispute/chargeback simulation test cards, a documented full test-card matrix, and independent hands-on confirmation that sandbox mirrors production behavior.

   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials.”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com documents a dedicated test-account environment with a public 'Get test account' signup, plus per-scenario testing docs covering payments testing, test cards, disputes testing, fraud-detection testing, and bank payouts testing — directly matching the story's requirement for a sandbox mirroring production with test cards for declines and disputes. Missing for 10: independent/hands-on developer corroboration that the sandbox truly mirrors production behavior end-to-end, and more detail on how comprehensive the decline-scenario coverage is beyond the docs listing.

   • [claimed-docs] “A dedicated test-account environment with per-scenario testing docs: payments testing, test cards, disputes testing, fraud-detection testing…”
   • [claimed-docs] “Test cards”
   • [claimed-docs] “Disputes testing”

   proof ↗⚑ flag

Ai disputes

1. ai-native userHave an agent handle a dispute end-to-end, retrieving it, assembling evidence, and submitting the response via the API

   weight 3 · round drawn
   Adyen—none0/10

   The evidence pack contains no mention of a Disputes API, chargeback evidence submission, or any agent/MCP workflow for handling disputes end-to-end—only risk/fraud detection (Protect), refusal reasons, and unrelated agentic-commerce checkout flows are documented. The MCP server's tool list (sessions, payment links, modifications, management API) explicitly does not include dispute retrieval or evidence submission.

   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “You can detect, monitor, and mitigate fraud using Protect, Adyen's risk management system.”
   • [claimed-docs] “Each payment goes through a risk evaluation. The risk evaluation reaches a decision that results in an action to block, allow, or review the…”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”

   proof ↗⚑ flag

   Checkout.com—none0/10

   Checkout.com's docs cover general dispute management topics (manage-disputes, disputes testing, preventing fraudulent disputes) but there's no evidence of an API endpoint for retrieving disputes or submitting evidence, and the documented MCP server's capabilities explicitly list only payment status queries, refunds, voids, and payment links — dispute handling is not among them. No evidence shows an agent can retrieve a dispute, assemble evidence, and submit a response end-to-end via API or MCP.

   • [claimed-docs] “Preventing fraudulent disputes”
   • [claimed-docs] “Disputes testing”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”

   proof ↗⚑ flag

Disputes

1. finance-ops userRespond to a chargeback with structured evidence and track the dispute lifecycle to resolution

   weight 3 · round to Checkout.com
   Adyen—none0/10

   The evidence pack covers Adyen's risk/fraud tooling (Protect, rule builder, ML fraud detection) but contains no documentation of a chargeback/dispute management API, structured evidence submission, or dispute lifecycle tracking/status workflow. A vague community comment says Stripe beats Adyen on chargebacks 'hands down' but gives no concrete detail to substantiate a documented-capability failure, so it doesn't rise to a disputed claim — it simply reinforces the absence of positive evidence.

   ⚑ flag

   Checkout.com~partialclaimed4/10

   Checkout.com documents a disputes management area ("Preventing fraudulent disputes"), dedicated disputes testing scenarios, and webhook events that report "progress on disputes," showing the platform supports dispute lifecycle tracking. However, there is no evidence of the actual structured-evidence submission workflow (e.g., uploading proof documents, dispute reason codes, response deadlines) or a documented end-to-end resolution tracking UI/API. Missing for 10: documentation of evidence submission fields/API, dispute status states and resolution outcomes, and any dashboard/API walkthrough of responding to a chargeback.

   • [claimed-docs] “Preventing fraudulent disputes”
   • [claimed-docs] “Disputes testing”
   • [claimed-docs] “Create risk rules and lists”
   • [claimed-docs] “Retrieve fraud reports”
   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”

   proof ↗⚑ flag

Fraud prevention

1. finance-ops userScreen transactions with machine-learning fraud scores and write custom block, review, and allow rules

   weight 3 · round to Adyen
   Adyen✓fullclaimed8/10

   Adyen's Protect risk management system explicitly provides ML-based fraud scoring plus a rule builder to create, backtest, and label custom rules, with risk evaluations resulting in block/allow/review actions — directly matching the story. Missing for 10: independent/hands-on validation of the rule builder UX and finance-ops-specific workflow evidence beyond first-party docs.

   • [claimed-docs] “You can detect, monitor, and mitigate fraud using Protect, Adyen's risk management system.”
   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”
   • [claimed-docs] “Each payment goes through a risk evaluation. The risk evaluation reaches a decision that results in an action to block, allow, or review the…”
   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com's docs explicitly cover 'Create risk rules and lists' and 'Retrieve fraud reports' under Prevent Fraud, giving finance-ops the ability to write custom block/review/allow-style rules, and it separately touts an 'AI-driven solution' for optimizing acceptance. However, the evidence never names a machine-learning fraud score, a scoring model, or how scores feed into rule conditions, nor a review-queue UI. Missing for 10: explicit ML fraud-score documentation, rule-to-score integration details, and hands-on/independent confirmation of the scoring engine's accuracy or usability.

   • [claimed-docs] “Create risk rules and lists”
   • [claimed-docs] “Retrieve fraud reports”
   • [claimed-docs] “Preventing fraudulent disputes”
   • [claimed-docs] “Automatically optimize payments to increase your acceptance rate with our powerful AI-driven solution.”

   proof ↗⚑ flag

Refunds

1. finance-ops userIssue full or partial refunds from both the dashboard and the API

   weight 3 · round to Checkout.com
   Adyen~partialclaimed5/10

   Evidence confirms API-level refund capability (Adyen's Management/Checkout 'modifications' API allows refunding a captured payment, and the MCP tool set explicitly includes 'refund a captured payment') and dashboard access to transaction management via the Customer Area, but no citation explicitly confirms partial-refund amount support or a documented dashboard refund button/workflow. missing for 10: explicit documentation of partial refund support (specifying an amount less than the captured total), explicit dashboard refund action screenshot/flow, and any independent/hands-on confirmation that refunds work as described.

   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Docs explicitly cover refunding a payment via API with or without a reference (checkout-com-docs-21, checkout-com-docs-55), implying support for full/partial refunds through the payments/{id}/refunds endpoint (also listed as idempotent, cko-supp-idempotency). Dashboard-based refund management is implied by broader webhook/dashboard management patterns but not explicitly documented with a dedicated dashboard refund walkthrough. Missing for 10: explicit dashboard UI screenshot/walkthrough for issuing refunds, and independent/hands-on confirmation of partial refund amounts being configurable.

   • [claimed-docs] “Refund a payment without a reference”
   • [claimed-docs] “Refund a payment with a reference”
   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”

   proof ↗⚑ flag

Multi currency

1. founderCharge customers in their local currencies and settle to my bank in mine with transparent FX handling

   weight 2 · round to Adyen
   Adyen~partialclaimed7/10

   Adyen documents accepting local payment methods/currencies, configuring multiple payout currencies per merchant account, and both local (no SWIFT fee) and cross-border (SWIFT) settlement options, plus flexible payout timing/currency choice — directly supporting charge-local/settle-in-own-currency workflows. However, there's no explicit documentation of FX rate transparency (e.g., disclosed markup, real-time rate reporting) beyond the currency/payout mechanics themselves. Missing for 10: explicit FX rate/markup transparency documentation, independent confirmation of settlement FX handling in practice.

   • [claimed-docs] “Local payouts are faster and avoid SWIFT fees. You need a local bank account in a country that uses that specific currency as the legal tend…”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “This means you have the option to change how you get paid for each of your merchant accounts.”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com clearly supports charging in local currencies (150+ currencies, local acquiring, FX rates API for acquiring/payouts) and provides settlement reporting and a documented FX rate fee for reconciliation, which supports the founder's need to settle in their own currency. However, evidence does not show a clear, transparent published FX markup/rate table or a self-serve explanation of exactly how conversion and settlement currency selection works — pricing and FX fees are sales-led/unpublished, undercutting the 'transparent' claim. Missing for 10: a documented transparent FX rate/markup disclosure mechanism, self-serve settlement currency selection docs, and independent verification of actual FX transparency in practice.

   • [claimed-docs] “Use the FX rates API to retrieve the indicative foreign exchange (FX) rates that Checkout.com uses for acquiring and card payouts.”
   • [claimed-docs] “Process worldwide in 150+ currencies. Plus domestic coverage in 45+ countries and counting.”
   • [claimed-docs] “Accept payments like a local business globally. Get paid in local currencies, settle funds fast, and gain valuable insights.”
   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”
   • [claimed-docs] “Exchange (FX) rate fee”
   • [claimed-docs] “Pricing is sales-led and unpublished: a tailored "Fully Flat-Rate" plan ("We price based on your business profile and risk category, nothing…”
   • [claimed-docs] “Settlement Breakdown Report”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Checkout.com
   Adyen~partialprobed5/10

   Adyen exposes extensive Management/Checkout/Platforms APIs covering payments, onboarding, payouts, webhooks, credentials, terminals, and even an MCP server wrapping many of these APIs, suggesting broad API/UI parity for core payment operations. However, some UI-only surfaces (Customer Area account/transaction overview, visual reporting dashboards) are described only as UI features with no explicit statement that every dashboard/report/action is also API-accessible, and no full OpenAPI spec was reachable at standard docs endpoints (404s), only a separate GitHub repo. Missing for 10: explicit parity claim or evidence that all Customer Area/reporting/dashboard actions have API equivalents, and a verified complete OpenAPI coverage confirmation.

   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “You can also create multiple API credentials to improve security and control access.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”

   proof ↗⚑ flag

   Checkout.com~partialprobed6/10

   Checkout.com's core payment lifecycle (payments, refunds, voids, payment links, webhooks, reconciliation, platforms/sub-entities, FX) is fully API-driven per docs, and the API is treated as the primary integration surface rather than the UI. However, some Dashboard-only or UI-centric functions (e.g., some fraud rule configuration, risk list management, business account setup, certain reporting views) are only shown via Dashboard screenshots/flows without confirmed API parity, and no OpenAPI spec was discoverable (404s on probes) to verify full API surface coverage. missing for 10: confirmed API parity for all Dashboard-configurable settings (risk rules, fraud lists, business account management), a public/complete OpenAPI spec, and independent evidence confirming no UI-only features exist.

   • [claimed-docs] “Unified Payments API: Connect to all payment methods through a single API integration.”
   • [claimed-docs] “Idempotent retries are first-class: "The following endpoints from our API support idempotent requests, so you can safely retry them without …”
   • [claimed-docs] “Two documented server-side authentication forms — "Access keys (OAuth 2.0)" (client-credentials flow) and "Secret keys" — plus public keys f…”
   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”
   • [claimed-docs] “"The Platforms solution enables marketplaces, payment facilitators (Payfacs), and other platform-based businesses to onboard sub-entities an…”
   • [claimed-docs] “Create risk rules and lists”
   • [claimed-docs] “Retrieve fraud reports”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.checkout.com/openapi.json, https://www.checkout.com/swagger.json, https://www.checkout.c…”
   • [claimed-docs] “Refund a payment without a reference”
   • [claimed-docs] “Refund a payment with a reference”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Checkout.com
   Adyen—none0/10

   The evidence pack shows reporting dashboards and general documentation transparency (llms.txt, markdown docs, OpenAPI specs) but nothing about a merchant being able to export their own transactional/account data in open formats or close their account and leave without lock-in. Reporting is described as visual dashboards (adyen-docs-10), not bulk open-format export, and no data-portability/account-closure mechanism is documented.

   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”

   proof ↗⚑ flag

   Checkout.com~partialclaimed3/10

   Checkout.com documents various financial reports (Settlement Breakdown, Balance, Payouts, Reconciliation) accessible via Dashboard/API, which implies some data export capability, but there is no explicit documentation of a comprehensive 'export all your data in open formats and leave' capability, no data portability policy, and no mention of open-format guarantees or full account data export upon departure. missing for 10: explicit full-data export tooling, open-format (CSV/JSON) export guarantees, documented data portability/account closure export process, and independent confirmation of completeness.

   • [claimed-docs] “Reconciliation is a crucial part of your business's bookkeeping process. You can reconcile your balances, fee categories, financial actions,…”
   • [claimed-docs] “Settlement Breakdown Report”
   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”

   proof ↗⚑ flag

Ai reconciliation

1. ai-native userHave an agent pull payout and balance-transaction data via the API and reconcile each bank deposit to its underlying charges

   weight 3 · round to Checkout.com
   Adyen—none0/10

   The evidence pack describes payouts, payout frequency, currencies, and a dashboard 'visual representation' of balances/payouts (adyen-docs-9,10,12,30,43), but nowhere documents an API for pulling balance/transaction-level data or a reconciliation workflow that an agent could invoke — the MCP tool list (adyen-supp-mcp-tools) covers checkout, payment links, and management API objects (merchants, terminals, webhooks, credentials) with no balance-transaction or reconciliation tools. Missing for 10: documented Balance/Transaction API endpoints, evidence of agent/MCP access to payout reconciliation data, and any reconciliation workflow example.

   • [claimed-docs] “Adyen supports paying out to cards instantly, and immediately returns the result of the payout attempt.”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com documents a report suite explicitly designed for reconciling payouts to underlying financial actions (Balance Breakdown, Balance, Financial Actions by Date Range/Payout ID, Payouts, Settlement Breakdown, Settlement Statement reports), and these are exposed via API alongside a documented MCP server and OAuth2/API-key auth suitable for agent-driven automation. Missing for 10: no explicit end-to-end example showing an agent script pulling payout+balance-transaction endpoints and matching them to charges, and no independent/hands-on confirmation of this reconciliation workflow being done via an agent.

   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”
   • [claimed-docs] “Reconciliation is a crucial part of your business's bookkeeping process. You can reconcile your balances, fee categories, financial actions,…”
   • [claimed-docs] “Settlement Breakdown Report”
   • [claimed-docs] “Two documented server-side authentication forms — "Access keys (OAuth 2.0)" (client-credentials flow) and "Secret keys" — plus public keys f…”
   • [claimed-docs] “The Checkout.com MCP Server (Beta) "enables you to search through our knowledge base and manage payment operations directly from your AI-ass…”
   • [claimed-docs] “The MCP server is hosted with documented per-environment endpoints — "Sandbox: https://checkout.mcp.sbox.cko.tech Production: https://mcp.ch…”

   proof ↗⚑ flag

Payouts

1. finance-ops userControl the payout schedule and see exactly which charges, fees, and refunds make up each payout

   weight 2 · round drawn
   Adyen~partialclaimed6/10

   Docs clearly support configuring payout frequency, currency, and timing per merchant account (adyen-docs-12, adyen-docs-30, adyen-docs-50, adyen-docs-22) and note local vs cross-border payout mechanics (adyen-docs-13, adyen-docs-43). Reporting is mentioned as giving a 'visual representation of balances, sales, and payouts' (adyen-docs-10) and the Customer Area gives an overview of payment channels (adyen-docs-16), but there is no explicit evidence of a line-item payout reconciliation report breaking down which specific charges, fees, and refunds compose each payout. Missing for 10: detailed payout reconciliation report/API showing per-payout transaction breakdown, fee itemization, and refund matching.

   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “This means you have the option to change how you get paid for each of your merchant accounts.”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “Local payouts are faster and avoid SWIFT fees. You need a local bank account in a country that uses that specific currency as the legal tend…”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”

   proof ↗⚑ flag

   Checkout.com~partialclaimed6/10

   Checkout.com documents a strong reconciliation report suite mapping payouts to their underlying financial actions — the 'Financial Actions by Payout ID Report', 'Payouts Report', 'Settlement Breakdown Report', and 'Balance' reports explicitly let finance-ops trace charges, fees, and refunds composing a payout, plus FX fee visibility. However, there is no evidence of the 'control the payout schedule' half of the story (e.g., configuring payout frequency/cadence or triggering ad hoc payouts) anywhere in the pack. Missing for 10: documentation of payout schedule/frequency configuration, self-serve payout timing controls.

   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”
   • [claimed-docs] “Settlement Breakdown Report”
   • [claimed-docs] “Exchange (FX) rate fee”
   • [claimed-docs] “Reconciliation is a crucial part of your business's bookkeeping process. You can reconcile your balances, fee categories, financial actions,…”

   proof ↗⚑ flag

Reconciliation

1. finance-ops userReconcile settlements to bank deposits with itemized reports covering fees, refunds, and chargebacks

   weight 3 · round to Checkout.com
   Adyen~partialclaimed3/10

   Adyen's reporting docs mention a dashboard 'visual representation of your balances, sales, and payouts' and configurable payout frequency/currency, implying some settlement reporting exists, but nothing in the evidence describes itemized reconciliation reports that break out fees, refunds, and chargebacks against bank deposits. Missing for 10: documented settlement/reconciliation report format, explicit fee/refund/chargeback itemization, and any bank-deposit matching workflow or independent confirmation it works as needed.

   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com documents a dedicated reconciliation report suite (Balance Breakdown, Balance Report, Financial Actions by Date Range/Payout ID, Payouts Report, Settlement Breakdown Report, Settlement Statement) explicitly mapping settlements to underlying financial actions including fee categories, and separate refund/dispute docs cover those transaction types. Missing for 10: independent/third-party corroboration (e.g. finance-ops user reviews) that reconciliation reports itemize chargebacks specifically and match to bank deposits in practice, and no sample report output shown.

   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”
   • [claimed-docs] “Reconciliation is a crucial part of your business's bookkeeping process. You can reconcile your balances, fee categories, financial actions,…”
   • [claimed-docs] “Settlement Breakdown Report”
   • [claimed-docs] “"Webhooks are automated messages that Checkout.com sends your server when events related to your account occur. For example, payment lifecyc…”
   • [claimed-docs] “Refund a payment without a reference”
   • [claimed-docs] “Refund a payment with a reference”
   • [claimed-docs] “Preventing fraudulent disputes”
   • [claimed-docs] “Exchange (FX) rate fee”

   proof ↗⚑ flag

Marketplace

1. developerBuild a marketplace or platform that onboards sellers, splits payments between parties, and pays out to each seller

   weight 2 · round drawn
   Adyen✓fullclaimed8/10

   Adyen for Platforms is explicitly documented to onboard sellers/contractors with verification (adyen-docs-11, adyen-docs-31, adyen-docs-36), split payments between parties and hold funds until payout (adyen-docs-21, adyen-docs-37), and configure flexible payout frequency/currency/local vs cross-border payouts (adyen-docs-12, adyen-docs-13, adyen-docs-22, adyen-docs-43, adyen-docs-50). Reporting/dashboards and risk management further round out the marketplace platform story (adyen-docs-10, adyen-docs-8). missing for 10: independent/hands-on developer account of building a full marketplace integration end-to-end, and more granular API-level detail (e.g., specific split-payment API request/response schemas) beyond docs summaries.

   • [claimed-docs] “Onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out.”
   • [claimed-docs] “Process payments: accept payments on behalf of your users using Adyen's payment processing platform. You can split the payments between one …”
   • [claimed-docs] “Onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out. Adyen informs you of th…”
   • [claimed-docs] “Onboard and verify your users: onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before payi…”
   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Local payouts are faster and avoid SWIFT fees. You need a local bank account in a country that uses that specific currency as the legal tend…”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”
   • [claimed-docs] “Allow your users to easily sign up, sell, and receive payments all within one solution.”
   • [claimed-docs] “This means you have the option to change how you get paid for each of your merchant accounts.”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”

   proof ↗⚑ flag

   Checkout.com✓fullclaimed8/10

   Checkout.com has a dedicated 'Platforms' product explicitly for marketplaces/payfacs that documents onboarding sub-entities, splitting funds between platform and sub-entities, and paying out sub-entities in their local currency/preferred method, backed by reconciliation and settlement reporting to track those splits and payouts. missing for 10: independent/hands-on validation of the onboarding flow, detailed KYC/sub-entity API reference specifics, and public case studies of marketplaces running this in production.

   • [claimed-docs] “"The Platforms solution enables marketplaces, payment facilitators (Payfacs), and other platform-based businesses to onboard sub-entities an…”
   • [claimed-docs] “The Platforms solution enables marketplaces, payment facilitators (Payfacs), and other platform-based businesses to onboard sub-entities and…”
   • [claimed-docs] “Split funds between your platform and sub-entities according to your business model.”
   • [claimed-docs] “Make payouts to your sub-entities in their local currency and preferred payment method.”
   • [claimed-docs] “"You can reconcile your balances, fee categories, financial actions, invoices, and settlements with Checkout.com using the following reports…”
   • [claimed-docs] “Settlement Breakdown Report”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Adyen—none0/10

   The evidence pack contains no mention of data residency, regional data storage options, or any control over where Adyen stores payment/customer data. While this is a fair question for a payments platform (compliance/data-residency is a common enterprise requirement), nothing in the docs, community posts, or agentic-commerce material addresses it.

   ⚑ flag

   Checkout.com—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or user/customer control over where data is stored; while the product processes payments across many currencies/countries, this does not address data residency choice. This axis is applicable to a payments platform handling sensitive data but no supporting evidence exists.

   ⚑ flag