Stripe vs PayPal

Agent access

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

   weight 2 · round drawn
   Stripe✓fullprobed9/10

   Stripe hosts a live llms.txt (probe confirms HTTP 200 with agent-oriented guidance), a full .md-suffixed docs mirror (docs.stripe.com/*.md), a machine-readable skills index at /.well-known/skills/index.json, and dedicated agent-oriented docs (agents.md, mcp.md, directory.md) explicitly designed for pointing agents at. This is independently verified by probes, not just vendor claims. missing for 10: no independent third-party (non-Stripe) report of an agent successfully consuming llms.txt end-to-end in production.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
   • [claimed-docs] “Stripe publishes a machine-readable agent-skills catalog: "You can use curl to fetch the index of available skills, what they do, and their …”
   • [probe] “PROBE skills-index (2026-09-14): GET https://docs.stripe.com/.well-known/skills/index.json returns HTTP 200 with 8 Stripe-maintained agent s…”
   • [claimed-docs] “Build your integration with agent-first developer tools, charge your users for AI features with usage-based billing, and let agents transact…”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe's kno…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

   Stripe's CLI and Workbench Shell provide scriptable, non-interactive access (stripe sandbox create, stripe products create, stripe listen, agent setup) usable in CI pipelines, backed by idempotency keys, restricted API keys, and a documented sandbox that requires no account registration — all designed for headless/automated use including by coding agents. missing for 10: no explicit first-party CI example (e.g. GitHub Actions workflow) or independent hands-on report of running the CLI in a CI pipeline.

   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
   • [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
   • [claimed-docs] “A sandbox is an isolated test environment. You can use your sandbox to test Stripe functionality in your account, and experiment with new fe…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe✓fullprobed9/10

   Stripe ships a well-documented, independently probed official hosted MCP server (mcp.stripe.com) exposing API tools, analytics, and knowledge-base search, with OAuth-based auth/governance, human-confirmation for write actions, and connected-account support; a live probe confirms the OAuth-gated endpoint is real and functioning. Missing for 10: no independent third-party hands-on review of actual agent usage beyond Stripe's own docs/probes.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe's kno…”
   • [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
   • [claimed-docs] “MCP access is governed like any credential: OAuth per the MCP spec ("OAuth lets you grant and revoke access without sharing an API key with …”
   • [claimed-docs] “Docs, "Use MCP with connected accounts": a Connect platform "can also use MCP to retrieve or update resources for your connected accounts...…”

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round to Stripe
   Stripe✓fullprobed9/10

   Stripe ships a well-documented official CLI (docs.stripe.com/stripe-cli) for building, testing, and managing integrations, explicitly positioned as 'agent-ready tooling' with commands like `stripe agent setup` (auto-configures Claude Code/Codex/Cursor), `stripe sandbox create` for keyless agent provisioning, `stripe directory search`, and `stripe projects init`. This is corroborated by an independent probe confirming the docs page exists and by Workbench's browser-based Shell mirroring CLI commands. Missing for 10: independent hands-on/community review specifically validating CLI usability for AI-native workflows beyond Stripe's own docs.

   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
   • [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “Stripe Projects "provisions and manages third-party services (such as hosting, databases, auth, AI, and observability) from the terminal. Ru…”
   • [claimed-docs] “"Stripe Directory helps developers and AI agents find the best external providers for a task and follow the best supported path to provision…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe✓fullprobed9/10

   Stripe exposes a comprehensive, well-documented REST API with idempotency, restricted keys, versioning, sandboxes, webhooks, OpenAPI-generated SDKs, and CLI/Workbench tooling, and this is independently corroborated by a probe confirming the API and llms.txt are live and reachable. missing for 10: no independent third-party benchmark of raw API completeness beyond docs/probes, and OpenAPI spec discovery via well-known paths returned 404s per stripe-probe-3.

   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “use an idempotency key... you can safely repeat the request without risk of creating a second object or performing the update twice”
   • [claimed-docs] “Stripe uses API keys to authenticate requests from your integration and determine which Stripe resources it can access.”
   • [claimed-docs] “A restricted API key (RAK) is an API key ... a RAK can do only what you give it permission to do.”
   • [claimed-docs] “You can safely upgrade to a new monthly release without breaking any existing code.”
   • [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
   • [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Stripe
   Stripe✓fullprobed9/10

   Stripe explicitly documents restricted API keys (RAKs) as the recommended least-privilege credential for AI agents—developers select per-resource Read/Write/None permissions—and pairs this with MCP OAuth sessions (per-client revocation, connected-account scoping via Stripe-Account header, human confirmation for write actions like refunds, and Workbench tool-call logs), giving concrete scoped-credential issuance and governance for agents. This is corroborated by a live probe confirming the OAuth-gated MCP endpoint. Missing for 10: independent/hands-on developer confirmation of the RAK issuance workflow in practice beyond first-party docs.

   • [claimed-docs] “A restricted API key (RAK) is an API key ... a RAK can do only what you give it permission to do.”
   • [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
   • [claimed-docs] “MCP access is governed like any credential: OAuth per the MCP spec ("OAuth lets you grant and revoke access without sharing an API key with …”
   • [claimed-docs] “Docs, "Use MCP with connected accounts": a Connect platform "can also use MCP to retrieve or update resources for your connected accounts...…”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
   • [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe
   Stripe✓fullprobed9/10

   Stripe publishes official SDKs/client libraries generated from OpenAPI specs, plus AI-native additions like @stripe/agent-toolkit, @stripe/ai-sdk, token-meter, a hosted OAuth-gated MCP server, agent plugins for Claude/Codex/Cursor, and a machine-readable skills catalog — strongly evidencing an AI-native developer can build against official SDKs. missing for 10: independent (non-Stripe) hands-on developer reports specifically validating the newer agent-toolkit/ai-sdk packages in production.

   • [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
   • [claimed-docs] “The stripe/ai repo (github.com/stripe/agent-toolkit now redirects here) is "the one-stop shop for building AI-powered products and businesse…”
   • [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
   • [claimed-docs] “Stripe publishes a machine-readable agent-skills catalog: "You can use curl to fetch the index of available skills, what they do, and their …”
   • [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
   • [probe] “PROBE skills-index (2026-09-14): GET https://docs.stripe.com/.well-known/skills/index.json returns HTTP 200 with 8 Stripe-maintained agent s…”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe's kno…”
   • [github] “a collection of SDKs to help you integrate Stripe with LLMs and agent frameworks”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe✓fullclaimed8/10

   Stripe supports registering HTTPS webhook endpoints that push real-time events (payment success, disputes, subscription renewals, etc.), and this is directly usable by AI agents via the MCP server's stripe_api_write tool (webhook endpoint creation is explicitly listed as a supported MCP method) and via event-destinations delivering to multiple destination types. missing for 10: no hands-on/independent example of an agent actually subscribing to and consuming webhook events end-to-end, and no dedicated agent-specific webhook subscription API distinct from the standard developer webhook flow.

   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
   • [claimed-docs] “After you register a webhook endpoint, Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

   Stripe supports AI-generated insights primarily through its MCP `stripe_analytics`/`stripe_report` tools, which let an AI agent query metrics like MRR, churn rate, and run custom SQL against reporting tables, and Radar applies AI algorithms to score fraud risk in real time. However, these insights are largely agent-mediated (via MCP) rather than a native in-Dashboard AI assistant proactively surfacing suggestions to the user. Missing for 10: evidence of a built-in conversational/insights UI inside the Dashboard itself (not just via external agent+MCP), broader proactive 'suggestions' beyond analytics queries, and independent/hands-on validation of insight quality.

   • [claimed-docs] “You can use an AI agent to analyze aggregated data across your Stripe account ... query metrics such as monthly recurring revenue (MRR)”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
   • [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe~partialclaimed7/10

   Stripe ships substantial infrastructure for background automation — webhooks that push real-time events for asynchronous processing, Billing's automated recurring payments/renewals, Smart Retries and revenue-recovery automation that requires no code, Radar's automatic fraud scoring, and an MCP server plus agent plugins that let AI agents act on Stripe data continuously. However, Stripe explicitly gates autonomous execution: 'Stripe requires human confirmation before it takes certain stripe_api_write actions, such as refunds and outbound payments,' meaning fully unattended agentic automation is capped for sensitive operations, and there's no independent/hands-on evidence of long-running autonomous background agent workflows in production. Missing for 10: evidence of fully unattended agent automations without human-in-the-loop gating, and independent corroboration of real-world background agent runs.

   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
   • [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
   • [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
   • [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe—none0/10

   The evidence pack shows Stripe exposing an MCP server, CLI, SDKs, and agent plugins so *external* AI agents (Claude, Codex, Cursor, etc.) can act on Stripe's behalf, and it describes AI-driven backend features (Radar fraud scoring, smart retries). But none of the evidence describes a built-in, in-product AI assistant/chat feature embedded in the Stripe Dashboard itself that a user converses with to delegate tasks — the 'analyze with AI' and analytics tooling are also delivered via the external MCP interface rather than a native assistant UI.

   • [claimed-docs] “You can use an AI agent to analyze aggregated data across your Stripe account ... query metrics such as monthly recurring revenue (MRR)”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   Stripe~partialprobed7/10

   Stripe exposes an MCP server plus Directory/Analytics tools that let AI agents perform natural-language-driven actions (search products, read/write API resources, query MRR, run implementation planner) confirmed live via probe, and CLI/agent-plugin tooling lets coding agents set up sandboxes and integrations via NL prompts. However, this is agent-mediated (a separate AI agent translates NL into MCP/CLI calls) rather than the product itself having a native NL command interface, and write actions require human confirmation clicks rather than pure NL operation. missing for 10: evidence of a first-party conversational NL interface within Stripe's own Dashboard/product (not via third-party agent), and confirmation that full workflows can complete end-to-end via NL without manual approval steps.

   • [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
   • [claimed-docs] “Stripe's agent plugins give your AI agent access to Stripe developer tools, live account data, and the latest skills and technical guidance.”
   • [claimed-docs] “"Stripe Directory helps developers and AI agents find the best external providers for a task and follow the best supported path to provision…”
   • [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to Stripe
   Stripe~partialprobed6/10

   Stripe's Workbench includes an in-Dashboard API Explorer/Shell that lets users visually explore API resources and execute real, runnable API calls (including against sandboxes), and Workbench's shell exposes CLI/API autocompletion — this is a genuine interactive, runnable API reference. However, evidence doesn't show a public-facing interactive API reference page (like a standalone docs.stripe.com/api with try-it-now runnable code snippets) accessible without Dashboard login, nor independent/community confirmation of the experience quality. missing for 10: evidence of a public runnable API reference outside the authenticated Dashboard, independent/hands-on user reviews of the API explorer experience, confirmation that all endpoints are runnable (not just Shell CLI-style commands).

   • [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
   • [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to PayPal
   Stripe✓fullprobed8/10

   Stripe publishes machine-readable OpenAPI spec files explicitly for generating SDKs/clients (stripe-docs-46, github.com/stripe/openapi), and docs.stripe.com also serves machine-readable .md versions of every doc page plus an llms.txt index (stripe-probe-1, stripe-probe-2), directly serving AI-native consumption needs. However, a direct openapi.json/swagger.json was not found at the docs.stripe.com domain itself (stripe-probe-3 shows 404s on guessed paths), meaning discovery requires knowing the separate GitHub repo rather than a single canonical documented download link. Missing for 10: a first-party documented URL/endpoint for the OpenAPI spec directly from docs.stripe.com (not just GitHub), and independent hands-on confirmation of spec completeness/versioning.

   • [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Stripe
   Stripe✓fullclaimed9/10

   Stripe documents a dedicated sandbox environment isolated from live/production data (stripe-docs-32, stripe-docs-43, stripe-docs-57), test cards/values that simulate transactions without moving real funds (stripe-docs-10, stripe-docs-65), and anonymous sandbox provisioning explicitly for coding agents via CLI (stripe-docs-16), plus MCP/Workbench access scoped per sandbox vs live mode (stripe-supp-mcp-sessions-governance, stripe-supp-workbench-shell). Missing for 10: independent hands-on confirmation from a third party that agent-driven sandbox testing works end-to-end without friction.

   • [claimed-docs] “A sandbox is an isolated test environment. You can use your sandbox to test Stripe functionality in your account, and experiment with new fe…”
   • [claimed-docs] “You can use your sandbox to test Stripe functionality in your account, and experiment with new features without affecting your live integrat…”
   • [claimed-docs] “Your team can test in separate sandboxes to make sure that data and actions are completely isolated from other sandboxes.”
   • [claimed-docs] “Test your integration in a sandbox ... by simulating transactions with test values—these transactions don't move funds.”
   • [claimed-docs] “Test cards act as "fake" credit cards, and allow you to simulate the following scenarios: - Successful payments... - Card errors due to decl…”
   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “MCP access is governed like any credential: OAuth per the MCP spec ("OAuth lets you grant and revoke access without sharing an API key with …”
   • [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
   • [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

   Stripe documents a clear API versioning policy: monthly releases contain only backward-compatible changes, and users can safely upgrade without breaking existing code, with explicit versioning docs. This directly matches the story's requirement of versioned APIs with a documented deprecation/compatibility policy. Missing for 10: no explicit deprecation timeline/sunset schedule detail or independent hands-on verification of long-term version support beyond the docs' own claims.

   • [claimed-docs] “You can safely upgrade to a new monthly release without breaking any existing code.”
   • [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe~partialclaimed6/10

   Stripe supports some bulk-style operations relevant to AI agents — bulk product catalog import via the v2 Product Catalog Import API (CSV up to 4GB, upsert/replace modes), List CheckoutSessions for bulk fulfillment, and MCP/analytics tools that can query/report across many objects (stripe_analytics, stripe_report) — but there is no documented generic bulk-write or batch-update API (e.g., bulk refunds, bulk subscription updates, bulk customer edits) that an AI agent could invoke across many arbitrary items at once; most single-object write tools (stripe_api_write, Refunds API, etc.) operate one record at a time with idempotency keys rather than true batch semantics. missing for 10: a documented bulk/batch API for core objects (customers, charges, subscriptions, refunds) beyond catalog import, evidence of MCP or CLI tools performing multi-item operations in one call, and independent/hands-on confirmation of bulk operation reliability.

   • [claimed-docs] “Agentic Commerce Suite ingests full product catalogs as bulk CSV imports via the v2 Product Catalog Import API: POST /v2/commerce/product_ca…”
   • [claimed-docs] “Orders placed through AI chat agents flow through standard Stripe rails: "Stripe sends checkout.session.completed after the agent completes …”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Stripe
   Stripe~partialclaimed6/10

   Stripe provides the event backbone needed for rule-based automation — webhooks/event destinations that fire on account events (stripe-docs-8, stripe-docs-53, stripe-supp-event-destinations) — plus some built-in automated actions like Smart Retries and Radar's real-time risk rules (stripe-docs-14, stripe-docs-22). A third-party Dashboard app (Kyber) explicitly offers a no-code rule builder that 'assigns tasks and automates common workflows based on Stripe events' (e.g., Slack alert on dispute), which matches the story closely (stripe-intdir-6). However, this rule-definition UI is a third-party app, not a native first-party Stripe rules engine, and there's no evidence of a built-in general-purpose 'if event X then action Y' configurator inside Stripe itself. Missing for 10: a native first-party no-code/low-code rule engine for arbitrary event-triggered actions, and independent hands-on confirmation of such rule-based automation in practice.

   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
   • [claimed-docs] “After you register a webhook endpoint, Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “The no-code builder Kyber lets users assign tasks and automate common workflows based on Stripe events. Users can quickly configure automati…”
   • [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

   Stripe Billing natively automates recurring payment jobs (subscriptions, invoicing, trials, renewals, smart retries) and this can be driven via API/MCP by an AI agent, plus Stripe Projects/CLI/Workbench let agents script and schedule integration tasks. However there is no evidence of a general-purpose 'schedule any workflow/job' primitive (e.g. cron-like task scheduler for arbitrary agent workflows) beyond payment/billing-specific recurrence. missing for 10: a generic workflow/job scheduler beyond billing recurrence, evidence of agents autonomously scheduling multi-step workflows (not just recurring payments), independent hands-on confirmation of this automation depth.

   • [claimed-docs] “It automates recurring payments, creates custom pricing plans, and handles billing periods, such as trials and renewals.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “Stripe Projects "provisions and manages third-party services (such as hosting, databases, auth, AI, and observability) from the terminal. Ru…”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “You can use an AI agent to analyze aggregated data across your Stripe account ... query metrics such as monthly recurring revenue (MRR)”

   proof ↗⚑ flag

   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

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

   Stripe documents the full loop an agent needs: webhooks/event destinations for detecting failed payments and dispute events (stripe-docs-8, stripe-docs-53, stripe-supp-event-destinations), Smart Retries and no-code revenue recovery/dunning automation with recovery analytics (stripe-docs-14, stripe-docs-15, stripe-docs-56), and API/MCP write access (subscriptions, invoices, disputes) with restricted-key scoping and human-confirmation guardrails so an agent can drive retries and outreach programmatically (stripe-supp-mcp-tools, stripe-supp-mcp-write-confirmation, stripe-supp-restricted-keys-agents, stripe-docs-41). Idempotency support further protects automated retry logic (stripe-docs-9). missing for 10: no first-party or hands-on example of an agent specifically orchestrating dunning outreach (e.g., emails/SMS) end-to-end, and no independent/community confirmation of this exact agent workflow in production.

   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
   • [claimed-docs] “Prevent lost revenue and reduce churn with Stripe’s revenue recovery features... None of the features require you to write code.”
   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
   • [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
   • [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe✓fullclaimed8/10

   Stripe's MCP server documents stripe_api_write with create/update support for products, prices, and payment links, plus stripe_implementation_planner to guide multi-step builds, enabling an agent to provision a product, price, and payment link in one session via a single authenticated MCP/API connection; the CLI/sandbox provisioning (stripe sandbox create) also lets agents get working keys without manual account setup. Missing for 10: a hands-on end-to-end transcript/independent report of an agent actually completing this exact three-step chain in one session, and clarity on whether human-confirmation gating (required for refunds/payments) also intercepts routine create-product/price/payment-link calls.

   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
   • [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
   • [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”

   proof ↗⚑ flag

   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

Invoicing

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

   weight 2 · round to PayPal
   Stripe~partialclaimed6/10

   Stripe clearly supports creating and sending hosted, customizable invoices with online payment collection, no code required (stripe-docs-21, stripe-docs-60, stripe-docs-51). However, the evidence pack does not explicitly document automatic reminder emails for unpaid invoices — the closest analog is 'Smart Retries' and revenue-recovery dunning for subscription payment failures (stripe-docs-14, stripe-docs-31), which is a related but distinct capability from invoice due-date reminders. Missing for 10: explicit documentation of automatic invoice payment reminder emails, and independent/hands-on confirmation of the reminder feature working in practice.

   • [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
   • [claimed-docs] “Customize invoices: Customize the content and branding of your invoices.”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “None of the features require you to write code, so you can start recovering revenue today.”
   • [claimed-docs] “Prevent lost revenue and reduce churn with Stripe’s revenue recovery features... None of the features require you to write code.”

   proof ↗⚑ flag

   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

Subscriptions

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

   Stripe Billing's revenue-recovery docs explicitly document Smart Retries for automatically retrying failed subscription payments plus recovery analytics, and this is a no-code feature within Billing. Missing for 10: explicit documentation of automated dunning/recovery email templates and independent hands-on validation of recovery email effectiveness.

   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
   • [claimed-docs] “None of the features require you to write code, so you can start recovering revenue today.”
   • [claimed-docs] “Prevent lost revenue and reduce churn with Stripe’s revenue recovery features... None of the features require you to write code.”
   • [claimed-docs] “Prevent lost revenue and reduce churn with Stripe's revenue recovery features. ... None of the features require you to write code”
   • [claimed-docs] “It automates recurring payments, creates custom pricing plans, and handles billing periods, such as trials and renewals.”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to PayPal
   Stripe✓fullclaimed8/10

   Stripe Billing explicitly automates recurring payments, custom pricing plans, trials, renewals, and subscription upgrades, plus a customer portal for self-service management, revenue recovery (smart retries), and subscription migration docs. Documentation confirms core subscription lifecycle features via first-party docs, though proration is only implied via 'upgrades' rather than explicitly named, and no independent/hands-on corroboration of proration mechanics is present. Missing for 10: explicit proration documentation/examples, independent developer corroboration of subscription setup experience.

   • [claimed-docs] “It automates recurring payments, creates custom pricing plans, and handles billing periods, such as trials and renewals.”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “Integrate the customer portal: The simplest way to build a subscription and billing management Dashboard.”
   • [claimed-docs] “Migrate your subscriptions: Learn how to migrate subscriptions to Stripe.”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
   • [claimed-docs] “None of the features require you to write code, so you can start recovering revenue today.”

   proof ↗⚑ flag

   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

Card acceptance

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

   weight 3 · round to PayPal
   Stripe!disputedcontradicted6/10

   Stripe's docs strongly support rapid onboarding: no-code Payment Links, hosted Checkout pages, and a live testimonial confirms setup and recurring payments working 'in less than an hour' (stripe-docs-4, stripe-docs-2, stripe-comm-9). However, independent community reports concretely contradict universal same-day acceptance — users report Stripe denying account creation entirely or 'nuking' an existing business's payment capability without quick support resolution (stripe-comm-1, stripe-comm-4, stripe-comm-5), showing that for some founders (especially certain geographies/business types) the promised fast, frictionless activation does not materialize. missing for 10: evidence resolving how common these denials/delays are, and first-party docs addressing account approval timelines or geographic/business restrictions.

   • [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
   • [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
   • [claimed-docs] “Create a payments page with prebuilt UIs using the Checkout Sessions API.”
   • [community] “Stripe is a game changer. I've been using it for a few months and honestly its the best API I've ever used. The documentation is clear and c…”
   • [community] “Funny, I have a Delaware LLC company registered in USA (it's an offshore company) but my bank account is outside the US (completely legal), …”
   • [community] “Stripe has decided to nuke my entire business... So currently, my product doesn't work for 35% of my customers. Cue torrent of pissed off cu…”
   • [community] “I wanted to enable issuing on my account to test card issuing, but there was a bug where the UI was looping. Asked support, got 2 weeks of '…”

   proof ↗⚑ flag

   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

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

   Stripe Elements and Checkout Sessions API let developers embed a fully customizable payment page directly in their own site (as opposed to only redirecting to a hosted page), with support for 125+ payment methods, subscriptions, and prebuilt/custom UI options documented extensively. Missing for 10: no independent/hands-on developer report specifically praising the embedded (non-redirect) Elements experience beyond docs.

   • [claimed-docs] “Build a fully customized payment page using elements”
   • [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
   • [claimed-docs] “Elements: Build a fully customized payment page using elements”
   • [claimed-docs] “Create a payments page with prebuilt UIs using the Checkout Sessions API.”
   • [claimed-docs] “Accept one-time and subscription payments from more than 125 local payment methods.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Stripe✓fullclaimed9/10

   Docs explicitly describe Stripe Checkout as a Stripe-hosted redirect page ('via a redirect to a Stripe-hosted page') with prebuilt UI via Checkout Sessions API, plus Payment Links for a fully no-code hosted checkout URL — directly matching the story. Multiple docs reinforce it supports many payment methods, currencies, tax collection, and no-code refunds on these hosted pages. missing for 10: no independent/hands-on corroboration of the hosted page's conversion-optimization claims beyond Stripe's own docs.

   • [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
   • [claimed-docs] “Create a payments page with prebuilt UIs using the Checkout Sessions API.”
   • [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
   • [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
   • [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”
   • [claimed-docs] “Accept one-time and subscription payments from more than 125 local payment methods.”

   proof ↗⚑ flag

   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

No code selling

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

   weight 2 · round drawn
   Stripe✓fullclaimed9/10

   Stripe Payment Links is explicitly documented as a no-code way to create a shareable payment link from the dashboard, supporting local currencies/payment methods, no-code tax collection, and no-code refunds — matching the founder story closely. Missing for 10: independent hands-on account of actually creating a payment link end-to-end (community evidence is general Stripe sentiment, not specific to Payment Links).

   • [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
   • [claimed-docs] “No-code refunds Yes”
   • [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
   • [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”

   proof ↗⚑ flag

   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

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
   Stripe~partialclaimed7/10

   Stripe Checkout/Elements documentation confirms 125+ local payment methods and localized payment links, which covers digital wallets, bank redirects, and local methods from one integration; however, the evidence never explicitly names Apple Pay, Google Pay, or specific BNPL providers, and there's no independent/hands-on confirmation of the exact method mix. missing for 10: explicit mention of Apple Pay/Google Pay support, named BNPL providers (e.g., Klarna/Afterpay), and independent verification of the full payment-method list.

   • [claimed-docs] “Accept one-time and subscription payments from more than 125 local payment methods.”
   • [claimed-docs] “Build a fully customized payment page using elements”
   • [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
   • [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”

   proof ↗⚑ flag

   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

Pci compliance

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

   Stripe's docs explicitly state that low-risk integrations (Checkout, Elements, hosted payment pages) collect and transmit payment data directly to Stripe without it passing through the developer's servers, explicitly reducing PCI obligations/scope, and these are backed by concrete hosted/embeddable products (Checkout, Payment Links, Elements). missing for 10: independent third-party PCI audit or compliance-report corroboration beyond Stripe's own docs.

   • [claimed-docs] “You can instead use one of our low risk payment integrations to securely collect and transmit payment information directly to Stripe without…”
   • [claimed-docs] “you can instead use one of our low risk payment integrations to securely collect and transmit payment information directly to Stripe without…”
   • [claimed-docs] “use one of our low risk payment integrations to securely collect and transmit payment information directly to Stripe without it passing thro…”
   • [claimed-docs] “Build a fully customized payment page using elements”
   • [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
   • [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”

   proof ↗⚑ flag

   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

Integration reliability

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

   Stripe's API docs explicitly document idempotency keys for safely retrying requests after connection errors without creating duplicate objects/charges, directly matching the story, and this is a well-known, widely used first-party API feature. Missing for 10: independent hands-on developer corroboration specifically testing idempotency behavior (community evidence in the pack is unrelated to this feature).

   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “use an idempotency key... you can safely repeat the request without risk of creating a second object or performing the update twice”
   • [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object or pe…”
   • [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object”

   proof ↗⚑ flag

   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

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

   Docs cover signed/HTTPS webhook endpoints, real-time event pushes, idempotency for safe retries, dispute/event handling via API+webhooks, and the newer event destinations feature with versioned snapshot/thin events; sandbox testing supports simulating webhook flows. However, explicit documentation of automatic retry schedules for failed webhook deliveries and a dedicated 'replay' UI/feature isn't directly cited (event destinations mention versioning but not an explicit replay tool), and there's no independent/hands-on corroboration of retry reliability. missing for 10: explicit docs on automatic webhook retry backoff schedule, a dedicated event replay feature/UI, independent developer corroboration of retry/replay reliability.

   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
   • [claimed-docs] “After you register a webhook endpoint, Stripe pushes real-time data to it when events happen in your Stripe account.”
   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “use an idempotency key... you can safely repeat the request without risk of creating a second object or performing the update twice”
   • [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object or pe…”
   • [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object”
   • [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”
   • [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”

   proof ↗⚑ flag

   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

Onboarding dx

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

   weight 2 · round to Stripe
   Stripe✓fullcommunity8/10

   Stripe's docs offer copy-paste checkout/payment-link/Elements integrations, sandbox testing with test cards, idempotency, webhooks, and API keys, and community testimony confirms fast integration ('up and running and accepting recurring payments in less than an hour', clear documentation) despite some unrelated support gripes. missing for 10: explicit multi-language SDK code-sample evidence in the pack (only generic doc references, not shown per-language snippets) and a broader/more recent independent corroboration beyond one old HN thread.

   • [claimed-docs] “Build a fully customized payment page using elements”
   • [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
   • [claimed-docs] “Test your integration in a sandbox ... by simulating transactions with test values—these transactions don't move funds.”
   • [claimed-docs] “Test cards act as "fake" credit cards, and allow you to simulate the following scenarios: - Successful payments... - Card errors due to decl…”
   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
   • [community] “Stripe is a game changer. I've been using it for a few months and honestly its the best API I've ever used. The documentation is clear and c…”

   proof ↗⚑ flag

   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

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

   Stripe provides a documented sandbox environment mirroring production (isolated per-team sandboxes, no live-data impact) plus an extensive test-card matrix covering successes, declines, fraud, and invalid data, and a full disputes API for simulating/handling chargebacks. CLI and Workbench also support building/testing/debugging integrations end-to-end. Missing for 10: no independent/hands-on developer testimonial specifically validating sandbox fidelity or test-card coverage beyond first-party docs.

   • [claimed-docs] “Test your integration in a sandbox ... by simulating transactions with test values—these transactions don't move funds.”
   • [claimed-docs] “A sandbox is an isolated test environment. You can use your sandbox to test Stripe functionality in your account, and experiment with new fe…”
   • [claimed-docs] “You can use your sandbox to test Stripe functionality in your account, and experiment with new features without affecting your live integrat…”
   • [claimed-docs] “You can invite another user, such as an implementation partner or design agency, to access all sandboxes, or a specific sandbox, without pro…”
   • [claimed-docs] “Your team can test in separate sandboxes to make sure that data and actions are completely isolated from other sandboxes.”
   • [claimed-docs] “Test cards act as "fake" credit cards, and allow you to simulate the following scenarios: - Successful payments... - Card errors due to decl…”
   • [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”

   proof ↗⚑ flag

   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

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

   Stripe docs explicitly state the Disputes API supports retrieving, uploading evidence, responding to disputes, and receiving dispute webhook events, and the hosted MCP server's documented tool surface includes 'disputes (update)' alongside generic read/write API access, restricted-key scoping for agents, and webhook-based event delivery — covering the retrieve→assemble→submit flow programmatically. Missing for 10: a concrete end-to-end worked example (e.g., a sample agent script that assembles and submits evidence), and clarity on whether dispute submission falls under the human-confirmation gate applied to other write actions.

   • [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”

   proof ↗⚑ flag

   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

Disputes

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

   Stripe's Disputes API lets finance-ops programmatically manage disputes, upload structured evidence, respond to disputes, and receive dispute lifecycle events via webhooks, plus dispute events surface in the Dashboard/Radar for tracking; MCP tooling also exposes a 'disputes: update' method for agent-assisted workflows. missing for 10: no independent/hands-on account of the full evidence-submission UX or explicit dispute-resolution outcome tracking beyond webhook events.

   • [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
   • [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”

   proof ↗⚑ flag

   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

Fraud prevention

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

   weight 3 · round to Stripe
   Stripe~partialclaimed5/10

   Stripe Radar is documented to use AI/ML algorithms in real time to assess fraud risk across transactions, accounts, and customers, which covers the ML fraud-scoring part of the story; however, the evidence pack does not show custom rule-writing capability (block/review/allow rules) beyond the single Radar mention, no details on rule builder UI, thresholds, or list management. missing for 10: documentation of custom rule creation/editing (block, review, allow lists), rule logic examples, and independent/hands-on confirmation of Radar's rule-writing workflow.

   • [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”

   proof ↗⚑ flag

   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

Refunds

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed9/10

   Docs explicitly state refunds can be issued via both the Refunds API and the Dashboard, including full or partial amounts, and refunded payments are viewable in the Dashboard. No-code refunds are also supported on Payment Links. missing for 10: no independent/hands-on confirmation of partial-refund UX in the dashboard.

   • [claimed-docs] “You can cancel a payment before it's completed at no cost. Or you can refund all or part of a payment after it succeeds, which might incur a…”
   • [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard”
   • [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard.”
   • [claimed-docs] “You can view your refunded payments in the Dashboard”
   • [claimed-docs] “No-code refunds Yes”

   proof ↗⚑ flag

   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

Multi currency

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

   Stripe documents charging in 135+ currencies with payout settlement in a merchant's preferred currency (stripe-docs-19), localized checkout/payment links that let customers pay in their own currency (stripe-docs-36), automated payout tracking to bank accounts (stripe-docs-34, stripe-docs-52, stripe-docs-68), and automated tax compliance across jurisdictions (stripe-docs-20, stripe-docs-48). This directly covers charging locally and settling in the founder's currency. Missing for 10: explicit documentation of FX conversion rate transparency/fee disclosure mechanics and independent/hands-on confirmation of FX rate fairness or settlement accuracy.

   • [claimed-docs] “You can charge customers in over 135 currencies and receive funds in your preferred currency.”
   • [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
   • [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
   • [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
   • [claimed-docs] “Set up your bank account to receive payouts.”
   • [claimed-docs] “Automate sales tax, VAT, and GST compliance on all your transactions.”
   • [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”

   proof ↗⚑ flag

   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

Tax

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

   Stripe Tax explicitly automates sales tax, VAT, and GST calculation and collection across transactions, including no-code tax collection on Payment Links, backed by first-party docs. Missing for 10: independent/hands-on corroboration of accuracy across jurisdictions and any detail on filing/remittance support beyond calculation and collection.

   • [claimed-docs] “Automate sales tax, VAT, and GST compliance on all your transactions.”
   • [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

   Stripe's core resources (payments, refunds, subscriptions, invoices, disputes, payouts, tax, Connect) are all documented as available via the REST API with idempotency, versioning, and restricted keys, and the MCP server explicitly exposes generic stripe_api_read/stripe_api_write tools plus task-specific tools mirroring Dashboard actions across most objects. Workbench Shell/CLI further lets agents run the same commands as the CLI/API interactively. missing for 10: independent confirmation that every Dashboard-only feature (e.g., third-party Stripe Apps like Kyber no-code automations) has a full API equivalent, and note that sensitive stripe_api_write actions require human confirmation rather than being fully autonomous.

   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
   • [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
   • [claimed-docs] “A restricted API key (RAK) is an API key ... a RAK can do only what you give it permission to do.”
   • [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
   • [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
   • [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Stripe
   Stripe~partialclaimed3/10

   Evidence shows only narrow CSV export of specific financial reports (balance, payouts, activity, tax, Revenue Recognition) via stripe_report/Workbench, not a comprehensive account data export mechanism for a user to leave the platform. Missing for 10: a documented full account/data export tool (customers, charges, subscriptions, full transaction history) in open/portable formats, and any explicit data-portability or account-closure export workflow.

   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”

   proof ↗⚑ flag

   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

Ai reconciliation

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

   weight 3 · round to Stripe
   Stripe~partialclaimed7/10

   Stripe's API and MCP tooling explicitly expose payout and balance-transaction data for programmatic/agent access — the documented stripe_api_read method list includes 'payouts, and balance transactions', and stripe_analytics/stripe_report can run balance and payout financial reports, letting an agent pull the data needed to match deposits to charges (stripe-supp-mcp-tools, stripe-supp-analytics-ai, stripe-docs-34/52/68). However, there is no first-party tutorial or worked example specifically demonstrating automated reconciliation logic (matching a bank deposit to its underlying charges), and no independent/hands-on evidence confirming this reconciliation workflow works end-to-end. Missing for 10: a documented reconciliation workflow/tutorial tying payout amounts to constituent balance-transaction charges, and independent verification of an agent successfully performing this reconciliation.

   • [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
   • [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
   • [claimed-docs] “Set up your bank account to receive payouts.”

   proof ↗⚑ flag

   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

Payouts

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

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

   Stripe documents payout basics (funds sent from balance to bank account, dashboard tracking of payouts and expected deposit dates, setting up bank accounts) and financial reporting via stripe_report/analytics (balance, payouts, activity reports downloadable as CSV), which supports reconciliation. However, evidence does not show explicit payout schedule controls (e.g., setting manual vs automatic schedule, daily/weekly/monthly cadence) nor a documented per-payout breakdown view showing exact charges/fees/refunds composing each payout. missing for 10: explicit payout schedule configuration docs, a documented itemized payout reconciliation report/API showing constituent charges/fees/refunds per payout, independent/hands-on confirmation of this reconciliation workflow.

   • [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
   • [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
   • [claimed-docs] “Set up your bank account to receive payouts.”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”

   proof ↗⚑ flag

   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

Reconciliation

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

   weight 3 · round to Stripe
   Stripe~partialclaimed5/10

   Stripe documents payouts to bank accounts with expected deposit dates (stripe-docs-34, stripe-docs-52), refunds and dispute management via API/Dashboard (stripe-docs-17, stripe-docs-33, stripe-docs-41), and AI-assisted analytics/report runs including a documented 'balance summary' report and other financial report types (stripe-supp-analytics-ai). However, there is no evidence of a purpose-built, itemized settlement-to-deposit reconciliation report that breaks out fees, refunds, and chargebacks against a specific bank deposit in one view — the closest evidence (report types: balance, payouts, activity, tax) implies this exists but doesn't confirm itemization matching finance-ops reconciliation workflows, and third-party accounting sync (QuickBooks, Xero) is only listed as partner integrations rather than native itemized reconciliation. missing for 10: a documented native 'payout reconciliation report' itemizing fees/refunds/chargebacks per deposit, confirmation of automatic matching to bank statement lines, and independent/hands-on evidence from finance-ops users that this reconciliation workflow works well in practice.

   • [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
   • [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
   • [claimed-docs] “You can cancel a payment before it's completed at no cost. Or you can refund all or part of a payment after it succeeds, which might incur a…”
   • [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
   • [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
   • [claimed-docs] “We are specialists in connecting Stripe to QuickBooks Online”
   • [claimed-docs] “View relevant Xero customer and transaction data within the Stripe Dashboard”

   proof ↗⚑ flag

   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

Marketplace

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

   Stripe Connect is explicitly documented as the product for building marketplaces/platforms that onboard sellers, split payments, and pay out to multiple parties, backed by supporting payouts, payment collection, refunds, disputes, and tax infrastructure. Missing for 10: independent hands-on evidence specifically of a marketplace/Connect integration (community evidence covers Stripe generally, not Connect specifically).

   • [claimed-docs] “Collect payments from customers and automatically pay out a portion to sellers or service providers on your marketplace.”
   • [claimed-docs] “Use Connect to build a platform, marketplace, or other business that manages payments and moves money between multiple parties.”
   • [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
   • [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
   • [claimed-docs] “Set up your bank account to receive payouts.”
   • [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard”
   • [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Stripe—none0/10

   No evidence in the pack discusses data residency, regional data storage choices, or GDPR/EU data localization options for Stripe accounts; the evidence covers payments, billing, MCP/agents, sandboxes, etc. but never data residency controls.

   ⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe—none0/10

   The evidence pack covers sandbox isolation, restricted API keys, MCP OAuth session revocation, and webhook/event architecture, but none of it addresses data retention policies or a mechanism for users to request deletion/erasure of stored payment or customer data. As a platform processing sensitive financial and personal data, this is a fair and applicable axis, but no documentation shows retention controls or deletion capabilities for AI-native users.

   ⚑ flag

   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