Paddle vs Polar

Agent access

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

   weight 2 · round drawn
   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle~partialprobed6/10

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

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

   proof ↗⚑ flag

   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
   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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
   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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 to Paddle
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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 to Polar
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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
   Paddle—none0/10

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

   ⚑ flag

   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 to Paddle
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 to Paddle
   Paddle✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle~partialprobed6/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   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
   Paddle—none0/10

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

   ⚑ flag

   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 to Paddle
   Paddle~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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
   Paddle~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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

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 drawn
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

Invoicing

1. finance-ops userSend hosted invoices with online payment and automatic reminders

   weight 2 · round to Paddle
   Paddle~partialclaimed6/10

   Paddle documents sales-assisted invoicing where a team can 'draft and send invoices for subscriptions, collecting payment manually rather than by charging a card on file' (paddle-docs-17/36), and Paddle automatically creates a subscription once an invoice is issued (paddle-docs-69), implying an online payment path. However, the 'automatic reminders' portion of the story is not clearly evidenced for invoices specifically — the documented dunning/Payment Recovery and Tactical Retries feature (paddle-docs-18, paddle-supp-dunning) applies to failed automatic subscription charges, not to reminders for outstanding hosted invoices. Missing for 10: explicit documentation of automated invoice reminder emails/schedules, and independent/hands-on confirmation that invoice payment links and reminders work as described.

   • [claimed-docs] “Your sales team can draft and send invoices for subscriptions, collecting payment manually rather than by charging a card on file.”
   • [claimed-docs] “Invoices let you offer sales-assisted billing. Your sales team can draft and send invoices for subscriptions, collecting payment manually ra…”
   • [claimed-docs] “Paddle automatically creates a subscription for you once an invoice is issued.”
   • [claimed-docs] “You can configure how Payment Recovery notifies customers about failed payments, turn on Tactical Retries, and choose what happens to past d…”
   • [claimed-docs] “Failed-payment recovery is built in at two tiers: "If you use Paddle Billing without integrating with Paddle Retain, failed payments for aut…”

   proof ↗⚑ flag

   Polar—none0/10

   Polar's documented feature set covers checkout links/sessions, subscriptions, usage-based billing, and payment-failure dunning (retry emails when a subscription charge fails), but there is no evidence of a distinct 'invoice' object — i.e., a finance-ops workflow to issue a one-off hosted invoice with a due date and automatic reminders for an unpaid bill. The dunning flow (polar-supp-dunning) only fires after a failed subscription charge, not as a general invoicing/reminder tool.

   ⚑ flag

Subscriptions

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

   weight 2 · round drawn
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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
   Paddle✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   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
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle—none0/10

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

   ⚑ flag

   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 Paddle
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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 Polar
   Paddle~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

Tax

1. finance-ops userCalculate and collect the correct sales tax, VAT, or GST on every transaction automatically

   weight 3 · round to Polar
   Paddle!disputedcontradicted6/10

   Paddle's merchant-of-record model is core to its tax story: docs explicitly state Paddle 'calculates, collects, and remits taxes for you' across 200+ countries with no extra engineering, and reconciliation reports break out tax rates/tax mode per transaction for compliance proof. However, a hands-on community report describes phenomenon-level VAT invoice errors (wrong post-Brexit VAT number, then wrong currency amounts) contradicting the 'just works' claim, while another user praises the same EU VAT handling as a key differentiator vs Stripe/Chargebee — a genuine mixed/contradictory record rather than mere skepticism. Missing for 10: independent audits or documented tax-accuracy testing across specific jurisdictions, and resolution/rebuttal of the VAT invoice complaint.

   • [claimed-docs] “As a merchant of record, Paddle calculates, collects, and remits taxes for you.”
   • [claimed-docs] “The merchant-of-record model is the tax story: "Go global and sell in over 200 countries and territories, fully tax compliant, with no extra…”
   • [claimed-docs] “Build pricing pages that show customers prices localized for their country and currency — including estimated taxes and discounts.”
   • [claimed-docs] “"Payout reconciliation reports help you reconcile payouts to transactions and adjustments to understand how your payout amounts are calculat…”
   • [community] “I had contacted Paddle for UK VAT invoice for our Setapp for Teams subscription and their incompetence is phenomenon: first they used an EU …”
   • [community] “I use Paddle for taking payments for a paid Chrome extension and they've been great with me. Big draw was 'tax management' handling EU VAT u…”

   proof ↗⚑ flag

   Polar✓fullclaimed8/10

   Polar acts as Merchant of Record and documents that it calculates, collects, and remits sales tax/VAT/GST worldwide, taking on international tax liability so sellers don't need to manage it, plus configurable tax-inclusive pricing controls. missing for 10: no independent/hands-on corroboration of actual tax calculation accuracy across jurisdictions, and no detail on specific tax rate/rule coverage per country.

   • [claimed-docs] “As your Merchant of Record, we handle all international tax compliance. We calculate, collect, and remit taxes worldwide.”
   • [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 gives you fine-grained control over this behavior at both the organization level and on individual product prices.”
   • [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: …”
   • [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

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

   weight 2 · round to Polar
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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 Paddle
   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Paddle—none0/10

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

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

   proof ↗⚑ flag

   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

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Paddle—none0/10

   The evidence pack contains extensive docs on billing, checkout, webhooks, API auth, and AI/MCP integrations, but nothing about data retention policies, customer data deletion/export controls, or GDPR-style right-to-be-forgotten mechanisms. Community comments even raise unresolved privacy concerns about Paddle's access to customer data (paddle-comm-3, paddle-comm-4) without any documented deletion/retention controls to address them.

   • [community] “I'm not sure if that pro Paddle list is good for me as a customer. The access to my data at least isn't.”
   • [community] “As a customer, I'd deliberately avoid Paddle to keep my privacy and avoid spam, referencing Paddle's access to customer emails feature.”

   proof ↗⚑ flag

   Polar—none0/10

   The evidence pack covers billing, checkout, subscriptions, webhooks, MCP integration, and merchant-of-record tax handling, but contains no mention of data retention policies, customer data deletion, GDPR/right-to-be-forgotten controls, or any user-facing mechanism to purge or manage stored data. As a platform that stores customer and transaction data, this is a fair question, but no capability is documented.

   ⚑ flag

2. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Paddle—none0/10

   The evidence pack contains no mention of telemetry or usage-tracking collection by Paddle's SDKs, MCP servers, or dashboard, nor any opt-out mechanism. Community items about customer data/spam concerns (paddle-comm-3, paddle-comm-4) relate to end-customer marketing data, not AI-agent telemetry, so they don't establish or contradict this capability.

   ⚑ flag

   Polar—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out; Polar's docs focus on billing, checkout, MCP, webhooks, and merchant-of-record features with no mention of a privacy/telemetry setting.

   ⚑ flag