Adyen vs PayPal

Agent access

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

   weight 2 · round to Adyen
   Adyen✓fullprobed10/10

   Adyen has a live, probed llms.txt (HTTP 200) plus markdown-renderable docs pages (append .md), a documented full-docs ZIP mirror explicitly for feeding AI agents/code assistants, and an OpenAPI spec repo positioned as LLM context — this is direct, independently-probed confirmation of agent-oriented docs.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.adyen.com/online-payments.md --- title: "Online payments" description: "Accept payments with cards, …”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”
   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”

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

   Adyen's core integration is a server-to-server REST API (docs-1, docs-2) that can be called entirely headlessly with no UI dependency, supports idempotency keys for safe automated retries (adyen-docs-4, adyen-docs-25), and provides a dedicated test environment with test credentials explicitly meant for pre-production integration testing (adyen-docs-6, adyen-docs-18). Scoped, multiple API credentials support automated/service-account style access (adyen-docs-26, adyen-supp-api-credential-scoping). However, there is no explicit CI/CD pipeline documentation, no CLI/SDK testing harness, and the MCP server is documented as running locally via npx rather than as a CI-oriented headless service. Missing for 10: explicit CI/CD integration guides, automated test-suite/SDK tooling, and confirmation of non-interactive credential provisioning for pipelines.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Your server makes three Checkout API requests: /paymentMethods, /payments, and /payments/details.”
   • [claimed-docs] “To submit a request for idempotent processing, send a request with the `idempotency-key:` in the header.”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”
   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials.”
   • [claimed-docs] “You can also create multiple API credentials to improve security and control access.”
   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”

   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 to PayPal
   Adyen✓fullprobed8/10

   Adyen documents and ships an official MCP server (github.com/Adyen/adyen-mcp) that lets LLM clients call Checkout, payment links, modifications, and Management API tools via natural language, with clear setup (npx install), scoped API-key auth, and role-based permissions. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice (only vendor docs and a live-probe confirming the doc page exists, no community usage reports) and clarity on production-readiness given its 'Alpha' status.

   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “MCP access rides on Adyen's standard scoped credentials: "To authenticate the requests you will make using the MCP, generate an API key. Mak…”

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

   Evidence covers an MCP server, OpenAPI specs, docs tooling, and agentic-commerce protocols, but there is no mention of an official Adyen CLI for AI-native workflows anywhere in the pack.

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

   Adyen ships extensive documented public REST APIs (Checkout, Management, Platforms, Payouts, Agentic Commerce, etc.), an OpenAPI spec repo as 'single source of truth' for client generation, idempotency keys, scoped API credentials, webhooks, and machine-readable docs (llms.txt, .md pages, full docs mirror) explicitly aimed at AI tooling. Probes independently confirm llms.txt and .md doc endpoints return 200. Missing for 10: a live discoverable OpenAPI/swagger endpoint directly under docs.adyen.com (probe found 404s on standard paths) and independent third-party corroboration of API usability beyond vendor docs.

   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”
   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.adyen.com/online-payments.md --- title: "Online payments" description: "Accept payments with cards, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

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

   Adyen documents scoped, role-based API credentials (roles define exactly what a credential can do, e.g. limiting to initiating vs capturing payments, per-merchant-account scoping) and explicitly recommends creating multiple credentials for finer-grained access control — and the MCP server docs instruct assigning a dedicated API credential with only the specific roles needed for agent use, plus a --tools flag to limit which MCP tools are exposed. This directly supports least-privilege credential issuance for an AI agent. missing for 10: no independent/hands-on verification of least-privilege enforcement in practice, and no explicit per-agent short-lived/ephemeral credential mechanism beyond static role-scoped API keys.

   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”
   • [claimed-docs] “MCP access rides on Adyen's standard scoped credentials: "To authenticate the requests you will make using the MCP, generate an API key. Mak…”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “You can also create multiple API credentials to improve security and control access.”

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

   Adyen documents official SDKs for web/iOS/Android/React Native/Flutter and a public OpenAPI spec repo as the 'single source of truth' usable to generate client libraries, which supports SDK-based building; however, the OpenAPI/spec endpoint probes returned 404s and there's no independent/hands-on corroboration of SDK quality or completeness for AI-native workflows specifically. missing for 10: independent verification of official SDK repos/quality, working OpenAPI spec endpoint (probe returned 404s), hands-on developer confirmation of SDK-based agentic integration.

   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

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

   Adyen provides first-party webhook subscriptions to avoid polling, with event logs visible in the Customer Area, and MCP tools to list/get/test webhooks, plus agentic-commerce flows that explicitly send webhook payment outcomes to merchant servers — showing webhooks are usable both directly and via AI-native/agent tooling. missing for 10: no independent/hands-on developer confirmation of webhook subscription setup via API or MCP, and no detail on webhook event types/payload schema management through natural-language/agentic tooling.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Google Agentic Commerce integration: "Use this integration for processing Google Pay payments through Adyen, when Google agents (Google AI M…”

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

   Adyen Uplift is documented as an AI layer that analyzes payment data and 'gives you recommendations that are tailored for your business' to optimize conversion, risk, and cost, and risk management includes ML-powered fraud detection using global transaction data. This matches the spirit of AI-generated insights/suggestions from account data, but it's narrowly scoped to payment-funnel optimization and fraud, not a general-purpose 'insights' feature across reporting/dashboards, and there's no independent/hands-on corroboration of how these suggestions surface in the UI. Missing for 10: broader AI-generated insights across reporting/analytics (not just Uplift/fraud), and third-party or hands-on evidence of the insights UX.

   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”
   • [claimed-docs] “Adyen Uplift helps you strike a balance between conversion, risk and cost. You get recommendations that are tailored for your business”
   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”

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

   Adyen supports several background/event-driven automations — webhooks that eliminate manual polling for async status changes, Uplift's AI-driven payment-funnel optimization experiments that can be started/evaluated/stopped autonomously, and risk-management rules/ML fraud detection that run continuously — but these are fixed platform features rather than a general-purpose mechanism for an AI-native user to author custom autonomous background automations. Missing for 10: a user-configurable automation/workflow builder or scheduler that an AI-native user can set up to run arbitrary agentic tasks unattended, and independent evidence of such automations running reliably in production.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”
   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”

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

   Adyen documents an MCP server (for external LLM clients to call Adyen's APIs) and 'Uplift' (automated AI-driven payment optimization), but no evidence of a built-in AI assistant/copilot inside the Adyen product itself that a user can converse with or delegate tasks to interactively.

   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”

   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
   Adyen~partialprobed7/10

   Adyen ships an official MCP server (adyen-mcp) that explicitly lets users 'use natural language with your chosen LLM client' to interact with Adyen APIs (create sessions, payment links, refunds, management API), with documented scoped-credential setup — a genuine natural-language operation surface for AI-native users. However, the MCP server is explicitly marked 'Alpha', runs only locally via npx, and only exposes a documented subset of tools rather than full product coverage. Missing for 10: production-grade/GA status, independent hands-on validation of the NL interface actually working reliably, and broader coverage beyond the documented tool subset.

   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”
   • [claimed-docs] “This allows developers to use natural language to connect with Adyen's platform more easily and build new payment solutions faster.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “MCP access rides on Adyen's standard scoped credentials: "To authenticate the requests you will make using the MCP, generate an API key. Mak…”
   • [probe] “official MCP server documented at https://docs.adyen.com/development-resources/mcp-server”

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

   The evidence describes OpenAPI specs (usable to generate Postman collections or client libraries), markdown-rendered docs, and an MCP server for natural-language API access, but there is no evidence of an actual interactive API reference/console embedded in Adyen's docs where a user can run live example requests. A probe for a standard OpenAPI/Swagger endpoint also returned 404s, and no 'try it' console or embedded runnable code examples are documented.

   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”

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

   Adyen documents a dedicated OpenAPI specification repository (github.com/Adyen/adyen-openapi) covering 'every public API Adyen offers' as the 'single source of truth,' explicitly positioned for machine consumption (client-library generation, Postman collections, and LLM/agent context). This is reinforced by llms.txt, markdown-renderable docs, and a full docs mirror ZIP for AI tooling. missing for 10: independent/hands-on confirmation that the OpenAPI repo is current and complete, and a direct in-docs discoverable openapi.json endpoint (probe found only 404s for openapi.json-style paths on the docs domain itself).

   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”
   • [claimed-docs] “"Adyen makes documentation accessible to developers as well as the software and AI tools they create." Documented agent-docs surface: llms.t…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.adyen.com/llms.txt # Adyen Docs > Developer and merchant documentation for Adyen payments, Adyen f…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”

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

   Adyen documents a dedicated test environment for the full integration (client- and server-side) using test credentials before going live, and this test environment is explicitly wired into AI-native workflows via the Adyen MCP server which runs with `--env=TEST` (or LIVE with a live prefix), letting an AI agent exercise Checkout, payment links, and modification tools against sandbox data. Missing for 10: no independent/hands-on confirmation that sandbox test data is fully isolated from production, and no detail on seeding/resetting sandbox state for repeatable AI-driven test runs.

   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Our Model Context Protocol (MCP) server lets you use natural language with your chosen Large Language Model (LLM) client.”

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

   The evidence pack covers API idempotency, webhooks, credentials, OpenAPI specs, and agentic commerce integrations, but contains no documentation of API versioning scheme or a deprecation policy for older API versions. Versioning/deprecation policy is a standard and fair axis for a payments API platform, so absence of evidence yields 'none'.

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

   Adyen documents concrete bulk operations in its agentic Product Feed API — batch ingest of up to 200 items per call and batch delete of up to 200 products per call — which is genuine 'many items at once' functionality for AI-platform inventory sync. However, evidence of bulk operations elsewhere in the platform (e.g., bulk payouts, bulk refunds/modifications, bulk reporting exports, or MCP tools operating on many resources at once) is absent; the MCP tool list is single-item oriented (create one session, one payment link, one refund). Missing for 10: bulk support evidenced across other core domains (payments, payouts, platforms/onboarding) and bulk-capable MCP tools, not just the product feed.

   • [claimed-docs] “You can upload batches of information about your inventory to Adyen, and we will synchronize it with AI platforms.”
   • [claimed-docs] “The Adyen Product Feed API is "a centralized product knowledge hub that synchronizes your inventory with AI platforms" via asynchronous batc…”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”

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

   Adyen documents a genuine rules mechanism — the risk management rule builder lets you 'create, backtest, and label custom rules' that automatically trigger block/allow/review actions on each transaction event (adyen-docs-20, adyen-docs-28, adyen-docs-48), and webhooks notify on async status-change events (adyen-docs-3/17). This satisfies the core 'rule triggers action on event' pattern, but only within the fraud/risk-decisioning domain, not as a general-purpose automation/workflow engine, and there's no evidence of AI-native rule authoring (e.g., via the MCP server or natural language) for these rules. Missing for 10: general cross-domain event-action automation beyond fraud rules, AI/LLM-driven rule creation or triggering, and independent evidence of real-world use of the rule builder.

   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”
   • [claimed-docs] “Each payment goes through a risk evaluation. The risk evaluation reaches a decision that results in an action to block, allow, or review the…”
   • [claimed-docs] “You can detect, monitor, and mitigate fraud using Protect, Adyen's risk management system.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”

   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

Ai billing ops

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

   weight 3 · round drawn
   Adyen~partialclaimed5/10

   Adyen provides the raw building blocks an agent could use—webhooks for status changes (adyen-docs-3/17/45), refusal-reason detail on failed payments (adyen-docs-7), idempotent retries (adyen-docs-4/25), and an MCP server exposing webhook list/get/test and payment tools (adyen-supp-mcp-tools)—but there is no documented dunning/subscription-retry feature, automated outreach mechanism, or agent workflow specifically for failed-payment recovery. Missing for 10: native dunning/retry orchestration, recurring-billing failed-payment workflow, and evidence of an agent actually driving retries/outreach rather than just monitoring raw webhook/API data.

   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”

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

   Adyen's API and MCP server cover payments, payment links, checkout sessions, and payouts, but there is no evidence of any 'product' or 'price' resource concept (billing/catalog objects like Stripe's Products/Prices) that an agent could provision alongside a payment link — Adyen is a payments processor, not a billing/invoicing product catalog system. The only 'product' references are to inventory feeds for agentic commerce (syncing existing catalog to AI platforms), not creating new products/prices via API. missing for 10: evidence of a Products/Prices API or equivalent billing object model, evidence of a single-session workflow that creates a product+price+payment link together, any documentation of provisioning billing entities (not just payment links) via API or MCP.

   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Offer payment links.”
   • [claimed-docs] “The Adyen Product Feed API is "a centralized product knowledge hub that synchronizes your inventory with AI platforms" via asynchronous batc…”

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

   Adyen's evidence covers payment links, checkout, platforms, payouts, and agentic commerce, but there is no mention of a hosted invoicing product, invoice generation, or automatic payment reminders anywhere in the pack — only generic 'payment links' (adyen-docs-24) which is a different capability.

   • [claimed-docs] “Offer payment links.”

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

   The evidence pack covers payments, payouts, webhooks, idempotency, risk management, platforms/marketplace payouts, and agentic commerce, but contains no mention of subscription billing, dunning management, automatic retry logic for failed recurring payments, or recovery emails. This is a plausible axis for a payments platform, but nothing in the docs or community evidence shows Adyen offering smart dunning/recovery workflows.

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

   Adyen's evidence pack covers payments, payouts, platforms, risk, reporting, and agentic commerce, but there is no mention of subscription/recurring billing constructs like plans, trial periods, upgrades/downgrades, or proration—these are the domain of a billing/subscription-management layer (e.g. Adyen has separate tooling or partners for this) not documented here.

   ⚑ 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
   Adyen!disputedcontradicted4/10

   Adyen's docs describe a fast technical integration (single /sessions call, test-then-go-live flow, no setup fees) that could suggest same-day acceptance, but independent community reports concretely contradict a founder's ability to just sign up and start accepting payments quickly: Adyen reportedly refuses small clients ('under the million'), requires large reserves for subscription businesses, and one user describes a multi-hundred-hour integration effort before abandoning it. These are hands-on, specific counter-examples, not generic skepticism, so the 'within a day' claim is disputed rather than simply partial. Missing for 10: any evidence of Adyen actually onboarding a small/new founder-level merchant same-day, or a rebuttal to the reserve/minimum-volume gating reports.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Pay per transaction, with no setup or monthly fees.”
   • [community] “Adyen refuses small clients, under the million :/”
   • [community] “One of the bigger drawbacks of Adyen vs Stripe... they require a crazy reserve (in the millions) if your model is subscription based, to be …”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”
   • [community] “Adyen's pricing model looks much more attractive on paper, but the integration complexity and minimum processing volumes usually keep early-…”

   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 Adyen
   Adyen✓fullcommunity8/10

   Adyen's Web/mobile Drop-in and Components let developers embed sessions-based payment UI directly in their own site/app (web, iOS, Android, React Native, Flutter) with customizable styling and localization, rather than redirecting to a hosted page. This is a core, well-documented capability with sample flows (create session, mount Components) and cross-platform SDK support. Missing for 10: independent hands-on confirmation of embedding ease (community feedback is mixed/critical on integration complexity), and no detailed code-level customization examples in the pack.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [claimed-docs] “Customize the styling of your checkout.”
   • [claimed-docs] “Customize the styling of your checkout. Present your payment form in the local language of your shoppers with our localization support.”
   • [claimed-docs] “With the client key, you have: A single key for all your allowed origins in an environment.”
   • [community] “I implemented Adyen for a company I was consulting for. I liked it. Their integration was not as terrible as many here make it seem. It allo…”

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

   Adyen explicitly offers hosted 'payment links' that developers can generate and redirect customers to without building payment UI (adyen-docs-24), and the MCP tool surface confirms this as a first-class API capability (create/get/expire payment links) (adyen-supp-mcp-tools). However, Adyen's primary integration path emphasized in the docs is the Sessions/Components client-side flow which requires building or embedding UI (adyen-docs-1), and there is no detailed documentation on conversion-optimization specifics of the hosted page itself. Missing for 10: dedicated documentation describing the hosted checkout page's design/conversion features, independent evidence of its effectiveness, and clarity on it being the recommended 'no-code UI' path rather than a secondary option.

   • [claimed-docs] “Offer payment links.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”

   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 to PayPal
   Adyen!disputedcontradicted4/10

   Adyen's docs confirm a payment-links feature exists ("Offer payment links" - adyen-docs-24) and a Customer Area dashboard for managing transactions (adyen-docs-16), but there is no evidence of a self-serve, no-code flow a founder can use to instantly start selling. Community reports concretely contradict the 'start immediately' premise for founders: Adyen is described as refusing small clients ('Adyen refuses small clients, under the million' - adyen-comm-1) and requiring underwriting/minimum volumes that keep early-stage startups away ('integration complexity and minimum processing volumes usually keep early-stage startups on Stripe' - adyen-comm-11), unlike a turnkey signup-and-sell experience. missing for 10: documented self-serve onboarding flow for small merchants, step-by-step dashboard payment-link creation, evidence that a founder can go live without a sales/underwriting process.

   • [claimed-docs] “Offer payment links.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [community] “Adyen refuses small clients, under the million :/”
   • [community] “Adyen's pricing model looks much more attractive on paper, but the integration complexity and minimum processing volumes usually keep early-…”

   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 drawn
   Adyen✓fullcommunity8/10

   Adyen docs explicitly promise 'one integration' covering all preferred payment methods (wallets, local methods, BNPL) via a single Checkout API/sessions flow, with community corroboration that it supports native local methods like iDEAL and Sofort. Missing for 10: an explicit itemized list of Apple Pay/Google Pay/BNPL support and independent hands-on confirmation of wallet/BNPL specifically (only general local-method corroboration exists), plus some community friction reports on integration complexity.

   • [claimed-docs] “Offer your customers all their preferred payment methods with a single integration.”
   • [claimed-docs] “One integration Offer your customers all their preferred payment methods with a single integration.”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Your server makes three Checkout API requests: /paymentMethods, /payments, and /payments/details.”
   • [community] “I implemented Adyen for a company I was consulting for. I liked it. Their integration was not as terrible as many here make it seem. It allo…”

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

   Adyen's Checkout API/sessions flow shows card data handled client-side and passed via Adyen's hosted fields/client key rather than touching the merchant's server (adyen-docs-1, adyen-docs-44), which implies the tokenization pattern developers rely on for reduced PCI scope. However, none of the evidence explicitly discusses PCI DSS, SAQ levels, or scope-reduction guidance, so the compliance benefit is only inferable from the technical integration pattern, not documented directly. missing for 10: explicit PCI DSS scope-reduction documentation, SAQ-A eligibility guidance, independent compliance certification evidence.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “With the client key, you have: A single key for all your allowed origins in an environment.”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”

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

   Adyen explicitly documents idempotency-key headers for retrying API requests without duplicate side-effects (adyen-docs-4, adyen-docs-25), directly matching the story. Missing for 10: independent/hands-on developer confirmation of idempotency behavior in production and detail on key expiration/edge cases.

   • [claimed-docs] “To submit a request for idempotent processing, send a request with the `idempotency-key:` in the header.”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”

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

   Adyen documents webhook event logs in the Customer Area (adyen-docs-45) and general webhook mechanics to avoid polling (adyen-docs-3/17), plus an MCP tool to 'test' webhooks (adyen-supp-mcp-tools) that hints at replay tooling. However, the evidence pack never explicitly documents HMAC/signature verification for webhook payloads, an automatic retry policy for failed webhook deliveries, or a dedicated replay mechanism. Missing for 10: explicit signed-webhook (HMAC) verification docs, documented automatic retry/backoff schedule for webhook delivery, and a concrete replay/redeliver feature beyond the vague MCP 'test' tool.

   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for…”
   • [claimed-docs] “With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “To submit a request for idempotent processing, send a request with the `idempotency-key:` in the header.”
   • [claimed-docs] “The Adyen API supports idempotency, allowing you to retry a request multiple times while only performing the action once.”

   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 PayPal
   Adyen!disputedcontradicted4/10

   Adyen's docs describe a clear-looking integration path (single /sessions call or paymentMethods/payments/payments/details flow, testing, webhooks) and multi-platform SDK support (web, iOS, Android, React Native, Flutter), but no evidence pack item actually shows copy-paste code samples per language, and independent hands-on reports directly contradict the 'under a day' claim: one integrator says 'after hundreds of hours invested, we ditched Adyen' and another states 'Stripe beats Adyen on ease of integration... hands down,' while a third calls it 'much more bare metal' than turnkey competitors. A counter-report says the integration 'was not as terrible as many here make it seem,' so the picture is mixed rather than uniformly negative. missing for 10: actual copy-paste language-specific code samples in the evidence, a documented time-to-first-payment benchmark, and independent confirmation that integration is fast rather than the reported multi-hundred-hour effort.

   • [claimed-docs] “Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side appl…”
   • [claimed-docs] “Your server makes three Checkout API requests: /paymentMethods, /payments, and /payments/details.”
   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Support online payments for web, iOS, Android, React Native, or Flutter.”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”
   • [community] “I implemented Adyen for a company I was consulting for. I liked it. Their integration was not as terrible as many here make it seem. It allo…”
   • [community] “Adyen is much more 'bare metal.' Think more like a modern Authorize.net. Nobody comes close to Stripe's turnkey developer-friendliness.”
   • [community] “Adyen's pricing model looks much more attractive on paper, but the integration complexity and minimum processing volumes usually keep early-…”

   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 Adyen
   Adyen~partialcommunity6/10

   Adyen documents a dedicated test environment with test credentials for exercising different transaction types (adyen-docs-18), recommends testing the full client+server integration before going live (adyen-docs-6), and documents refusal reasons/result codes for simulating declines (adyen-docs-7). However, the pack lacks explicit documentation of test cards for disputes/chargebacks specifically, or a catalog of scenario-specific test cards, and community evidence notes real-world integration friction (adyen-comm-9) though not specifically about sandbox fidelity. Missing for 10: explicit dispute/chargeback simulation test cards, a documented full test-card matrix, and independent hands-on confirmation that sandbox mirrors production behavior.

   • [claimed-docs] “We recommend testing your full integration, including the client-side and server-side parts, in your test environment before accepting live …”
   • [claimed-docs] “Test the different types of transactions with Adyen that your integration handles using test credentials.”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”

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

   The evidence pack contains no mention of a Disputes API, chargeback evidence submission, or any agent/MCP workflow for handling disputes end-to-end—only risk/fraud detection (Protect), refusal reasons, and unrelated agentic-commerce checkout flows are documented. The MCP server's tool list (sessions, payment links, modifications, management API) explicitly does not include dispute retrieval or evidence submission.

   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “You can detect, monitor, and mitigate fraud using Protect, Adyen's risk management system.”
   • [claimed-docs] “Each payment goes through a risk evaluation. The risk evaluation reaches a decision that results in an action to block, allow, or review the…”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”

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

   The evidence pack covers Adyen's risk/fraud tooling (Protect, rule builder, ML fraud detection) but contains no documentation of a chargeback/dispute management API, structured evidence submission, or dispute lifecycle tracking/status workflow. A vague community comment says Stripe beats Adyen on chargebacks 'hands down' but gives no concrete detail to substantiate a documented-capability failure, so it doesn't rise to a disputed claim — it simply reinforces the absence of positive evidence.

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

   Adyen's Protect risk management system explicitly provides ML-based fraud scoring plus a rule builder to create, backtest, and label custom rules, with risk evaluations resulting in block/allow/review actions — directly matching the story. Missing for 10: independent/hands-on validation of the rule builder UX and finance-ops-specific workflow evidence beyond first-party docs.

   • [claimed-docs] “You can detect, monitor, and mitigate fraud using Protect, Adyen's risk management system.”
   • [claimed-docs] “Create, backtest, and label custom rules with a rule builder interface | Machine learning powered fraud detection using global transaction d…”
   • [claimed-docs] “Machine learning powered fraud detection using global transaction data | | | Create, backtest, and label custom rules with a rule builder in…”
   • [claimed-docs] “Each payment goes through a risk evaluation. The risk evaluation reaches a decision that results in an action to block, allow, or review the…”
   • [claimed-docs] “Adyen Uplift is the platform's AI optimization layer: "Adyen Uplift helps you strike a balance between conversion, risk and cost. You get re…”

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

   Evidence confirms API-level refund capability (Adyen's Management/Checkout 'modifications' API allows refunding a captured payment, and the MCP tool set explicitly includes 'refund a captured payment') and dashboard access to transaction management via the Customer Area, but no citation explicitly confirms partial-refund amount support or a documented dashboard refund button/workflow. missing for 10: explicit documentation of partial refund support (specifying an amount less than the captured total), explicit dashboard refund action screenshot/flow, and any independent/hands-on confirmation that refunds work as described.

   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “When the payment or modification request is unsuccessful, the `resultCode`, `refusalReason`, and `refusalReasonCode` describe the issue.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “In your Customer Area, you can find a log of all webhook events sent to your server.”

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

   Adyen documents accepting local payment methods/currencies, configuring multiple payout currencies per merchant account, and both local (no SWIFT fee) and cross-border (SWIFT) settlement options, plus flexible payout timing/currency choice — directly supporting charge-local/settle-in-own-currency workflows. However, there's no explicit documentation of FX rate transparency (e.g., disclosed markup, real-time rate reporting) beyond the currency/payout mechanics themselves. Missing for 10: explicit FX rate/markup transparency documentation, independent confirmation of settlement FX handling in practice.

   • [claimed-docs] “Local payouts are faster and avoid SWIFT fees. You need a local bank account in a country that uses that specific currency as the legal tend…”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “This means you have the option to change how you get paid for each of your merchant accounts.”

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

   Adyen's evidence pack is entirely about payment processing, payouts, platforms, risk management, and agentic-commerce integrations — nothing addresses tax calculation, VAT/GST determination, tax collection, or tax compliance/remittance features. This axis applies since a payments platform could plausibly integrate tax calculation, but no evidence shows Adyen offers this.

   ⚑ 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 PayPal
   Adyen~partialprobed5/10

   Adyen exposes extensive Management/Checkout/Platforms APIs covering payments, onboarding, payouts, webhooks, credentials, terminals, and even an MCP server wrapping many of these APIs, suggesting broad API/UI parity for core payment operations. However, some UI-only surfaces (Customer Area account/transaction overview, visual reporting dashboards) are described only as UI features with no explicit statement that every dashboard/report/action is also API-accessible, and no full OpenAPI spec was reachable at standard docs endpoints (404s), only a separate GitHub repo. Missing for 10: explicit parity claim or evidence that all Customer Area/reporting/dashboard actions have API equivalents, and a verified complete OpenAPI coverage confirmation.

   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “You can also create multiple API credentials to improve security and control access.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”
   • [claimed-docs] “Adyen API credentials are scoped by construction: each credential carries "Roles: Permissions that define what the credential is allowed to …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.adyen.com/openapi.json, https://docs.adyen.com/swagger.json, https://docs.adyen.com/api…”
   • [claimed-docs] “The Adyen OpenAPI Specification repository (github.com/Adyen/adyen-openapi) "contains OpenAPI specifications for every public API Adyen offe…”

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

   The evidence pack shows reporting dashboards and general documentation transparency (llms.txt, markdown docs, OpenAPI specs) but nothing about a merchant being able to export their own transactional/account data in open formats or close their account and leave without lock-in. Reporting is described as visual dashboards (adyen-docs-10), not bulk open-format export, and no data-portability/account-closure mechanism is documented.

   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [community] “Longtime Stripe user did about a year-long stint with Adyen. Stripe beats Adyen on ease of integration, ease of using the back office, charg…”

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

   The evidence pack describes payouts, payout frequency, currencies, and a dashboard 'visual representation' of balances/payouts (adyen-docs-9,10,12,30,43), but nowhere documents an API for pulling balance/transaction-level data or a reconciliation workflow that an agent could invoke — the MCP tool list (adyen-supp-mcp-tools) covers checkout, payment links, and management API objects (merchants, terminals, webhooks, credentials) with no balance-transaction or reconciliation tools. Missing for 10: documented Balance/Transaction API endpoints, evidence of agent/MCP access to payout reconciliation data, and any reconciliation workflow example.

   • [claimed-docs] “Adyen supports paying out to cards instantly, and immediately returns the result of the payout attempt.”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”
   • [claimed-docs] “The Adyen MCP server (github.com/Adyen/adyen-mcp, Alpha) runs locally via `npx -y @adyen/mcp --env=TEST` (or `--env=LIVE --livePrefix=YOUR_P…”

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

   Docs clearly support configuring payout frequency, currency, and timing per merchant account (adyen-docs-12, adyen-docs-30, adyen-docs-50, adyen-docs-22) and note local vs cross-border payout mechanics (adyen-docs-13, adyen-docs-43). Reporting is mentioned as giving a 'visual representation of balances, sales, and payouts' (adyen-docs-10) and the Customer Area gives an overview of payment channels (adyen-docs-16), but there is no explicit evidence of a line-item payout reconciliation report breaking down which specific charges, fees, and refunds compose each payout. Missing for 10: detailed payout reconciliation report/API showing per-payout transaction breakdown, fee itemization, and refund matching.

   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “This means you have the option to change how you get paid for each of your merchant accounts.”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “Local payouts are faster and avoid SWIFT fees. You need a local bank account in a country that uses that specific currency as the legal tend…”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”

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

   Adyen's reporting docs mention a dashboard 'visual representation of your balances, sales, and payouts' and configurable payout frequency/currency, implying some settlement reporting exists, but nothing in the evidence describes itemized reconciliation reports that break out fees, refunds, and chargebacks against bank deposits. Missing for 10: documented settlement/reconciliation report format, explicit fee/refund/chargeback itemization, and any bank-deposit matching workflow or independent confirmation it works as needed.

   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Manage your account and transactions from our Customer Area, which shows an overview of all your payment channels.”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “Flexible payouts Choose when and in which currency you want to settle.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”

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

   Adyen for Platforms is explicitly documented to onboard sellers/contractors with verification (adyen-docs-11, adyen-docs-31, adyen-docs-36), split payments between parties and hold funds until payout (adyen-docs-21, adyen-docs-37), and configure flexible payout frequency/currency/local vs cross-border payouts (adyen-docs-12, adyen-docs-13, adyen-docs-22, adyen-docs-43, adyen-docs-50). Reporting/dashboards and risk management further round out the marketplace platform story (adyen-docs-10, adyen-docs-8). missing for 10: independent/hands-on developer account of building a full marketplace integration end-to-end, and more granular API-level detail (e.g., specific split-payment API request/response schemas) beyond docs summaries.

   • [claimed-docs] “Onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out.”
   • [claimed-docs] “Process payments: accept payments on behalf of your users using Adyen's payment processing platform. You can split the payments between one …”
   • [claimed-docs] “Onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before paying out. Adyen informs you of th…”
   • [claimed-docs] “Onboard and verify your users: onboard sellers, service providers, or contractors on to your platform, and let Adyen verify them before payi…”
   • [claimed-docs] “You can split the payments between one or more users, deduct costs as needed, and hold funds until payout.”
   • [claimed-docs] “You can configure the payout frequency for each of your merchant accounts.”
   • [claimed-docs] “Local payouts are faster and avoid SWIFT fees. You need a local bank account in a country that uses that specific currency as the legal tend…”
   • [claimed-docs] “You can configure multiple payout currencies for each merchant account.”
   • [claimed-docs] “You can receive payouts in two ways: Local payout ... Cross-border payout: We send funds through SWIFT.”
   • [claimed-docs] “Allow your users to easily sign up, sell, and receive payments all within one solution.”
   • [claimed-docs] “This means you have the option to change how you get paid for each of your merchant accounts.”
   • [claimed-docs] “Get a visual representation of your balances, sales, and payouts.”

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

   The evidence pack contains no mention of data residency, regional data storage options, or any control over where Adyen stores payment/customer data. While this is a fair question for a payments platform (compliance/data-residency is a common enterprise requirement), nothing in the docs, community posts, or agentic-commerce material addresses it.

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

   Adyen's evidence pack covers payments, payouts, risk management, and agentic commerce integrations, but there is no documentation on data retention policies, data deletion requests, or user/API-level controls to manage how long payment or transaction data is stored or how to purge it. This is a fair axis for a payments platform handling PII/PCI data, but no evidence addresses it.

   ⚑ 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

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

   weight 2 · round drawn
   Adyen—none0/10

   Adyen ships AI-native tooling (an MCP server, docs-for-LLMs surface, agentic commerce APIs) so a privacy-posture question about telemetry/usage-tracking opt-out is a fair axis to ask, but no evidence in the pack describes any telemetry collection by these tools or any opt-out mechanism for it.

   ⚑ flag

   PayPal—none0/10

   No evidence of any telemetry opt-out or usage tracking controls for AI-native users; PayPal's docs focus on payments APIs, and community items discuss account freezes/disputes, not telemetry settings.

   ⚑ flag