Checkout.com vs Polar

Agent access

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

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

   Polar✓fullprobed9/10

   Polar publishes an llms.txt at /docs/llms.txt (also live-probed at /llms.txt returning HTTP 200) with .md siblings for every doc page and versioned OpenAPI specs, explicitly designed for agent legibility; this is corroborated by a direct probe hit. Missing for 10: independent third-party confirmation that AI agents actually consume these docs successfully in practice (only first-party docs and probes provided), and the root-level docs.md probe returned 404, showing coverage isn't perfectly uniform across all URL patterns.

   • [claimed-docs] “Migrate to Polar: Get set up on Polar in minutes from an existing store”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://polar.sh/llms.txt # Polar > Payments & Billing with 6 lines of code. Open Source & Global Merchant of R…”
   • [probe] “PROBE docs-md: HTTP 404 at https://polar.sh/docs.md”

   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

   Polar~partialclaimed5/10

   Polar exposes a full API/SDKs (Python, TypeScript), a CLI (`polar listen` for webhook forwarding) and an isolated sandbox environment for testing without live money, all of which could be scripted into CI pipelines, and its OpenAPI/llms.txt makes it machine-legible for automation. However there is no explicit documentation of running Polar itself headlessly or CI/CD integration guidance (e.g., GitHub Actions examples, automated test suites against sandbox). missing for 10: explicit CI/CD pipeline documentation or examples, statement of headless/automation mode, independent evidence of running the CLI/SDKs unattended in a build pipeline.

   • [claimed-docs] “polar listen http://localhost:3000/”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “The official Python SDK provides fully typed synchronous and asynchronous clients for the Polar API.”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”

   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

   Polar✓fullprobed9/10

   Polar (a SaaS billing platform, not itself an agent) documents an official remote MCP server with production and sandbox endpoints, OAuth-based auth, and setup instructions for Cursor, Claude Code, ChatGPT, and Claude Desktop, letting agents securely act on the organization's data. Missing for 10: independent/community hands-on confirmation beyond vendor docs and probes.

   • [claimed-docs] “Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization.”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [probe] “official MCP server documented at https://polar.sh/docs/integrate/mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

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

   Polar~partialclaimed4/10

   The docs show a single CLI invocation, `polar listen http://localhost:3000/`, implying an official Polar CLI for local webhook forwarding/testing, but there's no dedicated CLI reference page, installation instructions, or list of subcommands beyond this one snippet. missing for 10: CLI installation/setup docs, full command reference, independent confirmation of broader CLI usage.

   • [claimed-docs] “polar listen http://localhost:3000/”

   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

   Polar✓fullprobed9/10

   Polar publishes a documented, versioned OpenAPI 3.1 spec, official typed SDKs (TypeScript/Python), webhooks, and llms.txt/agent-legible docs, giving AI-native users a fully documented public API surface to drive the product programmatically. missing for 10: independent third-party corroboration of the API's stability/completeness beyond first-party docs, and the probe showing openapi.json not reachable at the root domain (spec is only under /docs).

   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [claimed-docs] “The official Python SDK provides fully typed synchronous and asynchronous clients for the Polar API.”
   • [claimed-docs] “Webhooks follow the Standard Webhooks spec: "Secrets generated on or after 8 September 2026, 00:00 UTC follow Standard Webhooks. Older secre…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://polar.sh/openapi.json, https://polar.sh/swagger.json, https://polar.sh/api/openapi.json, htt…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://polar.sh/llms.txt # Polar > Payments & Billing with 6 lines of code. Open Source & Global Merchant of R…”

   proof ↗⚑ flag

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

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

   Polar~partialprobed5/10

   Polar's MCP server uses OAuth so agents authorize access to an organization via browser rather than embedding a raw API key, which is a step toward safer agent credentialing, but the docs describe org-level authorization only, not fine-grained/least-privilege scopes (e.g., read-only vs write, per-resource permissions) for issuing agent-specific credentials. Missing for 10: documented scope/permission granularity for API keys or OAuth tokens, ability to restrict an agent to specific resources/actions, and any explicit 'least privilege' credential-issuance workflow.

   • [claimed-docs] “Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization.”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [probe] “official MCP server documented at https://polar.sh/docs/integrate/mcp”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

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

   Polar✓fullclaimed8/10

   Polar documents official TypeScript and Python SDKs with full type safety, fully typed sync/async clients, framework adapters, versioned OpenAPI specs, and machine-legible llms.txt docs—clear support for AI-native developers building against official SDKs. missing for 10: independent third-party corroboration of SDK quality/coverage beyond vendor docs, and the openapi probe found no public root-level spec (though versioned specs are documented within docs).

   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”
   • [claimed-docs] “The official Python SDK provides fully typed synchronous and asynchronous clients for the Polar API.”
   • [claimed-docs] “Framework adapters make it dead simple to add Polar checkouts and webhooks to your stack.”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [claimed-docs] “Our TypeScript & Python SDKs come with a built-in helper function to easily validate and parse the webhook event”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   Polar✓fullclaimed9/10

   Polar provides comprehensive webhook subscription support: documented endpoint configuration, async event notifications instead of polling, Standard Webhooks spec compliance, typed payloads, signature validation SDK helpers, local testing via `polar listen`, and CRUD API for webhook endpoints — directly enabling event-driven/agentic integration patterns. missing for 10: independent third-party corroboration of webhook reliability at scale beyond vendor docs.

   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates”
   • [claimed-docs] “Our TypeScript & Python SDKs come with a built-in helper function to easily validate and parse the webhook event”
   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates... our webhooks offer built-in support for Slack & …”
   • [claimed-docs] “polar listen http://localhost:3000/”
   • [claimed-docs] “Webhooks follow the Standard Webhooks spec: "Secrets generated on or after 8 September 2026, 00:00 UTC follow Standard Webhooks. Older secre…”
   • [claimed-docs] “Customer State is a concept allowing you to query for the current state of a customer, including their active subscriptions and granted bene…”

   proof ↗⚑ flag

