Stripe vs Adyen
usage-based · enterprise-custom
·usage-based · enterprise-custom
Stripe wins · 34–4 (10 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to AdyenStripe hosts a live llms.txt (probe confirms HTTP 200 with agent-oriented guidance), a full .md-suffixed docs mirror (docs.stripe.com/*.md), a machine-readable skills index at /.well-known/skills/index.json, and dedicated agent-oriented docs (agents.md, mcp.md, directory.md) explicitly designed for pointing agents at. This is independently verified by probes, not just vendor claims. missing for 10: no independent third-party (non-Stripe) report of an agent successfully consuming llms.txt end-to-end in production.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
- [claimed-docs] “Stripe publishes a machine-readable agent-skills catalog: "You can use curl to fetch the index of available skills, what they do, and their …”
- [probe] “PROBE skills-index (2026-09-14): GET https://docs.stripe.com/.well-known/skills/index.json returns HTTP 200 with 8 Stripe-maintained agent s…”
- [claimed-docs] “Build your integration with agent-first developer tools, charge your users for AI features with usage-based billing, and let agents transact…”
- [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe's kno…”
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…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to StripeStripe's CLI and Workbench Shell provide scriptable, non-interactive access (stripe sandbox create, stripe products create, stripe listen, agent setup) usable in CI pipelines, backed by idempotency keys, restricted API keys, and a documented sandbox that requires no account registration — all designed for headless/automated use including by coding agents. missing for 10: no explicit first-party CI example (e.g. GitHub Actions workflow) or independent hands-on report of running the CLI in a CI pipeline.
- [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
- [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
- [claimed-docs] “A sandbox is an isolated test environment. You can use your sandbox to test Stripe functionality in your account, and experiment with new fe…”
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 …”
ai-native userConnect an agent via an official MCP server
weight 3 · round to StripeStripe ships a well-documented, independently probed official hosted MCP server (mcp.stripe.com) exposing API tools, analytics, and knowledge-base search, with OAuth-based auth/governance, human-confirmation for write actions, and connected-account support; a live probe confirms the OAuth-gated endpoint is real and functioning. Missing for 10: no independent third-party hands-on review of actual agent usage beyond Stripe's own docs/probes.
- [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe's kno…”
- [claimed-docs] “Let your AI agents interact with the Stripe API by using our MCP server.”
- [probe] “official MCP server documented at https://docs.stripe.com/mcp”
- [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
- [claimed-docs] “MCP access is governed like any credential: OAuth per the MCP spec ("OAuth lets you grant and revoke access without sharing an API key with …”
- [claimed-docs] “Docs, "Use MCP with connected accounts": a Connect platform "can also use MCP to retrieve or update resources for your connected accounts...…”
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…”
ai-native userUse an official CLI
weight 2 · round to StripeStripe ships a well-documented official CLI (docs.stripe.com/stripe-cli) for building, testing, and managing integrations, explicitly positioned as 'agent-ready tooling' with commands like `stripe agent setup` (auto-configures Claude Code/Codex/Cursor), `stripe sandbox create` for keyless agent provisioning, `stripe directory search`, and `stripe projects init`. This is corroborated by an independent probe confirming the docs page exists and by Workbench's browser-based Shell mirroring CLI commands. Missing for 10: independent hands-on/community review specifically validating CLI usability for AI-native workflows beyond Stripe's own docs.
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
- [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
- [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
- [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
- [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
- [claimed-docs] “Stripe Projects "provisions and manages third-party services (such as hosting, databases, auth, AI, and observability) from the terminal. Ru…”
- [claimed-docs] “"Stripe Directory helps developers and AI agents find the best external providers for a task and follow the best supported path to provision…”
ai-native userDrive the product through a documented public API
weight 3 · round drawnStripe exposes a comprehensive, well-documented REST API with idempotency, restricted keys, versioning, sandboxes, webhooks, OpenAPI-generated SDKs, and CLI/Workbench tooling, and this is independently corroborated by a probe confirming the API and llms.txt are live and reachable. missing for 10: no independent third-party benchmark of raw API completeness beyond docs/probes, and OpenAPI spec discovery via well-known paths returned 404s per stripe-probe-3.
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “use an idempotency key... you can safely repeat the request without risk of creating a second object or performing the update twice”
- [claimed-docs] “Stripe uses API keys to authenticate requests from your integration and determine which Stripe resources it can access.”
- [claimed-docs] “A restricted API key (RAK) is an API key ... a RAK can do only what you give it permission to do.”
- [claimed-docs] “You can safely upgrade to a new monthly release without breaking any existing code.”
- [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
- [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
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…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to StripeStripe explicitly documents restricted API keys (RAKs) as the recommended least-privilege credential for AI agents—developers select per-resource Read/Write/None permissions—and pairs this with MCP OAuth sessions (per-client revocation, connected-account scoping via Stripe-Account header, human confirmation for write actions like refunds, and Workbench tool-call logs), giving concrete scoped-credential issuance and governance for agents. This is corroborated by a live probe confirming the OAuth-gated MCP endpoint. Missing for 10: independent/hands-on developer confirmation of the RAK issuance workflow in practice beyond first-party docs.
- [claimed-docs] “A restricted API key (RAK) is an API key ... a RAK can do only what you give it permission to do.”
- [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
- [claimed-docs] “MCP access is governed like any credential: OAuth per the MCP spec ("OAuth lets you grant and revoke access without sharing an API key with …”
- [claimed-docs] “Docs, "Use MCP with connected accounts": a Connect platform "can also use MCP to retrieve or update resources for your connected accounts...…”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
- [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
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.”
ai-native userBuild against official SDKs
weight 2 · round to StripeStripe publishes official SDKs/client libraries generated from OpenAPI specs, plus AI-native additions like @stripe/agent-toolkit, @stripe/ai-sdk, token-meter, a hosted OAuth-gated MCP server, agent plugins for Claude/Codex/Cursor, and a machine-readable skills catalog — strongly evidencing an AI-native developer can build against official SDKs. missing for 10: independent (non-Stripe) hands-on developer reports specifically validating the newer agent-toolkit/ai-sdk packages in production.
- [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
- [claimed-docs] “The stripe/ai repo (github.com/stripe/agent-toolkit now redirects here) is "the one-stop shop for building AI-powered products and businesse…”
- [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
- [claimed-docs] “Stripe publishes a machine-readable agent-skills catalog: "You can use curl to fetch the index of available skills, what they do, and their …”
- [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
- [probe] “PROBE skills-index (2026-09-14): GET https://docs.stripe.com/.well-known/skills/index.json returns HTTP 200 with 8 Stripe-maintained agent s…”
- [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API and search Stripe's kno…”
- [github] “a collection of SDKs to help you integrate Stripe with LLMs and agent frameworks”
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…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnStripe supports registering HTTPS webhook endpoints that push real-time events (payment success, disputes, subscription renewals, etc.), and this is directly usable by AI agents via the MCP server's stripe_api_write tool (webhook endpoint creation is explicitly listed as a supported MCP method) and via event-destinations delivering to multiple destination types. missing for 10: no hands-on/independent example of an agent actually subscribing to and consuming webhook events end-to-end, and no dedicated agent-specific webhook subscription API distinct from the standard developer webhook flow.
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
- [claimed-docs] “After you register a webhook endpoint, Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”
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…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnStripe supports AI-generated insights primarily through its MCP `stripe_analytics`/`stripe_report` tools, which let an AI agent query metrics like MRR, churn rate, and run custom SQL against reporting tables, and Radar applies AI algorithms to score fraud risk in real time. However, these insights are largely agent-mediated (via MCP) rather than a native in-Dashboard AI assistant proactively surfacing suggestions to the user. Missing for 10: evidence of a built-in conversational/insights UI inside the Dashboard itself (not just via external agent+MCP), broader proactive 'suggestions' beyond analytics queries, and independent/hands-on validation of insight quality.
- [claimed-docs] “You can use an AI agent to analyze aggregated data across your Stripe account ... query metrics such as monthly recurring revenue (MRR)”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
- [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
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.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to StripeStripe ships substantial infrastructure for background automation — webhooks that push real-time events for asynchronous processing, Billing's automated recurring payments/renewals, Smart Retries and revenue-recovery automation that requires no code, Radar's automatic fraud scoring, and an MCP server plus agent plugins that let AI agents act on Stripe data continuously. However, Stripe explicitly gates autonomous execution: 'Stripe requires human confirmation before it takes certain stripe_api_write actions, such as refunds and outbound payments,' meaning fully unattended agentic automation is capped for sensitive operations, and there's no independent/hands-on evidence of long-running autonomous background agent workflows in production. Missing for 10: evidence of fully unattended agent automations without human-in-the-loop gating, and independent corroboration of real-world background agent runs.
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
- [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
- [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
- [claimed-docs] “"Machine payments let agents pay for APIs and services programmatically. Your server returns a payment challenge, the agent presents a valid…”
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…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnStripenone0/10The evidence pack shows Stripe exposing an MCP server, CLI, SDKs, and agent plugins so *external* AI agents (Claude, Codex, Cursor, etc.) can act on Stripe's behalf, and it describes AI-driven backend features (Radar fraud scoring, smart retries). But none of the evidence describes a built-in, in-product AI assistant/chat feature embedded in the Stripe Dashboard itself that a user converses with to delegate tasks — the 'analyze with AI' and analytics tooling are also delivered via the external MCP interface rather than a native assistant UI.
- [claimed-docs] “You can use an AI agent to analyze aggregated data across your Stripe account ... query metrics such as monthly recurring revenue (MRR)”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
Adyennone0/10Adyen 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…”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnStripe exposes an MCP server plus Directory/Analytics tools that let AI agents perform natural-language-driven actions (search products, read/write API resources, query MRR, run implementation planner) confirmed live via probe, and CLI/agent-plugin tooling lets coding agents set up sandboxes and integrations via NL prompts. However, this is agent-mediated (a separate AI agent translates NL into MCP/CLI calls) rather than the product itself having a native NL command interface, and write actions require human confirmation clicks rather than pure NL operation. missing for 10: evidence of a first-party conversational NL interface within Stripe's own Dashboard/product (not via third-party agent), and confirmation that full workflows can complete end-to-end via NL without manual approval steps.
- [probe] “PROBE mcp-oauth (2026-09-14): keyless JSON-RPC initialize to https://mcp.stripe.com answers HTTP 401 {"error":"Unauthorized. See https://doc…”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “Official agent plugins bundle MCP + skills with auto-update: "Stripe's agent plugins give your AI agent access to Stripe developer tools, li…”
- [claimed-docs] “Stripe's agent plugins give your AI agent access to Stripe developer tools, live account data, and the latest skills and technical guidance.”
- [claimed-docs] “"Stripe Directory helps developers and AI agents find the best external providers for a task and follow the best supported path to provision…”
- [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
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”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to StripeStripe's Workbench includes an in-Dashboard API Explorer/Shell that lets users visually explore API resources and execute real, runnable API calls (including against sandboxes), and Workbench's shell exposes CLI/API autocompletion — this is a genuine interactive, runnable API reference. However, evidence doesn't show a public-facing interactive API reference page (like a standalone docs.stripe.com/api with try-it-now runnable code snippets) accessible without Dashboard login, nor independent/community confirmation of the experience quality. missing for 10: evidence of a public runnable API reference outside the authenticated Dashboard, independent/hands-on user reviews of the API explorer experience, confirmation that all endpoints are runnable (not just Shell CLI-style commands).
- [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
- [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
Adyennone0/10The 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…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnStripe publishes machine-readable OpenAPI spec files explicitly for generating SDKs/clients (stripe-docs-46, github.com/stripe/openapi), and docs.stripe.com also serves machine-readable .md versions of every doc page plus an llms.txt index (stripe-probe-1, stripe-probe-2), directly serving AI-native consumption needs. However, a direct openapi.json/swagger.json was not found at the docs.stripe.com domain itself (stripe-probe-3 shows 404s on guessed paths), meaning discovery requires knowing the separate GitHub repo rather than a single canonical documented download link. Missing for 10: a first-party documented URL/endpoint for the OpenAPI spec directly from docs.stripe.com (not just GitHub), and independent hands-on confirmation of spec completeness/versioning.
- [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/payments.md # Payments Use Stripe to start accepting payments. ## Get started Integrat…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to StripeStripe documents a dedicated sandbox environment isolated from live/production data (stripe-docs-32, stripe-docs-43, stripe-docs-57), test cards/values that simulate transactions without moving real funds (stripe-docs-10, stripe-docs-65), and anonymous sandbox provisioning explicitly for coding agents via CLI (stripe-docs-16), plus MCP/Workbench access scoped per sandbox vs live mode (stripe-supp-mcp-sessions-governance, stripe-supp-workbench-shell). Missing for 10: independent hands-on confirmation from a third party that agent-driven sandbox testing works end-to-end without friction.
- [claimed-docs] “A sandbox is an isolated test environment. You can use your sandbox to test Stripe functionality in your account, and experiment with new fe…”
- [claimed-docs] “You can use your sandbox to test Stripe functionality in your account, and experiment with new features without affecting your live integrat…”
- [claimed-docs] “Your team can test in separate sandboxes to make sure that data and actions are completely isolated from other sandboxes.”
- [claimed-docs] “Test your integration in a sandbox ... by simulating transactions with test values—these transactions don't move funds.”
- [claimed-docs] “Test cards act as "fake" credit cards, and allow you to simulate the following scenarios: - Successful payments... - Card errors due to decl…”
- [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
- [claimed-docs] “MCP access is governed like any credential: OAuth per the MCP spec ("OAuth lets you grant and revoke access without sharing an API key with …”
- [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
- [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
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.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to StripeStripe documents a clear API versioning policy: monthly releases contain only backward-compatible changes, and users can safely upgrade without breaking existing code, with explicit versioning docs. This directly matches the story's requirement of versioned APIs with a documented deprecation/compatibility policy. Missing for 10: no explicit deprecation timeline/sunset schedule detail or independent hands-on verification of long-term version support beyond the docs' own claims.
- [claimed-docs] “You can safely upgrade to a new monthly release without breaking any existing code.”
- [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
Adyennone0/10The 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'.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnStripe supports some bulk-style operations relevant to AI agents — bulk product catalog import via the v2 Product Catalog Import API (CSV up to 4GB, upsert/replace modes), List CheckoutSessions for bulk fulfillment, and MCP/analytics tools that can query/report across many objects (stripe_analytics, stripe_report) — but there is no documented generic bulk-write or batch-update API (e.g., bulk refunds, bulk subscription updates, bulk customer edits) that an AI agent could invoke across many arbitrary items at once; most single-object write tools (stripe_api_write, Refunds API, etc.) operate one record at a time with idempotency keys rather than true batch semantics. missing for 10: a documented bulk/batch API for core objects (customers, charges, subscriptions, refunds) beyond catalog import, evidence of MCP or CLI tools performing multi-item operations in one call, and independent/hands-on confirmation of bulk operation reliability.
- [claimed-docs] “Agentic Commerce Suite ingests full product catalogs as bulk CSV imports via the v2 Product Catalog Import API: POST /v2/commerce/product_ca…”
- [claimed-docs] “Orders placed through AI chat agents flow through standard Stripe rails: "Stripe sends checkout.session.completed after the agent completes …”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
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…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to StripeStripe provides the event backbone needed for rule-based automation — webhooks/event destinations that fire on account events (stripe-docs-8, stripe-docs-53, stripe-supp-event-destinations) — plus some built-in automated actions like Smart Retries and Radar's real-time risk rules (stripe-docs-14, stripe-docs-22). A third-party Dashboard app (Kyber) explicitly offers a no-code rule builder that 'assigns tasks and automates common workflows based on Stripe events' (e.g., Slack alert on dispute), which matches the story closely (stripe-intdir-6). However, this rule-definition UI is a third-party app, not a native first-party Stripe rules engine, and there's no evidence of a built-in general-purpose 'if event X then action Y' configurator inside Stripe itself. Missing for 10: a native first-party no-code/low-code rule engine for arbitrary event-triggered actions, and independent hands-on confirmation of such rule-based automation in practice.
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
- [claimed-docs] “After you register a webhook endpoint, Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “The no-code builder Kyber lets users assign tasks and automate common workflows based on Stripe events. Users can quickly configure automati…”
- [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”
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”
Billing invoicing — stories about billing invoicing in this arenaBilling invoicing
Stories about billing invoicing in this arena
Ai billing ops
ai-native userHave an agent monitor failed payments via API and webhooks and drive retries and dunning outreach
weight 3 · round to StripeStripe documents the full loop an agent needs: webhooks/event destinations for detecting failed payments and dispute events (stripe-docs-8, stripe-docs-53, stripe-supp-event-destinations), Smart Retries and no-code revenue recovery/dunning automation with recovery analytics (stripe-docs-14, stripe-docs-15, stripe-docs-56), and API/MCP write access (subscriptions, invoices, disputes) with restricted-key scoping and human-confirmation guardrails so an agent can drive retries and outreach programmatically (stripe-supp-mcp-tools, stripe-supp-mcp-write-confirmation, stripe-supp-restricted-keys-agents, stripe-docs-41). Idempotency support further protects automated retry logic (stripe-docs-9). missing for 10: no first-party or hands-on example of an agent specifically orchestrating dunning outreach (e.g., emails/SMS) end-to-end, and no independent/community confirmation of this exact agent workflow in production.
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
- [claimed-docs] “Prevent lost revenue and reduce churn with Stripe’s revenue recovery features... None of the features require you to write code.”
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
- [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
- [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”
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…”
ai-native userHave an agent provision a new product, price, and payment link via the API in a single session
weight 3 · round to StripeStripe's MCP server documents stripe_api_write with create/update support for products, prices, and payment links, plus stripe_implementation_planner to guide multi-step builds, enabling an agent to provision a product, price, and payment link in one session via a single authenticated MCP/API connection; the CLI/sandbox provisioning (stripe sandbox create) also lets agents get working keys without manual account setup. Missing for 10: a hands-on end-to-end transcript/independent report of an agent actually completing this exact three-step chain in one session, and clarity on whether human-confirmation gating (required for refunds/payments) also intercepts routine create-product/price/payment-link calls.
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Coding agents should install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create --help to provision an anonymou…”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
- [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
- [claimed-docs] “The CLI landing page frames the command line as "Stripe's suite of agent-ready tooling", with "Agent setup: Automatically configure your age…”
Adyennone0/10Adyen'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…”
Invoicing
finance-ops userSend hosted invoices with online payment and automatic reminders
weight 2 · round to StripeStripe clearly supports creating and sending hosted, customizable invoices with online payment collection, no code required (stripe-docs-21, stripe-docs-60, stripe-docs-51). However, the evidence pack does not explicitly document automatic reminder emails for unpaid invoices — the closest analog is 'Smart Retries' and revenue-recovery dunning for subscription payment failures (stripe-docs-14, stripe-docs-31), which is a related but distinct capability from invoice due-date reminders. Missing for 10: explicit documentation of automatic invoice payment reminder emails, and independent/hands-on confirmation of the reminder feature working in practice.
- [claimed-docs] “Create, customize, and send a Stripe-hosted invoice from the Dashboard, with no code required.”
- [claimed-docs] “Customize invoices: Customize the content and branding of your invoices.”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “None of the features require you to write code, so you can start recovering revenue today.”
- [claimed-docs] “Prevent lost revenue and reduce churn with Stripe’s revenue recovery features... None of the features require you to write code.”
Adyennone0/10Adyen'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.”
Subscriptions
finance-ops userAutomatically retry failed subscription payments with smart dunning and recovery emails
weight 2 · round to StripeStripe Billing's revenue-recovery docs explicitly document Smart Retries for automatically retrying failed subscription payments plus recovery analytics, and this is a no-code feature within Billing. Missing for 10: explicit documentation of automated dunning/recovery email templates and independent hands-on validation of recovery email effectiveness.
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
- [claimed-docs] “None of the features require you to write code, so you can start recovering revenue today.”
- [claimed-docs] “Prevent lost revenue and reduce churn with Stripe’s revenue recovery features... None of the features require you to write code.”
- [claimed-docs] “Prevent lost revenue and reduce churn with Stripe's revenue recovery features. ... None of the features require you to write code”
- [claimed-docs] “It automates recurring payments, creates custom pricing plans, and handles billing periods, such as trials and renewals.”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
Adyennone0/10The 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.
developerSet up recurring subscription billing with plans, trials, upgrades, and proration
weight 3 · round to StripeStripe Billing explicitly automates recurring payments, custom pricing plans, trials, renewals, and subscription upgrades, plus a customer portal for self-service management, revenue recovery (smart retries), and subscription migration docs. Documentation confirms core subscription lifecycle features via first-party docs, though proration is only implied via 'upgrades' rather than explicitly named, and no independent/hands-on corroboration of proration mechanics is present. Missing for 10: explicit proration documentation/examples, independent developer corroboration of subscription setup experience.
- [claimed-docs] “It automates recurring payments, creates custom pricing plans, and handles billing periods, such as trials and renewals.”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “Integrate the customer portal: The simplest way to build a subscription and billing management Dashboard.”
- [claimed-docs] “Migrate your subscriptions: Learn how to migrate subscriptions to Stripe.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Recovery analytics: Analyze subscription payment failure rates, recovery rates, and recent failed payments for top customers.”
- [claimed-docs] “None of the features require you to write code, so you can start recovering revenue today.”
Adyennone0/10Adyen'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.
Checkout acceptance — stories about checkout acceptance in this arenaCheckout acceptance
Stories about checkout acceptance in this arena
Card acceptance
founderAccept an online card payment within a day of signing up
weight 3 · round to StripeStripedisputedcontradicted6/10Stripe's docs strongly support rapid onboarding: no-code Payment Links, hosted Checkout pages, and a live testimonial confirms setup and recurring payments working 'in less than an hour' (stripe-docs-4, stripe-docs-2, stripe-comm-9). However, independent community reports concretely contradict universal same-day acceptance — users report Stripe denying account creation entirely or 'nuking' an existing business's payment capability without quick support resolution (stripe-comm-1, stripe-comm-4, stripe-comm-5), showing that for some founders (especially certain geographies/business types) the promised fast, frictionless activation does not materialize. missing for 10: evidence resolving how common these denials/delays are, and first-party docs addressing account approval timelines or geographic/business restrictions.
- [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
- [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
- [claimed-docs] “Create a payments page with prebuilt UIs using the Checkout Sessions API.”
- [community] “Stripe is a game changer. I've been using it for a few months and honestly its the best API I've ever used. The documentation is clear and c…”
- [community] “Funny, I have a Delaware LLC company registered in USA (it's an offshore company) but my bank account is outside the US (completely legal), …”
- [community] “Stripe has decided to nuke my entire business... So currently, my product doesn't work for 35% of my customers. Cue torrent of pissed off cu…”
- [community] “I wanted to enable issuing on my account to test card issuing, but there was a bug where the UI was looping. Asked support, got 2 weeks of '…”
Adyendisputedcontradicted4/10Adyen'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-…”
Checkout surfaces
developerEmbed customizable payment components directly in my own site or app instead of redirecting to a hosted page
weight 3 · round to StripeStripe Elements and Checkout Sessions API let developers embed a fully customizable payment page directly in their own site (as opposed to only redirecting to a hosted page), with support for 125+ payment methods, subscriptions, and prebuilt/custom UI options documented extensively. Missing for 10: no independent/hands-on developer report specifically praising the embedded (non-redirect) Elements experience beyond docs.
- [claimed-docs] “Build a fully customized payment page using elements”
- [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
- [claimed-docs] “Elements: Build a fully customized payment page using elements”
- [claimed-docs] “Create a payments page with prebuilt UIs using the Checkout Sessions API.”
- [claimed-docs] “Accept one-time and subscription payments from more than 125 local payment methods.”
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…”
developerRedirect customers to a vendor-hosted, conversion-optimized checkout page without building my own payment UI
weight 3 · round to StripeDocs explicitly describe Stripe Checkout as a Stripe-hosted redirect page ('via a redirect to a Stripe-hosted page') with prebuilt UI via Checkout Sessions API, plus Payment Links for a fully no-code hosted checkout URL — directly matching the story. Multiple docs reinforce it supports many payment methods, currencies, tax collection, and no-code refunds on these hosted pages. missing for 10: no independent/hands-on corroboration of the hosted page's conversion-optimization claims beyond Stripe's own docs.
- [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
- [claimed-docs] “Create a payments page with prebuilt UIs using the Checkout Sessions API.”
- [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
- [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
- [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”
- [claimed-docs] “Accept one-time and subscription payments from more than 125 local payment methods.”
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…”
No code selling
founderCreate a shareable payment link from the dashboard with no code and start selling immediately
weight 2 · round to StripeStripe Payment Links is explicitly documented as a no-code way to create a shareable payment link from the dashboard, supporting local currencies/payment methods, no-code tax collection, and no-code refunds — matching the founder story closely. Missing for 10: independent hands-on account of actually creating a payment link end-to-end (community evidence is general Stripe sentiment, not specific to Payment Links).
- [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
- [claimed-docs] “No-code refunds Yes”
- [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
- [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”
Adyendisputedcontradicted4/10Adyen'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-…”
Payment methods
founderOffer digital wallets and local payment methods (Apple Pay, Google Pay, bank redirects, BNPL) from the same integration
weight 2 · round to AdyenStripe Checkout/Elements documentation confirms 125+ local payment methods and localized payment links, which covers digital wallets, bank redirects, and local methods from one integration; however, the evidence never explicitly names Apple Pay, Google Pay, or specific BNPL providers, and there's no independent/hands-on confirmation of the exact method mix. missing for 10: explicit mention of Apple Pay/Google Pay support, named BNPL providers (e.g., Klarna/Afterpay), and independent verification of the full payment-method list.
- [claimed-docs] “Accept one-time and subscription payments from more than 125 local payment methods.”
- [claimed-docs] “Build a fully customized payment page using elements”
- [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
- [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
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…”
Compliance security — stories about compliance security in this arenaCompliance security
Stories about compliance security in this arena
Pci compliance
developerKeep my systems out of most of PCI DSS scope because card data is tokenized and never touches my servers
weight 2 · round to StripeStripe's docs explicitly state that low-risk integrations (Checkout, Elements, hosted payment pages) collect and transmit payment data directly to Stripe without it passing through the developer's servers, explicitly reducing PCI obligations/scope, and these are backed by concrete hosted/embeddable products (Checkout, Payment Links, Elements). missing for 10: independent third-party PCI audit or compliance-report corroboration beyond Stripe's own docs.
- [claimed-docs] “You can instead use one of our low risk payment integrations to securely collect and transmit payment information directly to Stripe without…”
- [claimed-docs] “you can instead use one of our low risk payment integrations to securely collect and transmit payment information directly to Stripe without…”
- [claimed-docs] “use one of our low risk payment integrations to securely collect and transmit payment information directly to Stripe without it passing thro…”
- [claimed-docs] “Build a fully customized payment page using elements”
- [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
- [claimed-docs] “Create a payment link and share it on social media, in emails, or on your website.”
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.”
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Integration reliability
developerSafely retry any API request using idempotency keys so network failures never create duplicate charges
weight 2 · round to StripeStripe's API docs explicitly document idempotency keys for safely retrying requests after connection errors without creating duplicate objects/charges, directly matching the story, and this is a well-known, widely used first-party API feature. Missing for 10: independent hands-on developer corroboration specifically testing idempotency behavior (community evidence in the pack is unrelated to this feature).
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “use an idempotency key... you can safely repeat the request without risk of creating a second object or performing the update twice”
- [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object or pe…”
- [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object”
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.”
developerRely on signed webhook deliveries with automatic retries, event logs, and replay to keep my system consistent with payment state
weight 3 · round to StripeDocs cover signed/HTTPS webhook endpoints, real-time event pushes, idempotency for safe retries, dispute/event handling via API+webhooks, and the newer event destinations feature with versioned snapshot/thin events; sandbox testing supports simulating webhook flows. However, explicit documentation of automatic retry schedules for failed webhook deliveries and a dedicated 'replay' UI/feature isn't directly cited (event destinations mention versioning but not an explicit replay tool), and there's no independent/hands-on corroboration of retry reliability. missing for 10: explicit docs on automatic webhook retry backoff schedule, a dedicated event replay feature/UI, independent developer corroboration of retry/replay reliability.
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
- [claimed-docs] “After you register a webhook endpoint, Stripe pushes real-time data to it when events happen in your Stripe account.”
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “use an idempotency key... you can safely repeat the request without risk of creating a second object or performing the update twice”
- [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object or pe…”
- [claimed-docs] “use an idempotency key. Then, if a connection error occurs, you can safely repeat the request without risk of creating a second object”
- [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “Event destinations deliver real-time events "across multiple destination types, including webhook endpoints, Amazon EventBridge, and Azure E…”
- [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
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.”
Onboarding dx
developerIntegrate a working payment flow from the docs alone in under a day, with copy-paste examples in my language
weight 2 · round to StripeStripe's docs offer copy-paste checkout/payment-link/Elements integrations, sandbox testing with test cards, idempotency, webhooks, and API keys, and community testimony confirms fast integration ('up and running and accepting recurring payments in less than an hour', clear documentation) despite some unrelated support gripes. missing for 10: explicit multi-language SDK code-sample evidence in the pack (only generic doc references, not shown per-language snippets) and a broader/more recent independent corroboration beyond one old HN thread.
- [claimed-docs] “Build a fully customized payment page using elements”
- [claimed-docs] “Customers enter their payment details in a fully-featured payment page, either embedded on your site or via a redirect to a Stripe-hosted pa…”
- [claimed-docs] “Test your integration in a sandbox ... by simulating transactions with test values—these transactions don't move funds.”
- [claimed-docs] “Test cards act as "fake" credit cards, and allow you to simulate the following scenarios: - Successful payments... - Card errors due to decl…”
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “You can create an HTTPS webhook endpoint to receive events.”
- [community] “Stripe is a game changer. I've been using it for a few months and honestly its the best API I've ever used. The documentation is clear and c…”
Adyendisputedcontradicted4/10Adyen'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-…”
Sandbox fidelity
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 StripeStripe provides a documented sandbox environment mirroring production (isolated per-team sandboxes, no live-data impact) plus an extensive test-card matrix covering successes, declines, fraud, and invalid data, and a full disputes API for simulating/handling chargebacks. CLI and Workbench also support building/testing/debugging integrations end-to-end. Missing for 10: no independent/hands-on developer testimonial specifically validating sandbox fidelity or test-card coverage beyond first-party docs.
- [claimed-docs] “Test your integration in a sandbox ... by simulating transactions with test values—these transactions don't move funds.”
- [claimed-docs] “A sandbox is an isolated test environment. You can use your sandbox to test Stripe functionality in your account, and experiment with new fe…”
- [claimed-docs] “You can use your sandbox to test Stripe functionality in your account, and experiment with new features without affecting your live integrat…”
- [claimed-docs] “You can invite another user, such as an implementation partner or design agency, to access all sandboxes, or a specific sandbox, without pro…”
- [claimed-docs] “Your team can test in separate sandboxes to make sure that data and actions are completely isolated from other sandboxes.”
- [claimed-docs] “Test cards act as "fake" credit cards, and allow you to simulate the following scenarios: - Successful payments... - Card errors due to decl…”
- [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “Workbench provides powerful tools that help you build, test, and debug your Stripe integration.”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
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…”
Disputes fraud — stories about disputes fraud in this arenaDisputes fraud
Stories about disputes fraud in this arena
Ai disputes
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 StripeStripe docs explicitly state the Disputes API supports retrieving, uploading evidence, responding to disputes, and receiving dispute webhook events, and the hosted MCP server's documented tool surface includes 'disputes (update)' alongside generic read/write API access, restricted-key scoping for agents, and webhook-based event delivery — covering the retrieve→assemble→submit flow programmatically. Missing for 10: a concrete end-to-end worked example (e.g., a sample agent script that assembles and submits evidence), and clarity on whether dispute submission falls under the human-confirmation gate applied to other write actions.
- [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “Restricted API keys are Stripe's documented least-privilege credential for agents: "When you create a RAK in the Stripe Dashboard, you selec…”
Adyennone0/10The 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.”
Disputes
finance-ops userRespond to a chargeback with structured evidence and track the dispute lifecycle to resolution
weight 3 · round to StripeStripe's Disputes API lets finance-ops programmatically manage disputes, upload structured evidence, respond to disputes, and receive dispute lifecycle events via webhooks, plus dispute events surface in the Dashboard/Radar for tracking; MCP tooling also exposes a 'disputes: update' method for agent-assisted workflows. missing for 10: no independent/hands-on account of the full evidence-submission UX or explicit dispute-resolution outcome tracking beyond webhook events.
- [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “Receiving webhook events helps you respond to asynchronous events, such as when a customer's bank confirms a payment, a customer disputes a …”
- [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
Adyennone0/10The 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.
Fraud prevention
finance-ops userScreen transactions with machine-learning fraud scores and write custom block, review, and allow rules
weight 3 · round to AdyenStripe Radar is documented to use AI/ML algorithms in real time to assess fraud risk across transactions, accounts, and customers, which covers the ML fraud-scoring part of the story; however, the evidence pack does not show custom rule-writing capability (block/review/allow rules) beyond the single Radar mention, no details on rule builder UI, thresholds, or list management. missing for 10: documentation of custom rule creation/editing (block, review, allow lists), rule logic examples, and independent/hands-on confirmation of Radar's rule-writing workflow.
- [claimed-docs] “Use Radar to evaluate transactions, accounts, and customers in real time, using AI algorithms to assess the risk of fraud.”
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…”
Refunds
finance-ops userIssue full or partial refunds from both the dashboard and the API
weight 3 · round to StripeDocs explicitly state refunds can be issued via both the Refunds API and the Dashboard, including full or partial amounts, and refunded payments are viewable in the Dashboard. No-code refunds are also supported on Payment Links. missing for 10: no independent/hands-on confirmation of partial-refund UX in the dashboard.
- [claimed-docs] “You can cancel a payment before it's completed at no cost. Or you can refund all or part of a payment after it succeeds, which might incur a…”
- [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard”
- [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard.”
- [claimed-docs] “You can view your refunded payments in the Dashboard”
- [claimed-docs] “No-code refunds Yes”
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.”
Global currency tax — stories about global currency tax in this arenaGlobal currency tax
Stories about global currency tax in this arena
Multi currency
founderCharge customers in their local currencies and settle to my bank in mine with transparent FX handling
weight 2 · round to StripeStripe documents charging in 135+ currencies with payout settlement in a merchant's preferred currency (stripe-docs-19), localized checkout/payment links that let customers pay in their own currency (stripe-docs-36), automated payout tracking to bank accounts (stripe-docs-34, stripe-docs-52, stripe-docs-68), and automated tax compliance across jurisdictions (stripe-docs-20, stripe-docs-48). This directly covers charging locally and settling in the founder's currency. Missing for 10: explicit documentation of FX conversion rate transparency/fee disclosure mechanics and independent/hands-on confirmation of FX rate fairness or settlement accuracy.
- [claimed-docs] “You can charge customers in over 135 currencies and receive funds in your preferred currency.”
- [claimed-docs] “Let your customers use a link to pay in their local language and currency with their preferred payment method.”
- [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
- [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
- [claimed-docs] “Set up your bank account to receive payouts.”
- [claimed-docs] “Automate sales tax, VAT, and GST compliance on all your transactions.”
- [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”
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.”
Tax
finance-ops userCalculate and collect the correct sales tax, VAT, or GST on every transaction automatically
weight 3 · round to StripeStripe Tax explicitly automates sales tax, VAT, and GST calculation and collection across transactions, including no-code tax collection on Payment Links, backed by first-party docs. Missing for 10: independent/hands-on corroboration of accuracy across jurisdictions and any detail on filing/remittance support beyond calculation and collection.
- [claimed-docs] “Automate sales tax, VAT, and GST compliance on all your transactions.”
- [claimed-docs] “Collect tax on Payment Links: Learn how to calculate and collect tax on a payment page without writing any code.”
Adyennone0/10Adyen'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.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to StripeStripe's core resources (payments, refunds, subscriptions, invoices, disputes, payouts, tax, Connect) are all documented as available via the REST API with idempotency, versioning, and restricted keys, and the MCP server explicitly exposes generic stripe_api_read/stripe_api_write tools plus task-specific tools mirroring Dashboard actions across most objects. Workbench Shell/CLI further lets agents run the same commands as the CLI/API interactively. missing for 10: independent confirmation that every Dashboard-only feature (e.g., third-party Stripe Apps like Kyber no-code automations) has a full API equivalent, and note that sensitive stripe_api_write actions require human confirmation rather than being fully autonomous.
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “With the API, you can upload evidence, respond to disputes, and receive dispute events using webhooks.”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “The API supports idempotency for safely retrying requests without accidentally performing the same operation twice.”
- [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
- [claimed-docs] “A restricted API key (RAK) is an API key ... a RAK can do only what you give it permission to do.”
- [claimed-docs] “Workbench (Dashboard > Developers > Workbench) ships an interactive Shell and API Explorer: "Shell is a command line interface within Workbe…”
- [claimed-docs] “Build, test, and manage your Stripe integration from the command line.”
- [claimed-docs] “Docs, "Confirm actions by agents acting on your behalf": "To prevent agents from making mistakes, Stripe requires human confirmation before …”
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…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to StripeEvidence shows only narrow CSV export of specific financial reports (balance, payouts, activity, tax, Revenue Recognition) via stripe_report/Workbench, not a comprehensive account data export mechanism for a user to leave the platform. Missing for 10: a documented full account/data export tool (customers, charges, subscriptions, full transaction history) in open/portable formats, and any explicit data-portability or account-closure export workflow.
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “Use these files to generate SDKs or client libraries that support Stripe's API.”
Adyennone0/10The 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…”
ai-native userRead the product's source under an open license
weight 2 · round to AdyenStripenone0/10Stripe's core payments platform is proprietary SaaS; the evidence pack shows only open-source SDKs/CLI/agent-toolkit wrappers (e.g. stripe/ai, stripe-cli) but no license for the actual product/service source code, so there is no basis to claim the product itself is open-license readable.
Adyen's core payment-processing platform is closed, proprietary SaaS with no evidence of the underlying service source being published under any license. However, evidence shows genuinely open-source ancillary components: the Adyen MCP server (github.com/Adyen/adyen-mcp) and the OpenAPI specification repo (github.com/Adyen/adyen-openapi) described as 'the single source of truth for our APIs,' both publicly viewable on GitHub. Missing for 10: any open license on the actual platform/service code, no stated license type for the repos, no independent confirmation of license terms, and no indication the core product itself is inspectable beyond API specs and a thin MCP client tool.
- [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] “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…”
Payouts reconciliation — stories about payouts reconciliation in this arenaPayouts reconciliation
Stories about payouts reconciliation in this arena
Ai reconciliation
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 StripeStripe's API and MCP tooling explicitly expose payout and balance-transaction data for programmatic/agent access — the documented stripe_api_read method list includes 'payouts, and balance transactions', and stripe_analytics/stripe_report can run balance and payout financial reports, letting an agent pull the data needed to match deposits to charges (stripe-supp-mcp-tools, stripe-supp-analytics-ai, stripe-docs-34/52/68). However, there is no first-party tutorial or worked example specifically demonstrating automated reconciliation logic (matching a bank deposit to its underlying charges), and no independent/hands-on evidence confirming this reconciliation workflow works end-to-end. Missing for 10: a documented reconciliation workflow/tutorial tying payout amounts to constituent balance-transaction charges, and independent verification of an agent successfully performing this reconciliation.
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
- [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
- [claimed-docs] “Set up your bank account to receive payouts.”
Adyennone0/10The 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…”
Payouts
finance-ops userControl the payout schedule and see exactly which charges, fees, and refunds make up each payout
weight 2 · round drawnStripe documents payout basics (funds sent from balance to bank account, dashboard tracking of payouts and expected deposit dates, setting up bank accounts) and financial reporting via stripe_report/analytics (balance, payouts, activity reports downloadable as CSV), which supports reconciliation. However, evidence does not show explicit payout schedule controls (e.g., setting manual vs automatic schedule, daily/weekly/monthly cadence) nor a documented per-payout breakdown view showing exact charges/fees/refunds composing each payout. missing for 10: explicit payout schedule configuration docs, a documented itemized payout reconciliation report/API showing constituent charges/fees/refunds per payout, independent/hands-on confirmation of this reconciliation workflow.
- [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
- [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
- [claimed-docs] “Set up your bank account to receive payouts.”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
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.”
Reconciliation
finance-ops userReconcile settlements to bank deposits with itemized reports covering fees, refunds, and chargebacks
weight 3 · round to StripeStripe documents payouts to bank accounts with expected deposit dates (stripe-docs-34, stripe-docs-52), refunds and dispute management via API/Dashboard (stripe-docs-17, stripe-docs-33, stripe-docs-41), and AI-assisted analytics/report runs including a documented 'balance summary' report and other financial report types (stripe-supp-analytics-ai). However, there is no evidence of a purpose-built, itemized settlement-to-deposit reconciliation report that breaks out fees, refunds, and chargebacks against a specific bank deposit in one view — the closest evidence (report types: balance, payouts, activity, tax) implies this exists but doesn't confirm itemization matching finance-ops reconciliation workflows, and third-party accounting sync (QuickBooks, Xero) is only listed as partner integrations rather than native itemized reconciliation. missing for 10: a documented native 'payout reconciliation report' itemizing fees/refunds/chargebacks per deposit, confirmation of automatic matching to bank statement lines, and independent/hands-on evidence from finance-ops users that this reconciliation workflow works well in practice.
- [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
- [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
- [claimed-docs] “You can cancel a payment before it's completed at no cost. Or you can refund all or part of a payment after it succeeds, which might incur a…”
- [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
- [claimed-docs] “Agents can analyze aggregated account data through MCP: `stripe_analytics` "handles three kinds of requests: Metric queries for Stripe-defin…”
- [claimed-docs] “We are specialists in connecting Stripe to QuickBooks Online”
- [claimed-docs] “View relevant Xero customer and transaction data within the Stripe Dashboard”
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.”
Platform marketplace — stories about platform marketplace in this arenaPlatform marketplace
Stories about platform marketplace in this arena
Marketplace
developerBuild a marketplace or platform that onboards sellers, splits payments between parties, and pays out to each seller
weight 2 · round to StripeStripe Connect is explicitly documented as the product for building marketplaces/platforms that onboard sellers, split payments, and pay out to multiple parties, backed by supporting payouts, payment collection, refunds, disputes, and tax infrastructure. Missing for 10: independent hands-on evidence specifically of a marketplace/Connect integration (community evidence covers Stripe generally, not Connect specifically).
- [claimed-docs] “Collect payments from customers and automatically pay out a portion to sellers or service providers on your marketplace.”
- [claimed-docs] “Use Connect to build a platform, marketplace, or other business that manages payments and moves money between multiple parties.”
- [claimed-docs] “Stripe sends funds from your available balance to your bank account as payouts”
- [claimed-docs] “Track a payout: View your payouts and their expected deposit dates in the Dashboard.”
- [claimed-docs] “Set up your bank account to receive payouts.”
- [claimed-docs] “You can issue refunds by using the Refunds API or the Dashboard”
- [claimed-docs] “You can programmatically manage disputes using the API. With the API, you can upload evidence, respond to disputes, and receive dispute even…”
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.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnStripenone0/10No evidence in the pack discusses data residency, regional data storage choices, or GDPR/EU data localization options for Stripe accounts; the evidence covers payments, billing, MCP/agents, sandboxes, etc. but never data residency controls.
Adyennone0/10The 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.
ai-native userControl data retention and deletion
weight 2 · round drawnStripenone0/10The evidence pack covers sandbox isolation, restricted API keys, MCP OAuth session revocation, and webhook/event architecture, but none of it addresses data retention policies or a mechanism for users to request deletion/erasure of stored payment or customer data. As a platform processing sensitive financial and personal data, this is a fair and applicable axis, but no documentation shows retention controls or deletion capabilities for AI-native users.
Adyennone0/10Adyen'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.
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableStripen/aStripe is a payments platform/API, not an agent host or assistant application that a user configures with pluggable MCP servers for its own use; all evidence instead shows Stripe publishing its own MCP server (server role) and shipping plugins/skills for other agents like Claude Code/Cursor to consume, which is the opposite direction from this story's client-role axis.
Adyenn/aAdyen is a payments platform/API, not an AI agent or assistant host; it ships an MCP *server* exposing its own payment tools (adyen-docs-5, adyen-supp-mcp-tools) but nothing suggests Adyen itself acts as an MCP client/host that plugs in and consumes external MCP servers' tools. This 'plug servers into it' client-role story is a category error for a payments API product.
- [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…”
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableStripe Billing natively automates recurring payment jobs (subscriptions, invoicing, trials, renewals, smart retries) and this can be driven via API/MCP by an AI agent, plus Stripe Projects/CLI/Workbench let agents script and schedule integration tasks. However there is no evidence of a general-purpose 'schedule any workflow/job' primitive (e.g. cron-like task scheduler for arbitrary agent workflows) beyond payment/billing-specific recurrence. missing for 10: a generic workflow/job scheduler beyond billing recurrence, evidence of agents autonomously scheduling multi-step workflows (not just recurring payments), independent hands-on confirmation of this automation depth.
- [claimed-docs] “It automates recurring payments, creates custom pricing plans, and handles billing periods, such as trials and renewals.”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “Stripe Projects "provisions and manages third-party services (such as hosting, databases, auth, AI, and observability) from the terminal. Ru…”
- [claimed-docs] “The hosted MCP server (mcp.stripe.com) exposes generic API tools plus task tools: `stripe_api_search` ("Search for Stripe API methods by key…”
- [claimed-docs] “You can use an AI agent to analyze aggregated data across your Stripe account ... query metrics such as monthly recurring revenue (MRR)”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableStripenone0/10Stripe's automation features (Billing recurring rules, Smart Retries, Radar rules, webhooks, Kyber no-code flows) have no documented version-history, review/diff, or rollback mechanism in the evidence. API versioning (stripe-docs-45/59) covers backward-compatible monthly API releases, not versioning of a user's automation configurations, so it doesn't satisfy this story.
- [claimed-docs] “You can safely upgrade to a new monthly release without breaking any existing code.”
- [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
- [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
- [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
- [claimed-docs] “The no-code builder Kyber lets users assign tasks and automate common workflows based on Stripe events. Users can quickly configure automati…”
ai-native userSelf-host the core product
weight 3 · not comparableStripen/aStripe is a hosted, regulated financial-services platform (payment processing, PCI compliance, banking rails, fraud detection via aggregated network data) — self-hosting the core product is a category error for this kind of service, not a capability gap.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableStripen/aStripe is a payments infrastructure platform, not an AI model provider or chatbot that trains models on user data; the story about opting out of AI-model-training data usage is a category error for this product type — there is no evidence Stripe trains generative AI models on customer data as a core offering, so this privacy-posture axis about AI training opt-out does not apply.
Adyenn/aAdyen is a payment processing platform, not an AI model provider or chat product that trains models on user data; there's no evidence of any AI-training data usage to opt out of. This axis targets consumer-facing AI/chat tools, which is a category error for a payments infrastructure API.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableStripen/aStripe is a payments platform, not an AI dev tool with client-side telemetry to opt out of; this privacy-posture axis about telemetry/usage tracking opt-out is a category error for this product type and no evidence contradicts that.
Adyennone0/10Adyen 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.