Stripe vs Mollie

Agent access

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

   weight 2 · round drawn
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullprobed9/10

   Mollie publishes a live llms.txt index (verified by probe returning HTTP 200) and documents the markdown-mirror convention (append .md to any doc page) so agents can systematically discover and fetch docs; this is corroborated by an independent probe hit, not just vendor claims. missing for 10: no independent third-party (non-Mollie) report of an agent actually using llms.txt successfully in practice.

   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed7/10

   Mollie is a REST API-based payment platform designed for headless/server-side integration: API keys, idempotency keys, webhooks, and test mode all support fully automated, non-interactive/CI-driven operation without a UI. Missing for 10: no explicit CI/CD pipeline examples, SDK/CLI tooling for automated test suites, or independent hands-on reports of running Mollie flows inside a CI pipeline.

   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullprobed9/10

   Mollie documents an official hosted MCP server at https://mcp.mollie.com/mcp acting as a proxy for its public API, with documented API coverage (Payments, Balances, Subscriptions, Webhooks, etc.), scoped access tokens, and setup instructions for Claude Desktop, Cursor, and VS Code. Missing for 10: independent/hands-on third-party corroboration beyond vendor docs and probe confirmation.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Stripe
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie is a payments API/platform; while it offers an MCP server, llms.txt index, and REST API/SDKs, no evidence pack item describes an official CLI tool for managing Mollie resources or workflows. Absence of evidence for this applicable capability yields 'none'.

   ⚑ flag

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

   weight 3 · round to Stripe
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullprobed8/10

   Mollie exposes a comprehensive, well-documented public REST API (Payments, Subscriptions, Balances, Webhooks, etc.), plus auth schemes, idempotency headers, test mode, and an llms.txt documentation index explicitly designed for AI agent discovery, alongside an official MCP server proxying the public API for AI tools like Claude/Cursor. Missing for 10: no discoverable OpenAPI/Swagger spec (probe returned 404s) and no independent hands-on corroboration beyond vendor docs.

   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie documents scoped credential mechanisms applicable to agent use: Advanced access tokens can be scoped to a specific mode or profile, API keys are scoped per payment profile with granular permissions grouped by business area/API, and the MCP server explicitly requires profile.read plus optional per-API scopes to enable individual tools. This shows a real least-privilege model usable when provisioning an agent, but there's no dedicated 'agent credential' concept, no fine-grained per-action/per-amount limits, and no independent evidence of this being used in practice for agent scoping. Missing for 10: agent-specific credential issuance workflow, granular per-action/spend-limit scoping beyond API/profile level, independent/hands-on confirmation of least-privilege enforcement in an agentic context.

   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   The evidence pack documents Mollie's REST API references, webhooks, testing mode, and an MCP server for AI agents, but never mentions official client SDKs/libraries (e.g., PHP, Node, Python, Java clients) that developers or AI agents could build against. Since SDK availability is a standard axis for a payments API platform, its absence here is a gap rather than a category mismatch.

   ⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed8/10

   Mollie's next-gen Webhooks API explicitly supports permanent subscriptions to specific event types (replacing one-off payment webhooks), backed by a Webhook Events API for auditing past events and documented HMAC signature verification for security. This directly satisfies event-driven subscription via webhooks for programmatic/agentic consumption. Missing for 10: independent/hands-on verification of webhook delivery reliability and broader real-world event-type coverage beyond docs.

   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: 1. Retrieve the signature from the request header (X-Mollie-Signature)...”
   • [claimed-docs] “New event types to offer a broader context for your business processes (e.g. payment creation, invoice creation, onboarding status changes e…”
   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: Retrieve the signature from the request header (X-Mollie-Signature) and obtain t…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie's AI-related evidence covers an MCP server that lets external AI tools create/manage payment resources via natural language, but there is no evidence of the product itself generating insights, analytics, or suggestions from a merchant's data within Mollie's own interface or reports.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe
   Stripe~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie ships genuine background automation primitives — Subscriptions/Recurring Payments run autonomously after initial setup ('happen in the background', 'we automatically create recurring payments for you at the interval you specified') and webhooks push real-time async updates — and its MCP server lets AI tools like Claude Desktop/Cursor create these resources via natural language. However, the automation scope is narrow (payment-related resources only) and the MCP server is documented for one-off resource creation/queries, not for orchestrating persistent autonomous agent workflows. Missing for 10: evidence of AI agents scheduling/monitoring ongoing automations themselves (vs. one-time setup), and any broader workflow/automation-builder beyond payments primitives.

   • [claimed-docs] “Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “When using this API, we automatically create recurring payments for you at the interval you specified.”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe—none0/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie's evidence describes an MCP server that lets external AI tools (Claude Desktop, Cursor, VS Code) call Mollie's APIs via natural language — this is Mollie acting as a tool/backend for other assistants, not a built-in AI assistant inside Mollie's own product that users delegate tasks to. No dashboard chatbot, in-app assistant, or similar built-in AI feature is documented.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

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

   weight 2 · round to Mollie
   Stripe~partialprobed7/10

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

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

   proof ↗⚑ flag

   Mollie✓fullprobed7/10

   Mollie ships an official MCP server (hosted at mcp.mollie.com/mcp) explicitly documented as enabling merchants to use natural language via AI tools like Claude Desktop and Cursor AI to create resources in their Mollie account, with scoped OAuth access and documented client configs. Missing for 10: independent/hands-on user reports confirming reliability, and broader coverage details (only a subset of APIs are exposed via MCP, e.g. no Payments creation confirmation beyond listed APIs).

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Stripe
   Stripe~partialprobed6/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Evidence covers static markdown documentation, an llms.txt index, and reference pages, but there is no mention of an interactive API console, 'try it' runnable examples, or Postman/OpenAPI-based playground; a probe for OpenAPI/swagger specs returned 404s, suggesting no such interactive reference exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe
   Stripe✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Probes for standard OpenAPI/Swagger spec locations on Mollie's docs site all returned 404, and no evidence pack item shows a published, downloadable OpenAPI/Swagger spec; the llms.txt index and markdown mirrors are documentation aids, not a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”

   proof ↗⚑ flag

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

   weight 1 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed8/10

   Mollie documents a first-class test mode that isolates test resources from live data, supports test API keys or a testmode parameter, replaces hosted checkout with a simulated flow, and even allows simulating refunds/chargebacks via changePaymentState — directly matching the sandbox-without-production-data story. missing for 10: no independent/hands-on third-party confirmation of sandbox behavior beyond vendor docs, and no explicit mention of sandbox support specifically for the MCP/AI-agent workflow (only general API test mode is documented).

   • [claimed-docs] “Any payments or other resources you create in test mode are completely isolated from your live mode data.”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   The evidence shows Mollie has a v2 API (mollie-docs-12) but nothing documents a versioning scheme, deprecation policy, changelog, or sunset timeline for older API versions/endpoints. Missing for 10: explicit API versioning documentation, deprecation/sunset policy, changelog or migration guide evidence.

   • [claimed-docs] “Mollie enables you to accept payments in currencies beyond EUR through its v2 APIs, allowing international customers to transact in their pr…”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie's documented APIs (Payments, Refunds, Subscriptions, Balances, MCP server, etc.) are all single-resource endpoints; there is no evidence of a batch/bulk API, bulk payment creation, or bulk refund/webhook management across many items at once. The MCP server description explicitly frames it as creating individual resources via natural language, not bulk operations.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Next to the API endpoint, you can also create refunds manually via the Mollie Web app.”

   proof ↗⚑ flag

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

   weight 3 · round to Stripe
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed4/10

   Mollie provides event-driven building blocks — webhooks that fire on payment status changes, subscriptions that auto-create recurring payments, and application fees that auto-collect on every payment — but these are fixed, pre-built automations, not a general rules engine where a user defines arbitrary 'if event X then action Y' logic. Actual custom rule logic must be built externally by consuming webhooks in the merchant's own system. Missing for 10: a native rules/automation builder, conditional trigger-action configuration UI or API, and evidence of user-defined (vs. Mollie-predefined) automated actions.

   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “Application Fees allow your platform to collect a fee on every payment you process on behalf of a connected account. You define the amount, …”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie's Subscriptions API automatically creates recurring payments at specified intervals without further manual action, which is a genuine recurring-job capability, but it is scoped strictly to payment charges rather than general workflow/job scheduling. Missing for 10: any general-purpose task/workflow scheduler, cron-like triggers beyond billing, or orchestration hooks usable outside payments.

   • [claimed-docs] “When using this API, we automatically create recurring payments for you at the interval you specified.”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “Recurring payments can be used to charge customers on a regular basis or to offer automatic top-ups with credits-based services.”
   • [claimed-docs] “Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.”

   proof ↗⚑ flag

Ai billing ops

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed4/10

   Mollie exposes webhooks with real-time payment status updates (including failures) and a Subscriptions/Payments API that an agent could poll or subscribe to via the MCP server, giving raw building blocks for monitoring failed payments programmatically. However, there is no documented dunning/retry-management feature, automated retry scheduling, or outreach tooling — an agent would have to build all retry/dunning logic itself on top of raw webhook events and API calls. Missing for 10: native dunning/retry automation, documented failed-payment recovery workflow, and evidence of an agent orchestrating retries end-to-end.

   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid. It is a URL Mollie will call with the ID of the u…”

   proof ↗⚑ flag

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed4/10

   Mollie's MCP server (mollie-supp-mcp-server) lets an agent create resources including Payment Links via natural language in one session, and the Payment Links API supports generating a shareable payment link directly from an amount/description (mollie-docs-5, mollie-docs-23). However, Mollie has no documented 'Product' or 'Price' catalog objects (unlike Stripe-style billing) — the MCP tool coverage list (Balances, Captures, Customers, Invoices, Mandates, Methods, Payments, Payment Links, Settlements, Subscriptions, Terminals, Webhooks) never mentions Products or Prices APIs, so the exact three-step workflow described isn't evidenced. Missing for 10: a Products/Prices API or equivalent catalog resource, an end-to-end documented/independent example of an agent chaining product+price+link creation in one session.

   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”

   proof ↗⚑ flag

Invoicing

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

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed3/10

   Mollie's Payment Links can be attached to an unpaid invoice and shared via email/chat, giving a hosted payment option for invoices, and an 'Invoices API' is listed among MCP-server-exposed APIs, but there is no documentation of generating/sending actual hosted invoice documents or of automatic payment reminders. missing for 10: dedicated hosted-invoice creation/send flow, automatic reminder scheduling, and any invoice-status/reminder API details.

   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

Subscriptions

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie's docs cover Subscriptions API, recurring payments, webhooks, and idempotency, but none of the evidence describes automatic retry logic for failed subscription payments, dunning schedules, or recovery emails to customers — this is a distinct capability not documented anywhere in the pack.

   ⚑ flag

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed4/10

   Mollie's Subscriptions API automates recurring payments at set intervals, which covers basic recurring billing, but the evidence shows no concept of 'plans' as reusable templates, no trial period support, no subscription upgrade/downgrade mechanism, and no proration logic — these are core parts of the story. missing for 10: plan/catalog abstraction, trial period support, upgrade/downgrade workflows, proration calculation, and any documented example of managing subscription lifecycle changes.

   • [claimed-docs] “When using this API, we automatically create recurring payments for you at the interval you specified.”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.”
   • [claimed-docs] “Recurring payments can be used to charge customers on a regular basis or to offer automatic top-ups with credits-based services.”

   proof ↗⚑ flag

Card acceptance

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

   weight 3 · round to Mollie
   Stripe!disputedcontradicted6/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie offers multiple fast paths to accept a card payment—hosted checkout, plug-and-play e-commerce plugins (Shopify/WooCommerce/Magento), and no-code Payment Links shareable via email/chat—all of which could plausibly go live quickly after signup. However, there is no explicit evidence about account verification/KYC turnaround time or a documented 'go live same day' onboarding flow, which is the crux of the founder's story. Missing for 10: explicit onboarding/KYC approval timeline evidence, first-party or independent confirmation that a new merchant can complete verification and accept a live payment within 24 hours.

   • [claimed-docs] “we provide integrations for all common e-commerce platforms, such as Shopify, WooCommerce, and Magento. Simply installing the Mollie module …”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”

   proof ↗⚑ flag

Checkout surfaces

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed8/10

   Mollie Components (Mollie JS) let developers embed PCI-DSS-compliant card fields directly in their own checkout UI rather than redirecting to a hosted page, and docs explicitly outline build-your-own-checkout via the Payments API as an alternative to hosted checkout. This covers the core story of embeddable, customizable payment components. Missing for 10: independent/hands-on developer corroboration of styling customization depth and broader component coverage beyond card fields.

   • [claimed-docs] “If, however, you are keen on building your own checkout experience, below we offer a way to implement it.”
   • [claimed-docs] “Mollie JS is a set of Javascript APIs that allow you to add the fields needed for credit card holder data to your own checkout, in a way tha…”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed9/10

   Mollie's hosted checkout is explicitly documented as a Mollie-hosted, device-optimized payment page that lets developers redirect customers without building their own UI, with e-commerce platform plugins and Payments API integration for redirect flows. missing for 10: independent/hands-on conversion-optimization evidence beyond vendor docs.

   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “Mollie's hosted payment pages have been optimized for devices of all common brands and sizes, including phones and tablets.”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “we provide integrations for all common e-commerce platforms, such as Shopify, WooCommerce, and Magento. Simply installing the Mollie module …”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”

   proof ↗⚑ flag

No code selling

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie's docs confirm a no-code Payment Links capability that lets founders generate a shareable link (email/chat) without building a full checkout, and it's explicitly called out as a 'no-code' option alongside hosted/API checkouts [mollie-docs-5, mollie-docs-23, mollie-supp-hosted-checkout]. However, the evidence never explicitly shows the dashboard UI flow for creating a payment link (it frames it as an API), so it's unclear if a founder can do this purely by clicking in the dashboard with zero technical setup. Missing for 10: explicit dashboard UI screenshots/steps for generating a payment link with no code, and confirmation that no account/API key setup is needed before selling.

   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”

   proof ↗⚑ flag

Payment methods

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

   weight 2 · round to Stripe
   Stripe~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed5/10

   Mollie's hosted checkout is documented as a single integration where 'customer can select their payment method of choice' (mollie-docs-21), and Apple Pay is explicitly called out as a checkout button option (mollie-docs-35), supporting the core 'one integration, many methods' claim. However, the evidence pack never explicitly names Google Pay, bank redirects (iDEAL/SEPA/Bancontact), or BNPL options (Klarna/Riverty) as available methods within this single integration. Missing for 10: explicit documentation of Google Pay support, bank redirect methods, and BNPL options within the same checkout integration.

   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “Display the Apple Pay button on your cart, checkout, and product pages... to speed up checkout.”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “Mollie's hosted payment pages have been optimized for devices of all common brands and sizes, including phones and tablets.”

   proof ↗⚑ flag

Pci compliance

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed8/10

   Mollie offers hosted checkout, Payment Links, and Mollie Components explicitly documented as 'fully PCI-DSS SAQ-A compliant', keeping card data off the merchant's own servers via tokenized/embedded fields or redirect, which minimizes PCI scope. missing for 10: no independent third-party audit or compliance certificate evidence, and no explicit statement of merchant SAQ-A eligibility requirements/limitations.

   • [claimed-docs] “Mollie JS is a set of Javascript APIs that allow you to add the fields needed for credit card holder data to your own checkout, in a way tha…”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “Mollie's hosted payment pages have been optimized for devices of all common brands and sizes, including phones and tablets.”
   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”

   proof ↗⚑ flag

Integration reliability

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

   weight 2 · round drawn
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed9/10

   Mollie documents the Idempotency-Key header explicitly for safe retries and even calls out the exact danger scenarios (double charges on recurring payments/subscriptions, duplicate partial refunds) that it prevents. missing for 10: independent/hands-on developer confirmation of idempotency behavior in production beyond vendor docs.

   • [claimed-docs] “you can send a unique value with every API request via the Idempotency-Key header. If two requests come in with the same value, the second r…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “In the Mollie API, these sorts of problems can be solved in two ways... you can actively i[dentify requests with an idempotency key]”

   proof ↗⚑ flag

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed5/10

   Mollie documents signed webhooks via HMAC verification (X-Mollie-Signature) and a next-gen Webhook Events API that lets developers 'retroactively inspect past events' and retrieve detailed info per triggered event, giving an audit/event-log capability. However, there is no documented automatic retry mechanism for webhook delivery, and no explicit 'replay' feature to resend a webhook event to reprocess it — idempotency keys only cover client-side API request retries, not Mollie's own webhook delivery retries. missing for 10: documented automatic webhook delivery retry policy, explicit replay/resend capability for webhook events, independent/hands-on confirmation of retry behavior.

   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: 1. Retrieve the signature from the request header (X-Mollie-Signature)...”
   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: Retrieve the signature from the request header (X-Mollie-Signature) and obtain t…”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “New event types to offer a broader context for your business processes (e.g. payment creation, invoice creation, onboarding status changes e…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”

   proof ↗⚑ flag

Onboarding dx

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

   weight 2 · round to Stripe
   Stripe✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed5/10

   Mollie's docs give a clear, well-structured path (hosted checkout, Payments API, webhooks, test mode, idempotency) that a developer could follow to build a working payment flow, and llms.txt/markdown mirrors make the docs easily consumable. However, the evidence pack never shows actual copy-paste code snippets in a specific programming language (e.g. PHP/Node/Python SDK examples) or confirms a 'under a day' end-to-end tutorial — only conceptual/API-reference descriptions are present. missing for 10: language-specific copy-paste code samples/SDK quickstarts, an explicit fast end-to-end tutorial timeline, independent developer corroboration of setup speed

   • [claimed-docs] “If, however, you are keen on building your own checkout experience, below we offer a way to implement it.”
   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”

   proof ↗⚑ flag

Sandbox fidelity

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie documents a genuine test mode that isolates test data from production, replaces hosted checkout with a walkthrough screen, and exposes a changePaymentState URL to simulate refunds and chargebacks (mollie-supp-testing, mollie-docs-18). However, the evidence never mentions specific test card numbers or a documented list of decline/failure scenarios by card, which the story explicitly calls for. Missing for 10: documented test card numbers per scenario (success, decline, insufficient funds, etc.), and independent/hands-on confirmation that test mode fully mirrors all production payment method behaviors.

   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Any payments or other resources you create in test mode are completely isolated from your live mode data.”

   proof ↗⚑ flag

Ai disputes

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie's Chargebacks API only supports retrieving chargeback details (mollie-docs-9); there is no documented capability for assembling evidence or submitting a dispute response via the API, and the MCP server's supported API list does not even include Chargebacks (mollie-supp-mcp-server). No evidence supports the 'submitting the response' half of this story.

   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

Disputes

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed3/10

   Mollie's Chargebacks API only lets merchants retrieve details of chargebacks that occurred on their account (mollie-docs-9); there is no documented capability to submit structured evidence in response to a dispute or to track a dispute lifecycle through stages to resolution. Settlement reports and balances APIs (mollie-docs-10, mollie-docs-11) help reconcile chargeback deductions financially, but this is reconciliation, not dispute-response workflow. missing for 10: evidence-submission/response mechanism for chargebacks, dispute status/lifecycle states, resolution outcome tracking, any UI or API for contesting a chargeback.

   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”

   proof ↗⚑ flag

Fraud prevention

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

   weight 3 · round to Stripe
   Stripe~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Evidence covers chargebacks retrieval, webhooks, idempotency, and testing, but there is no mention of ML-based fraud scoring or a rules engine for block/review/allow decisions on transactions.

   ⚑ flag

Refunds

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed8/10

   Docs confirm refunds can be created via the API endpoint and manually via the Mollie Web app (dashboard), and the idempotency docs explicitly reference 'partial refunds' as a supported operation, confirming both full and partial refund support across both surfaces. Missing for 10: no dedicated Refunds API reference doc explicitly listing full vs partial refund parameters, and no independent/hands-on confirmation beyond first-party docs.

   • [claimed-docs] “you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “Next to the API endpoint, you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”

   proof ↗⚑ flag

Multi currency

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed5/10

   Mollie documents accepting payments in currencies beyond EUR via its v2 APIs [mollie-docs-12], and provides Settlement Reports and Balances API for reconciling payouts [mollie-docs-10, mollie-docs-27, mollie-docs-11, mollie-docs-28], which supports part of the founder's need. However, there is no evidence detailing FX conversion rates, markup/fee transparency, or explicit confirmation that funds settle to the merchant's bank account in their own currency after conversion. Missing for 10: explicit FX rate/markup disclosure, settlement-currency selection/conversion mechanics, and independent confirmation of how multi-currency payments reconcile to a single bank currency.

   • [claimed-docs] “Mollie enables you to accept payments in currencies beyond EUR through its v2 APIs, allowing international customers to transact in their pr…”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”

   proof ↗⚑ flag

Tax

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie is a payment processing platform (checkout, payments, subscriptions, payouts, connect/marketplace splits) with no evidence of tax/VAT/GST calculation, rate lookup, or automated tax collection features anywhere in the evidence pack.

   ⚑ flag

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed7/10

   Mollie's API surface is extensive and mirrors most Dashboard functionality: payments, refunds (explicitly noted as available both via API and manually in the 'Mollie Web app'), subscriptions, balances, settlement reports, chargebacks, webhooks, and Connect split-payments/application-fees are all API-accessible. However, no evidence explicitly asserts full 1:1 API/UI parity across every dashboard feature (e.g., account settings, onboarding flows, reporting UI extras), and the MCP server itself only proxies a subset of APIs (missing Refunds, Chargebacks, Orders), leaving some UI-only gaps unconfirmed either way. Missing for 10: explicit parity statement, independent confirmation that every dashboard action has an API equivalent, and coverage of admin/config UI features not mentioned in docs.

   • [claimed-docs] “you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “Next to the API endpoint, you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “Marketplace money movement is documented under Mollie Connect: "Split payments let marketplaces distribute funds across multiple sellers in …”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”

   proof ↗⚑ flag

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

   weight 3 · round to Stripe
   Stripe~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Mollie—none0/10

   Mollie's docs show only piecemeal transaction-reporting APIs (Settlement Report, Balances API) for reconciliation, not a comprehensive account data export or account-closure/portability feature; there's no evidence of a full data export in open formats or a documented way to close an account and take all data with you.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”

   proof ↗⚑ flag

Ai reconciliation

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

   weight 3 · round to Stripe
   Stripe~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie documents a Balances API for real-time/historical balance data and a Settlement Report that breaks down transactions, fees, and deductions per payout for reconciliation, both accessible via API and exposed through the Mollie MCP server (Balances, Settlements listed as covered APIs). However, evidence doesn't show a documented API endpoint for retrieving the underlying settlement/payout line items programmatically beyond the Settlements API listing itself, nor concrete agent-driven examples of matching balance transactions to charges. missing for 10: explicit documented Settlements API line-item/transactions endpoint schema, worked example of an agent reconciling deposits to charges end-to-end, and independent/hands-on confirmation of this reconciliation workflow via API or MCP.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

Payouts

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

   weight 2 · round drawn
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed6/10

   Mollie's Settlement Report gives a full breakdown of transactions, fees, and deductions per payout, and the Balances API exposes real-time/historical balance data useful for reconciliation, directly supporting the 'see what makes up each payout' half of the story. However, there is no evidence of finance-ops controls to set or change the payout schedule (e.g., daily/weekly/custom payout frequency settings) — the docs only describe reporting/retrieval APIs, not schedule configuration. missing for 10: documented payout schedule/frequency controls, UI or API to set payout timing, confirmation that fees/refunds/chargebacks are itemized per payout beyond settlement report summary.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round to Mollie
   Stripe~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Mollie~partialclaimed7/10

   Mollie's Settlement Report explicitly gives a breakdown of a payout showing 'all transactions, fees and deductions,' and the Balances API supports bookkeeping reconciliation, while separate Chargebacks and Refunds APIs let finance-ops retrieve those items — together covering the core of the story. However, no evidence shows a single itemized report combining fees, refunds, and chargebacks in one reconciliation view, nor any bank-deposit matching feature or independent/hands-on validation of the reconciliation workflow. Missing for 10: unified itemized settlement report explicitly breaking out refunds/chargebacks line-by-line, bank-deposit matching capability, and independent user corroboration.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “you can also create refunds manually via the Mollie Web app.”

   proof ↗⚑ flag

Marketplace

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Mollie✓fullclaimed8/10

   Mollie Connect explicitly supports onboarding connected merchants, escrow-like holding of funds, split payments to multiple sellers, and application fees/commission retention for the platform, backed by documented onboarding, reporting, and payout mechanisms (settlement reports, balances API). missing for 10: independent/hands-on developer case studies building a full marketplace end-to-end, and more detail on seller onboarding KYC flow specifics beyond doc mentions.

   • [claimed-docs] “Mollie Connect lets software platforms and marketplaces offer payment and money management capabilities to their merchants under their own b…”
   • [claimed-docs] “Split payments let marketplaces distribute funds across multiple sellers in a single transaction.”
   • [claimed-docs] “Application Fees allow your platform to collect a fee on every payment you process on behalf of a connected account.”
   • [claimed-docs] “Marketplace money movement is documented under Mollie Connect: "Split payments let marketplaces distribute funds across multiple sellers in …”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “Application Fees allow your platform to collect a fee on every payment you process on behalf of a connected account. You define the amount, …”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe—none0/10

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

   ⚑ flag

   Mollie—none0/10

   Mollie is a payments API/platform; no evidence in the pack addresses data retention policies, data deletion controls, or export/erasure mechanisms for AI-native users. The evidence covers payments, checkout, webhooks, Connect, and MCP server capabilities but nothing about privacy/data lifecycle controls.

   ⚑ flag