Agentic features

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

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

   Polar—none0/10

   Polar's evidence covers billing, checkout, usage metering, webhooks, and an MCP server for external agent access, but nothing describes the product itself generating AI insights, suggestions, or analytics narratives from customer/revenue data for the user inside the dashboard.

   ⚑ flag

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

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

   Polar~partialclaimed5/10

   Polar ships genuine autonomous background automations — automated dunning/payment retries on a fixed schedule, automatic subscription renewal and proration, async webhooks instead of polling, and usage meters that compute continuously — and its MCP server lets AI agents take actions on the account. However, none of this is presented as a user-configurable 'automation builder' or agent-driven workflow scheduler; the autonomy is built into Polar's own billing engine rather than something the AI-native user 'sets up' themselves. Missing for 10: evidence of user-defined trigger/action automation rules, scheduled/cron-like agent workflows, or any explicit 'automation' feature beyond fixed billing/dunning logic.

   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “Polar renews it automatically. At the end of each billing period, Polar advances the subscription to the next cycle and creates a new order”
   • [claimed-docs] “You pick the proration behavior either at the organization level (as the default) or per API call.”
   • [claimed-docs] “Webhooks follow the Standard Webhooks spec: "Secrets generated on or after 8 September 2026, 00:00 UTC follow Standard Webhooks. Older secre…”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [claimed-docs] “Polar has a powerful Usage Based Billing infrastructure that allows you to charge your customers based on the usage of your application.”

   proof ↗⚑ flag

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

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

   Polar—none0/10

   Polar's evidence shows an MCP server that lets external AI agents connect to Polar's data/actions (polar-docs-24, polar-supp-mcp), which is the reverse of the story — it's Polar being used as a tool by outside agents, not a built-in assistant inside Polar's own product that a user can delegate tasks to. No evidence of any in-product chat/assistant UI exists in the pack.

   • [claimed-docs] “Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization.”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [probe] “official MCP server documented at https://polar.sh/docs/integrate/mcp”

   proof ↗⚑ flag

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

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

   Polar✓fullprobed8/10

   Polar ships a documented remote MCP server (OAuth-secured) that lets AI agents look up data and take actions across products, customers, subscriptions, orders, and benefits, with explicit setup for Claude Code, Cursor, ChatGPT, and Claude Desktop — enabling natural-language operation of the product via an agent client. Missing for 10: independent/hands-on validation of the MCP server working in practice and concrete examples of successful natural-language command execution beyond vendor docs.

   • [claimed-docs] “Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization.”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [probe] “official MCP server documented at https://polar.sh/docs/integrate/mcp”

   proof ↗⚑ flag

