Stripe vs Airwallex

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

   Airwallex✓fullprobed9/10

   Airwallex publishes a live llms.txt (confirmed HTTP 200 probe) plus explicit agent-oriented docs (developer-connector.md, agentos.md, ai-agent-instructions.md) designed for machine/agent consumption, including instructions written specifically for AI agents and dedicated MCP endpoints. This directly matches pointing an agent at llms.txt/agent-oriented docs. Missing for 10: independent third-party confirmation that agents successfully consume these docs in practice (only vendor docs and a probe, no hands-on community report).

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.airwallex.com/llms.txt # Airwallex > Airwallex is a leading global financial platform for modern bus…”
   • [claimed-docs] “The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar tools — to Airwallex documentation an…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”

   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

   Airwallex✓fullprobed8/10

   Airwallex ships a documented CLI explicitly designed for scripting and CI ("script repeatable tasks, and wire Airwallex into automated systems"), plus API/webhook infrastructure enabling headless automation, corroborated by a probe confirming the CLI docs exist. Missing for 10: independent third-party evidence of actual CI pipeline usage and explicit CI/CD examples (e.g., GitHub Actions integration) beyond vendor docs.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”

   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

   Airwallex✓fullprobed9/10

   Airwallex documents an official hosted remote MCP server (AgentOS MCP at https://mcp.airwallex.com/mcp) with OAuth authentication, safety guardrails, and explicit connection instructions for MCP clients like Claude Code, plus a separate Developer MCP for docs/sandbox integration work — both first-party and independently probed as live docs. Missing for 10: independent hands-on third-party verification of the MCP server actually working end-to-end beyond vendor docs and a probe confirming the doc page exists.

   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   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

   Airwallex✓fullprobed9/10

   Airwallex documents an official CLI (installable via a public install script) that exposes API resources as terminal commands, supports sandbox/production modes, scripting, and is explicitly positioned as the foundation for AI coding agents to operate accounts, corroborated by a probe confirming the docs page exists. Missing for 10: independent/hands-on third-party review of the CLI beyond vendor docs and probes.

   • [claimed-docs] “The Airwallex CLI lets you work with your Airwallex account directly from a command line.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex publishes extensive first-party API documentation, scoped API keys, a sandbox environment, CLI, webhooks with retry semantics, and even dedicated 'Instructions for AI agents' pages plus AgentOS/MCP tooling explicitly built for agentic/programmatic use, confirmed live via probes (llms.txt 200, CLI and AgentOS docs pages resolving). Missing for 10: independent third-party developer corroboration (e.g. community reviews of the public API itself) beyond vendor docs and probes.

   • [claimed-docs] “Programmatically create connected accounts for businesses and individuals, and enable them with rich financial capabilities.”
   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”
   • [claimed-docs] “The Airwallex CLI lets you work with your Airwallex account directly from a command line.”
   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.airwallex.com/llms.txt # Airwallex > Airwallex is a leading global financial platform for modern bus…”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   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

   Airwallex✓fullclaimed8/10

   Airwallex documents scoped API keys with granular Read/Write permissions per resource (not full account access), and explicitly ties this to agent use cases via AgentOS/MCP with additional layered safety defaults (no money-out actions by default, OAuth-scoped roles, role-gated CLI authorization). This directly matches the story of issuing least-privilege credentials for an agent. Missing for 10: independent/hands-on verification of scope enforcement and no documented UI/API walkthrough of creating a scoped key specifically for an agent identity.

   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   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

   Airwallex✓fullprobed9/10

   Airwallex documents a full official SDK/API surface for AI-native building: REST API, official CLI, hosted MCP servers (AgentOS MCP and Developer MCP), dedicated AI-agent instructions pages, sandbox environment, webhooks, and plugin installs for Claude Code/Cursor. This is well beyond a typical SDK — it includes machine-readable docs, scoped API keys, and agent-specific tooling with safety guardrails, confirmed by both docs and independent probes. Missing for 10: independent third-party developer reviews/hands-on validation of SDK ergonomics beyond vendor docs.

   • [claimed-docs] “The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar tools — to Airwallex documentation an…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Airwallex
   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

   Airwallex✓fullclaimed9/10

   Airwallex documents a full webhooks system with real-time push notifications, stable event IDs for safe retry handling, delivery status inspection, and re-delivery for debugging — clearly enabling event subscription for automated/AI-native workflows. Missing for 10: no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”

   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

   Airwallex~partialclaimed4/10

   AgentOS documents pre-built agent workflows including 'building cashflow reports' and 'cashflow management' skills, which implies some data-driven insight generation via AI agents, but this is framed as an external agent toolkit for action-taking (transfers, beneficiaries, cards) rather than a native in-product analytics/insights feature surfaced to users. Missing for 10: evidence of a built-in AI insights/suggestions panel or dashboard inside the Airwallex web app itself, and independent/hands-on confirmation that agent-generated 'reports' actually surface proactive suggestions rather than just executing user-directed tasks.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiaries, issuing…”

   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

   Airwallex~partialclaimed6/10

   AgentOS bundles a hosted MCP server, CLI, and pre-built 'Skills' explicitly designed for agents to run multi-step financial workflows 'on your behalf', and webhooks provide event-driven triggers with retry/dedup semantics for automated systems (awx-supp-agentos, awx-supp-agentos-mcp, awx-supp-cli, awx-supp-webhooks). However, these are agent-invoked or event-triggered rather than a documented persistent scheduler/orchestrator, and AgentOS enforces 'no money-out actions by default', limiting true autonomous background operation. Missing for 10: evidence of a native scheduling/cron mechanism or always-on background execution engine, and independent confirmation that automations run unattended without per-invocation agent triggering.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”

   proof ↗⚑ flag

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

   weight 3 · round to Airwallex
   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

   Airwallex~partialclaimed5/10

   Airwallex doesn't ship a native in-product chat assistant, but its AgentOS toolkit (CLI + hosted MCP server + pre-built 'skills') lets an AI agent read balances, create beneficiaries, issue cards, and run multi-step workflows on the user's behalf, effectively delegating account tasks — though the actual assistant runs in an external client (Claude Code, Cursor, Claude Cowork) rather than being embedded in Airwallex's own UI. Missing for 10: a first-party assistant surfaced directly inside the Airwallex web app/dashboard, and independent hands-on evidence of end-users delegating tasks this way.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”

   proof ↗⚑ flag

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

   weight 2 · round to Airwallex
   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

   Airwallex✓fullprobed8/10

   Airwallex ships AgentOS with an MCP server and CLI explicitly designed so AI agents (Claude Code, Cursor, Codex) can read balances, create beneficiaries, issue cards, and run multi-step financial workflows via natural-language instructions, plus dedicated 'AI agent instructions' docs to guide correct NL-driven API use. Missing for 10: independent/hands-on validation of real-world NL command reliability and no third-party review beyond first-party docs.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   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

   Airwallex~partialclaimed5/10

   Airwallex docs claim you can 'explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration' via the CLI, and a sandbox environment lets you run real requests without live money, which together approximate an interactive, runnable API exploration experience. However, there's no evidence of a traditional in-browser interactive API reference (e.g., Swagger/Redoc-style docs with embedded runnable code snippets) — the interactivity is CLI-driven rather than a reference page. Missing for 10: a dedicated interactive web API reference UI, embedded runnable code samples in docs, and independent confirmation of this workflow.

   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”

   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

   Airwallex—none0/10

   While Airwallex documents extensive API tooling (CLI, MCP servers, sandbox, interactive schema explorer), none of the evidence explicitly confirms a downloadable OpenAPI (or equivalent) spec file. The 'inspect schemas' feature (airwallex-docs-20) hints at schema-driven tooling but doesn't confirm exportable machine-readable spec access.

   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Airwallex✓fullclaimed9/10

   Airwallex documents a dedicated sandbox environment fully separate from production, covering nearly all products/APIs, with self-serve signup and simulation guides, and even AI-specific sandbox MCP/connector tooling (mcp.sandbox.airwallex.com/developer) explicitly for agents to 'create test resources, simulate events, and call sandbox endpoints' without touching production. The CLI also defaults to sandbox unless --prod is passed, reinforcing safe-by-default testing. Missing for 10: independent/hands-on confirmation of sandbox parity beyond docs.

   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   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

   Airwallex—none0/10

   The evidence pack covers API keys, sandbox, CLI, MCP/AgentOS, webhooks, and AI-agent instructions, but nowhere documents API versioning conventions or a formal deprecation policy/timeline for endpoints. The only related hint is steering away from a 'legacy' SDK library, which is not evidence of a documented API versioning/deprecation policy.

   ⚑ 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

   Airwallex~partialclaimed4/10

   The Airwallex CLI and AgentOS toolkit let AI agents 'script repeatable tasks' and 'wire Airwallex into automated systems' or run 'multi-step financial workflows,' which implies looping over many items via API/CLI calls, but there is no documented native batch/bulk endpoint (e.g., bulk beneficiary creation, batch payouts, bulk invoice generation) for processing many items in a single call. Missing for 10: explicit bulk/batch API or CLI subcommands, evidence of batch-processing limits or throughput, and independent confirmation of bulk usage in practice.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”

   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

   Airwallex~partialclaimed5/10

   Airwallex supports event-driven automation via webhooks (real-time push notifications with retry/dedupe semantics) and AgentOS/CLI/MCP tooling that lets agents run multi-step workflows, but there is no documented user-facing 'rules engine' where an AI-native user declaratively defines trigger-condition-action rules — automation still requires building a webhook consumer or scripting agent workflows rather than configuring rules in-product. missing for 10: a native rules/automation builder (event + condition + action) exposed via API or UI, and independent evidence of such rule-based automation actually firing in production.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Airwallex~partialclaimed3/10

   Airwallex's Billing product supports recurring invoices and multi-frequency subscription billing, and AgentOS advertises 'multi-step financial workflows' and pre-built 'Skills,' but there is no documented scheduler/cron capability letting an AI agent set up or trigger recurring automated jobs itself — recurring billing is a finance feature, not an agent-orchestrated recurring workflow mechanism. missing for 10: an explicit job/workflow scheduler API or cron-like trigger for AgentOS/CLI/MCP, evidence of agents autonomously re-running workflows on a schedule, independent confirmation of recurring automation in practice.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiaries, issuing…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Stripe—none0/10

   Stripe's automation features (Billing recurring rules, Smart Retries, Radar rules, webhooks, Kyber no-code flows) have no documented version-history, review/diff, or rollback mechanism in the evidence. API versioning (stripe-docs-45/59) covers backward-compatible monthly API releases, not versioning of a user's automation configurations, so it doesn't satisfy this story.

   • [claimed-docs] “You can safely upgrade to a new monthly release without breaking any existing code.”
   • [claimed-docs] “Each monthly release includes only backward-compatible changes... You can safely upgrade to a new monthly release without breaking any exist…”
   • [claimed-docs] “Smart Retries: Automatically retry failed payments to prevent involuntary churn due to temporary issues.”
   • [claimed-docs] “Use Stripe Billing to manage subscriptions and invoicing. It automates recurring payments, creates custom pricing plans, and handles billing…”
   • [claimed-docs] “The no-code builder Kyber lets users assign tasks and automate common workflows based on Stripe events. Users can quickly configure automati…”

   proof ↗⚑ flag

   Airwallex—none0/10

   Airwallex documents AI agent tooling (AgentOS, MCP, CLI, skills/plugins) for executing financial workflows, but there is no evidence of version control, review workflows, or rollback capability for automations themselves — e.g. no changelog/versioning of skills, no diff/review UI, no rollback mechanism for executed multi-step workflows beyond webhook event replay (which is for delivery, not automation state).

   ⚑ 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

   Airwallex~partialclaimed5/10

   Airwallex provides the raw building blocks an agent could use for this story: webhooks with retry-safe event IDs and delivery inspection/re-delivery, an AgentOS MCP/CLI toolkit that can read balances and act on the production account, and API access to payments/billing data. However, there is no documented failed-payment monitoring workflow, no dunning/retry-specific Skill, and 'no money-out actions by default' in AgentOS suggests retry/charge actions would be restricted, requiring custom agent logic rather than a built-in capability. missing for 10: a documented failed-payment retry or dunning skill/workflow, evidence of automated retry logic tied to webhook failed-payment events, and confirmation that money-out/retry actions are actually permitted for agents rather than blocked by default guardrails.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”

   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

   Airwallex~partialclaimed6/10

   Airwallex has real billing/invoicing/payment-link APIs and an agent-facing toolkit (AgentOS/CLI/MCP) that can create beneficiaries, cards, and run multi-step workflows, and docs explicitly cover products, subscriptions, invoicing, and payment links, but no evidence shows a documented single-session flow where an agent creates a product, sets a price, and generates a payment link end-to-end via one skill/workflow. missing for 10: an explicit worked example or skill covering product+price+payment-link creation in one agent session, and independent/hands-on confirmation this multi-step billing workflow works in practice.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

Invoicing

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

   weight 2 · round drawn
   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

   Airwallex~partialclaimed6/10

   Airwallex Billing supports one-time and recurring invoicing with online payment via 160+ local payment methods (docs-14, docs-25), but the evidence pack does not explicitly confirm automatic payment reminders for unpaid invoices. missing for 10: explicit documentation of automated reminder scheduling/notifications for overdue invoices, independent/hands-on confirmation of the reminder feature working in practice.

   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”

   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

   Airwallex—none0/10

   Airwallex Billing docs cover subscriptions, invoicing, and payment collection but there is no mention of automatic retry logic for failed subscription payments, smart dunning rules, or automated recovery email sequences.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ 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

   Airwallex~partialclaimed5/10

   Airwallex Billing documents subscription management with multi-item and multi-frequency billing plus recurring invoicing, indicating core plan-based recurring billing capability. However, the evidence pack never mentions trial periods, plan upgrades/downgrades, or proration logic explicitly. Missing for 10: documented trial period support, upgrade/downgrade workflows, and proration calculation mechanics.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

Card acceptance

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

   weight 3 · round to Airwallex
   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

   Airwallex~partialclaimed6/10

   Airwallex offers fast-to-integrate options for accepting online card payments quickly (Payment Links requiring no storefront, Hosted Payment Page, Drop-in Element, sandbox quickstart), which are consistent with a founder going live within a day. However, the evidence does not document the actual account-opening/KYC onboarding timeline or approval SLA for a brand-new founder signing up, which is the critical gatekeeper before any live payment can be accepted. Missing for 10: documented onboarding/KYB approval turnaround time, explicit same-day go-live confirmation, and independent/hands-on evidence of a founder completing signup-to-first-payment within 24 hours.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   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

   Airwallex✓fullclaimed8/10

   Airwallex offers a Drop-in Element and embeddable checkout components (createElement with customizable appearance/layout, field auto-adjustment) as an alternative to the Hosted Payment Page, plus embedded checkout in Billing, directly enabling in-page/in-app embedded payments rather than redirects. Missing for 10: independent/hands-on developer corroboration of the embedded element's real-world customization depth and no evidence of broader UI kit flexibility beyond docs.

   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Pass appearance and layout in createElement(...). For examples and supported values, see Customize style and appearance”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”
   • [claimed-docs] “Custom styling rules so you can match the look and feel of your site”

   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

   Airwallex✓fullclaimed9/10

   Airwallex documents a Hosted Payment Page — a secure, pre-built, Airwallex-hosted checkout supporting multiple payment methods with custom styling, plus a quickstart showing end-to-end integration without building custom payment UI, and payment links for no-code acceptance. missing for 10: independent/hands-on conversion-optimization benchmarks beyond vendor docs.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Custom styling rules so you can match the look and feel of your site”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”

   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

   Airwallex~partialclaimed6/10

   Payment Links are documented as 'the easiest way to accept payments online without a digital storefront,' supporting no-code shareable link creation, and other docs (invoicing, quickstart) reinforce a self-serve dashboard flow. However, there's no direct evidence of the dashboard UI/UX for founders (e.g., screenshots, step count, signup-to-first-sale time) or independent/hands-on confirmation of ease of setup. missing for 10: dashboard UI walkthrough or screenshots, independent/hands-on confirmation of no-code simplicity, evidence of account approval/KYC turnaround time before selling.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   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

   Airwallex~partialclaimed6/10

   Docs confirm a single integration (Hosted Payment Page / Drop-in Element / Payment Links) that adapts fields per payment method/country and mentions 160+ local payment methods via invoicing, plus multi-currency pricing to unlock local methods, but no explicit evidence naming Apple Pay, Google Pay, bank redirects, or BNPL support. Missing for 10: explicit listing/documentation of specific wallets (Apple Pay/Google Pay) and BNPL providers, and independent confirmation these render correctly in a single checkout integration.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies, while also…”
   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”

   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

   Airwallex~partialclaimed5/10

   Airwallex offers a Hosted Payment Page and Drop-in Elements that are pre-built, Airwallex-hosted card collection UIs implying card data doesn't touch the merchant's servers, which is the typical mechanism for reducing PCI scope. However, no evidence explicitly discusses PCI DSS compliance, SAQ scope reduction, or tokenization-for-compliance framing. missing for 10: explicit PCI DSS scope statements, tokenization/vaulting documentation, SAQ-A or compliance certification details, independent confirmation that card data never touches merchant servers.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

Integration reliability

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

   weight 2 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Airwallex—none0/10

   The evidence pack describes webhook delivery reliability (stable event IDs for webhook retries) but contains no documentation of idempotency keys for outbound API requests (e.g., payment creation) to prevent duplicate charges on retry. This is a distinct, applicable axis for a payments API but is unevidenced here.

   ⚑ 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

   Airwallex~partialclaimed6/10

   Airwallex's webhook docs describe reliability primitives that map to most of this story: a required 200 response for delivery confirmation, a stable event id explicitly for safe retry handling/deduplication, and a web app view to inspect delivery status and re-deliver events after downtime or debugging (covers automatic retries, event logs, and replay). However, none of the evidence explicitly documents cryptographic signature verification for webhook payloads. Missing for 10: explicit signed-webhook/signature-verification documentation, and independent/hands-on confirmation of retry behavior in practice.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”

   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

   Airwallex~partialclaimed6/10

   There is a clear quickstart doc ('Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page') plus a self-serve sandbox and multiple integration options (Hosted Payment Page, Drop-in Element) with styling/config snippets, suggesting a fast path to a working payment flow. However, the evidence pack never shows actual copy-paste code samples in specific languages (e.g., Node, Python, PHP) or confirms multi-language SDK coverage, nor any independent developer report confirming a sub-day integration time. Missing for 10: concrete multi-language code snippets, language/SDK coverage, and independent hands-on confirmation of integration speed.

   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Pass appearance and layout in createElement(...). For examples and supported values, see Customize style and appearance”

   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

   Airwallex~partialclaimed6/10

   Airwallex documents a full sandbox environment mirroring production (all products except Connected Account APIs), simulation docs for payments/payouts/deposits/issuing/risk, and a quickstart for an end-to-end sandbox payment flow, plus dispute-handling docs. However, there is no explicit mention of a documented set of test card numbers covering specific decline reason codes or dispute-triggering scenarios. missing for 10: documented test card numbers/scenarios for specific decline codes, explicit dispute-simulation test cards, independent developer confirmation of sandbox fidelity to production.

   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”

   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

   Airwallex—none0/10

   Airwallex documents a general disputes process page (docs-26) but no API endpoints for retrieving disputes, assembling evidence, or submitting responses, and the AgentOS/CLI 'skills' list (contract-to-billing, beneficiary creation, card provisioning, cashflow management) never mentions disputes as a supported agent workflow. Missing for 10: dispute-retrieval API, evidence-assembly workflow, dispute-response submission API, and any AgentOS/CLI skill or MCP tool covering disputes end-to-end.

   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”

   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

   Airwallex~partialclaimed3/10

   Airwallex docs confirm a dispute-management feature exists ('Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome'), implying some workflow for chargebacks, but there is no evidence of structured evidence submission templates, evidence checklists, or dispute lifecycle status tracking in the UI/API. Missing for 10: documentation of evidence upload/structuring, dispute status/lifecycle tracking (open/under review/won/lost), API or webhook events specifically for dispute state changes, and any independent confirmation of the workflow.

   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”

   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

   Airwallex—none0/10

   The evidence pack covers payments, billing, transfers, AI/developer tooling, webhooks, and dispute facilitation, but contains no mention of ML-based fraud scoring or a rules engine for custom block/review/allow rules; only generic dispute-management language and a sandbox mention of 'risk' simulations without detail. This is a fair capability to expect from a payments platform, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”

   proof ↗⚑ flag

Refunds

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

   weight 3 · round to Stripe
   Stripe✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Docs confirm refunds are a documented capability ('When a shopper returns goods or services, you can issue a refund to return their funds') and the CLI/API expose broad read/write access to Airwallex resources including presumably refunds, but no evidence explicitly confirms a dashboard refund UI or distinguishes full vs partial refund support at the API/dashboard level. Missing for 10: explicit documentation of partial refund amounts, dashboard UI screenshots/flow for issuing refunds, and independent/hands-on confirmation of both channels working.

   • [claimed-docs] “When a shopper returns goods or services, you can issue a refund to return their funds.”

   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 drawn
   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

   Airwallex✓fullclaimed8/10

   Airwallex directly supports charging customers via 160+ local payment methods and multi-currency pricing (accepting in local currencies), and its multi-currency Wallet enables like-for-like settlement without forced FX conversion, explicitly marketed as eliminating FX fees versus traditional gateways that force home-currency settlement. Transfers/payouts and invoicing further round out the collect-and-settle flow, backed by first-party docs. Missing for 10: independent/hands-on verification of actual FX rates charged and real-world transparency (e.g., third-party review of fee disclosure) beyond vendor documentation.

   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies, while also…”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies”

   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

   Airwallex~partialclaimed6/10

   Airwallex's Merchant of Record add-on explicitly automates sales tax, VAT, and GST calculation and collection per sale, letting sellers avoid registering for tax in each market. However, it is documented as a beta feature limited to digital products only (physical goods unsupported), has restricted eligibility, and leaves refunds/disputes to the merchant — so it doesn't cover all transaction types a finance-ops user might need automated tax handling for. Missing for 10: general availability (non-beta) status, physical goods/product coverage, and independent/hands-on verification of tax accuracy across jurisdictions.

   • [claimed-docs] “Sell digital products globally without registering for tax in every market. With Airwallex Merchant of Record, Airwallex acts as the legal s…”
   • [claimed-docs] “Airwallex also documents a merchant-of-record add-on (beta): "With Airwallex Merchant of Record, Airwallex acts as the legal seller and mana…”

   proof ↗⚑ 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

   Airwallex~partialclaimed7/10

   Airwallex documents an extensive API surface plus a CLI that 'exposes a broad slice of the Airwallex API as terminal commands' and an AgentOS/MCP toolkit letting agents read balances, create beneficiaries, issue cards, and run workflows — strong evidence that most UI actions have programmatic equivalents. However, AgentOS explicitly ships with 'no money-out actions by default' as a safety guardrail, and Connected Account APIs are excluded from sandbox, indicating some UI-capable actions are deliberately restricted or gated via role/OAuth permissions rather than fully mirrored in the API/agent tooling. Missing for 10: confirmation that all money-movement and account-management UI actions are reachable via API without special unlocking, and independent/hands-on verification that the CLI/MCP truly cover 100% of UI functionality.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”

   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

   Airwallex—none0/10

   Airwallex is a financial platform (payments, treasury, billing) with an API/CLI/MCP for account operations, but there is no evidence of a bulk data export feature or open-format data portability that would let a user export all their account data and leave the platform. The APIs allow reading individual resources but no documented full-account export/migration tool is mentioned.

   ⚑ 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

   Airwallex~partialclaimed6/10

   Airwallex documents agent-facing tooling (AgentOS, CLI, MCP server) that lets an agent read balances, build cashflow reports, and pull payout/transfer data programmatically, and the CLI/MCP explicitly support scripting/read access to production resources. However, there is no specific mention of a 'balance transaction' API endpoint or a documented reconciliation workflow matching bank deposits to underlying charges — the closest is generic 'cashflow reports' and 'Skills' bundles. Missing for 10: explicit balance-transactions API/reconciliation endpoint docs, a worked example of matching payouts to charges, and independent/hands-on evidence of this reconciliation working end-to-end.

   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”

   proof ↗⚑ flag

Payouts

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

   weight 2 · round to Stripe
   Stripe~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Airwallex—none0/10

   The evidence pack covers Airwallex's transfers, billing, invoicing, and webhook capabilities but contains no mention of configurable payout schedules or itemized payout reports that break down constituent charges, fees, and refunds — a distinct reconciliation feature payment platforms typically document separately.

   ⚑ flag

Reconciliation

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

   weight 3 · round to Stripe
   Stripe~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Airwallex—none0/10

   Evidence covers payments, payouts/transfers, refunds, disputes, webhooks, billing/invoicing, and treasury, but there is no mention of a settlement-to-bank-deposit reconciliation report, itemized fee/refund/chargeback breakdowns tied to deposits, or any reconciliation-specific reporting feature for finance-ops. Refunds and disputes are documented in isolation but not connected to a reconciliation/report workflow.

   • [claimed-docs] “When a shopper returns goods or services, you can issue a refund to return their funds.”
   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”

   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

   Airwallex✓fullclaimed8/10

   Airwallex explicitly documents programmatic creation of connected accounts for businesses/individuals with financial capabilities (marketplace onboarding), plus Transfers/payouts to move funds to suppliers/contractors, and multi-currency wallet settlement — the core building blocks for onboarding sellers and paying them out. Payment splitting isn't explicitly named as a feature but is a natural extension of connected accounts + transfers, and sandbox/webhooks support building and testing such flows end-to-end. Missing for 10: explicit documentation of a 'split payment' or marketplace-specific API/feature, and independent case studies of marketplaces built on Airwallex.

   • [claimed-docs] “Programmatically create connected accounts for businesses and individuals, and enable them with rich financial capabilities.”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe—none0/10

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

   ⚑ flag

   Airwallex—none0/10

   No documentation describes a data residency/region-selection feature letting users choose where their data is stored; the community item raises concerns about China/HK data access but does not confirm or deny any residency-choice capability.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe—none0/10

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

   ⚑ flag

   Airwallex—none0/10

   Airwallex's evidence pack covers API scoping, sandbox environments, MCP/CLI tooling, and payment features, but nowhere addresses data retention policies or user-initiated data deletion controls (e.g., GDPR/CCPA-style deletion requests, retention period configuration). This is a fair axis for a fintech handling AI-agent data, but no capability is documented.

   ⚑ flag