PayPal vs Square

Agent access

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

   weight 2 · round drawn
   PayPal✓fullprobed9/10

   Direct probe confirms a live llms.txt at developer.paypal.com/llms.txt (HTTP 200) plus .md-suffixed docs pages (e.g., api/rest.md) that agents can fetch directly, exactly matching the agent-oriented docs pattern. This is corroborated by extensive first-party agent tooling (MCP server, agent toolkit) showing PayPal actively supports agent-native consumption of its docs/APIs. Missing for 10: no independent/community verification of an agent actually using llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.paypal.com/llms.txt # PayPal Developer Documentation > PayPal's developer documentation for i…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.paypal.com/api/rest.md # Get started with PayPal REST APIs (/api/rest) Get started with PayPal…”
   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   PayPal✓fullclaimed7/10

   PayPal's core developer experience is API-first: OAuth client-credentials tokens authenticate calls without a UI, REST APIs cover orders/payments/subscriptions/invoicing/payouts, webhooks provide event-driven automation, and a sandbox environment exists for automated testing — all of which support headless/CI usage. missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions integration), and independent hands-on confirmation of running PayPal API calls in a CI environment.

   • [claimed-docs] “Exchange your client ID and client secret for an access token. The access token authenticates your app when calling PayPal REST APIs.”
   • [claimed-docs] “Exchange your client ID and client secret for an access token.”
   • [claimed-docs] “Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.”
   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The initial setup for receiving webhooks is to subscribe a listening URL for a specific app”
   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks... to integrate with PayPal APIs through function calling.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   PayPal✓fullprobed9/10

   PayPal ships a well-documented official MCP server in both local (npx @paypal/mcp) and remote hosted forms (mcp.sandbox.paypal.com / mcp.paypal.com) with SSE and Streamable HTTP transports, OAuth-based auth, and a broad tool inventory (orders, invoices, subscriptions, disputes, catalog, insights) usable from any MCP client; docs also confirm support for Anthropic/OpenAI LLMs. Missing for 10: independent/community hands-on validation of the MCP server itself (only vendor docs cited).

   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients.”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “"PayPal recently launched a Model Context Protocol (MCP) server that customers can use to access the power of PayPal using natural language …”
   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”
   • [probe] “official MCP server documented at https://developer.paypal.com/ai-tools/mcp-server”

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round drawn
   PayPal—none0/10

   Evidence covers PayPal's REST APIs, SDKs, MCP server, and agent toolkit, but no official CLI tool is mentioned anywhere in the docs or GitHub references. Missing for 10: any documented PayPal CLI, command-line tool, or terminal-based interface for developers/agents.

   ⚑ flag

   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

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

   weight 3 · round drawn
   PayPal✓fullclaimed9/10

   PayPal has extensive, well-documented public REST APIs (OAuth token exchange, checkout, subscriptions, invoicing, payouts, disputes, webhooks) plus an OpenAPI spec/codegen tooling and a sandbox environment, all directly consumable by an AI-native user or agent. It also ships an official MCP server (local and remote), an agent toolkit for LangChain/CrewAI/OpenAI Agents SDK/Bedrock, and documented agentic commerce protocols (ACP/UCP), showing the API is explicitly built for agent-driven use. Missing for 10: independent/third-party developer corroboration of API reliability or friction beyond PayPal's own docs.

   • [claimed-docs] “Exchange your client ID and client secret for an access token. The access token authenticates your app when calling PayPal REST APIs.”
   • [claimed-docs] “Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.”
   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks... to integrate with PayPal APIs through function calling.”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Square
   PayPal—none0/10

   Evidence shows only standard OAuth client-credentials token exchange (client ID/secret → access token) and general agent-toolkit/MCP integration, but nothing documenting scoped, restricted, or least-privilege credential issuance specifically for agent use (e.g., limited-permission API keys, granular scopes, or per-agent restricted tokens).

   • [claimed-docs] “Exchange your client ID and client secret for an access token. The access token authenticates your app when calling PayPal REST APIs.”
   • [claimed-docs] “Exchange your client ID and client secret for an access token.”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”
   • [claimed-docs] “"PayPal recently launched a Model Context Protocol (MCP) server that customers can use to access the power of PayPal using natural language …”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   PayPal✓fullclaimed8/10

   PayPal ships official REST API SDKs, OpenAPI specs with codegen, and a dedicated open-source Agent Toolkit (GitHub) supporting LangChain, OpenAI Agents SDK, CrewAI, Vercel AI SDK, Bedrock, and MCP for building AI-native payment workflows, backed by sandbox testing and detailed tool docs. Missing for 10: independent/hands-on developer corroboration of SDK quality beyond first-party docs and GitHub README.

   • [github] “The PayPal Agent Toolkit enables popular agent frameworks... to integrate with PayPal APIs through function calling.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks including OpenAI's Agent SDK, LangChain, Vercel's AI SDK, and Model Context Protoc…”
   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.”
   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [claimed-docs] “npm run codegen-java -- openapi/checkout_orders_v2.json --artifact-id orders”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   PayPal✓fullclaimed8/10

   PayPal's REST API documents webhooks as HTTPS posts to a subscribed endpoint whenever a specified event occurs, with a clear subscription setup flow (paypal-docs-9, paypal-docs-28). This is a standard developer-facing capability well documented for programmatic/agentic integration. Missing for 10: no independent/hands-on corroboration of webhook reliability or delivery guarantees, and no explicit mention of AI-agent-specific webhook consumption patterns.

   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The initial setup for receiving webhooks is to subscribe a listening URL for a specific app”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Square
   PayPal~partialclaimed4/10

   PayPal's agent toolkit exposes a `get_merchant_insights` tool that retrieves 'business intelligence metrics and analytics for a merchant' filtered by date/type/interval, which could power AI-generated insights — but this is a data-retrieval function for external AI agents to call via the toolkit/MCP, not a native in-product AI feature that surfaces insights or suggestions directly inside PayPal's own dashboard to end users. Missing for 10: evidence of a first-party AI assistant embedded in PayPal's UI/dashboard that proactively generates insights or suggestions, and independent/hands-on confirmation of such a feature in use.

   • [claimed-docs] “Agents can pull business analytics through a dedicated tool: `get_merchant_insights` — "Retrieve business intelligence metrics and analytics…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   PayPal~partialclaimed7/10

   PayPal ships several building blocks for background automation: webhooks that fire automatically on events, subscriptions with autonomous recurring billing and automated failed-payment recovery, batch payouts, an automatable Disputes API, and an Agent Toolkit/MCP server that lets developers build AI agents to execute payment workflows (create orders, invoices, subscriptions, refunds) via function calling. However, these are separate mechanisms rather than a unified 'set up an automation that runs autonomously in the background' feature, and there's no evidence of PayPal hosting persistent scheduled/cron-style agent tasks — the agent toolkit requires the user's own agent runtime to invoke tools. Missing for 10: a dedicated scheduling/trigger-based automation builder, evidence of PayPal-hosted persistent agent execution, and independent/hands-on confirmation that autonomous background workflows actually run unattended.

   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The initial setup for receiving webhooks is to subscribe a listening URL for a specific app”
   • [claimed-docs] “You can customize a subscriptions integration to: Create plans that charge users a fixed amount at regular intervals or a variable amount ba…”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies.”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks... to integrate with PayPal APIs through function calling.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks including OpenAI's Agent SDK, LangChain, Vercel's AI SDK, and Model Context Protoc…”
   • [claimed-docs] “Build custom agents: Create AI agents that handle payment workflows and customer interactions using the agent toolkit quickstart guide.”
   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Square
   PayPal—none0/10

   The story asks for a built-in AI assistant inside the PayPal product itself that an end-user can delegate tasks to (e.g., 'pay this invoice', 'check my balance' via a native PayPal chat assistant). All AI-related evidence describes the reverse: PayPal exposing an MCP server/agent toolkit so *external* AI agents (Claude, ChatGPT, LangChain, etc.) can call PayPal's APIs, or enabling other platforms' shopping assistants (ChatGPT, Gemini) to check out via PayPal/Braintree. There is no evidence of a native, built-in assistant surfaced inside the PayPal app/website that a user converses with to delegate PayPal tasks. Missing for 10: any documented in-product PayPal assistant/chatbot for end-users, evidence of natural-language task delegation within the PayPal UI itself, and confirmation this isn't just developer-facing agent tooling.

   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients.”
   • [claimed-docs] “Build custom agents: Create AI agents that handle payment workflows and customer interactions using the agent toolkit quickstart guide.”
   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”
   • [claimed-docs] “"Merchants can use PayPal's agentic commerce services to create AI-powered shopping experiences, so customers can shop using everyday langua…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   PayPal✓fullclaimed8/10

   PayPal ships an official MCP server (local and remote) plus an Agent Toolkit supporting multiple agent frameworks, letting users/agents issue natural-language commands to create orders, invoices, subscriptions, refunds, and get merchant insights, and also supports agentic commerce protocols (ACP/UCP) for conversational checkout. missing for 10: independent/hands-on user reports confirming reliability of natural-language command execution, and some commerce tools are gated behind access requests or feature flags (gift-cards-only, limited to US physical goods).

   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks... to integrate with PayPal APIs through function calling.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks including OpenAI's Agent SDK, LangChain, Vercel's AI SDK, and Model Context Protoc…”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “"PayPal recently launched a Model Context Protocol (MCP) server that customers can use to access the power of PayPal using natural language …”
   • [claimed-docs] “"Merchants can use PayPal's agentic commerce services to create AI-powered shopping experiences, so customers can shop using everyday langua…”
   • [claimed-docs] “Store Sync "connects your product catalog and commerce API with PayPal's agentic commerce services, enabling AI agents to discover your prod…”
   • [claimed-docs] “PayPal's remote MCP server now supports large language models (LLMs) from Anthropic and OpenAI, which brings even greater flexibility.”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to Square
   PayPal~partialclaimed5/10

   PayPal's docs let you generate client code and import OpenAPI specs, and Braintree's GraphQL developer hub explicitly offers 'an in-browser API Explorer for testing queries' with runnable example integrations — concrete evidence of an interactive, runnable API reference for at least one product line. However, no evidence shows an equivalent try-it-now/runnable console for the core PayPal REST APIs (orders, checkout, subscriptions, etc.) themselves. Missing for 10: in-browser runnable examples for the main REST API reference, independent/hands-on confirmation of the interactive experience quality.

   • [claimed-docs] “Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.”
   • [claimed-docs] “npm run codegen-java -- openapi/checkout_orders_v2.json --artifact-id orders”
   • [claimed-docs] “Braintree (PayPal's gateway) exposes a first-class GraphQL API — "Resources and tools to integrate with Braintree's GraphQL API" — with guid…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   PayPal✓fullclaimed9/10

   PayPal explicitly documents downloadable/importable OpenAPI specs: 'Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools' and provides a GitHub repo (paypal-rest-api-specifications) with actual OpenAPI JSON files used for codegen. Missing for 10: no independent third-party confirmation of spec completeness/versioning outside PayPal's own repo.

   • [claimed-docs] “Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.”
   • [claimed-docs] “npm run codegen-java -- openapi/checkout_orders_v2.json --artifact-id orders”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   PayPal✓fullclaimed8/10

   PayPal documents a dedicated sandbox as 'a self-contained, virtual testing environment that simulates the live PayPal production environment' (paypal-docs-11), and the agent toolkit explicitly instructs AI-native builders to 'Always use the sandbox environment for initial testing to avoid real transactions' (paypal-supp-toolkit-frameworks), with both local and remote MCP servers supporting PAYPAL_ENVIRONMENT=SANDBOX and a distinct sandbox endpoint (mcp.sandbox.paypal.com) separate from production (paypal-supp-remote-mcp). missing for 10: independent/hands-on confirmation that sandbox behavior fully mirrors production for agentic/AI workflows, and more detail on how sandbox data isolation is verified beyond vendor docs.

   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “PayPal ships BOTH deployment modes of its MCP server: local via `npx -y @paypal/mcp --tools=all` (PAYPAL_ACCESS_TOKEN + PAYPAL_ENVIRONMENT=S…”
   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Square
   PayPal—none0/10

   Evidence shows PayPal APIs use version numbers (e.g., 'checkout_orders_v2.json') and OpenAPI specs, but no evidence pack item documents a formal deprecation policy, sunset timeline, or versioning support commitment that an AI-native integrator could rely on.

   • [claimed-docs] “npm run codegen-java -- openapi/checkout_orders_v2.json --artifact-id orders”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   PayPal~partialclaimed6/10

   PayPal's Payouts API explicitly supports true bulk operations — sending money to 'thousands of recipients at once' via email, phone, or PayPal ID in a single batch call — which is a strong general REST-API bulk capability accessible to automation. However, the AI-agent-specific surface (MCP server / Agent Toolkit tool inventory) exposes only single-item tools (create_order, get_invoice, list_transaction, etc.) with no documented batch/bulk tool for an AI agent to invoke across many items at once. Missing for 10: an AI-native (MCP/agent-toolkit) tool that explicitly performs bulk/batch actions, and any hands-on evidence of an agent successfully driving the Payouts batch API end-to-end.

   • [claimed-docs] “Send money immediately to multiple recipients with their emails, phone numbers, or PayPal IDs.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies... A basic solution for sending batch paym…”
   • [claimed-docs] “A basic solution for sending batch payments using recipients' email addresses, phone numbers, or PayPal IDs.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   PayPal~partialclaimed4/10

   PayPal exposes webhooks that fire on transaction/dispute/subscription events (paypal-docs-9, paypal-docs-28) and has some built-in automated behaviors like automated payment recovery for failed subscriptions (paypal-docs-40) and a Disputes API for automating dispute actions (paypal-docs-26), which together give developers the raw event/trigger primitives needed to build 'if event then action' automation. However, there is no evidence of a declarative rules interface where an AI-native user defines conditions and actions without writing custom server-side handling code — webhooks require the developer to build the listener and action logic themselves. Missing for 10: a no-code/low-code rule-definition UI or API, support for arbitrary conditional logic across events, and evidence that AI agents can create/manage such rules via the MCP/agent toolkit (which only exposes discrete action tools, not rule/trigger definitions).

   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The initial setup for receiving webhooks is to subscribe a listening URL for a specific app”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”
   • [claimed-docs] “You can customize a subscriptions integration to: Create plans that charge users a fixed amount at regular intervals or a variable amount ba…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to PayPal
   PayPal~partialclaimed5/10

   PayPal's Subscriptions API lets merchants (and, via the documented agent-toolkit, AI agents) create/update/cancel recurring billing plans with fixed intervals, trials, and automated payment recovery, which is a form of 'recurring job' automation exposed to AI-native tooling. However this is scoped strictly to billing/payment cycles, not a general-purpose scheduler for arbitrary recurring workflows or tasks that an AI agent could set up and manage. Missing for 10: a generic workflow/job scheduling primitive (e.g., cron-like triggers, scheduled webhooks, or task orchestration) beyond subscription billing, and independent evidence of AI agents actually using this to schedule non-payment workflows.

   • [claimed-docs] “Create plans that charge users a fixed amount at regular intervals or a variable amount based on the number of users subscribed.”
   • [claimed-docs] “You can customize a subscriptions integration to: Create plans that charge users a fixed amount at regular intervals or a variable amount ba…”
   • [claimed-docs] “Create customizable PayPal subscription plans for regular billing, offering trials, upgrades, and automated payment recovery for flexible cu…”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”

   proof ↗⚑ flag

   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

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

   PayPal's subscriptions API documents 'Automate payment recovery for failed payments' (dunning) and webhooks can notify apps of billing failures, and the agent-toolkit/MCP tools expose subscription and invoice management functions an agent could call. However, there's no documented dedicated 'failed payment' webhook-driven retry workflow guide, no specific dunning/outreach tooling in the agent-tools inventory (only generic subscription create/update/cancel), and no evidence of an agent specifically monitoring failed payments end-to-end. missing for 10: explicit failed-payment webhook event documentation, a dedicated retry/dunning API or agent tool, and a concrete example of an agent autonomously handling failed payment recovery.

   • [claimed-docs] “You can customize a subscriptions integration to: Create plans that charge users a fixed amount at regular intervals or a variable amount ba…”
   • [claimed-docs] “Create customizable PayPal subscription plans for regular billing, offering trials, upgrades, and automated payment recovery for flexible cu…”
   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The initial setup for receiving webhooks is to subscribe a listening URL for a specific app”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks... to integrate with PayPal APIs through function calling.”

   proof ↗⚑ flag

   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

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

   PayPal's agent-toolkit/MCP tool inventory explicitly includes create_product, and subscription/plan creation tools (create plan, create_order/pay_order) plus payment-link style checkout order creation, all callable via API/function-calling in one agent session with sandbox testing supported. missing for 10: no single documented end-to-end walkthrough showing product+price+payment-link created in one session, and no independent/hands-on report confirming this exact multi-step flow works in practice.

   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “create_product: Create a new product in the PayPal catalog.”
   • [claimed-docs] “`create_product`: Create a new product in the PayPal catalog.”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “Create plans that charge users a fixed amount at regular intervals or a variable amount based on the number of users subscribed.”
   • [claimed-docs] “Swiftly create a Payment Link to share on your website, via email, on social media, or through text. No coding skills required.”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks including OpenAI's Agent SDK, LangChain, Vercel's AI SDK, and Model Context Protoc…”

   proof ↗⚑ flag

   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

Invoicing

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

   weight 2 · round to PayPal
   PayPal✓fullclaimed8/10

   PayPal Invoicing API/product explicitly supports creating, sending, and managing hosted invoices with a secure payment page, branding, and automatic payment reminders (paypal-docs-4, paypal-docs-22, paypal-docs-50), and the agent-tools inventory confirms send_invoice and send_invoice_reminder tools. missing for 10: independent/hands-on corroboration of reminder cadence/customization and no third-party review confirming real-world reliability of the reminder feature.

   • [claimed-docs] “The Invoicing REST API helps you create, update, send, and manage invoices programmatically from your backend systems.”
   • [claimed-docs] “PayPal Invoicing lets merchants and partners create and send itemized invoices and get paid through a secure PayPal payment page, without bu…”
   • [claimed-docs] “Customization | Invoice branding and business details.”
   • [claimed-docs] “Merchants can share invoices via a secure URL, merchant-branded email, or scannable QR code, and configure automatic payment reminders.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”

   proof ↗⚑ flag

   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

Subscriptions

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

   weight 2 · round to PayPal
   PayPal~partialclaimed5/10

   PayPal's Subscriptions docs explicitly list 'Automate payment recovery for failed payments' as a built-in capability, directly matching the dunning/retry story, but the evidence is a single bullet point with no detail on retry schedules, dunning logic, or recovery email customization/branding. Invoicing docs also mention 'automatic payment reminders' but that's for invoices, not subscription dunning specifically. missing for 10: detailed documentation of retry cadence/logic, evidence of customizable recovery email templates, and independent/hands-on confirmation that dunning actually reduces churn.

   • [claimed-docs] “You can customize a subscriptions integration to: Create plans that charge users a fixed amount at regular intervals or a variable amount ba…”
   • [claimed-docs] “Create customizable PayPal subscription plans for regular billing, offering trials, upgrades, and automated payment recovery for flexible cu…”
   • [claimed-docs] “Merchants can share invoices via a secure URL, merchant-branded email, or scannable QR code, and configure automatic payment reminders.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to PayPal
   PayPal✓fullclaimed9/10

   PayPal's Subscriptions API docs explicitly cover creating fixed/variable billing plans, free/discounted trials, upgrade/downgrade of plans, and automated payment recovery for failed payments — covering plans, trials, upgrades and proration-like variable billing. Dashboard management and REST API integration paths are both documented. Missing for 10: no independent/hands-on third-party corroboration of proration mechanics or edge-case billing behavior.

   • [claimed-docs] “Offer your subscribers free or discounted trials... Enable subscribers to upgrade or downgrade their plans.”
   • [claimed-docs] “Create plans that charge users a fixed amount at regular intervals or a variable amount based on the number of users subscribed.”
   • [claimed-docs] “Offer your subscribers free or discounted trials.”
   • [claimed-docs] “You can customize a subscriptions integration to: Create plans that charge users a fixed amount at regular intervals or a variable amount ba…”
   • [claimed-docs] “Create customizable PayPal subscription plans for regular billing, offering trials, upgrades, and automated payment recovery for flexible cu…”
   • [claimed-docs] “Manage Subscriptions on your account dashboard... Recommended if you don't need to integrate Subscriptions into your product UI.”
   • [claimed-docs] “Manage Subscriptions on your account dashboard - Recommended if you don't need to integrate Subscriptions into your product UI.”

   proof ↗⚑ flag

   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

Card acceptance

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

   weight 3 · round drawn
   PayPal✓fullcommunity7/10

   PayPal explicitly markets no-code, fast paths to accept card payments — Payment Links ('swiftly create... no coding skills required'), PayPal Checkout buttons, and card field support — alongside sandbox testing and REST APIs for those wanting custom integration, all consistent with a founder starting to accept card payments quickly after signup. No independent hands-on report confirms the exact 'within a day' timeline, and community threads flag post-signup fund holds/verification friction that could affect real-world speed, though none concretely refute the initial-setup speed claim. Missing for 10: independent/hands-on confirmation of same-day account approval and first live transaction, and documentation of KYC/verification turnaround times.

   • [claimed-docs] “Swiftly create a Payment Link to share on your website, via email, on social media, or through text. No coding skills required.”
   • [claimed-docs] “Offer up to 400M users1 the choice to pay with PayPal, Venmo, Pay Later, debit and credit cards, and more.”
   • [claimed-docs] “Accept PayPal payments on your website. Customers can select the PayPal button on your site and pay with any funding source linked to their …”
   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [claimed-docs] “Automatically recognize guest shoppers with Fastlane by PayPal. Next time they shop, we’ll autofill their checkout credentials.”
   • [community] “After two eBay/PayPal sales cycles, PayPal emailed: 'money from payments you receive will be placed in a pending balance for up to 21 days..…”

   proof ↗⚑ flag

   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

Checkout surfaces

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

   weight 3 · round to Square
   PayPal~partialclaimed6/10

   PayPal Checkout docs confirm embeddable buttons and card fields ('card field customization with your business branding') plus server-side endpoints for refunds/voids/captures, allowing developers to embed payment UI without full redirect to a hosted PayPal page. However, evidence leans heavily on button/card-field embedding rather than deep low-level UI customization (e.g., fully styled custom checkout forms), and PayPal's classic checkout flow still often redirects/pops up an approval window rather than a fully inline, brandless flow. missing for 10: detailed documentation on styling/theming APIs for embedded components, independent/hands-on confirmation that redirect can be fully eliminated, and clarity on which products (Checkout vs Braintree) offer the most customizable embedded UI.

   • [claimed-docs] “Customers can select the PayPal button on your site and pay with any funding source linked to their PayPal account.”
   • [claimed-docs] “Accept PayPal payments on your website. Customers can select the PayPal button on your site and pay with any funding source linked to their …”
   • [claimed-docs] “Expanded Checkout includes all offerings from PayPal Checkout and card field customization with your business branding.”
   • [claimed-docs] “Add server-side endpoints to handle refunds, voids, delayed captures, and specialized checkout flows.”
   • [claimed-docs] “Delay capture (/checkout/delay-capture): Charge after service delivery.”
   • [claimed-docs] “Void an authorization (/checkout/void-authorized-payment): Cancel holds before charging.”
   • [claimed-docs] “Automatically recognize guest shoppers with Fastlane by PayPal. Next time they shop, we’ll autofill their checkout credentials.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to PayPal
   PayPal✓fullclaimed9/10

   PayPal Checkout provides a hosted PayPal button/payment page where customers pay via their PayPal-linked funding sources, and Invoicing explicitly offers 'a secure PayPal payment page, without building their own payment flow' — both are vendor-hosted, conversion-optimized checkout surfaces requiring only redirect/embed integration plus server-side endpoints for capture/void/refund. Missing for 10: no independent conversion-rate benchmarking or hands-on developer review confirming the 'conversion-optimized' claim beyond PayPal's own marketing copy.

   • [claimed-docs] “Customers can select the PayPal button on your site and pay with any funding source linked to their PayPal account.”
   • [claimed-docs] “Accept PayPal payments on your website. Customers can select the PayPal button on your site and pay with any funding source linked to their …”
   • [claimed-docs] “Add server-side endpoints to handle refunds, voids, delayed captures, and specialized checkout flows.”
   • [claimed-docs] “PayPal Invoicing lets merchants and partners create and send itemized invoices and get paid through a secure PayPal payment page, without bu…”
   • [claimed-docs] “Automatically recognize guest shoppers with Fastlane by PayPal. Next time they shop, we’ll autofill their checkout credentials.”
   • [claimed-docs] “Delay capture (/checkout/delay-capture): Charge after service delivery.”
   • [claimed-docs] “Void an authorization (/checkout/void-authorized-payment): Cancel holds before charging.”

   proof ↗⚑ flag

   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

No code selling

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

   weight 2 · round to PayPal
   PayPal✓fullclaimed9/10

   PayPal's business site directly documents no-code Payment Links: 'Swiftly create a Payment Link to share on your website, via email, on social media, or through text. No coding skills required,' alongside broad acceptance of PayPal, Venmo, cards, and Pay Later. This directly matches the founder story of creating a shareable link with no code and selling immediately. Missing for 10: independent hands-on confirmation of the payment-link creation flow beyond vendor docs.

   • [claimed-docs] “Swiftly create a Payment Link to share on your website, via email, on social media, or through text. No coding skills required.”
   • [claimed-docs] “Offer up to 400M users1 the choice to pay with PayPal, Venmo, Pay Later, debit and credit cards, and more.”
   • [claimed-docs] “PayPal Open helps you accept payments online, in person, and on the go.”

   proof ↗⚑ flag

   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

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

   PayPal Checkout explicitly bundles wallet funding sources (any linked PayPal funding source), Pay in 4 BNPL, and in-store tap-to-pay with Apple Pay/Google Pay/Samsung Pay via a single PayPal Open/Checkout integration, plus Expanded Checkout adds card fields and branding under the same account. This covers wallets, BNPL, and digital wallet acceptance from one integration, though bank redirect methods (e.g., iDEAL, SEPA, giropay) and full country-by-country local payment method coverage aren't explicitly enumerated in evidence. missing for 10: explicit documentation of bank-redirect/local APM coverage (iDEAL, SOFORT, giropay, etc.) and confirmation these are enabled via the same single API call without extra per-method integration work.

   • [claimed-docs] “Customers can select the PayPal button on your site and pay with any funding source linked to their PayPal account.”
   • [claimed-docs] “Pay in 4 interest-free payments. Paid every two weeks. No late fees. Won't affect your credit score to apply.”
   • [claimed-docs] “Expanded Checkout includes all offerings from PayPal Checkout and card field customization with your business branding.”
   • [claimed-docs] “Offer up to 400M users1 the choice to pay with PayPal, Venmo, Pay Later, debit and credit cards, and more.”
   • [claimed-docs] “Use your phone and our PayPal app to take contactless cards and digital wallet payments including Apple Pay®, Google Pay, and Samsung Pay.”
   • [claimed-docs] “Accept PayPal payments on your website. Customers can select the PayPal button on your site and pay with any funding source linked to their …”
   • [claimed-docs] “PayPal Open helps you accept payments online, in person, and on the go. Wherever you do business.”

   proof ↗⚑ flag

   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

Pci compliance

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

   weight 2 · round drawn
   PayPal~partialclaimed5/10

   PayPal's hosted checkout button and 'card field customization' checkout (paypal-docs-2, paypal-docs-27) plus Braintree's GraphQL 'Vault a payment method' (paypal-supp-braintree-graphql) imply that raw card data can be tokenized/hosted rather than touching merchant servers, and server-side endpoints only handle refunds/captures rather than card numbers (paypal-docs-19). However, none of the evidence explicitly states PCI DSS scope reduction, SAQ-A eligibility, or a formal compliance statement. Missing for 10: explicit PCI DSS/SAQ-A documentation, third-party compliance audit or certification evidence, and confirmation that card fields are always iframe-hosted (vs. merchant-collected) across all checkout flows.

   • [claimed-docs] “Customers can select the PayPal button on your site and pay with any funding source linked to their PayPal account.”
   • [claimed-docs] “Expanded Checkout includes all offerings from PayPal Checkout and card field customization with your business branding.”
   • [claimed-docs] “Add server-side endpoints to handle refunds, voids, delayed captures, and specialized checkout flows.”
   • [claimed-docs] “Braintree (PayPal's gateway) exposes a first-class GraphQL API — "Resources and tools to integrate with Braintree's GraphQL API" — with guid…”

   proof ↗⚑ flag

   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

Integration reliability

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

   weight 2 · round to Square
   PayPal—none0/10

   No evidence pack item mentions idempotency keys, PayPal-Request-Id header, or any mechanism for safely retrying API requests to prevent duplicate charges, despite extensive docs on REST API auth, checkout, webhooks, and MCP tools.

   ⚑ flag

   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

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

   PayPal documents basic webhooks (HTTPS POSTs to a subscribed endpoint) but the evidence pack contains no mention of signature verification/signing, automatic retry behavior, an event log/dashboard, or a replay/redelivery mechanism. Missing for 10: documented webhook signature verification, retry policy details, event log/dashboard access, and replay/resend capability.

   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The initial setup for receiving webhooks is to subscribe a listening URL for a specific app”

   proof ↗⚑ flag

   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

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

   PayPal's dev docs cover the core building blocks needed for a checkout integration—OAuth token exchange, the Checkout REST flow, webhooks, and a sandbox test environment—plus a mention of generating client code for multiple languages and per-language SDK codegen (Java example shown). However, the evidence pack doesn't show concrete copy-paste code samples in multiple languages (e.g., Node/PHP/Python snippets) nor any independent confirmation that a developer can go from zero to working payment flow in under a day. missing for 10: multi-language copy-paste code snippets, independent time-to-integrate validation, end-to-end quickstart walkthrough evidence.

   • [claimed-docs] “Exchange your client ID and client secret for an access token. The access token authenticates your app when calling PayPal REST APIs.”
   • [claimed-docs] “Customers can select the PayPal button on your site and pay with any funding source linked to their PayPal account.”
   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [claimed-docs] “Explore our REST API descriptions, generate code for your API clients, and import OpenAPI documents into compatible third-party tools.”
   • [claimed-docs] “npm run codegen-java -- openapi/checkout_orders_v2.json --artifact-id orders”
   • [claimed-docs] “Add server-side endpoints to handle refunds, voids, delayed captures, and specialized checkout flows.”

   proof ↗⚑ flag

   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

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

   PayPal documents a dedicated sandbox that 'simulates the live PayPal production environment' (paypal-docs-11), and the agent-toolkit docs explicitly recommend 'Always use the sandbox environment for initial testing' with a PAYPAL_ENVIRONMENT=SANDBOX flag (paypal-supp-toolkit-frameworks), confirming sandbox/production parity for both REST and MCP flows. However, the evidence pack contains no documentation of specific test card numbers or scenario coverage (e.g., simulating declines, chargebacks, or disputes) within the sandbox — only that a live Disputes API and Resolution Center exist for production dispute handling. Missing for 10: documented test card list/scenarios for declines, dispute simulation tooling in sandbox, and independent developer corroboration of sandbox fidelity.

   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Conte…”
   • [claimed-docs] “Automated operations: Scale dispute management, reduce manual effort, and save time with Disputes API that works seamlessly with your existi…”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”

   proof ↗⚑ flag

   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

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

   PayPal's Disputes API and agent-toolkit both document dispute-related tools (list_disputes, get_dispute, accept_dispute_claim) accessible via API/agent frameworks, enabling an agent to retrieve and act on disputes programmatically. However, evidence shows only 'accept_dispute_claim' (resolving in favor of the buyer) as a documented action tool — there's no evidence of a tool for assembling/submitting counter-evidence or contesting a dispute (e.g., uploading evidence documents, filing a merchant-side response) end-to-end via the agent toolkit or MCP. missing for 10: a documented tool/endpoint for submitting evidence or contesting a dispute (not just accepting it), end-to-end automated evidence-assembly workflow, and independent/hands-on confirmation that an agent can fully close the loop on a contested dispute.

   • [claimed-docs] “Automated operations: Scale dispute management, reduce manual effort, and save time with Disputes API that works seamlessly with your existi…”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks including OpenAI's Agent SDK, LangChain, Vercel's AI SDK, and Model Context Protoc…”
   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”

   proof ↗⚑ flag

   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

Disputes

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

   weight 3 · round drawn
   PayPal~partialcommunity6/10

   PayPal documents both a no-code Resolution Center for manually responding to and monitoring disputes and a Disputes API for automating dispute actions (paypal-docs-6/7/25/26), and the agent-toolkit inventory adds list_disputes/get_dispute/accept_dispute_claim tools for programmatic dispute tracking. However, the pack never documents actual structured-evidence submission (e.g., uploading proof of delivery/tracking, evidence codes) as part of the API, and accept_dispute_claim only resolves disputes in the buyer's favor rather than contesting a chargeback. Community reports (paypal-comm-4/5/6/7) describe merchants losing chargebacks despite appeals/evidence and arbitrary outcomes, raising real doubts about resolution reliability though not proving the API/dashboard mechanics themselves fail. missing for 10: explicit evidence-submission/upload API documentation, a documented merchant-side evidence code list, and independent confirmation that submitted evidence measurably improves dispute outcomes.

   • [claimed-docs] “No-code solution: Simplify dispute handling with Resolution Center, a ready-to-use web interface that requires no technical integration.”
   • [claimed-docs] “Automated operations: Scale dispute management, reduce manual effort, and save time with Disputes API that works seamlessly with your existi…”
   • [claimed-docs] “Resolution Center: A web-based dashboard where you can view, monitor, and manually respond to disputes.”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [community] “I'm stuck with $680 in chargebacks on paypal. A buyer used the same bank account for months without issue, then filed a chargeback and someh…”
   • [community] “A scammer bought my Android phone, claimed it was broken, and sent back a different broken phone with the swapped serial sticker. I appealed…”
   • [community] “As a purchaser on Paypal, you only get 45 days after the transaction. We missed the window waiting on a company that never shipped, and PayP…”
   • [community] “PayPal reportedly told a buyer to destroy a $2500 pre-WWII antique violin after deeming it 'counterfeit' in a dispute, despite no clear coun…”

   proof ↗⚑ flag

   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

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

   The evidence pack covers disputes handling (Resolution Center, Disputes API) and general risk/compliance mentions, but there is no documentation of ML-based fraud scoring or a rules engine for finance-ops to write custom block/review/allow rules. Missing for 10: any mention of fraud risk scores, a rules/policy engine, or finance-ops configurable block/review/allow controls.

   • [claimed-docs] “No-code solution: Simplify dispute handling with Resolution Center, a ready-to-use web interface that requires no technical integration.”
   • [claimed-docs] “Automated operations: Scale dispute management, reduce manual effort, and save time with Disputes API that works seamlessly with your existi…”
   • [claimed-docs] “Resolution Center: A web-based dashboard where you can view, monitor, and manually respond to disputes.”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”

   proof ↗⚑ flag

   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

Refunds

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

   weight 3 · round to Square
   PayPal~partialclaimed6/10

   Evidence confirms API-side refund capability (create_refund, get_refund tools; 'Add server-side endpoints to handle refunds, voids, delayed captures') and dashboard-side refund ability ('Merchants can also add tracking, mark shipments, and issue refunds directly in the PayPal business dashboard'), covering both API and dashboard channels. However, there is no explicit documentation of partial vs full refund distinction, no dedicated Refunds API reference page, and community evidence shows disputes/chargeback handling can be inconsistent, though not specifically contradicting refund issuance itself. Missing for 10: explicit partial-refund API documentation/parameters, a dedicated Refunds API reference, and independent/hands-on confirmation of dashboard refund workflow.

   • [claimed-docs] “Add server-side endpoints to handle refunds, voids, delayed captures, and specialized checkout flows.”
   • [claimed-docs] “Merchants can also add tracking, mark shipments, and issue refunds directly in the PayPal business dashboard.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”

   proof ↗⚑ flag

   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

Multi currency

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

   weight 2 · round to PayPal
   PayPal~partialcommunity5/10

   PayPal supports multi-currency transactions (ISO-4217 currency codes, blocking payments in currencies not held, multi-currency payouts) and can accept payments from customers globally, but the evidence pack provides no explicit documentation of automatic FX conversion mechanics, disclosed FX margin/spread, or a transparent rate-and-fee breakdown at settlement — a specific founder concern given community reports of fund holds and account limitations (paypal-comm-3, paypal-comm-8) that could affect predictable settlement. missing for 10: documented FX conversion rate/margin transparency, explicit multi-currency settlement-to-single-bank-account flow, and independent confirmation that FX handling is clear/predictable in practice.

   • [claimed-docs] “To specify currencies in request URI and body parameters, use three-character ISO-4217 codes.”
   • [claimed-docs] “Block or unblock payments sent to you in a currency you don't hold.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies... A basic solution for sending batch paym…”
   • [community] “I advise people not to depend solely on PayPal because of their tendency to freeze funds over nothing.”
   • [community] “After two eBay/PayPal sales cycles, PayPal emailed: 'money from payments you receive will be placed in a pending balance for up to 21 days..…”

   proof ↗⚑ flag

   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

Tax

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

   weight 3 · round drawn
   PayPal—none0/10

   The evidence pack covers currency codes, checkout, invoicing, subscriptions, payouts, disputes, and AI/agent tooling, but contains no mention of automated sales tax, VAT, or GST calculation/collection engines or tax-rate rules per jurisdiction. This is a fair capability to expect from a payments platform serving finance-ops, but no evidence shows PayPal delivers it.

   ⚑ flag

   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

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

   weight 2 · round to Square
   PayPal~partialclaimed6/10

   PayPal documents strong API/UI parity for core merchant flows (checkout, subscriptions, invoicing, payouts, disputes via API vs. Resolution Center, webhooks, platform onboarding) and even an MCP/agent-toolkit layer for natural-language access to many of these (create_order, create_invoice, list_disputes, get_merchant_insights, etc.). However, several consumer-facing PayPal.com UI features (Pay in 4, Savings account APY, debit card cashback, 'pool money' group gifts, Fastlane autofill) have no documented API equivalent, and agentic commerce tools are explicitly gated/limited (e.g., commerce tools 'for gift cards only for now', Store Sync restricted to US physical goods in USD). missing for 10: API parity for consumer money-app features (Pay in 4, Savings, cashback, group pooling), unrestricted access to agentic commerce tools without approval gating.

   • [claimed-docs] “No-code solution: Simplify dispute handling with Resolution Center, a ready-to-use web interface that requires no technical integration.”
   • [claimed-docs] “Automated operations: Scale dispute management, reduce manual effort, and save time with Disputes API that works seamlessly with your existi…”
   • [claimed-docs] “Resolution Center: A web-based dashboard where you can view, monitor, and manually respond to disputes.”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”
   • [claimed-docs] “Manage Subscriptions on your account dashboard... Recommended if you don't need to integrate Subscriptions into your product UI.”
   • [claimed-docs] “Manage Subscriptions on your account dashboard - Recommended if you don't need to integrate Subscriptions into your product UI.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “Agents can pull business analytics through a dedicated tool: `get_merchant_insights` — "Retrieve business intelligence metrics and analytics…”
   • [claimed-docs] “Store Sync "connects your product catalog and commerce API with PayPal's agentic commerce services, enabling AI agents to discover your prod…”
   • [claimed-docs] “"Merchants can use PayPal's agentic commerce services to create AI-powered shopping experiences, so customers can shop using everyday langua…”
   • [claimed-docs] “Get 3.30% APY11 with your PayPal Savings account”
   • [claimed-docs] “Pool money up front for group gifts and more.”
   • [claimed-docs] “Pay in 4 interest-free payments. Paid every two weeks. No late fees. Won't affect your credit score to apply.”
   • [claimed-docs] “Automatically recognize guest shoppers with Fastlane by PayPal. Next time they shop, we’ll autofill their checkout credentials.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   PayPal—none0/10

   No evidence of any user-facing data export feature or open-format data portability tool; PayPal's evidence pack covers APIs, payments, and AI/agent tooling but nothing about exporting a user's own account/transaction data in open formats or account closure/data portability guarantees.

   ⚑ flag

   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

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 drawn
   PayPal~partialclaimed5/10

   PayPal's REST API and agent-toolkit expose transaction/reporting data (list_transaction, get_merchant_insights) and payouts (Payouts API), and the agent-toolkit explicitly advertises access to 'transaction details' for AI agents via function calling, which supports an agent pulling data programmatically. However, there is no evidence of a dedicated payout-item/balance-transaction endpoint or tool that maps bank deposits to underlying charges (no reconciliation-specific tool, no balance-transaction-to-deposit linkage documented). missing for 10: explicit Payouts/Balance-transaction reconciliation API or MCP tool, documented deposit-to-charge matching logic, and independent/hands-on evidence of an agent performing this reconciliation successfully.

   • [claimed-docs] “Send money immediately to multiple recipients with their emails, phone numbers, or PayPal IDs.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies.”
   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “Agents can pull business analytics through a dedicated tool: `get_merchant_insights` — "Retrieve business intelligence metrics and analytics…”
   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”
   • [github] “The PayPal Agent Toolkit enables popular agent frameworks including OpenAI's Agent SDK, LangChain, Vercel's AI SDK, and Model Context Protoc…”

   proof ↗⚑ flag

   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

Payouts

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

   weight 2 · round to Square
   PayPal—none0/10

   Evidence covers PayPal's mass Payouts API (sending batch payments) and general merchant insights/analytics, but nothing documents controlling a payout schedule or a reconciliation view mapping each payout to its constituent charges, fees, and refunds.

   • [claimed-docs] “Send money immediately to multiple recipients with their emails, phone numbers, or PayPal IDs.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies... A basic solution for sending batch paym…”
   • [claimed-docs] “A basic solution for sending batch payments using recipients' email addresses, phone numbers, or PayPal IDs.”
   • [claimed-docs] “Agents can pull business analytics through a dedicated tool: `get_merchant_insights` — "Retrieve business intelligence metrics and analytics…”

   proof ↗⚑ flag

   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

Reconciliation

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

   weight 3 · round to Square
   PayPal~partialclaimed3/10

   PayPal's evidence shows transaction-level reporting and dispute/refund tooling (get_merchant_insights, list_transaction, dispute and refund APIs) that could feed reconciliation workflows, but there is no documented settlement report or bank-deposit-matching feature tying fees, refunds, and chargebacks together. missing for 10: dedicated settlement/reconciliation report, bank deposit matching, itemized fee breakdown tied to payouts.

   • [claimed-docs] “The documented agent-toolkit tool inventory spans the merchant back office: catalog (`create_product`, `list_product`, `show_product_details…”
   • [claimed-docs] “Agents can pull business analytics through a dedicated tool: `get_merchant_insights` — "Retrieve business intelligence metrics and analytics…”
   • [claimed-docs] “Disputes API: A programmatic interface that enables you to automate dispute management actions directly from your systems.”
   • [claimed-docs] “Add server-side endpoints to handle refunds, voids, delayed captures, and specialized checkout flows.”

   proof ↗⚑ flag

   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

Marketplace

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

   weight 2 · round to PayPal
   PayPal✓fullclaimed8/10

   PayPal's Complete Payments Platform explicitly targets marketplaces/platforms with seller onboarding under local regulations, expanded checkout, and multiparty payment processing (paypal-docs-8, paypal-docs-42, paypal-docs-27), while Payouts supports splitting/sending funds to thousands of recipients via email/phone/PayPal ID in various currencies (paypal-docs-5, paypal-docs-24, paypal-docs-41), and REST auth/webhooks/sandbox round out the developer integration story (paypal-docs-1, paypal-docs-9, paypal-docs-11). missing for 10: no explicit hands-on/independent case study of a full marketplace build (onboarding+split+payout) working end-to-end, and details on partner/seller onboarding flows (e.g., Partner Referrals API specifics) are only briefly summarized rather than deeply documented.

   • [claimed-docs] “you can onboard global sellers by applying local regulations and compliance rules”
   • [claimed-docs] “PayPal Complete Payments Platform offers multiparty payment processing solutions for marketplaces and platforms. With these solutions, you c…”
   • [claimed-docs] “Expanded Checkout includes all offerings from PayPal Checkout and card field customization with your business branding.”
   • [claimed-docs] “Send money immediately to multiple recipients with their emails, phone numbers, or PayPal IDs.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies.”
   • [claimed-docs] “Send money to thousands of recipients at once for vendors and disbursements in various currencies... A basic solution for sending batch paym…”
   • [claimed-docs] “Exchange your client ID and client secret for an access token. The access token authenticates your app when calling PayPal REST APIs.”
   • [claimed-docs] “Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs”
   • [claimed-docs] “The PayPal sandbox is a self-contained, virtual testing environment that simulates the live PayPal production environment.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   PayPal—none0/10

   No evidence in the pack discusses data residency, regional data storage options, or configurable data location for PayPal accounts or its AI tools; this is a fair privacy-posture question for a payments platform handling personal/financial data, but no supporting documentation is present.

   ⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   PayPal—none0/10

   No evidence pack items discuss data retention policies, data deletion controls, or user-facing privacy/data management settings for AI-native usage of PayPal; the material covers payments, APIs, MCP tools, and unrelated community complaints about fund holds/disputes. missing for 10: documentation of data retention periods, user/agent-initiated deletion or export controls, and any AI-specific data governance policy.

   ⚑ flag

   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