Adyen vs Airwallex

Agent access

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

   weight 2 · round to Adyen
   Adyen✓fullprobed10/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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

Ai billing ops

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

   weight 3 · round drawn
   Adyen~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

   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