Api quality

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

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

   Polar~partialprobed5/10

   Polar publishes versioned OpenAPI specs and machine-readable docs (llms.txt/.md pages) plus a sandbox environment for testing API calls with test cards, which supports API exploration, but there is no evidence of an actual interactive API reference UI (e.g., a Swagger/Redoc-style console) with embedded runnable examples directly in the docs. Missing for 10: an in-docs interactive 'try it' console, embedded runnable code examples per endpoint, and independent confirmation the OpenAPI spec renders as an explorable reference.

   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “The sandbox environment allows you to experience the complete customer funnel, including checkout. You can perform test payments using Strip…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://polar.sh/openapi.json, https://polar.sh/swagger.json, https://polar.sh/api/openapi.json, htt…”

   proof ↗⚑ flag

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

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

   Polar✓fullprobed7/10

   Polar's docs explicitly state it serves versioned OpenAPI 3.1.0 specs (2026-04.openapi.json, 2026-10.openapi.json) directly from the docs site alongside llms.txt and per-page .md files, giving AI-native users machine-readable spec access. However, probes only tested root-domain paths (polar.sh/openapi.json etc., all 404) rather than the actual documented docs-site paths, so there's no independent confirmation of a successful direct download. Missing for 10: independent verification of the exact documented OpenAPI URL resolving successfully, and no mention of spec discoverability via standard well-known paths.

   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://polar.sh/llms.txt # Polar > Payments & Billing with 6 lines of code. Open Source & Global Merchant of R…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://polar.sh/openapi.json, https://polar.sh/swagger.json, https://polar.sh/api/openapi.json, htt…”

   proof ↗⚑ flag

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

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

   Polar✓fullclaimed9/10

   Polar documents a fully isolated sandbox environment (separate server, unlimited test accounts/orgs) that supports end-to-end testing including checkout with Stripe test cards, explicitly to avoid touching production data or money — and a dedicated sandbox MCP endpoint further supports AI-agent testing workflows. missing for 10: independent/hands-on third-party confirmation beyond vendor docs.

   • [claimed-docs] “The sandbox environment allows you to experience the complete customer funnel, including checkout. You can perform test payments using Strip…”
   • [claimed-docs] “To test Polar or work on your integration without worrying about actual money processing or breaking your live organization, you can use our…”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”

   proof ↗⚑ flag

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

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

   Polar~partialprobed4/10

   Evidence shows Polar publishes dated, versioned OpenAPI specs (2026-04.openapi.json and 2026-10.openapi.json) alongside machine-readable docs (llms.txt), indicating an API versioning scheme exists. However, no evidence describes an explicit deprecation policy, sunset timelines, or migration guidance between API versions; probes for a root-level openapi.json also 404 outside the documented docs-site paths. Missing for 10: documented deprecation/sunset policy, version lifecycle timelines, migration guides between dated API versions, independent confirmation of long-term version support.

   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://polar.sh/openapi.json, https://polar.sh/swagger.json, https://polar.sh/api/openapi.json, htt…”

   proof ↗⚑ flag

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

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

   Polar—none0/10

   Polar's docs describe individual resource APIs, webhooks, SDKs, and an MCP server for agents to look up/take actions, but nothing in the evidence pack describes batch or bulk endpoints (e.g., bulk refunds, bulk customer/product updates, batch import) that would let an AI-native user act on many items in one call.

   ⚑ 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

   Polar~partialclaimed4/10

   Polar ships built-in automated behaviors for specific billing events (auto-renewal, dunning/retry schedules, proration) and webhooks that notify external systems asynchronously when events occur, which a user can wire up to trigger their own actions. However, there is no evidence of a native rule-definition engine (e.g., 'if event X then do Y' conditions/workflows) inside Polar itself — automation requires building a webhook consumer outside the product. Missing for 10: a first-party rules/workflow builder, conditional logic on events, and any evidence of user-authored automation rules beyond webhook delivery.

   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates”
   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates... our webhooks offer built-in support for Slack & …”
   • [claimed-docs] “Webhooks follow the Standard Webhooks spec: "Secrets generated on or after 8 September 2026, 00:00 UTC follow Standard Webhooks. Older secre…”
   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “If that charge fails, the subscription moves to past_due and enters Polar's automated payment recovery (dunning) flow instead of being cance…”
   • [claimed-docs] “polar listen http://localhost:3000/”

   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

   Polar—none0/10

   Polar's automation is limited to internal billing mechanics (auto-renewing subscriptions, fixed dunning retry schedules, meter aggregation) rather than a general-purpose job/workflow scheduler that an AI-native user or agent could configure for arbitrary recurring tasks. The MCP server lets agents take one-off actions on billing data, but there is no evidence of scheduling recurring jobs or workflows via API, MCP, or dashboard.

   • [claimed-docs] “Polar renews it automatically. At the end of each billing period, Polar advances the subscription to the next cycle and creates a new order”
   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “Events are sent to Polar using the Events Ingestion API and are stored in our database.”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

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

   Checkout.com is a payments platform; the evidence covers webhooks, idempotency, MCP server, and flows/plugins, but nothing documents versioning, review workflows, or rollback of 'automations' (e.g. Flow configs, webhook rules, risk rules) as artifacts with history/diff/rollback capability.

   ⚑ flag

   Polar—none0/10

   Polar has automated flows (webhooks, dunning, usage-based billing meters, subscriptions) that could plausibly be configured and changed, but nothing in the evidence describes version history, review workflows, or rollback for these configurations — no changelog, no audit trail, no revert capability is documented.

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

   Polar~partialclaimed6/10

   Polar documents automated dunning (fixed retry schedule 2/5/7/7 days, past_due state, customer emails) plus webhooks for async notifications and an official MCP server letting agents 'look up data and take actions' across subscriptions/orders — enough for an agent to monitor failed payments and dunning state via API/webhooks. However, dunning/retries are built-in automatic Polar behavior rather than agent-driven; there's no documented API/webhook event specifically for failed-charge notification or an endpoint for an agent to manually trigger a retry or custom outreach message. Missing for 10: explicit failed-payment webhook event schema, an API to trigger/override retry attempts, and evidence of agent-customized dunning outreach beyond Polar's built-in emails.

   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “Polar then retries the charge on a fixed schedule, starting from the time of the first failure”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates”
   • [claimed-docs] “Polar lets you run these off-session charges against a customer's saved payment method, without the customer being present.”

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

   Polar~partialclaimed7/10

   Polar documents a remote MCP server giving agents OAuth-secured access to 'take actions across your products, customers, subscriptions, orders, benefits, and more,' plus a full API/SDK stack (Checkout Session API, versioned OpenAPI specs, llms.txt) that would let an agent create a product, price, and payment link programmatically in one session. However, there's no first-party walkthrough or hands-on example explicitly chaining product+price+payment-link creation via MCP or API in a single session. Missing for 10: an explicit documented example/tutorial showing an agent creating product, price, and checkout link together in one session, and independent confirmation the MCP tool schema exposes create-product/create-price actions (not just 'look up' access).

   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [claimed-docs] “Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”

   proof ↗⚑ flag

