Square vs Paddle

Agent access

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

   weight 2 · round drawn
   Square✓fullprobed9/10

   Square publishes a live, verified llms.txt (probe confirms HTTP 200) explicitly designed for AI agents, with agent-specific guidance on idempotency keys, pagination, and instructions to fetch llms-full.txt or per-page .md files instead of loading the whole corpus; docs pages also render as raw markdown. This is corroborated by an independent probe hit. missing for 10: no independent third-party (non-vendor) confirmation that agents successfully consume this file in practice, and the docs.md/openapi fallback endpoints 404 rather than existing.

   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.squareup.com/llms.txt # Square Developer Platform > Square APIs and SDKs for accepting paymen…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.squareup.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”

   proof ↗⚑ flag

   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Square~partialclaimed6/10

   Square's platform is fundamentally API/SDK-driven (Node.js SDK, REST/GraphQL APIs, idempotency keys) and ships a dedicated Sandbox environment explicitly for testing automation, plus a local MCP server mode (`npx square-mcp-server start`) with env-var controls like SANDBOX=true and DISALLOW_WRITES=true that suit scripted/CI use. However, there is no explicit CI/CD pipeline documentation, GitHub Actions integration, or hands-on evidence of running Square headlessly in an actual CI pipeline. Missing for 10: explicit CI/pipeline integration guides, documented headless automation examples beyond sandbox testing, independent confirmation of CI usage.

   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Square Sandbox”
   • [claimed-docs] “Idempotency”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [github] “const client = new SquareClient({ token: "YOUR_TOKEN" });”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”

   proof ↗⚑ flag

   Paddle~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Square✓fullprobed9/10

   Square documents an official hosted remote MCP server (mcp.squareup.com/mcp) with OAuth-based scoped auth plus an open-source local server, both exposing the full Square API platform, and provides setup guidance for Claude, Cursor, Windsurf, Goose. This is well-documented first-party evidence with a public GitHub repo, though independent hands-on user validation is limited. Missing for 10: independent/community confirmation of real-world agent usage beyond vendor docs.

   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “npx square-mcp-server start”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “The remote MCP is recommended as it uses OAuth authentication, allowing you to log in with your Square account directly without having to cr…”
   • [probe] “official MCP server documented at https://developer.squareup.com/docs/mcp”

   proof ↗⚑ flag

   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Square—none0/10

   Square's evidence shows an MCP server, SDKs, GraphQL, and API Explorer, but no dedicated official CLI tool (e.g., a 'square' command-line utility for managing resources, testing APIs, or agentic workflows) is documented anywhere in the pack. The `npx square-mcp-server start` command is for launching an MCP server, not a general-purpose CLI.

   • [claimed-docs] “npx square-mcp-server start”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs.”

   proof ↗⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Square✓fullprobed9/10

   Square publishes an extensive documented public REST API (payments, refunds, disputes, subscriptions, invoices, webhooks) plus GraphQL, SDKs (e.g. square-nodejs-sdk), API Explorer, sandbox testing, OAuth scopes, and an explicit llms.txt/llms-full.txt agent-consumption index with agent-specific guidance (idempotency keys, pagination) — directly supporting AI-native, agentic driving of the product. Missing for 10: no public OpenAPI/swagger spec discoverable (probe returned 404s), and no independent third-party corroboration beyond vendor docs.

   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”
   • [claimed-docs] “Square access is scope-controlled: "Access tokens are credentials that allow applications to securely interact with Square APIs. An access t…”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.squareup.com/llms.txt # Square Developer Platform > Square APIs and SDKs for accepting paymen…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”

   proof ↗⚑ flag

   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square supports OAuth with per-permission scopes for granular access control, and its remote MCP server explicitly uses OAuth login to 'authorize only the scopes your application needs' for agent connections; the local MCP server also supports a DISALLOW_WRITES read-only mode and SANDBOX flag for least-privilege agent setups. Missing for 10: no independent/hands-on verification of scope granularity in practice, and no explicit documentation of fine-grained scope lists specifically tailored for agent use cases beyond general OAuth scopes.

   • [claimed-docs] “Square access is scope-controlled: "Access tokens are credentials that allow applications to securely interact with Square APIs. An access t…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”
   • [claimed-docs] “The remote MCP is recommended as it uses OAuth authentication, allowing you to log in with your Square account directly without having to cr…”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Paddle
   Square✓fullclaimed8/10

   Square ships official, first-party SDKs (e.g. square-nodejs-sdk/TypeScript library) with documented code examples for payments, versioning, and client setup, plus broader API coverage (REST, GraphQL, OAuth, webhooks, sandbox) that AI-native developers can build against, reinforced by an explicit llms.txt/agent-guidance file and an official MCP server for programmatic AI tool access. Missing for 10: independent/hands-on developer corroboration of SDK quality beyond GitHub README snippets, and broader multi-language SDK evidence beyond Node/TypeScript.

   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [github] “await client.payments.create(..., { version: "2024-05-04" // override the version used })”
   • [github] “const client = new SquareClient({ token: "YOUR_TOKEN" });”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”

   proof ↗⚑ flag

   Paddle✓fullprobed9/10

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

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Square✓fullclaimed8/10

   Square provides a documented Webhooks system with subscribing to event notifications, verifying/validating events, sandbox testing, and event logs — a standard webhook mechanism usable by any AI-native integration (including via its MCP server/API access). missing for 10: no explicit example of an AI agent programmatically subscribing to webhooks, and no independent hands-on corroboration beyond first-party docs.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “[Verify and Validate an Event Notification](/docs/webhooks/step3validate)”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square AI (Beta) is a first-party in-product assistant that answers natural-language questions over the seller's own sales/inventory data, surfaces proactive insights, and even pulls in web data (weather, events, reviews), with seller testimonials confirming real use for sales analysis. Missing for 10: independent/third-party validation beyond vendor testimonials and more detail on breadth/accuracy of suggestions across all data types.

   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”
   • [claimed-docs] “Square AI | Unlock Growth with AI-Powered Insights”

   proof ↗⚑ flag

   Paddle~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Square
   Square~partialclaimed4/10

   Square provides building blocks (Webhooks for event-driven triggers, Subscriptions API for recurring billing, and an MCP server letting AI tools call the API) that a developer could wire into an autonomous background automation, but there is no evidence of a native workflow/automation engine or scheduled-agent feature that runs independently without custom integration work. Square AI is described as an on-demand insight assistant, not an autonomous background automation runner. Missing for 10: a documented no-code/low-code automation or workflow builder, evidence of scheduled/triggered autonomous agent execution, and confirmation that MCP-driven agents can run unattended in the background rather than only via an interactive AI client.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “Subscriptions API”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”

   proof ↗⚑ flag

   Paddle—none0/10

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

   ⚑ flag

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

   weight 3 · round to Square
   Square✓fullclaimed7/10

   Square AI (Beta) is documented as an in-product assistant built into seller tools that answers natural-language questions over sales/inventory data, handles routine tasks, and pulls in web data, with seller testimonials of real usage. Missing for 10: independent/hands-on verification beyond vendor testimonials, and detail on the breadth of tasks it can autonomously execute versus just answer questions.

   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”
   • [claimed-docs] “Square AI | Unlock Growth with AI-Powered Insights”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Paddle
   Square~partialclaimed7/10

   Square ships a first-party beta 'Square AI' seller assistant for natural-language queries over sales/inventory data, and a documented MCP server (local + hosted, OAuth-scoped) that lets AI agents like Claude/Cursor issue natural-language-driven API calls (payments, orders, catalog, etc.) via discovery tools. This gives real NL-command operability, but it's split across a beta insights assistant (limited to analysis/reporting) and third-party agent integration (MCP) rather than a single native NL control surface for all product actions. Missing for 10: evidence that Square AI itself can execute broad write/operational commands (not just analysis), and independent/hands-on validation of MCP agent workflows beyond vendor docs.

   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “Square AI | Unlock Growth with AI-Powered Insights”

   proof ↗⚑ flag

   Paddle✓fullclaimed9/10

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

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Square
   Square✓fullprobed8/10

   Square documents a genuine interactive API Explorer that builds/sends real HTTP requests against Sandbox or production resources (customers, orders, catalog), plus a GraphQL Explorer for runnable queries, giving developers a hands-on interactive reference. Missing for 10: no independent/third-party corroboration of the API Explorer's usability and no discoverable OpenAPI spec (probe confirms 404s), so tooling depth is documented only by the vendor.

   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”
   • [claimed-docs] “API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs.”
   • [claimed-docs] “API Explorer lets you test your requests using actual Sandbox or production resources in your account such as customers, orders, and catalog…”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”

   proof ↗⚑ flag

   Paddle~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Paddle
   Square—none0/10

   No documentation page or probe in the evidence pack shows a downloadable OpenAPI/Swagger spec; explicit probes for common OpenAPI paths (openapi.json, swagger.json, etc.) all returned 404, and no docs page links to a machine-readable spec file (only an interactive API Explorer, GraphQL schema, and SDKs are mentioned).

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.squareup.com/docs.md”
   • [claimed-docs] “API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs.”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   Paddle✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Paddle
   Square✓fullclaimed8/10

   Square documents a dedicated Sandbox environment (square-docs-21, square-docs-40) with sandbox testing for disputes/payments, and the API Explorer and MCP server explicitly support running against Sandbox resources instead of production (square-docs-48, square-supp-api-explorer, square-supp-mcp-remote with 'run a local instance configured to access a seller's Sandbox environment', and SANDBOX=true env var in square-supp-mcp-tools). This directly enables AI-native agents to test without touching production data. Missing for 10: independent/hands-on confirmation that sandbox parity with production is complete and that MCP sandbox mode is broadly validated by third-party users rather than only vendor docs.

   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Square Sandbox”
   • [claimed-docs] “API Explorer lets you test your requests using actual Sandbox or production resources in your account such as customers, orders, and catalog…”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “[Test in the Sandbox](/docs/disputes-api/sandbox-testing)”

   proof ↗⚑ flag

   Paddle✓fullclaimed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Square
   Square~partialclaimed5/10

   Square's API clearly supports date-based versioning — SDK calls can override the API version ("version: '2024-05-04'") and the MCP tool documents a SQUARE_VERSION pinning control — showing a live, explicit versioning scheme. However, no evidence in the pack shows a documented deprecation policy (timelines, sunset notices, migration guides) that would let an AI-native user reliably plan around version lifecycle changes. Missing for 10: an explicit deprecation/sunset policy document, version changelog, or migration guidance referenced anywhere in the evidence.

   • [github] “await client.payments.create(..., { version: "2024-05-04" // override the version used })”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Idempotency”

   proof ↗⚑ flag

   Paddle—none0/10

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

   ⚑ flag

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

   weight 2 · round to Paddle
   Square—none0/10

   The evidence pack shows GraphQL reducing multiple API calls into one query (square-docs-41/square-supp-graphql) and a generic MCP `make_api_request` tool, but no documentation or example of true bulk/batch operations (e.g., batch-upserting catalog items, bulk inventory adjustments, or bulk order processing) that would let an AI-native user act across many items in one call.

   • [claimed-docs] “One GraphQL query can retrieve data that requires multiple Square API calls.”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”

   proof ↗⚑ flag

   Paddle~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Square~partialclaimed4/10

   Square exposes webhooks/event notifications that let a developer wire custom code to react to events (square-docs-19, square-docs-39) and has narrow built-in 'custom rules and alerts' for fraud/risk management (square-docs-28), but there is no general-purpose, user-definable rules/automation engine ('if event X then action Y') across the platform's business events. Missing for 10: a documented no-code/low-code rule builder, broader event-trigger coverage beyond payments/fraud, and evidence of the AI-native user directly authoring such rules (vs. developers writing webhook handlers).

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “Prevent loss online. Get insights into payment fraud patterns, and set custom rules and alerts to manage risk.”
   • [claimed-docs] “[Verify and Validate an Event Notification](/docs/webhooks/step3validate)”

   proof ↗⚑ flag

   Paddle~partialclaimed4/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Square
   Square~partialclaimed4/10

   Square's Subscriptions API and Invoices API let sellers configure recurring billing plans, which is a form of scheduled recurring workflow accessible via the platform's API/MCP surface, but there is no evidence of a general-purpose job/task scheduler or cron-like automation mechanism that an AI agent could use to schedule arbitrary recurring workflows beyond billing. missing for 10: a generic scheduling/automation API (cron, timers, recurring task triggers) independent of payments/subscriptions, evidence of MCP tools exposing scheduling controls, and any hands-on confirmation of recurring workflow automation working end-to-end.

   • [claimed-docs] “Subscriptions API”
   • [claimed-docs] “Invoices API”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”

   proof ↗⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

Ai billing ops

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

   weight 3 · round to Paddle
   Square—none0/10

   Square documents webhooks, a Subscriptions API, and Payments API, but the evidence pack has no mention of failed-payment monitoring, automated retry logic, or dunning outreach features/APIs; the community note even flags subscriptions as a historical gap. An agent could theoretically be built on top of webhooks, but no first-party capability or workflow for this specific story is evidenced.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “Subscriptions API”
   • [community] “Does square have a way to handle subscriptions yet? Seems to be the only thing they are missing”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Paddle
   Square~partialclaimed7/10

   Square's remote/local MCP server (square-mcp-server) exposes a discovery-oriented `make_api_request` tool spanning Catalog, Checkout, and Payments services, and Square's llms.txt explicitly frames the API as agent-consumable with idempotency-key guidance for writes — together these support an agent creating a catalog item (product), its price, and a payment link (via Checkout/Payment Links API) in one session using a single access token/OAuth session. However, no evidence pack item shows an actual end-to-end worked example or transcript of an agent doing product+price+payment-link creation in one session, and Payment Links API itself is not separately documented in the pack (only Checkout/Catalog mentioned generically). missing for 10: an explicit end-to-end tutorial/example chaining catalog item + price + payment link creation, and independent/hands-on confirmation the MCP tool can complete this multi-step flow in a single session.

   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “Learn how to nest modifier lists under modifiers with the Catalog API to build multi-step customization flows”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Invoicing

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

   weight 2 · round to Paddle
   Square~partialclaimed5/10

   Square has a documented Invoices API confirming hosted invoicing exists, but the evidence pack lacks detail on automatic reminders, online payment collection specifics within invoices, or hosted invoice pages. Missing for 10: documentation on automatic reminder scheduling, hosted payment page details, and independent/hands-on confirmation of the invoicing workflow.

   • [claimed-docs] “Invoices API”

   proof ↗⚑ flag

   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

Subscriptions

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

   weight 2 · round to Paddle
   Square—none0/10

   Square documents a Subscriptions API and general payments/invoicing capabilities, but no evidence describes automated retry logic, smart dunning, or recovery emails for failed subscription payments; a community comment even questions whether Square's subscription handling is mature.

   • [claimed-docs] “Subscriptions API”
   • [community] “Does square have a way to handle subscriptions yet? Seems to be the only thing they are missing”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Paddle
   Square~partialcommunity5/10

   Square documents a dedicated Subscriptions API (square-docs-23), confirming recurring billing support, but the evidence pack gives no detail on plan configuration, trial periods, upgrade/downgrade flows, or proration logic. An old community comment (square-comm-1) also shows subscriptions were historically seen as a gap, though this predates the current API's existence. Missing for 10: documented support for trials, plan upgrades/downgrades, and proration calculations; independent/hands-on confirmation these work as expected.

   • [claimed-docs] “Subscriptions API”
   • [community] “Does square have a way to handle subscriptions yet? Seems to be the only thing they are missing”

   proof ↗⚑ flag

   Paddle✓fullclaimed7/10

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

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

   proof ↗⚑ flag

Card acceptance

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

   weight 3 · round to Square
   Square✓fullclaimed7/10

   Square documents self-serve signup with a Web Payments SDK, Card Payments API, and prebuilt eCommerce integrations that 'can be completed in just a few clicks,' plus a Sandbox for immediate testing—consistent with a founder going from signup to live online card acceptance quickly without sales calls. Missing for 10: explicit 'time-to-first-payment' documentation or independent/hands-on account of actual signup-to-live timing.

   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “Square has prebuilt online payment solutions with top eCommerce providers. Most connections can be completed in just a few clicks.”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Take payments in person and online. Securely save recurring payment methods. Easily sync sales, inventory, and customer data with your Squ…”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

Checkout surfaces

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

   weight 3 · round drawn
   Square✓fullclaimed8/10

   Square's Web Payments SDK is explicitly documented for embedding customizable card/ACH/Cash App/Afterpay payment components directly into a developer's own site rather than redirecting to a hosted checkout page, and this is backed by a full Payments API, Node SDK, and sandbox testing tools. missing for 10: no independent/hands-on developer report confirming ease of customization or styling flexibility beyond first-party docs.

   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “[ACH Bank Transfer Payment](/docs/payments-api/take-payments/ach-payments)”
   • [claimed-docs] “[Afterpay and Clearpay Payments](/docs/payments-api/take-payments/afterpay-payments)”
   • [claimed-docs] “[Cash App Payments](/docs/payments-api/take-payments/cash-app-payments)”
   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Take payments in person and online. Securely save recurring payment methods. Easily sync sales, inventory, and customer data with your Squ…”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Paddle
   Square—none0/10

   The evidence pack covers Square's Payments API, Web Payments SDK (embeddable UI), Invoices, and various backend APIs, but never mentions a vendor-hosted, conversion-optimized checkout page (e.g., a Checkout API or Payment Links) that a developer could redirect customers to without building payment UI. Web Payments SDK (square-docs-31) actually requires building your own UI, the opposite of this story.

   ⚑ flag

   Paddle✓fullclaimed9/10

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

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

   proof ↗⚑ flag

No code selling

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

   weight 2 · round drawn
   Square—none0/10

   The evidence pack focuses almost entirely on Square's developer APIs, SDKs, and MCP/AI tooling for building payment integrations, not on the no-code merchant dashboard feature of generating a shareable payment link. No citation mentions 'Payment Links' or a dashboard flow for founders to create a link without coding.

   ⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

Payment methods

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

   weight 2 · round to Square
   Square~partialclaimed6/10

   Square's Payments API and Web Payments SDK docs confirm ACH bank transfers, Afterpay/Clearpay (BNPL), Cash App, and card payments in one integration, but the evidence never explicitly documents Apple Pay or Google Pay wallet support alongside these, nor generic 'bank redirect' methods beyond ACH. missing for 10: explicit Apple Pay/Google Pay digital wallet docs, broader local bank-redirect methods (iDEAL, etc.), and independent confirmation that all these methods coexist in a single unified checkout flow.

   • [claimed-docs] “[ACH Bank Transfer Payment](/docs/payments-api/take-payments/ach-payments)”
   • [claimed-docs] “[Afterpay and Clearpay Payments](/docs/payments-api/take-payments/afterpay-payments)”
   • [claimed-docs] “[Cash App Payments](/docs/payments-api/take-payments/cash-app-payments)”
   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “ACH Bank Transfer Payment”
   • [claimed-docs] “Afterpay and Clearpay Payments”
   • [claimed-docs] “Cash App Payments”

   proof ↗⚑ flag

   Paddle~partialclaimed3/10

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

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

   proof ↗⚑ flag

Pci compliance

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

   weight 2 · round to Paddle
   Square~partialclaimed5/10

   Square's Web Payments SDK and Card Payments API use client-side tokenization (e.g., sourceId/ccof: tokens in the SDK, 'Save Card on File') so raw card numbers are handled by Square's SDK rather than the developer's server, which is the standard architecture for reducing PCI scope. However, the evidence pack contains no explicit statement about PCI DSS compliance level, SAQ A eligibility, or scope-reduction guidance from Square itself. Missing for 10: an explicit PCI DSS/SAQ-A scope statement, documentation of compliance certifications, and independent confirmation that using these SDKs actually reduces a merchant's PCI scope.

   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [claimed-docs] “[Save Card on File](/docs/terminal-api/advanced-features/save-card-on-file)”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

Integration reliability

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

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square has a dedicated 'Idempotency' documentation page and its agent-facing llms.txt explicitly states 'every write endpoint accepts an idempotency key' to prevent duplicate charges from retries. This directly matches the story's core requirement. Missing for 10: independent/hands-on developer confirmation of idempotency behavior under real network-failure retries, and more detail on key expiration/scope beyond the doc title.

   • [claimed-docs] “Idempotency”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”

   proof ↗⚑ flag

   Paddle—none0/10

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

   ⚑ flag

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

   weight 3 · round to Paddle
   Square~partialclaimed5/10

   Square documents webhook subscriptions and signature verification/validation of event notifications, plus mentions of webhook event logs in the dev tools, which covers signed delivery and basic observability. However, the evidence pack contains no explicit documentation of automatic retry behavior or an event replay mechanism, which are core parts of the story. missing for 10: documented automatic retry policy for failed webhook deliveries, explicit event replay/resend capability, independent confirmation of retry/replay behavior.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “[Verify and Validate an Event Notification](/docs/webhooks/step3validate)”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

Onboarding dx

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

   weight 2 · round to Paddle
   Square~partialclaimed6/10

   Square provides extensive first-party docs for card, ACH, Cash App, Afterpay payments, plus sandbox testing and idempotency guidance, and the Node.js/TypeScript SDK shows concrete copy-paste code (client.payments.create). This supports fast integration, but the evidence pack shows only one language's SDK example, no explicit 'under a day' quickstart guide, and no cross-language parity proof (Python, Java, PHP, etc.) or independent developer testimony confirming a same-day integration timeline. missing for 10: multi-language copy-paste examples, an explicit time-to-integrate quickstart, independent hands-on confirmation of a sub-day integration.

   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Idempotency”
   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [github] “const client = new SquareClient({ token: "YOUR_TOKEN" });”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [claimed-docs] “Square Sandbox”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Sandbox fidelity

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

   weight 3 · round to Square
   Square✓fullclaimed7/10

   Square documents a dedicated Sandbox environment (square-docs-21, square-docs-40) with Sandbox Payments docs, sandbox-specific dispute testing (square-docs-16), and an API Explorer that lets developers run requests against actual Sandbox or production resources (square-docs-48, square-supp-api-explorer), covering the core sandbox/test-mode workflow for payments and disputes. missing for 10: explicit enumeration of test card numbers for every decline/dispute scenario and independent developer corroboration that the sandbox fully mirrors production edge cases.

   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Square Sandbox”
   • [claimed-docs] “[Test in the Sandbox](/docs/disputes-api/sandbox-testing)”
   • [claimed-docs] “API Explorer lets you test your requests using actual Sandbox or production resources in your account such as customers, orders, and catalog…”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

Ai disputes

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

   weight 3 · round to Square
   Square~partialclaimed5/10

   Square publishes a Disputes API (retrieve disputes, process them, sandbox testing) and its MCP server's service catalog explicitly includes 'disputes' alongside a generic make_api_request tool, so an agent could plausibly retrieve a dispute and call dispute-related endpoints programmatically. However, there is no documented evidence-assembly workflow (e.g., specific evidence-submission endpoint, required evidence fields) or any hands-on/community example of an agent completing a dispute end-to-end via the API or MCP. missing for 10: explicit evidence-submission API details, a demonstrated end-to-end agent workflow, and independent confirmation the MCP disputes tools work as claimed.

   • [claimed-docs] “[Process Disputes](/docs/disputes-api/process-disputes)”
   • [claimed-docs] “Disputes API”
   • [claimed-docs] “[Test in the Sandbox](/docs/disputes-api/sandbox-testing)”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”

   proof ↗⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

Disputes

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

   weight 3 · round to Square
   Square~partialclaimed6/10

   Square documents a dedicated Disputes API with a 'Process Disputes' guide and sandbox testing support, indicating sellers/developers can submit evidence and interact with dispute records programmatically. However, the evidence pack lacks detail on structured evidence-submission fields, dispute status/lifecycle event types, or webhook notifications specific to dispute state changes, and marketing copy suggests Square often manages the dispute process on the seller's behalf rather than the user actively tracking it end-to-end. Missing for 10: detailed evidence-field schema, dispute status/lifecycle event documentation, and independent confirmation of end-to-end resolution tracking.

   • [claimed-docs] “[Process Disputes](/docs/disputes-api/process-disputes)”
   • [claimed-docs] “[Test in the Sandbox](/docs/disputes-api/sandbox-testing)”
   • [claimed-docs] “Disputes API”
   • [claimed-docs] “With no chargeback fees, we save you money and time by managing the credit card dispute process for you.”

   proof ↗⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

Fraud prevention

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

   weight 3 · round to Square
   Square~partialclaimed5/10

   Square's marketing docs explicitly claim ML-based fraud blocking and custom rules and alerts to manage risk, matching the story's core ask, but this is a single marketing page with no API or developer documentation detailing how block, review, and allow rules are configured or how fraud scores are surfaced to finance-ops users. missing for 10: developer-facing API/dashboard docs for configuring block vs review vs allow rules, detail on the fraud-score output format, independent or hands-on corroboration of the ML scoring and rule engine.

   • [claimed-docs] “Prevent loss online. Get insights into payment fraud patterns, and set custom rules and alerts to manage risk.”
   • [claimed-docs] “Square uses sophisticated machine learning to spot and block payment fraud at no extra cost.”

   proof ↗⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

Refunds

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

   weight 3 · round to Square
   Square~partialclaimed7/10

   Square documents a dedicated Refunds API supporting both linked and unlinked refunds (full/partial refunds for existing or off-platform payments), which covers the API side, and the dashboard is implied via the broader Square seller product but not explicitly documented for refund issuance in the evidence pack. missing for 10: explicit dashboard UI documentation/screenshots showing refund issuance from the Seller Dashboard, and confirmation of partial-amount refund support in docs text.

   • [claimed-docs] “[Refund Payments](/docs/payments-api/refund-payments)”
   • [claimed-docs] “[Process an Unlinked Refund](/docs/refunds-api/unlinked-refunds)”
   • [claimed-docs] “Refund Payments”

   proof ↗⚑ flag

   Paddle~partialclaimed4/10

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

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

   proof ↗⚑ flag

Multi currency

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

   weight 2 · round to Paddle
   Square—none0/10

   The evidence pack contains no mention of multi-currency charging, FX conversion, or cross-currency settlement anywhere in Square's docs, GraphQL/REST APIs, MCP server, or payments pages — all payment method docs (cards, ACH, Afterpay, Cash App) are silent on currency handling. This is a fair axis for a payments platform, so absence of evidence yields none rather than na.

   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “[ACH Bank Transfer Payment](/docs/payments-api/take-payments/ach-payments)”
   • [claimed-docs] “[Afterpay and Clearpay Payments](/docs/payments-api/take-payments/afterpay-payments)”
   • [claimed-docs] “[Cash App Payments](/docs/payments-api/take-payments/cash-app-payments)”
   • [claimed-docs] “Payouts API”
   • [claimed-docs] “Take payments in person and online. Securely save recurring payment methods. Easily sync sales, inventory, and customer data with your Squ…”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Tax

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

   weight 3 · round to Paddle
   Square—none0/10

   The evidence pack covers payments, refunds, disputes, webhooks, invoices, and MCP tooling but contains no mention of tax calculation, tax rates, VAT/GST handling, or automated tax collection features.

   ⚑ flag

   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

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

   weight 2 · round to Square
   Square~partialclaimed7/10

   Square's developer platform exposes an extensive set of APIs (payments, refunds, disputes, invoices, subscriptions, payouts, webhooks, OAuth, GraphQL, catalog/customers/orders/inventory/labor) plus an MCP server giving 'programmatic access to everything the APIs offer', suggesting broad UI/API parity for core commerce and back-office functions. However, some UI-only surfaces (e.g., the in-product Square AI seller assistant, POS idle-screen customization, dashboard reporting UI) are not shown to have full API equivalents, and there is no explicit vendor or independent claim of 100% UI-API parity. missing for 10: an explicit parity statement or audit confirming every UI feature (e.g., Square AI insights, POS-specific dashboard views) is fully API-accessible, and independent/hands-on verification of edge-case coverage.

   • [claimed-docs] “Payouts API”
   • [claimed-docs] “Invoices API”
   • [claimed-docs] “Subscriptions API”
   • [claimed-docs] “Disputes API”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “One GraphQL query can retrieve data that requires multiple Square API calls.”
   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Square—none0/10

   Square's docs describe extensive APIs to create/read individual objects (payments, customers, orders, catalog) and even an MCP/GraphQL layer, but there is no evidence of a bulk data-export feature, standard open-format export (CSV/JSON dump), or documented account-closure/data-portability process letting a user take all their data and leave.

   ⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

Ai reconciliation

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

   weight 3 · round to Paddle
   Square~partialclaimed5/10

   Square has a documented Payouts API and API access (via SDK, MCP server, GraphQL, webhooks) that an agent could use to pull payout and balance-transaction data programmatically, and payments/refunds/disputes APIs provide the underlying charge data needed for reconciliation. However, there is no direct evidence of a balance-transactions endpoint equivalent to Stripe's, nor documentation showing how payout line items map to underlying charges/fees for reconciliation workflows. missing for 10: explicit balance-transaction/payout-entries API detail, worked reconciliation example or docs linking deposits to charges, independent/hands-on confirmation of this specific workflow.

   • [claimed-docs] “Payouts API”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “One GraphQL query can retrieve data that requires multiple Square API calls.”
   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”

   proof ↗⚑ flag

   Paddle✓fullclaimed7/10

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

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

   proof ↗⚑ flag

Payouts

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

   weight 2 · round to Paddle
   Square~partialclaimed4/10

   Square exposes a Payouts API (square-docs-17) which presumably supports payout schedule and reconciliation data, but the evidence pack gives no detail on schedule controls (e.g., daily/weekly/manual), nor on how payouts break down into constituent charges, fees, and refunds. missing for 10: documentation of payout schedule configuration options, payout entries/line-item breakdown by charge/fee/refund, and any independent/hands-on confirmation of reconciliation accuracy.

   • [claimed-docs] “Payouts API”
   • [claimed-docs] “[Refund Payments](/docs/payments-api/refund-payments)”
   • [claimed-docs] “[Process an Unlinked Refund](/docs/refunds-api/unlinked-refunds)”

   proof ↗⚑ flag

   Paddle~partialclaimed6/10

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

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

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round to Paddle
   Square~partialclaimed5/10

   Square provides a Payouts API for settlement data and separate Refunds and Disputes APIs, plus marketing copy about seeing 'all your sales in one report' to reduce reconciliation effort, but there's no dedicated documentation showing an itemized report that ties bank deposits to fees, refunds, and chargebacks in one place. missing for 10: explicit itemized payout/settlement report schema breaking down fees, refunds, chargebacks; documentation linking payout amounts directly to bank deposit records; independent confirmation from finance-ops users that reconciliation works end-to-end.

   • [claimed-docs] “Payouts API”
   • [claimed-docs] “[Refund Payments](/docs/payments-api/refund-payments)”
   • [claimed-docs] “[Process Disputes](/docs/disputes-api/process-disputes)”
   • [claimed-docs] “See all your sales in one report. Spend less time reconciling data across payment systems and more time optimizing sales based on your real-…”

   proof ↗⚑ flag

   Paddle✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Marketplace

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

   weight 2 · round to Square
   Square~partialclaimed6/10

   Square provides the core building blocks for a marketplace: OAuth to onboard sellers to their own Square accounts (square-docs-42, square-docs-51), the OAuth access-token scope model (square-supp-oauth-scopes), Payments API with 'Collect Application Fees' for platform fee splitting (square-docs-37), and a Payouts API for disbursing funds to sellers (square-docs-17). However, the evidence never documents a unified 'split payment across multiple parties in one transaction' primitive or destination-account payout routing akin to Stripe Connect transfers—application fees and payouts appear as separate mechanisms rather than an integrated marketplace split-and-payout flow, and there's no dedicated marketplace/platform guide or case study. missing for 10: explicit multi-party split-payment/transfer API documentation, an end-to-end marketplace onboarding+split+payout guide, and independent/hands-on validation that this pattern works in production.

   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”
   • [claimed-docs] “multi-tenant applications that serve multiple sellers should use OAuth access tokens”
   • [claimed-docs] “Square access is scope-controlled: "Access tokens are credentials that allow applications to securely interact with Square APIs. An access t…”
   • [claimed-docs] “Collect Application Fees”
   • [claimed-docs] “Payouts API”
   • [claimed-docs] “For custom integrations that only access your own Square account, personal access tokens are suitable for production use.”

   proof ↗⚑ flag

   Paddle—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Square—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or geographic control over where Square account/API data is stored; the pack covers payments features, MCP/AI tooling, and dev tools but never addresses data residency.

   ⚑ flag

   Paddle—none0/10

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

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Square—none0/10

   No evidence in the pack addresses data retention policies, data deletion capabilities, or privacy controls for AI/MCP interactions with Square data. While OAuth scopes and access-token controls are documented, nothing speaks to retaining or deleting data collected via AI tools or the MCP server.

   ⚑ flag

   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