Checkout.com vs Paddle

Agent access

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

   weight 2 · round to Paddle
   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

   Paddle✓fullprobed9/10

   Paddle publishes a dedicated llms.txt (confirmed live via HTTP 200 probe) plus a full suite of agent-oriented docs including agent-skills, MCP servers, and an LLM integration benchmark explicitly instructing agents to load skills first. missing for 10: independent third-party (non-Paddle) confirmation that an agent successfully consumed llms.txt end-to-end in the wild.

   • [claimed-docs] “We support four official server-side SDKs: Node.js, Python, Go, and PHP.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.paddle.com/llms.txt # Paddle Developer Docs > Official developer documentation for Paddle Bil…”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [claimed-docs] “Paddle publishes an LLM integration benchmark as agent-facing guidance: "Real-world test of how well LLMs build with Paddle. 23 models teste…”
   • [claimed-docs] “Connect AI agents like Claude and Cursor directly to Paddle to work through complex flows in seconds. Build pricing models, investigate fail…”

   proof ↗⚑ flag

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

   weight 2 · round to Checkout.com
   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

   Paddle~partialprobed6/10

   Paddle exposes a full REST API with Bearer-token auth, OpenAPI spec, Postman collection, and server-side SDKs (Node/Python/Go/PHP) that can all be scripted headlessly in CI, plus a documented Sandbox environment for automated testing and webhooks for event-driven automation. However, this evidence is all API/SDK automation rather than a CLI or headless mode for the product's own dashboard/UI workflows, and there's no explicit CI pipeline example, GitHub Actions integration, or independent hands-on confirmation of running Paddle in CI. missing for 10: dedicated CLI tool, documented CI/CD pipeline examples (e.g., GitHub Actions), independent/community verification of headless CI usage.

   • [claimed-docs] “Paddle publishes an OpenAPI 3.1 specification for the Paddle Billing API. Use it to generate client libraries, drive editor autocomplete, or…”
   • [claimed-docs] “Use Bearer authentication when making requests to the Paddle API. Get a key from Paddle > Developer tools > Authentication.”
   • [claimed-docs] “"Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments..…”
   • [claimed-docs] “We support four official server-side SDKs: Node.js, Python, Go, and PHP.”
   • [claimed-docs] “Import the Paddle Postman collection to explore and test the Paddle Billing API interactively.”
   • [claimed-docs] “Paddle uses webhooks to push real-time notifications to your server when things happen in your account.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.paddle.com/llms.txt # Paddle Developer Docs > Official developer documentation for Paddle Bil…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Paddle✓fullprobed9/10

   Paddle documents an official, hosted, remote MCP server (sandbox and live endpoints, OAuth/API-key auth) that lets agents like Claude and Cursor perform real account actions—pricing, billing, refunds, subscription changes—plus a separate docs MCP server and agent skills, all corroborated by an independent probe confirming the docs URL. This is a first-party, production MCP integration well beyond a generic API wrapper. Missing for 10: independent hands-on user report of connecting an agent to the live MCP server (only vendor docs and a URL probe, no third-party usage account).

   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “A separate docs MCP server connects "AI agents to current Paddle documentation, the OpenAPI specification, and SDK references" (hosted at pa…”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [claimed-docs] “Connect AI agents like Claude and Cursor directly to Paddle to work through complex flows in seconds.”
   • [claimed-docs] “The Paddle MCP server lets AI agents interact with your Paddle account. Instead of navigating the dashboard or making API calls, you can ask…”
   • [probe] “official MCP server documented at https://developer.paddle.com/sdks/ai/paddle-mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   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

   Paddle—none0/10

   Paddle's evidence covers SDKs, MCP servers, agent skills, OpenAPI/Postman specs, and webhooks, but nowhere documents an official Paddle CLI tool; the mentions of 'Claude Code, Codex, and Gemini CLI' refer to third-party AI coding CLIs that Paddle plugins integrate with, not a Paddle-branded CLI.

   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [claimed-docs] “We support four official server-side SDKs: Node.js, Python, Go, and PHP.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.paddle.com/openapi.json, https://developer.paddle.com/swagger.json, https://develo…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Paddle✓fullprobed9/10

   Paddle exposes a full public REST API with Bearer auth, granular permissions, key rotation, an OpenAPI 3.1 spec, Postman collection, and official SDKs (Node, Python, Go, PHP) — plus a purpose-built MCP server with codemode search/execute tools, agent skills, and a docs MCP, explicitly designed for AI agents to drive the product end-to-end. Missing for 10: independent third-party corroboration of the MCP/API working reliably at scale (evidence is entirely vendor docs), and the probe found the OpenAPI spec not resolvable at common guessed paths.

   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “Machine-readable API surface: "Download the Paddle OpenAPI specification to generate client libraries, power editor tooling, or import into …”
   • [claimed-docs] “Use Bearer authentication when making requests to the Paddle API. Get a key from Paddle > Developer tools > Authentication.”
   • [claimed-docs] “Permissions grant an API key access to specific entities or allow it to take specific actions in Paddle.”
   • [claimed-docs] “Paddle publishes an OpenAPI 3.1 specification for the Paddle Billing API. Use it to generate client libraries, drive editor autocomplete, or…”
   • [claimed-docs] “Bearer-token API keys with documented granular permissions: keys are created in "Paddle > Developer tools > Authentication", scoped per the …”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [probe] “official MCP server documented at https://developer.paddle.com/sdks/ai/paddle-mcp”

   proof ↗⚑ flag

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

   weight 2 · round to Paddle
   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

   Paddle~partialclaimed6/10

   Paddle supports API keys with documented granular permissions/scopes (paddle-docs-9, paddle-supp-auth-permissions) and sandbox-only keys (paddle-supp-sandbox) that can be issued for agent use via the MCP server, and Live OAuth MCP connections default to read-only access initially (paddle-supp-mcp-server). However, the MCP server itself explicitly does not gate destructive operations and relies on the user manually creating least-privilege keys rather than the product enforcing scoped credential issuance for agents (paddle-supp-mcp-codemode). missing for 10: no dedicated agent-specific credential/token issuance flow (e.g. per-agent scoped key generation UI or API), no evidence of fine-grained action-level restriction enforced automatically for MCP/agent use, no independent confirmation that permission scoping actually restricts agent behavior in practice.

   • [claimed-docs] “Permissions grant an API key access to specific entities or allow it to take specific actions in Paddle.”
   • [claimed-docs] “Bearer-token API keys with documented granular permissions: keys are created in "Paddle > Developer tools > Authentication", scoped per the …”
   • [claimed-docs] “"Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments..…”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Paddle
   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

   Paddle✓fullprobed9/10

   Paddle publishes official server-side SDKs (Node.js, Python, Go, PHP) with TypeScript definitions, pagination helpers, and webhook signature verification, alongside a maintained OpenAPI 3.1 spec (GitHub repo) and Postman collection for generating clients — all documented as first-party, developer-facing tooling suited to AI-native/agentic building workflows. Missing for 10: independent hands-on developer corroboration of SDK quality/DX beyond Paddle's own docs, and the direct openapi.json endpoint probe 404'd (spec is hosted elsewhere per docs, a minor discrepancy).

   • [claimed-docs] “We support four official server-side SDKs: Node.js, Python, Go, and PHP.”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps.”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps. It ships with TypeScript definitions, iter…”
   • [claimed-docs] “The Paddle Python SDK integrates Paddle Billing with Python applications. It handles pagination automatically, exposes operation classes for…”
   • [claimed-docs] “Machine-readable API surface: "Download the Paddle OpenAPI specification to generate client libraries, power editor tooling, or import into …”
   • [claimed-docs] “Paddle publishes an OpenAPI 3.1 specification for the Paddle Billing API. Use it to generate client libraries, drive editor autocomplete, or…”
   • [claimed-docs] “Postman is the quickest way to explore and test the Paddle Billing API. The Paddle Postman collection includes every operation, so you can t…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.paddle.com/openapi.json, https://developer.paddle.com/swagger.json, https://develo…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Checkout.com
   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

   Paddle✓fullclaimed8/10

   Paddle has robust first-party webhook documentation: real-time push notifications for account events, signature verification via Paddle-Signature header, IP allowlisting guidance, and SDK helpers (Node.js, Python) for verifying webhook signatures. MCP tooling also explicitly supports 'configure webhooks, and simulate events for testing,' making this agent-accessible. Missing for 10: independent/hands-on confirmation of webhook reliability or agent-driven webhook subscription workflows beyond vendor docs.

   • [claimed-docs] “Paddle uses webhooks to push real-time notifications to your server when things happen in your account.”
   • [claimed-docs] “you can use the secret key to generate your own signature for each webhook... if both signatures match then you can be sure that a received …”
   • [claimed-docs] “All webhooks sent by Paddle include a `Paddle-Signature` header. Paddle generates this header using a secret key that only you and Paddle kn…”
   • [claimed-docs] “We recommend adding Paddle webhook IP addresses to your allowlist, and rejecting webhooks that come from other sources.”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps. It ships with TypeScript definitions, iter…”
   • [claimed-docs] “The Paddle Python SDK integrates Paddle Billing with Python applications. It handles pagination automatically, exposes operation classes for…”
   • [claimed-docs] “Generate integration code, configure webhooks, and simulate events for testing.”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Paddle
   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

   Paddle~partialclaimed4/10

   Paddle's MCP server explicitly supports 'analyze revenue, refunds, and transaction patterns' and 'investigate failed payments' via natural-language queries from a connected AI agent (Claude, Cursor, etc.), which can surface insights from account data. However, this requires an external agent/tool to connect via MCP rather than an in-product, always-on AI insights/suggestions feature (e.g., no evidence of a native dashboard widget proactively surfacing AI-generated recommendations). Missing for 10: evidence of built-in, in-app AI-generated insights/suggestions surfaced automatically to users without requiring a separate agent connection, and independent/hands-on corroboration of the MCP-driven analysis actually producing useful insights in practice.

   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “Process subscription upgrades, downgrades, pauses, and cancellatio”
   • [claimed-docs] “Build pricing models, investigate failed payments, integrate Paddle features, or process customer refunds — all in natural language.”
   • [claimed-docs] “Filter, break down, and investigate the metrics and data available in your Paddle account from the dashboard or the API.”

   proof ↗⚑ flag

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

   weight 2 · round to Checkout.com
   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

   Paddle—none0/10

   Paddle's evidence covers webhooks, MCP servers, and agent skills for integration purposes, but none of this describes autonomous background automations (e.g., scheduled/triggered workflows that run without user invocation) — the product is a payments/billing platform with agent-assisted integration tooling, not an automation/workflow engine that runs tasks autonomously in the background. missing for 10: any evidence of scheduled jobs, autonomous triggers, or background automation execution initiated by the user rather than by an explicit API/webhook call.

   ⚑ flag

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

   weight 3 · round to Paddle
   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

   Paddle~partialclaimed6/10

   Paddle doesn't ship a native, in-dashboard AI assistant chat UI; instead it exposes a hosted MCP server and agent-skills that let external AI agents (Claude, Cursor, etc.) connect to Paddle and perform pricing, billing, and integration tasks in natural language, plus a codemode search/execute interface for chaining API calls. This delivers the 'delegate tasks to AI' outcome but only via a third-party agent client rather than an assistant embedded inside Paddle's own product surface. Missing for 10: a first-party in-product chat/assistant UI (not just an MCP endpoint for external agents), and independent hands-on evidence of the delegation experience.

   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The Paddle MCP server lets AI agents interact with your Paddle account. Instead of navigating the dashboard or making API calls, you can ask…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [claimed-docs] “Build pricing models, investigate failed payments, integrate Paddle features, or process customer refunds — all in natural language.”

   proof ↗⚑ flag

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

   weight 2 · round to Paddle
   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

   Paddle✓fullclaimed9/10

   Paddle documents an extensive MCP-based natural-language interface: the hosted Paddle MCP server lets agents 'ask an agent in natural language to handle pricing, billing, support, and integration workflows,' covering pricing changes, refunds, subscription upgrades/downgrades/cancellations, webhook config, and report generation, backed by a codemode search/execute interface, agent skills, and a published LLM benchmark showing measured task success. This is rich, detailed first-party documentation directly on-topic for natural-language operation. Missing for 10: independent/hands-on third-party corroboration that the natural-language commands work reliably in practice (community evidence available is unrelated to AI/MCP usage).

   • [claimed-docs] “Connect AI agents like Claude and Cursor directly to Paddle to work through complex flows in seconds.”
   • [claimed-docs] “Connect AI agents like Claude and Cursor directly to Paddle to work through complex flows in seconds. Build pricing models, investigate fail…”
   • [claimed-docs] “The Paddle MCP server lets AI agents interact with your Paddle account. Instead of navigating the dashboard or making API calls, you can ask…”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [claimed-docs] “Paddle publishes an LLM integration benchmark as agent-facing guidance: "Real-world test of how well LLMs build with Paddle. 23 models teste…”
   • [claimed-docs] “Lets AI agents read data and take actions in your Paddle account.”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Paddle
   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

   Paddle~partialprobed6/10

   Paddle documents an OpenAPI 3.1 spec and an importable Postman collection explicitly framed for interactive exploration/testing ('try the API interactively before writing code', 'explore and test the Paddle Billing API interactively'), which supports runnable-example exploration for AI-native/developer users. However, a probe for a directly hosted interactive reference page (Swagger/Redoc-style) on the docs site returned 404s at common paths, suggesting the 'interactive reference' is delegated to external tools (Postman, Scalar, Redocly) rather than a first-party built-in interactive console. Missing for 10: confirmed first-party hosted interactive API console with live runnable examples, and independent hands-on corroboration of the interactive experience.

   • [claimed-docs] “Import the Paddle Postman collection to explore and test the Paddle Billing API interactively.”
   • [claimed-docs] “Paddle publishes an OpenAPI 3.1 specification for the Paddle Billing API. Use it to generate client libraries, drive editor autocomplete, or…”
   • [claimed-docs] “Postman is the quickest way to explore and test the Paddle Billing API. The Paddle Postman collection includes every operation, so you can t…”
   • [claimed-docs] “Machine-readable API surface: "Download the Paddle OpenAPI specification to generate client libraries, power editor tooling, or import into …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.paddle.com/openapi.json, https://developer.paddle.com/swagger.json, https://develo…”

   proof ↗⚑ flag

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

   weight 2 · round to Paddle
   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

   Paddle✓fullprobed8/10

   Paddle publishes an OpenAPI 3.1 spec maintained in a public GitHub repo (github.com/PaddleHQ/paddle-openapi) documented for generating client libraries and editor tooling, plus a Postman collection, giving AI-native users a downloadable machine-readable spec. However, a live probe found the spec not hosted at common guessable URLs on developer.paddle.com itself, so discoverability outside docs pages is imperfect. missing for 10: direct probe confirmation of a working download URL, independent third-party corroboration of the spec's completeness/currency.

   • [claimed-docs] “Paddle publishes an OpenAPI 3.1 specification for the Paddle Billing API. Use it to generate client libraries, drive editor autocomplete, or…”
   • [claimed-docs] “Paddle publishes an OpenAPI 3.1 specification for the Paddle Billing API. Use it to generate client libraries, drive editor autocomplete, or…”
   • [claimed-docs] “Machine-readable API surface: "Download the Paddle OpenAPI specification to generate client libraries, power editor tooling, or import into …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.paddle.com/openapi.json, https://developer.paddle.com/swagger.json, https://develo…”

   proof ↗⚑ flag

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

   weight 1 · round to Paddle
   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

   Paddle✓fullclaimed9/10

   Paddle documents a dedicated Sandbox environment with fully separate datasets, credentials, dashboards and even a distinct sandbox MCP endpoint/API key prefix, explicitly for building and testing integrations without touching real data or payments — directly serving an AI agent's need to safely test flows. Agent skills and MCP server docs also explicitly reference sandbox testing workflows. Missing for 10: independent/hands-on confirmation that AI agents actually operate correctly against sandbox-mcp.paddle.com in practice (only vendor docs, no third-party corroboration).

   • [claimed-docs] “Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments.”
   • [claimed-docs] “"Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments..…”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Paddle—none0/10

   The evidence pack covers OpenAPI specs, SDKs, authentication, and a changelog, but nowhere documents an explicit API versioning scheme or a deprecation policy for breaking changes. Missing for 10: documented API version headers/scheme, explicit deprecation/sunset policy, and migration timelines for breaking changes.

   ⚑ flag

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

   weight 2 · round to Paddle
   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

   Paddle~partialclaimed5/10

   The MCP 'execute' tool lets an agent chain multiple Paddle API calls in a single invocation, and SDKs offer iterator-based pagination for reading many records, which supports scripted bulk-style workflows for AI agents. However, there is no documented bulk/batch API endpoint (e.g., bulk update prices, bulk refunds) or evidence of handling large-scale operations reliably. Missing for 10: explicit bulk/batch endpoints, evidence of rate-limit handling for large batch jobs, and hands-on proof of bulk operations succeeding at scale.

   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps. It ships with TypeScript definitions, iter…”
   • [claimed-docs] “The Paddle Python SDK integrates Paddle Billing with Python applications. It handles pagination automatically, exposes operation classes for…”
   • [claimed-docs] “Permissions grant an API key access to specific entities or allow it to take specific actions in Paddle.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Paddle~partialclaimed4/10

   Paddle exposes event-driven webhooks that fire on billing events (paddle-docs-11, paddle-docs-45) and lets users configure some built-in automated behaviors like payment recovery/dunning rules and tactical retries (paddle-supp-dunning, paddle-docs-18), which count as rudimentary 'if event X happens, do Y' automation. However, this is limited to a handful of pre-built scenarios (dunning, webhook delivery) rather than a general-purpose rules engine where an AI-native user can define arbitrary custom triggers/actions; actually triggering an action still requires the developer to write server-side code to consume the webhook. Missing for 10: a native no-code/rules-builder UI for arbitrary event-to-action automation, evidence of user-defined conditional logic beyond dunning settings, and any AI-agent-specific example of autonomously creating such rules.

   • [claimed-docs] “Paddle uses webhooks to push real-time notifications to your server when things happen in your account.”
   • [claimed-docs] “We recommend adding Paddle webhook IP addresses to your allowlist, and rejecting webhooks that come from other sources.”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”
   • [claimed-docs] “You can configure how Payment Recovery notifies customers about failed payments, turn on Tactical Retries, and choose what happens to past d…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Checkout.com—none0/10

   The evidence pack documents payment processing, webhooks, MCP-driven operations, and reconciliation reports, but nowhere describes recurring/scheduled job or workflow automation (e.g., subscription billing, cron-like scheduling, recurring payment automation) that an AI-native user could set up. No mention of scheduling, recurring billing, or workflow orchestration exists in the pack.

   ⚑ flag

   Paddle—none0/10

   Paddle's AI/MCP tooling (paddle-mcp, docs-mcp, agent-skills) lets agents execute one-off actions like billing, refunds, and integration tasks in real time, and its subscriptions themselves are recurring billing cycles, but there is no evidence of a scheduler or cron-like mechanism letting an AI agent set up or manage recurring automated jobs/workflows (e.g., scheduled reports, recurring agent-triggered tasks) beyond subscription billing itself.

   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “Pause subscriptions to stop billing for them temporarily. Paddle doesn't bill for paused subscriptions until they're resumed.”
   • [claimed-docs] “Customers want to change their base plan, for example going from Pro to Enterprise... Customers want to change their billing frequency, for …”

   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 Paddle
   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

   Paddle~partialclaimed6/10

   Paddle documents webhooks for real-time payment-failure notifications, an API/MCP server that lets agents 'Investigate failed payments and resolve billing issues,' and built-in dunning (Tactical Retries, notification config) — covering the monitoring and resolution loop an AI agent could drive via API/MCP. However, the dunning/retry mechanism itself is a built-in automated system (configured, not actively 'driven' step-by-step by an agent), and there's no explicit example of an agent initiating a retry or outreach action end-to-end. Missing for 10: a concrete agent-driven retry/outreach workflow example, and clarity on whether MCP actions can actually trigger/override the automatic retry schedule rather than just configure it.

   • [claimed-docs] “Paddle uses webhooks to push real-time notifications to your server when things happen in your account.”
   • [claimed-docs] “You can configure how Payment Recovery notifies customers about failed payments, turn on Tactical Retries, and choose what happens to past d…”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “you can use the secret key to generate your own signature for each webhook... if both signatures match then you can be sure that a received …”

   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 Paddle
   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

   Paddle✓fullclaimed8/10

   Paddle's hosted MCP server gives agents a codemode interface (search + execute) that can chain arbitrary Paddle API calls — including creating products, prices, and payment/checkout links — all within one authenticated session, backed by API key/OAuth auth and full OpenAPI coverage (paddle-supp-mcp-server, paddle-supp-mcp-codemode, paddle-docs-15, paddle-docs-46). This directly supports an agent provisioning product+price+payment link end-to-end via API in one session. missing for 10: no independent/hands-on report of an agent actually completing this exact three-step flow (product→price→link) in one session, and no explicit example transcript showing payment-link creation specifically via the MCP execute tool.

   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “The MCP server "uses a codemode interface": three tools cover the full API — `search` ("Looks up Paddle API methods by name or description. …”
   • [claimed-docs] “you may also create your own transactions using the API or Paddle dashboard.”
   • [claimed-docs] “Paddle automatically creates transactions for subscription lifecycle events and when checkouts are opened, but you can create your own trans…”
   • [claimed-docs] “Use Bearer authentication when making requests to the Paddle API. Get a key from Paddle > Developer tools > Authentication.”
   • [claimed-docs] “"Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments..…”

   proof ↗⚑ flag

Subscriptions

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

   weight 2 · round to Paddle
   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

   Paddle✓fullclaimed8/10

   Paddle's docs explicitly describe built-in dunning: failed payments are automatically retried up to seven times over 30 days, and Paddle Retain's Payment Recovery adds configurable Tactical Retries, optimized recovery email notifications, and in-app retry forms, plus control over past-due subscription outcomes. missing for 10: independent/hands-on evidence of recovery-email effectiveness or customer testimonials, and the pack notes Retain can't be tested in sandbox, limiting pre-production verification.

   • [claimed-docs] “You can configure how Payment Recovery notifies customers about failed payments, turn on Tactical Retries, and choose what happens to past d…”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”

   proof ↗⚑ flag

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

   weight 3 · round to Paddle
   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

   Paddle✓fullclaimed7/10

   Paddle's docs comprehensively cover setting up subscription checkouts, plans/prices, pausing subscriptions, and upgrading/downgrading (including changing base plan and billing frequency) via replacing products/prices, plus sales-assisted invoicing and dunning for failed payments — a solid recurring-billing foundation. missing for 10: explicit documentation of free-trial period setup and how proration is calculated/applied on plan changes (evidence only implies plan-change mechanics without naming proration).

   • [claimed-docs] “Add a checkout to your app or website using Paddle.js to let customers buy one-time products and sign up for a subscriptions.”
   • [claimed-docs] “Upgrade a subscription Add or remove recurring addons, move from month to annual, or switch plans by”
   • [claimed-docs] “Pause subscriptions to stop billing for them temporarily. Paddle doesn't bill for paused subscriptions until they're resumed.”
   • [claimed-docs] “Customers want to change their base plan, for example going from Pro to Enterprise... Customers want to change their billing frequency, for …”
   • [claimed-docs] “Depending on your billing model, you might let customers upgrade or downgrade their plan. This could mean: Customers want to change their ba…”
   • [claimed-docs] “Upgrade or downgrade subscriptions by replacing items on a subscription.”
   • [claimed-docs] “You can configure how Payment Recovery notifies customers about failed payments, turn on Tactical Retries, and choose what happens to past d…”
   • [claimed-docs] “Your sales team can draft and send invoices for subscriptions, collecting payment manually rather than by charging a card on file.”

   proof ↗⚑ flag

Card acceptance

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

   weight 3 · round drawn
   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

   Paddle~partialclaimed6/10

   Paddle's docs show clear fast paths to a live checkout: overlay checkout requiring 'minimal frontend coding,' Paddle.js embeds, a sandbox for testing without real payments, and ready-made Next.js/Supabase starter kits that bundle checkout + billing in a day-scale setup. However, nothing in the evidence pack addresses the merchant-of-record account verification/KYC timeline that typically gates going live with real card payments, so the 'within a day' claim is not directly substantiated. Missing for 10: explicit onboarding/verification turnaround time, first-party or independent confirmation of same-day live acceptance.

   • [claimed-docs] “Overlay checkout lets you present customers with an overlay that handles all parts of the checkout process — minimal frontend coding require…”
   • [claimed-docs] “Inline checkout lets you embed a checkout and display information about items and totals in your own interface, creating checkout experience…”
   • [claimed-docs] “"Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments..…”
   • [claimed-docs] “Production-ready Next.js SaaS starter kit with Paddle Billing, Supabase auth, and Vercel deployment. Includes a localized pricing page, inte…”
   • [claimed-docs] “By the end, you'll have a working three-tier subscription app integrated with Supabase for auth and Paddle webhooks for syncing customer dat…”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps.”

   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 Paddle
   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

   Paddle✓fullclaimed8/10

   Paddle documents both Inline checkout (embed checkout and totals fully within your own UI/interface) and Overlay checkout, explicitly positioned as alternatives to a hosted redirect page, backed by Paddle.js and localized pricing components. missing for 10: independent/hands-on developer corroboration of embedding customization depth, and no visual/styling API detail beyond docs claims.

   • [claimed-docs] “Inline checkout lets you embed a checkout and display information about items and totals in your own interface, creating checkout experience…”
   • [claimed-docs] “Overlay checkout lets you present customers with an overlay that handles all parts of the checkout process — minimal frontend coding require…”
   • [claimed-docs] “Add a checkout to your app or website using Paddle.js to let customers buy one-time products and sign up for a subscriptions.”
   • [claimed-docs] “Build pricing pages that show customers prices localized for their country and currency — including estimated taxes and discounts.”

   proof ↗⚑ flag

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

   weight 3 · round to Paddle
   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

   Paddle✓fullclaimed9/10

   Paddle explicitly documents overlay checkout ('present customers with an overlay that handles all parts of the checkout process — minimal frontend coding required') and Paddle.js checkout integration, which is vendor-hosted and conversion-optimized without building a custom payment UI. This is corroborated by supporting docs on inline vs overlay checkout options and sandbox testing. Missing for 10: independent hands-on developer reports validating conversion optimization or checkout UX quality beyond vendor docs.

   • [claimed-docs] “Add a checkout to your app or website using Paddle.js to let customers buy one-time products and sign up for a subscriptions.”
   • [claimed-docs] “Overlay checkout lets you present customers with an overlay that handles all parts of the checkout process — minimal frontend coding require…”
   • [claimed-docs] “Inline checkout lets you embed a checkout and display information about items and totals in your own interface, creating checkout experience…”
   • [claimed-docs] “Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments.”

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

   Paddle—none0/10

   Paddle's evidence centers on developer-integrated checkout (Paddle.js overlay/inline checkout embedded in a website or app) and dashboard-created transactions for internal use, but there is no evidence of a standalone, no-code 'shareable payment link' a founder could generate and immediately distribute (e.g., via email or social media) without any integration work. The closest hints — overlay checkout needing 'minimal frontend coding' and dashboard-created transactions — still imply some setup/integration rather than a pure link-generation flow.

   • [claimed-docs] “Inline checkout lets you embed a checkout and display information about items and totals in your own interface, creating checkout experience…”
   • [claimed-docs] “Overlay checkout lets you present customers with an overlay that handles all parts of the checkout process — minimal frontend coding require…”
   • [claimed-docs] “you may also create your own transactions using the API or Paddle dashboard.”
   • [claimed-docs] “Paddle automatically creates transactions for subscription lifecycle events and when checkouts are opened, but you can create your own trans…”

   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 to Checkout.com
   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

   Paddle~partialclaimed3/10

   Evidence confirms Paddle's broad multi-currency and 200+-country reach, and a specific local payment method (Pix recurring mandate for Brazil) was added, showing the platform does add local payment methods over time. However, there is no explicit documentation of Apple Pay, Google Pay, bank redirects, or BNPL options being available through the same checkout integration. missing for 10: explicit mention/docs of Apple Pay, Google Pay, bank redirect methods, and BNPL support in checkout.

   • [claimed-docs] “Turn on Pix to accept subscription payments from customers in Brazil with a recurring Pix Automático mandate that customers set up at checko…”
   • [claimed-docs] “Paddle has built-in support for multi-currency for both payments and payouts, letting customers purchase in their local currency and letting…”
   • [claimed-docs] “you can unlock new revenue by selling in over 200 countries and territories across the world — no additional setup needed.”
   • [claimed-docs] “With Paddle, you can unlock new revenue by selling in over 200 countries and territories across the world — no additional setup needed.”

   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 drawn
   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

   Paddle~partialclaimed6/10

   Paddle's checkout products (overlay and inline via Paddle.js) handle card capture directly, and as merchant of record Paddle also handles tax/compliance — this strongly implies card data never touches the developer's servers, which is the basis for reduced PCI scope. However, the evidence pack never explicitly states PCI DSS compliance or scope reduction, or names a SAQ level, so the compliance-specific claim is inferred rather than documented. missing for 10: explicit PCI DSS compliance/certification statement, explicit scope-reduction language, and independent/third-party confirmation of PCI posture.

   • [claimed-docs] “Inline checkout lets you embed a checkout and display information about items and totals in your own interface, creating checkout experience…”
   • [claimed-docs] “Overlay checkout lets you present customers with an overlay that handles all parts of the checkout process — minimal frontend coding require…”
   • [claimed-docs] “Add a checkout to your app or website using Paddle.js to let customers buy one-time products and sign up for a subscriptions.”
   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”
   • [claimed-docs] “We take care of payments, tax, subscriptions, and metrics with one unified API that does it all.”

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

   Paddle—none0/10

   No evidence in the pack mentions idempotency keys or any mechanism for safely retrying API requests without duplicate charges; the API auth/rate-limit docs cover bearer tokens, permissions, and key rotation but nothing about idempotency handling.

   ⚑ 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 drawn
   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

   Paddle~partialclaimed6/10

   Paddle documents signed webhooks (Paddle-Signature header + secret-key verification), IP allowlisting guidance, and automatic retries for failed payments/dunning (up to 7 retries over 30 days, Tactical Retries via Retain), plus SDK helpers for signature verification. However, there is no documented event log/dashboard for webhook delivery history, no explicit replay/resend mechanism for missed webhook events, and no mention of delivery guarantees or dead-letter handling. missing for 10: webhook event log/delivery history UI, explicit event replay/resend capability, delivery guarantee/idempotency documentation, independent hands-on confirmation of retry behavior.

   • [claimed-docs] “Paddle uses webhooks to push real-time notifications to your server when things happen in your account.”
   • [claimed-docs] “you can use the secret key to generate your own signature for each webhook... if both signatures match then you can be sure that a received …”
   • [claimed-docs] “All webhooks sent by Paddle include a `Paddle-Signature` header. Paddle generates this header using a secret key that only you and Paddle kn…”
   • [claimed-docs] “We recommend adding Paddle webhook IP addresses to your allowlist, and rejecting webhooks that come from other sources.”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps. It ships with TypeScript definitions, iter…”
   • [claimed-docs] “The Paddle Python SDK integrates Paddle Billing with Python applications. It handles pagination automatically, exposes operation classes for…”

   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 Paddle
   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

   Paddle✓fullclaimed8/10

   Paddle's docs include multiple checkout integration paths (inline/overlay), official SDKs for Node.js, Python, Go and PHP with copy-paste style code and TypeScript support, a sandbox for testing without real payments, and a production-ready Next.js SaaS starter kit that yields 'a working three-tier subscription app' with Paddle checkout and webhooks — directly matching the 'working payment flow in under a day' story across languages. missing for 10: independent/hands-on third-party confirmation of the 'under a day' timeframe and broader language coverage beyond the four official SDKs.

   • [claimed-docs] “Inline checkout lets you embed a checkout and display information about items and totals in your own interface, creating checkout experience…”
   • [claimed-docs] “Overlay checkout lets you present customers with an overlay that handles all parts of the checkout process — minimal frontend coding require…”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps.”
   • [claimed-docs] “We support four official server-side SDKs: Node.js, Python, Go, and PHP.”
   • [claimed-docs] “The Paddle Node.js SDK integrates Paddle Billing with server-side JavaScript and TypeScript apps. It ships with TypeScript definitions, iter…”
   • [claimed-docs] “The Paddle Python SDK integrates Paddle Billing with Python applications. It handles pagination automatically, exposes operation classes for…”
   • [claimed-docs] “Production-ready Next.js SaaS starter kit with Paddle Billing, Supabase auth, and Vercel deployment. Includes a localized pricing page, inte…”
   • [claimed-docs] “By the end, you'll have a working three-tier subscription app integrated with Supabase for auth and Paddle webhooks for syncing customer dat…”
   • [claimed-docs] “Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments.”

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

   Paddle~partialclaimed6/10

   Paddle documents a full Sandbox environment that mirrors production ("same features and APIs but completely separate datasets, credentials, and dashboards") with sandbox-specific API keys, and the MCP tooling explicitly supports simulating webhook events for testing. However, the evidence pack contains no documentation of specific test card numbers for scenario coverage (e.g., decline codes, dispute/chargeback simulation), and notes that Paddle Retain's dunning/payment-recovery features explicitly cannot be tested in sandbox ('you can't integrate or test with sandbox accounts'), which undercuts full parity for testing the entire payment flow. missing for 10: documented test-card list for various decline/failure scenarios, explicit dispute/chargeback simulation support, and confirmation that all payment-flow features (including Retain) are testable in sandbox.

   • [claimed-docs] “Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments.”
   • [claimed-docs] “"Sandbox is a separate Paddle environment for building and testing your integration without affecting real data or accepting real payments..…”
   • [claimed-docs] “Generate integration code, configure webhooks, and simulate events for testing.”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”

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

   Paddle—none0/10

   The evidence pack contains no mention of a Disputes/Chargebacks API endpoint, no ability to retrieve dispute details, assemble evidence, or submit a response programmatically. The only related mentions are generic references to 'chargeback defense' as part of Paddle's merchant-of-record fee and 'investigate failed payments' in the MCP server description, neither of which constitutes dispute-evidence submission via API.

   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”

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

   Paddle—none0/10

   Evidence only shows chargebacks appearing as a fee line-item in payout reconciliation reports and a passing mention that Paddle's merchant-of-record fee includes 'chargeback defense,' but there is no documentation of a finance-ops workflow for submitting structured dispute evidence or tracking a chargeback's lifecycle to resolution.

   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”
   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”

   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 Checkout.com
   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

   Paddle—none0/10

   Evidence only mentions Paddle's merchant-of-record fee covering generic 'fraud protection' and 'chargeback defense' as a bundled service, with no documentation of ML-generated fraud scores or of any UI/API for finance-ops to write custom block/review/allow rules. This axis is fair for a payments platform, but no capability is evidenced.

   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”

   proof ↗⚑ flag

Refunds

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

   weight 3 · round to Checkout.com
   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

   Paddle~partialclaimed4/10

   Refunds are mentioned only indirectly, e.g. AI/MCP docs say agents can 'process customer refunds' and MCP can 'analyze revenue, refunds, and transaction patterns,' implying refund capability exists in the underlying API, but no dedicated dashboard or API documentation on issuing full/partial refunds is present in the evidence pack. missing for 10: explicit API endpoint or dashboard walkthrough for issuing refunds, confirmation of partial-refund support, and independent/hands-on evidence of refund flow working.

   • [claimed-docs] “Connect AI agents like Claude and Cursor directly to Paddle to work through complex flows in seconds. Build pricing models, investigate fail…”
   • [claimed-docs] “Build pricing models, investigate failed payments, integrate Paddle features, or process customer refunds — all in natural language.”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “Process subscription upgrades, downgrades, pauses, and cancellatio”

   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 Paddle
   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

   Paddle✓fullclaimed8/10

   Paddle explicitly documents built-in multi-currency support for both payments and payouts ('customers purchase in their local currency and letting you get paid in yours'), plus localized pricing pages, 200+ country/currency support, and payout reconciliation reports that break down amounts in both transaction and balance currencies for transparency. As merchant of record, Paddle also handles tax compliance alongside FX, directly matching the story. Missing for 10: no explicit documentation of FX conversion rates/margins used, and no independent/hands-on corroboration of settlement transparency beyond vendor docs.

   • [claimed-docs] “Paddle has built-in support for multi-currency for both payments and payouts, letting customers purchase in their local currency and letting…”
   • [claimed-docs] “you can unlock new revenue by selling in over 200 countries and territories across the world — no additional setup needed.”
   • [claimed-docs] “Build pricing pages that show customers prices localized for their country and currency — including estimated taxes and discounts.”
   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”
   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”
   • [claimed-docs] “Available in over 17 languages, across 200+ markets.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Paddle~partialclaimed6/10

   Paddle's docs show broad API coverage for most UI-surfaced flows — checkout, transactions, subscriptions (pause/upgrade), invoices, webhooks, reports, customer portal — plus MCP/agent-skill tooling that lets agents perform catalog, billing, and integration tasks end-to-end (paddle-docs-3, paddle-docs-15-19, paddle-supp-mcp-server, paddle-supp-agent-skills). However, the pack also documents explicit exceptions, e.g. Paddle Retain's dunning/payment-recovery features 'work with live data... you can't integrate or test with sandbox accounts' (paddle-supp-dunning), showing at least one dashboard-configurable feature not fully API/sandbox-equivalent, and there's no blanket claim or independent audit confirming total UI/API parity. missing for 10: an explicit vendor or third-party statement of full UI-API feature parity, and confirmation that Retain-style dashboard-only configurations have API equivalents.

   • [claimed-docs] “you may also create your own transactions using the API or Paddle dashboard.”
   • [claimed-docs] “Upgrade a subscription Add or remove recurring addons, move from month to annual, or switch plans by”
   • [claimed-docs] “Your sales team can draft and send invoices for subscriptions, collecting payment manually rather than by charging a card on file.”
   • [claimed-docs] “Generate reports via API to feed into accounting and BI systems so monthly reconciliations, checks, and dashboards”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “"Agent skills are a standardized way to give AI agents instructions on how to integrate Paddle... written specifically for agents, rather th…”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”

   proof ↗⚑ flag

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

   weight 3 · round to Checkout.com
   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

   Paddle—none0/10

   Paddle documents reports/reconciliation exports and an OpenAPI spec for building integrations, but there is no evidence of a customer-facing 'export all my account/business data in an open format to leave' capability — no GDPR-style data export, no full account data dump, nothing enabling migration away from Paddle with your data intact. Community comments even raise concerns about Paddle's control over customer data rather than showing an exit/export path.

   • [claimed-docs] “Generate reports via API to feed into accounting and BI systems so monthly reconciliations, checks, and dashboards”
   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”
   • [community] “I'm not sure if that pro Paddle list is good for me as a customer. The access to my data at least isn't.”
   • [community] “As a customer, I'd deliberately avoid Paddle to keep my privacy and avoid spam, referencing Paddle's access to customer emails feature.”

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

   Paddle✓fullclaimed7/10

   Paddle publishes dedicated payout reconciliation reports that explicitly reconcile payouts to transactions/adjustments, itemized by gross, tax, fees and currency, generated via API for feeding into accounting/BI systems, and the hosted Paddle MCP server exposes this data to agents (report generation, revenue/refund/transaction analysis) alongside Bearer-token API access with granular permissions. This directly matches the ai-native reconciliation workflow described in the story. missing for 10: independent/hands-on evidence of an agent actually executing an end-to-end payout-to-charge reconciliation via the API/MCP, and explicit documentation of a 'balance transaction' endpoint terminology matching the story's phrasing

   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”
   • [claimed-docs] “Generate reports via API to feed into accounting and BI systems so monthly reconciliations, checks, and dashboards”
   • [claimed-docs] “Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculate…”
   • [claimed-docs] “Generate detailed reports that connect your Paddle payouts to the underlying transaction movements for accurate financial reconciliation.”
   • [claimed-docs] “"The Paddle MCP server is a remote, hosted MCP server" with per-environment endpoints — Sandbox `https://sandbox-mcp.paddle.com/mcp` (API ke…”
   • [claimed-docs] “Bearer-token API keys with documented granular permissions: keys are created in "Paddle > Developer tools > Authentication", scoped per the …”
   • [claimed-docs] “Use Bearer authentication when making requests to the Paddle API. Get a key from Paddle > Developer tools > Authentication.”

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

   Paddle~partialclaimed6/10

   Paddle provides detailed payout reconciliation reports that itemize gross, taxes, Paddle fees, chargebacks, and retained fees per payout, in both transaction and balance currencies, split by invoice entity — directly matching the 'see exactly which charges/fees/refunds' half of the story. However, no evidence describes finance-ops controlling or configuring the payout schedule itself (frequency, timing, thresholds). Missing for 10: documentation of payout schedule/frequency configuration, independent/hands-on confirmation of reconciliation report accuracy.

   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”
   • [claimed-docs] “Generate reports via API to feed into accounting and BI systems so monthly reconciliations, checks, and dashboards”
   • [claimed-docs] “Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculate…”
   • [claimed-docs] “Generate detailed reports that connect your Paddle payouts to the underlying transaction movements for accurate financial reconciliation.”

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round drawn
   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

   Paddle✓fullclaimed8/10

   Paddle publishes dedicated payout reconciliation documentation describing itemized breakdowns of gross, taxes, fees, chargebacks and retained fees split by transaction/balance currency, invoice entity, and even US state/ZIP, explicitly framed as reconciling payouts to remittance advice/bank deposits, plus an API to feed accounting/BI systems for monthly reconciliation. missing for 10: independent/hands-on customer confirmation that the reports actually match bank deposits in practice, and no detail on report formats/exports beyond API generation.

   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”
   • [claimed-docs] “Generate reports via API to feed into accounting and BI systems so monthly reconciliations, checks, and dashboards”
   • [claimed-docs] “Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculate…”
   • [claimed-docs] “Generate detailed reports that connect your Paddle payouts to the underlying transaction movements for accurate financial reconciliation.”
   • [claimed-docs] “Paddle has built-in support for multi-currency for both payments and payouts, letting customers purchase in their local currency and letting…”

   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 to Checkout.com
   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

   Paddle—none0/10

   The evidence pack describes Paddle purely as a merchant-of-record billing/subscription platform for a single seller (checkout, subscriptions, invoices, payouts to the seller's own account, tax compliance) — there is no mention of onboarding multiple third-party sellers, split payments between parties, or marketplace payout distribution akin to Stripe Connect. Nothing in the docs, MCP tooling, or SDKs addresses multi-party marketplace flows.

   • [claimed-docs] “Paddle has built-in support for multi-currency for both payments and payouts, letting customers purchase in their local currency and letting…”
   • [claimed-docs] “With Paddle, you can unlock new revenue by selling in over 200 countries and territories across the world — no additional setup needed.”
   • [claimed-docs] “As a merchant of record, Paddle calculates, collects, and remits taxes for you.”
   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”
   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Paddle—none0/10

   No evidence addresses data residency or region-specific storage choices for Paddle accounts/customers; the pack covers billing, checkout, tax compliance, and AI/MCP tooling but never data residency or regional storage options. Missing for 10: any mention of data center regions, data residency guarantees, or ability to select storage location.

   ⚑ flag