Subscriptions

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

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

   Polar✓fullclaimed8/10

   Polar documents automated dunning explicitly: failed charges move the subscription to past_due, trigger a fixed retry schedule (2,5,7,7 days up to 21 days), stamp next_payment_attempt_at, and send the customer a recovery email with a Customer Portal link to update payment method rather than canceling immediately. This directly matches the story's core ask of automatic retries with recovery emails. Missing for 10: no evidence of customizable dunning schedules, multi-channel (SMS/in-app) recovery notifications, or independent/hands-on confirmation beyond vendor docs.

   • [claimed-docs] “Polar then retries the charge on a fixed schedule, starting from the time of the first failure”
   • [claimed-docs] “If that charge fails, the subscription moves to past_due and enters Polar's automated payment recovery (dunning) flow instead of being cance…”
   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “The Customer Portal is a hosted, self-service page where your customers can manage everything related to their relationship with your busine…”

   proof ↗⚑ flag

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

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

   Polar✓fullclaimed9/10

   Polar documents recurring subscriptions with automatic renewal, plan upgrades/downgrades with immediate rate changes, configurable proration behavior (org-level or per-call), trials are implied via subscription lifecycle, and dunning/failed-payment retry schedules; seat-based proration is also documented. Missing for 10: explicit first-party documentation of trial period configuration (only inferred, not directly cited) and independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Polar renews it automatically. At the end of each billing period, Polar advances the subscription to the next cycle and creates a new order”
   • [claimed-docs] “You pick the proration behavior either at the organization level (as the default) or per API call.”
   • [claimed-docs] “You can switch between plans anytime, and your rate adjusts immediately.”
   • [claimed-docs] “Polar then retries the charge on a fixed schedule, starting from the time of the first failure”
   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “Add, remove and prorate seats automatically.”
   • [claimed-docs] “If that charge fails, the subscription moves to past_due and enters Polar's automated payment recovery (dunning) flow instead of being cance…”

   proof ↗⚑ flag

Card acceptance

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

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

   Polar✓fullclaimed8/10

   Polar documents fast onboarding ('minutes from an existing store'), no-code Checkout Links you can 'share the URL anywhere,' embedded checkout, and a Merchant-of-Record model that lets founders accept international card payments without setting up separate processors — plus a sandbox to test cards before going live. This directly supports going from signup to accepting a real card payment within a day. Missing for 10: independent/hands-on account confirming actual time-to-first-live-payment (all evidence is vendor docs) and no explicit account approval/KYC timeline that could delay live payments.

   • [claimed-docs] “Migrate to Polar: Get set up on Polar in minutes from an existing store”
   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”
   • [claimed-docs] “Our embedded checkout allows you to provide a seamless purchasing experience without redirecting users away from your site.”
   • [claimed-docs] “We take on the liability of international sales taxes globally for you. So you can focus on growing your business vs. accounting bills.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “As the Merchant of Record, Polar takes care of charging customers, so Stripe Payments doesn't need to be available in your country.”

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

   Polar✓fullclaimed8/10

   Polar documents an embedded checkout explicitly designed to avoid redirecting users off-site, plus a Checkout Session API for deeper custom integration, alongside the simpler hosted checkout links option — directly matching the story's ask for embeddable, customizable in-app payment components. Missing for 10: independent/hands-on confirmation of embed customization depth (styling, component-level control) beyond first-party docs.

   • [claimed-docs] “Our embedded checkout allows you to provide a seamless purchasing experience without redirecting users away from your site.”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”

   proof ↗⚑ flag

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

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

   Polar✓fullclaimed9/10

   Polar documents no-code Checkout Links that developers configure once and redirect to (share URL anywhere, hosted, Polar handles the rest), plus a Checkout Session API for deeper redirect flows, and a sandbox to test the full checkout funnel end-to-end — directly matching a vendor-hosted redirect checkout without building custom payment UI. missing for 10: independent third-party review of checkout conversion/UX quality beyond vendor docs.

   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “The sandbox environment allows you to experience the complete customer funnel, including checkout. You can perform test payments using Strip…”

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

   Polar✓fullclaimed8/10

   Polar explicitly documents no-code Checkout Links: 'Configure once in the dashboard, share the URL anywhere... and Polar handles the rest,' as one of three checkout surfaces alongside embedded and API-driven flows, and Polar acts as Merchant of Record so a founder can sell immediately without separate tax/payment setup. Missing for 10: independent/hands-on confirmation of the dashboard link-creation flow beyond vendor docs, and no third-party account of actual end-to-end usage.

   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “We take on the liability of international sales taxes globally for you. So you can focus on growing your business vs. accounting bills.”
   • [claimed-docs] “Migrate to Polar: Get set up on Polar in minutes from an existing store”

   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

   Polar—none0/10

   The evidence pack extensively documents Polar's checkout flows (links, embedded, API-driven), merchant-of-record tax handling, subscriptions, and payments infrastructure, but nowhere mentions specific payment method support such as Apple Pay, Google Pay, bank redirects, or BNPL options. Sandbox testing is documented only via Stripe test card numbers, not wallet/local payment coverage.

   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Our embedded checkout allows you to provide a seamless purchasing experience without redirecting users away from your site.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “The sandbox environment allows you to experience the complete customer funnel, including checkout. You can perform test payments using Strip…”

   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

   Polar~partialclaimed6/10

   Polar's checkout is hosted/embedded (never redirecting raw card data to the developer's own servers) and it acts as Merchant of Record, handling payment processing, tax and compliance obligations, which strongly implies card data tokenization keeps most PCI scope off the developer's infrastructure (polar-docs-7, polar-docs-8, polar-docs-9, polar-supp-checkout-links, polar-docs-40, polar-docs-26). However, the evidence pack never explicitly states a PCI DSS compliance certification or scope-reduction claim, and off-session/saved-card charges (polar-docs-13) aren't tied to any documented tokenization/PCI statement. Missing for 10: an explicit PCI DSS SAQ-A or compliance statement, documentation of card tokenization mechanics, and independent/third-party confirmation of reduced PCI scope.

   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Our embedded checkout allows you to provide a seamless purchasing experience without redirecting users away from your site.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “We take on the liability of international sales taxes globally for you. So you can focus on growing your business vs. accounting bills.”
   • [claimed-docs] “As the Merchant of Record, Polar takes care of charging customers, so Stripe Payments doesn't need to be available in your country.”
   • [claimed-docs] “Polar lets you run these off-session charges against a customer's saved payment method, without the customer being present.”

   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

   Polar—none0/10

   The evidence pack covers checkout, subscriptions, webhooks, SDKs, and dunning/retry logic for failed payments, but nowhere mentions idempotency keys or a documented mechanism for safely retrying API requests to prevent duplicate charges. This is a standard, fair expectation for a payments API, so its absence is 'none' rather than 'na'.

   ⚑ flag

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

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

   Polar~partialclaimed5/10

   Polar's webhooks are signed per the Standard Webhooks spec with SDK-side signature validation, typed payloads, and a Webhook Events API for endpoint management, plus delivery monitoring and Slack/Discord alerts. However, the evidence does not document automatic retry behavior for webhook deliveries specifically, nor event logs of delivery attempts, nor a replay/redeliver mechanism — the retry/dunning schedule cited is for failed payment charges, not webhook redelivery. missing for 10: explicit webhook delivery retry policy, delivery attempt/event log UI, and a replay/resend mechanism for missed webhooks.

   • [claimed-docs] “Webhooks follow the Standard Webhooks spec: "Secrets generated on or after 8 September 2026, 00:00 UTC follow Standard Webhooks. Older secre…”
   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates”
   • [claimed-docs] “Our TypeScript & Python SDKs come with a built-in helper function to easily validate and parse the webhook event”
   • [claimed-docs] “Get notifications asynchronously when events occur instead of having to poll for updates... our webhooks offer built-in support for Slack & …”
   • [claimed-docs] “polar listen http://localhost:3000/”

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

   Polar✓fullclaimed7/10

   Polar's docs provide copy-paste checkout flows (links, embed, session API), official TypeScript & Python SDKs, framework adapters, a full sandbox with test cards, local webhook testing CLI, and an explicit '6 lines of code' quick-start claim—together covering a realistic under-a-day integration path. Missing for 10: independent/hands-on confirmation of the 'under a day' timeline, broader language SDK coverage beyond TS/Python/adapters, and corroboration beyond first-party docs.

   • [claimed-docs] “Configure once in the dashboard, share the URL anywhere (your website, social media, email, a button in your app), and Polar handles the res…”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Our embedded checkout allows you to provide a seamless purchasing experience without redirecting users away from your site.”
   • [claimed-docs] “The sandbox environment allows you to experience the complete customer funnel, including checkout. You can perform test payments using Strip…”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”
   • [claimed-docs] “The official Python SDK provides fully typed synchronous and asynchronous clients for the Polar API.”
   • [claimed-docs] “Framework adapters make it dead simple to add Polar checkouts and webhooks to your stack.”
   • [claimed-docs] “polar listen http://localhost:3000/”
   • [claimed-docs] “Payments & Billing with 6 lines of code. Open Source & Global Merchant of Record.”

   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

   Polar~partialclaimed6/10

   Polar documents a dedicated, isolated sandbox environment that mirrors the full checkout/customer funnel and supports Stripe test card numbers (e.g., 4242...), letting developers test payment flows without real money. However, evidence does not confirm dedicated test cards for every scenario (e.g., specific decline codes, dispute/chargeback simulation) — it relies on generic Stripe test cards with no documented list of scenario-specific cards or dispute-simulation tooling. missing for 10: explicit test-card matrix for various decline reasons, documented way to simulate disputes/chargebacks in sandbox, independent/hands-on confirmation of sandbox fidelity.

   • [claimed-docs] “The sandbox environment allows you to experience the complete customer funnel, including checkout. You can perform test payments using Strip…”
   • [claimed-docs] “A fully isolated test environment rather than a test-mode flag: "you can use our sandbox environment. It's a dedicated server, completely is…”
   • [claimed-docs] “To test Polar or work on your integration without worrying about actual money processing or breaking your live organization, you can use our…”

   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

   Polar—none0/10

   The evidence pack contains no mention of a disputes/chargebacks feature, API, or workflow at all — only refunds, failed payments/dunning, and payouts are documented. As a Merchant of Record, dispute handling is a plausible expected capability, but nothing shows Polar exposes dispute retrieval, evidence assembly, or response submission via API for an agent to act on end-to-end.

   • [claimed-docs] “No matter what refund policy you offer to customers, Polar makes it easy to issue both full and partial refunds”
   • [claimed-docs] “Automated dunning with a published schedule: "If that charge fails, the subscription moves to `past_due` and enters Polar's automated paymen…”
   • [claimed-docs] “If that charge fails, the subscription moves to past_due and enters Polar's automated payment recovery (dunning) flow instead of being cance…”

   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

   Polar—none0/10

   The evidence pack covers refunds, failed payments/dunning, payouts, checkout, and usage billing extensively, but contains no mention of chargebacks, dispute evidence submission, or a dispute lifecycle tracking feature anywhere in the docs or probes.

   ⚑ 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

   Polar~partialclaimed6/10

   Polar's docs explicitly state that full and partial refunds can be issued regardless of refund policy (polar-docs-25), and the product exposes a general typed API/SDK for all resources (polar-docs-23), implying refund actions are API-accessible. However, no evidence explicitly confirms a dedicated refunds API endpoint or dashboard refund UI walkthrough — missing for 10: explicit refunds API endpoint documentation, dashboard UI screenshot/flow evidence, and independent confirmation that partial refund amounts can be specified via API.

   • [claimed-docs] “No matter what refund policy you offer to customers, Polar makes it easy to issue both full and partial refunds”
   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”

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

   Polar—none0/10

   Polar's docs cover MoR tax handling, payouts, and pricing plans, but none of the evidence describes charging customers in their local currency or explains FX conversion/settlement transparency — payouts are described only in terms of a single 'account currency' threshold, with no mention of multi-currency checkout or FX rate disclosure.

   • [claimed-docs] “You can issue a withdrawal — also called a payout — once your balance meets the minimum threshold for your account currency.”
   • [claimed-docs] “You can see your available balance for payout at any time under your Finance page.”
   • [claimed-docs] “We take on the liability of international sales taxes globally for you. So you can focus on growing your business vs. accounting bills.”
   • [claimed-docs] “Polar is the merchant of record ("We take on the liability of international sales taxes globally for you") with public, self-serve pricing: …”

   proof ↗⚑ flag

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

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

   Polar~partialprobed7/10

   Polar documents a broad, versioned API/SDK surface covering checkout, subscriptions, meters/usage billing, customer state, webhooks, refunds, and payouts, plus an official MCP server letting agents 'look up data and take actions across your products, customers, subscriptions, orders, benefits, and more' without needing the UI, and agent-legible docs (llms.txt, OpenAPI specs). However, no explicit vendor statement guarantees 1:1 UI/API parity, some dashboard-only mentions (e.g., 'create and manage your meters from the dashboard') aren't cross-confirmed with an API equivalent in the pack, and root-level openapi.json probes 404'd (spec is only reachable via versioned docs paths). Missing for 10: an explicit parity claim/audit, confirmation every dashboard action (e.g., payouts, balance views) has a documented API call, and independent corroboration of full API/UI equivalence.

   • [claimed-docs] “Customer State is a concept allowing you to query for the current state of a customer, including their active subscriptions and granted bene…”
   • [claimed-docs] “If you want to integrate more deeply the checkout process with your website or application, you can use our dedicated API.”
   • [claimed-docs] “Our embedded checkout allows you to provide a seamless purchasing experience without redirecting users away from your site.”
   • [claimed-docs] “Three documented checkout surfaces: no-code Checkout Links, embedded checkout (embed.md — drop-in on your own site, including an embedded pa…”
   • [claimed-docs] “"Polar has a powerful Usage Based Billing infrastructure that allows you to charge your customers based on the usage of your application. Th…”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”
   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://polar.sh/openapi.json, https://polar.sh/swagger.json, https://polar.sh/api/openapi.json, htt…”

   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

   Polar—none0/10

   Polar is a merchant-of-record billing/payments platform; the evidence pack covers API access, webhooks, MCP, and OpenAPI specs for developers to integrate with, but there is no mention of a data export feature letting a user (customer or merchant) export all of their own data (orders, subscriptions, customer records, transaction history) in an open, portable format for the purpose of leaving the platform. Having an API is not the same as a documented bulk data-export/portability capability.

   ⚑ 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

   Polar~partialclaimed5/10

   Polar documents payout thresholds and balance visibility (polar-docs-14, polar-docs-15), a full typed API/SDK (polar-docs-23, polar-docs-38), webhooks, and a remote MCP server letting agents access 'products, customers, subscriptions, orders, benefits' (polar-supp-mcp). However, there is no explicit documentation of a balance-transaction/ledger API endpoint, nor confirmation that the MCP server or SDK exposes payout/balance data specifically (the MCP scope list omits payouts/balance), so reconciling deposits to charges via an agent is only indirectly supported. Missing for 10: explicit balance-transaction API endpoint docs, MCP/agent access to payout and balance data, and any documented reconciliation workflow or example.

   • [claimed-docs] “You can issue a withdrawal — also called a payout — once your balance meets the minimum threshold for your account currency.”
   • [claimed-docs] “You can see your available balance for payout at any time under your Finance page.”
   • [claimed-docs] “Call the Polar API with full type safety using one of our official SDKs.”
   • [claimed-docs] “"Use Polar's remote Model Context Protocol (MCP) server to give AI agents secure access to your Polar organization. Agents can look up data …”
   • [claimed-docs] “The official Python SDK provides fully typed synchronous and asynchronous clients for the Polar API.”
   • [claimed-docs] “Agent-legible docs and machine specs: polar.sh/docs publishes llms.txt with `.md` siblings for every page, and serves versioned OpenAPI spec…”

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

   Polar~partialclaimed5/10

   Polar documents balance visibility and a manual withdrawal/payout mechanism gated by a minimum threshold, plus refunds and order/charge tracking, giving finance-ops some reconciliation ability. However, there's no evidence of a configurable payout schedule (e.g., automatic weekly/monthly payout cadence) or a consolidated payout report itemizing which specific charges, fees, and refunds roll up into a given payout. missing for 10: documented payout scheduling/cadence controls, a per-payout itemized breakdown of constituent charges/fees/refunds, and any reconciliation report or export tying payouts to transactions.

   • [claimed-docs] “You can issue a withdrawal — also called a payout — once your balance meets the minimum threshold for your account currency.”
   • [claimed-docs] “You can see your available balance for payout at any time under your Finance page.”
   • [claimed-docs] “No matter what refund policy you offer to customers, Polar makes it easy to issue both full and partial refunds”
   • [claimed-docs] “Polar is the merchant of record ("We take on the liability of international sales taxes globally for you") with public, self-serve pricing: …”

   proof ↗⚑ flag

Reconciliation

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

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

   Polar—none0/10

   Polar's docs cover payouts, balance tracking, and refunds, but there is no evidence of itemized reconciliation reports matching settlements to bank deposits, nor any mention of chargeback handling or reporting at all.

   • [claimed-docs] “You can issue a withdrawal — also called a payout — once your balance meets the minimum threshold for your account currency.”
   • [claimed-docs] “You can see your available balance for payout at any time under your Finance page.”
   • [claimed-docs] “No matter what refund policy you offer to customers, Polar makes it easy to issue both full and partial refunds”

   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

   Polar—none0/10

   Polar's evidence describes single-organization merchant-of-record billing, payouts, and balances for one seller, but nothing about onboarding multiple sellers/sub-accounts, splitting a single transaction's proceeds between parties, or a Connect-like marketplace primitive. The axis is plausible for a payments platform, but no evidence supports multi-seller marketplace functionality.

   • [claimed-docs] “You can issue a withdrawal — also called a payout — once your balance meets the minimum threshold for your account currency.”
   • [claimed-docs] “You can see your available balance for payout at any time under your Finance page.”
   • [claimed-docs] “We take on the liability of international sales taxes globally for you. So you can focus on growing your business vs. accounting bills.”
   • [claimed-docs] “Polar is the merchant of record ("We take on the liability of international sales taxes globally for you") with public, self-serve pricing: …”

   proof ↗⚑ flag