Stripe Crypto & Stablecoins vs Coinbase Payments (CDP)

Agent access

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

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins✓fullprobed8/10

   Stripe's docs.stripe.com exposes an llms.txt file (HTTP 200) and per-page .md agent-readable docs (e.g. crypto.md, stablecoin-payments.md, machine.md), confirmed by direct probes, so an agent can be pointed at llms.txt or markdown docs directly. Missing for 10: no independent/community confirmation of an agent actually consuming llms.txt successfully, and no dedicated agent-oriented documentation index beyond the generic llms.txt.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed9/10

   Probe confirms llms.txt is live (HTTP 200) at docs.cdp.coinbase.com, listing 538 pages of docs, and multiple docs entries are directly sourced from that llms.txt, showing agent-oriented documentation is real and accessible. Missing for 10: no independent third-party report of an agent successfully consuming llms.txt to complete a task.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (538 pages)](https://docs.cdp…”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe provides a documented CLI (stripe-cli) and API-based integration for crypto/stablecoin payments, which enables headless/automated/CI usage of the broader Stripe platform, and a machine-payment protocol (x402) suited for agentic/automated payment flows. However, there's no crypto-specific evidence of CI/test-mode tooling, fixtures, or automation examples tailored to the crypto product beyond generic docs. Missing for 10: crypto-specific CI/test examples, sandbox/test-mode automation docs, and independent confirmation of headless workflows for stablecoin features.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialprobed6/10

   CDP offers SDKs and a CLI (with an MCP server exposing every API endpoint as a tool) that can be scripted headlessly for automation and CI, and its API-first design (webhooks, x402, wallet SDKs) supports programmatic/agentic use. However, there's no explicit documentation of CI-specific patterns (e.g., service-account auth for pipelines, GitHub Actions examples, or headless auth flows without browser/UI steps). missing for 10: explicit CI/headless authentication guidance, CI pipeline examples, independent confirmation of non-interactive operation.

   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”

   proof ↗⚑ flag

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

   weight 3 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins✓fullprobed6/10

   Stripe publishes an official MCP server (docs.stripe.com/mcp) that lets AI agents connect to Stripe capabilities, and Stripe itself is a service/platform (not an agent), so the axis applies and is satisfied. missing for 10: no detail on which crypto/stablecoin tools are exposed via MCP, no independent/hands-on corroboration of the MCP server's functionality.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed8/10

   Coinbase Payments (CDP) ships an official MCP server via the CDP CLI (`cdp mcp`) exposing every API endpoint as a tool, plus a separate Coinbase Wallet MCP for AI agent wallet actions, both documented and probe-confirmed. missing for 10: independent/hands-on third-party corroboration beyond first-party docs and probes.

   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
   • [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins✓fullprobed7/10

   Stripe documents an official CLI (stripe-cli) as part of its platform, which applies to the Crypto & Stablecoins product since it's built on the same Stripe API/tooling. missing for 10: X, Y - no crypto-specific CLI command examples, no independent/hands-on confirmation of CLI use for crypto endpoints.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed8/10

   CDP ships an official CLI that also includes an MCP server (`cdp mcp`) exposing every API endpoint as a tool, and docs explicitly reference using the CDP CLI for treasury/payout workflows, directly supporting AI-native/agentic use. Missing for 10: independent hands-on verification of CLI usage and richer documentation of CLI command coverage beyond MCP exposure.

   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”

   proof ↗⚑ flag

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

   weight 3 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialprobed6/10

   Stripe Crypto is part of the broader Stripe API/platform, which is documented and programmatically drivable (docs.stripe.com, CLI, MCP server referenced), and x402 protocol support suggests machine-native payment flows. However, the evidence pack lacks crypto-specific API reference/OpenAPI spec (openapi probe returned 404s) or SDK examples for driving crypto/stablecoin features specifically via API. missing for 10: crypto-specific API reference or OpenAPI schema, explicit SDK/code examples for stablecoin endpoints, independent confirmation of agentic/API-driven crypto workflows beyond x402 mention.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed8/10

   CDP exposes a documented public API/SDK covering wallets, payments, onramp, x402, and webhooks, with client libraries (cdp-sdk) and an explicit CLI/MCP server (`cdp mcp`) exposing every API endpoint as a tool for AI-native workflows. missing for 10: a discoverable OpenAPI/swagger spec (probe found all candidate paths 404), and independent third-party corroboration beyond vendor docs.

   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
   • [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Coinbase Payments (CDP)—none0/10

   The evidence pack describes CDP's payment features, wallets, webhooks, and an MCP/CLI surface for agents, but nowhere documents scoped or least-privilege API key/credential issuance (e.g., permission-limited API keys, role-based scopes, or agent-specific credential restrictions). Missing for 10: any mention of API key scopes/permissions, credential restriction mechanisms, or least-privilege agent authentication documentation.

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe's crypto/stablecoin docs are exposed as machine-readable markdown, an llms.txt index, an official CLI, and a documented MCP server, suggesting the crypto APIs are reachable via Stripe's standard official SDKs, but the evidence never explicitly names or links official language SDKs (e.g., stripe-node/python/ruby) covering crypto/stablecoin endpoints. Missing for 10: explicit SDK documentation/examples for crypto features, independent corroboration of SDK usage in agentic/AI workflows, and confirmation the OpenAPI spec (needed for SDK generation) is accessible (probe found it 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed8/10

   Coinbase Payments provides official client SDKs (cdp-sdk on GitHub for EVM/Solana wallets), plus CLI and MCP server tooling explicitly aimed at AI-native/agentic use (x402 payments, MCP for AI assistants, wallet-per-agent support), all documented first-party. Missing for 10: independent/third-party corroboration of SDK quality and a public OpenAPI spec (probe found openapi.json 404s), which would strengthen developer trust.

   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
   • [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
   • [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
   • [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack covers crypto/stablecoin payment features, onramp, payouts, financial accounts, and even x402 protocol support, but contains no mention of webhooks or event subscription mechanisms for the crypto/stablecoin product. Webhooks are a plausible and expected capability for a payments API, so the axis applies, but no evidence supports it here.

   ⚑ flag

   Coinbase Payments (CDP)✓fullclaimed8/10

   Docs explicitly describe webhooks for real-time HTTP notifications on CDP integration events, including multi-address wallet activity subscriptions, which fits the ai-native agenticness theme of event-driven automation. Missing for 10: independent/hands-on confirmation of webhook reliability and no explicit event-type catalog or signature-verification detail in evidence.

   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack covers crypto/stablecoin payment features (onramp, payouts, financial accounts) but contains no mention of automation setup, scheduling, workflows, or autonomous background agent execution tied to this product. missing for 10: any evidence of automation/workflow builder, scheduling or triggers, autonomous agent execution, or background task orchestration.

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed6/10

   CDP provides building blocks for autonomous background automation—webhooks for event-driven triggers, auto-liquidation/auto-convert on incoming payments, x402 for agent-to-agent programmatic payments, and an MCP server exposing all API endpoints as tools for AI agents to call—which together let developers wire up unattended, background-running payment flows. However, this is a set of APIs/SDKs and integration primitives rather than a hosted, first-party autonomous automation/orchestration runtime that runs itself; the user must build and host the actual automation logic. Missing for 10: evidence of a native scheduler or persistent agent-runtime service, and independent/hands-on confirmation that these pieces compose into a working autonomous background automation.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
   • [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
   • [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Coinbase Payments (CDP)—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe documents an official MCP server (docs.stripe.com/mcp) that would let AI agents/LLMs invoke Stripe functionality via natural-language-driven tool calls, and the crypto/stablecoin docs describe machine-native payment support over the x402 protocol for agentic/automated transactions. However, there is no direct evidence of a natural-language command interface specifically for the crypto/stablecoin product surface (onramp, financial accounts, payouts), and no hands-on confirmation of AI-native operation. Missing for 10: crypto-specific natural-language command examples, hands-on/independent verification of MCP or x402 usage for stablecoin flows, and documentation tying the MCP server to crypto-specific actions.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialprobed6/10

   CDP exposes an MCP server (`cdp mcp`) that surfaces every API endpoint as a tool, and Coinbase Wallet MCP lets an AI assistant check balances, send funds, swap tokens, and pay with x402 — enabling natural-language operation via an MCP-compatible AI client. However, this requires a separate AI client/agent host to interpret NL commands; there's no evidence of a built-in chat/NL interface within CDP itself, no independent hands-on validation of the MCP tool coverage, and no examples of complex NL command sequences being executed reliably. missing for 10: first-party or independent demonstration of end-to-end natural-language command execution, evidence of NL interface beyond MCP tool exposure, and confirmation of reliability/robustness of the MCP tool-calling across the full API surface.

   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
   • [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   Evidence shows Stripe docs, an llms.txt file, and a CLI/MCP server, but there is no mention of an interactive API reference with runnable examples (e.g., API explorer, try-it console). OpenAPI probe returned 404s, and no docs cite an interactive playground for crypto/stablecoin endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   There is no evidence of an interactive API reference with runnable examples; the OpenAPI spec probe returned 404s on all candidate paths, and no docs mention interactive playgrounds or executable code snippets. Missing for 10: interactive API reference UI, runnable/executable examples, OpenAPI/Swagger spec availability.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack explicitly shows a probe that checked common OpenAPI spec locations (openapi.json, swagger.json, etc.) and all returned 404, and no other citation confirms a downloadable machine-readable API spec for Stripe Crypto & Stablecoins. Only llms.txt and markdown docs are shown as available, not a structured OpenAPI/JSON schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   A direct probe for common OpenAPI spec paths returned 404s, and no evidence pack item links to a downloadable machine-readable API spec; only an llms.txt docs index and MCP/CLI tooling are documented, which are not equivalent to an OpenAPI spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (538 pages)](https://docs.cdp…”

   proof ↗⚑ flag

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

   weight 1 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack for Stripe Crypto & Stablecoins covers wallets, onramp, payouts, refunds, and cards, but nowhere mentions a test/sandbox mode or non-production environment for crypto/stablecoin flows. Since sandbox testing is a plausible and expected capability for an API-based payments product, its absence here is a gap rather than an inapplicable axis.

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed6/10

   Docs explicitly describe a Sandbox as 'a fully isolated testing environment for custodial features without connecting real funds,' directly matching the story. However, evidence doesn't clarify sandbox coverage for non-custodial/onchain, x402, or webhook features, nor provide hands-on confirmation of the isolation guarantee. Missing for 10: independent/hands-on verification of sandbox isolation, detail on which product areas are sandbox-covered vs not, and any test-data seeding or reset tooling.

   • [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   No evidence in the pack discusses API versioning practices or a documented deprecation policy for Stripe's crypto/stablecoin APIs; the OpenAPI probe even returned 404s. missing for 10: any mention of API version headers, changelog, or deprecation policy documentation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes 404'd and none of the docs mention version numbers, sunset timelines, or deprecation notices.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   No evidence of bulk/batch operations across many items (e.g., batch payouts, bulk API calls, batch job endpoints) for the crypto/stablecoin product; docs describe single-transaction flows (onramp, payouts, refunds).

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed3/10

   The only concrete bulk-scale capability is watching up to 100 wallet addresses under one webhook subscription (`wallet.activity.multi`); all other documented operations (send payouts, provision addresses, checkout, onramp) are described as single-item flows with no batch/bulk endpoints shown. Missing for 10: bulk payout/disbursement APIs, batch transaction submission, bulk provisioning of addresses, and any explicit multi-item automation beyond webhook address watching.

   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
   • [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”

   proof ↗⚑ flag

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

   weight 3 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack covers crypto/stablecoin payment rails, onramp, payouts, and financial accounts, but contains no mention of user-definable event-triggered rules or automation/workflow logic. Webhooks or event-based automation are not referenced anywhere in the pack. missing for 10: rule-definition mechanism, event-trigger automation framework, evidence of conditional action execution.

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed5/10

   CDP offers event-driven building blocks — webhooks for real-time notifications on wallet/payment activity, and built-in auto-liquidation/auto-convert triggered on fund receipt — that let a developer wire up automation, but there is no documented user-facing rules engine where an AI-native user declaratively defines 'if event X then action Y' logic; the developer must write the handling logic themselves. missing for 10: a declarative rules/automation engine, conditional logic support, or evidence of no-code rule definitions tied to webhook events.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”

   proof ↗⚑ flag

Kyc

1. ops leadCustomer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves

   weight 2 · round to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialcommunity3/10

   Stripe states it internally handles KYC verifications and sanctions screening for onramp transactions, and community evidence shows recipient-type restrictions (individuals/sole proprietors only) implying some vetting occurs — but there are no documented KYC/KYB endpoints, verification statuses, or flows that an ops lead can programmatically invoke to clear a counterparty before sending/receiving. missing for 10: documented KYC/KYB API endpoints, verification status objects, or ops-controllable onboarding flow for senders/recipients.

   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”
   • [community] “Recipients paid in crypto must be individuals or sole proprietors. Paying companies and non-profits in crypto is not currently supported. 'O…”
   • [community] “Confusion over Stripe Crypto Payouts: 'Can you checkout with USDC? ... Then I can pay myself out with USD or USDC? I feel like I have this w…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   No evidence pack items mention KYC/KYB endpoints, counterparty verification, or onboarding flows to clear senders/recipients before funds move; docs cover payment rails, wallets, checkouts, webhooks, and stablecoins but nothing about identity/compliance verification APIs.

   ⚑ flag

Licensing

1. founderSee who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   No evidence pack item discloses which licensed/registered legal entities operate Stripe's crypto/stablecoin products or lists jurisdictional coverage of those entities; docs describe features and networks, not corporate/regulatory entity structure. Community threads even highlight regulatory murkiness ('the regulatory details are complex') without clarifying entity/jurisdiction transparency.

   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”
   • [community] “Stripe employee: 'Until very recently, we weren't able to support businesses selling crypto. (The regulatory details are complex.) We're now…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   No evidence pack item discloses the specific licensed/registered legal entities behind Coinbase Payments products or the jurisdictions/licenses they operate under; all evidence is product/API documentation with no legal-entity or licensing disclosure page cited.

   ⚑ flag

Screening

1. ops leadThe platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at

   weight 2 · round to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Docs mention Stripe handles 'regulatory requirements, KYC verifications, and sanctions screening' for onramp transactions (stripe-crypto-docs-15), but this is a single generic line, not a detailed compliance framework. There is no mention of wallet risk-scoring/checks or travel-rule handling anywhere in the pack. Missing for 10: named wallet risk-check mechanism, travel-rule compliance documentation, detail on sanctions screening process/providers.

   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   The evidence pack lists payment, wallet, onramp, and MCP features but never names sanctions screening, wallet risk scoring, or travel-rule handling as documented compliance machinery; these terms simply do not appear anywhere in the pack.

   ⚑ flag

Abstraction

1. developerI never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language

   weight 3 · round drawn
   Stripe Crypto & Stablecoins~partialprobed6/10

   Stripe's crypto/stablecoin docs present a conventional REST-style API (via standard Stripe API, Financial Accounts, onramp, x402) abstracting settlement, custody, and payouts without requiring developers to run nodes or manage gas directly, and Stripe's general SDKs cover multiple languages. However, the evidence pack doesn't explicitly confirm crypto-specific client libraries or SDK coverage for these crypto endpoints, and community comments raise confusion over how crypto payouts/checkout actually work in practice. missing for 10: explicit confirmation of crypto-specific client library support across languages, clearer docs on gas/chain abstraction mechanics, and independent developer confirmation that no chain-level operations leak into the integration.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “Authorize recurring stablecoin withdrawals from your customers’ crypto wallets.”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [community] “Confusion over Stripe Crypto Payouts: 'Can you checkout with USDC? ... Then I can pay myself out with USD or USDC? I feel like I have this w…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialprobed6/10

   CDP provides a REST API plus client SDKs (cdp-sdk on GitHub for EVM/Solana wallets) that abstract key management, signing, and broadcasting, and custodial payment features (stable addresses, payouts, checkout) explicitly avoid onchain complexity for the developer. However, some flows (non-custodial send, wallet management) still expose wallet/chain concepts like signing and gas isn't fully hidden everywhere, and no OpenAPI spec was found (probe 404s) suggesting API conventionality is asserted but not independently verifiable, and multi-language client library breadth is unconfirmed beyond the single GitHub SDK repo. Missing for 10: verifiable OpenAPI/REST spec, evidence of multiple language SDKs, and confirmation gas/chain mechanics are fully invisible across all product surfaces.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Accept stablecoin payments at checkout with a two-step auth and capture flow, without onchain complexity”
   • [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

Sandbox

1. developerRehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically

   weight 3 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   No evidence pack item mentions a sandbox, testnet, or deterministic test values for crypto/stablecoin payments, payouts, or conversions; Stripe's general test-mode is not documented here for this crypto product. Missing for 10: documented testnet/sandbox mode, test API keys or test wallet addresses for crypto flows, deterministic test value behavior for payments/payouts/conversions.

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed5/10

   Coinbase documents a dedicated Sandbox as a fully isolated testing environment for custodial features without real funds, which covers payments-type scenarios. However, evidence doesn't confirm sandbox/testnet coverage extends deterministically to payouts and conversions specifically, nor describe deterministic test values/behaviors. Missing for 10: explicit documentation of testnet/sandbox coverage for payouts and conversions flows, description of deterministic test value behavior, and independent/hands-on confirmation of sandbox reliability.

   • [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”

   proof ↗⚑ flag

Webhooks

1. developerMoney movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack documents Stripe Crypto's onramp, stablecoin payments, financial accounts, and payouts, but contains no mention of webhooks, event types, or signed notifications for crypto-specific state changes (payment confirmed, payout settled, conversion executed). Since this is an applicable axis for a payments platform but no supporting evidence exists in the pack, it must be judged 'none' rather than 'na'.

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed5/10

   CDP docs confirm a webhooks system delivering 'real-time HTTP notifications when things happen across your CDP integration' and wallet-activity subscriptions, which supports state-tracking without polling. However, the evidence never confirms webhook payloads are cryptographically signed, nor does it enumerate the specific events named in the story (payment confirmed, payout settled, conversion executed) — it only shows generic notification and wallet-activity events. Missing for 10: explicit signature/verification mechanism documentation, and confirmation of payment/payout/conversion-specific event types.

   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”

   proof ↗⚑ flag

Conversion

1. developerConversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialclaimed4/10

   Stripe offers onramp (fiat-to-crypto) and stablecoin payments/payouts, but there is no documented quote/conversion-rate API exposing exchange rates, fees, or settlement times for conversions between fiat and stablecoins or between stablecoins — pricing and rate details are absent from the evidence pack. missing for 10: a dedicated conversion/quote endpoint, documented FX rate and fee schedule for stablecoin conversions, documented settlement-time SLAs, and stablecoin-to-stablecoin conversion support.

   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Stripe-hosted onramp to redirect your customer to check out in the standalone page.”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed5/10

   CDP docs show real conversion capabilities (auto-liquidation of onchain funds to fiat, USDC-to-USD auto-conversion into treasury, and converting crypto earnings to fiat) via docs-1, docs-14, docs-19, docs-20, indicating conversion is treated as a core, documented capability rather than a side effect. However, there's no evidence of a distinct quote endpoint, or documented exchange rates, fee schedules, or settlement-time SLAs for these conversions. Missing for 10: explicit quote API, documented conversion fee tables, documented settlement-time guarantees, stablecoin-to-stablecoin conversion documentation.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”

   proof ↗⚑ flag

Onramp

1. developerEmbed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product

   weight 2 · round drawn
   Stripe Crypto & Stablecoins✓fullclaimed8/10

   Stripe documents a fiat-to-crypto onramp with hosted, embedded (web), and embedded components (mobile SDK) options for buying stablecoins via cards/bank transfers, with Stripe as merchant of record handling KYC/fraud (stripe-crypto-docs-11 through 15). This directly matches the story of a documented widget/API for in-product onramp embedding. Missing for 10: independent hands-on developer confirmation of the embedded widget integration experience and no code-sample evidence in the pack.

   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Stripe-hosted onramp to redirect your customer to check out in the standalone page.”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Use the Embedded components onramp (mobile SDK) to let your customers check out directly in your application.”
   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullclaimed8/10

   Coinbase Payments docs explicitly describe an Onramp letting end users buy crypto/stablecoins with card, Apple Pay, Google Pay, or Coinbase account delivered to a wallet, plus a Sandbox for isolated testing — matching the embedded fiat-to-stablecoin onramp story. Missing for 10: no widget code sample or explicit UI-embedding snippet shown, and no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Let users buy crypto with a card, Apple Pay, Google Pay, or a Coinbase account, delivered directly to their wallet”
   • [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
   • [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe's crypto/stablecoin docs describe everything as API/SDK-driven integrations (Payment Intents, Financial Accounts, onramp embedded/API components, payouts), suggesting an API-first design typical of Stripe, but the evidence never explicitly confirms that every UI-exposed action (e.g., wallet linking in the Express Dashboard, card issuance flows) has a documented equivalent API call, nor is there any AI-agent-specific tooling cited beyond the general Stripe MCP/CLI probes which aren't crypto-specific. missing for 10: explicit statement or example that all Dashboard/Express UI crypto actions map 1:1 to API endpoints, and independent verification of full API/UI parity for this specific crypto product.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Use the Embedded components onramp (mobile SDK) to let your customers check out directly in your application.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed8/10

   CDP's docs show extensive API/SDK/CLI coverage across virtually all payment features (onramp, offramp, checkout, payouts, custom stablecoins, x402, webhooks, treasury), and the CDP CLI even ships an MCP server exposing every API endpoint as a tool, indicating near-total API/CLI parity with any dashboard UI. Missing for 10: no explicit UI-vs-API feature parity statement and no discoverable OpenAPI spec (probe returned 404s for common spec paths), so full completeness/discoverability can't be fully confirmed.

   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”

   proof ↗⚑ flag

Batch

1. ops leadRun mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   Evidence shows Stripe can pay out stablecoins to individual connected accounts and issue cards, but there is no documentation of a batch/bulk payout API, mass disbursement endpoint, or per-item status reporting for many payouts in one operation.

   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [claimed-docs] “Issue virtual or physical prepaid cards for connected accounts, backed by stablecoin balances.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   Evidence confirms CDP supports sending fiat/crypto payouts from a custodial account and paying USDC onchain to any wallet, but nothing in the pack documents a batch or bulk payout API, a single-call multi-payee operation, or per-item status reporting for mass disbursements.

   • [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
   • [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”

   proof ↗⚑ flag

Offramp

1. ops leadRecipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Docs describe crypto payments settling as fiat in the merchant's Stripe balance and stablecoin payouts to connected accounts/financial accounts, but there is no documented dedicated 'off-ramp' feature converting stablecoin balances into bank transfers with a published list of supported currencies/countries — in fact docs note stablecoin balances exist precisely in markets where fiat Treasury isn't available, implying no guaranteed bank conversion there. Missing for 10: explicit off-ramp/conversion mechanism from stablecoin to bank transfer, a published country/currency coverage list, and independent confirmation it works as described.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed6/10

   Docs confirm off-ramp functionality — converting stablecoins/USDC to fiat and depositing to bank accounts via ACH, Fedwire, Swift, and SEPA rails (docs-2, docs-14, docs-19) — implying multi-currency support (USD, EUR, GBP) across supported regions. However, no evidence provides a published, explicit list of supported currencies or countries, which the story specifically asks for. Missing for 10: an explicit published table/list of supported countries and currencies, and independent confirmation of real-world payout coverage.

   • [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
   • [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”

   proof ↗⚑ flag

Payouts

1. developerSend stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement

   weight 3 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialcommunity5/10

   Stripe documents stablecoin payouts to connected accounts (platforms/marketplaces) and wallet-linking via Express Dashboard, implying an API-driven payout path, but the evidence never shows a generic 'pay any wallet address or stored recipient' API call, nor documented status-tracking fields through to final settlement. Community reports also note real constraints (recipients must be individuals/sole proprietors, confusion about payout flow), and a Connect-only payout model is narrower than the story's general wallet-payout claim. Missing for 10: explicit API reference/status object for tracking payout progress to settlement, confirmation that arbitrary external wallet addresses (not just linked connected accounts) can be paid, and resolution of community confusion about how payouts actually work.

   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [community] “Recipients paid in crypto must be individuals or sole proprietors. Paying companies and non-profits in crypto is not currently supported. 'O…”
   • [community] “Confusion over Stripe Crypto Payouts: 'Can you checkout with USDC? ... Then I can pay myself out with USD or USDC? I feel like I have this w…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialprobed6/10

   Docs confirm programmatic stablecoin payouts to wallet addresses (fund a USD treasury and pay out USDC onchain to any wallet, or send payouts/disbursements in fiat or crypto from a custodial account) plus webhook-based status notifications for tracking events. However, there's no evidence of a 'stored recipient' concept, no detailed settlement-status API docs (e.g., payout lifecycle states), and no OpenAPI spec was found (probe-2 returned 404s) to confirm the full request/response tracking flow. Missing for 10: stored-recipient/beneficiary management, explicit payout status/settlement lifecycle documentation, and independent corroboration of end-to-end settlement tracking.

   • [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
   • [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
   • [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

Settlement

1. finance leadSettlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   Docs confirm crypto payments settle as fiat into the Stripe balance and mention refunds support, but there is no evidence of documented settlement timing (e.g., T+n days), no published fee schedule per rail/network, and no mention of statements or accounting-ready reports for crypto/stablecoin transactions.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “Refunds / Partial refunds [Yes / Yes](https://docs.stripe.com/payments/stablecoin-payments.md#refunds)”

   proof ↗⚑ flag

   Coinbase Payments (CDP)—none0/10

   Evidence covers payment rails, payouts, checkouts, and treasury flows, but there is no documented settlement-timing SLA per rail, no published fee schedule, and no mention of accounting-consumable statements or reports. The only 'settlement details' reference is a vague migration note with no actual content shown.

   • [claimed-docs] “Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additiona…”
   • [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
   • [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”

   proof ↗⚑ flag

Treasury

1. finance leadMove value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialclaimed5/10

   Stripe documents stablecoin Financial Accounts that let businesses hold, receive, and send stablecoin balances alongside fiat Treasury, plus card issuance backed by those balances, but there is no explicit documentation of a finance-lead-facing internal transfer/rebalancing flow moving value between fiat and stablecoin balances via API or dashboard — the onramp/payout docs are customer- or payout-facing, not treasury rebalancing tools. missing for 10: dedicated API/dashboard endpoint or flow for converting/rebalancing between fiat and stablecoin balances, end-to-end docs for finance-lead treasury operations, independent confirmation of this workflow.

   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “Create a virtual or physical card to spend funds”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed6/10

   CDP docs describe multiple building blocks for fiat↔stablecoin movement: auto-liquidation of onchain funds into a custodial account, fiat payouts via ACH/Fedwire/Swift/SEPA, converting crypto earnings to fiat, and treasury funding/payout flows (fund USD treasury, pay out USDC onchain) via CLI/SDK. This covers most of the 'rebalancing' story but is spread across separate features rather than a single documented end-to-end internal transfer/rebalancing workflow, and there is no dashboard evidence for these treasury operations (only API/CLI/SDK). Missing for 10: a unified internal transfer ledger view, dashboard-based rebalancing UI, and independent/hands-on confirmation of the full fiat↔stablecoin loop.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
   • [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
   • [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”

   proof ↗⚑ flag

Acceptance

1. developerAccept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmatically

   weight 3 · round drawn
   Stripe Crypto & Stablecoins✓fullclaimed7/10

   Stripe documents a stablecoin payments API supporting USDC/USDP/USDG across multiple networks, with refunds/partial refunds, checkout/onramp flows (hosted, embedded, mobile SDK), and even machine-to-machine stablecoin payments via x402 — covering the create-payment-present-flow-confirm-settlement lifecycle described in the story. Missing for 10: explicit code-level API reference (e.g., PaymentIntent creation with stablecoin payment method, webhook/settlement confirmation snippet) and independent hands-on developer confirmation that programmatic settlement works as documented.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Refunds / Partial refunds [Yes / Yes](https://docs.stripe.com/payments/stablecoin-payments.md#refunds)”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Stripe-hosted onramp to redirect your customer to check out in the standalone page.”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Use the Embedded components onramp (mobile SDK) to let your customers check out directly in your application.”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed7/10

   Docs describe a full checkout/payment-acceptance flow: provisioning stable onchain addresses that auto-credit a custodial account, a two-step auth/capture checkout API with developer control over auth timing, partial captures and voids, plus migration guidance from the older Commerce Charge API to the newer Checkouts API with settlement details. This covers create-payment, present-address/flow, and confirm-settlement programmatically. Missing for 10: no independent/hands-on developer confirmation of the checkout flow working end-to-end, and no concrete code sample or OpenAPI spec (probe found openapi.json 404) showing the settlement confirmation call.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Accept stablecoin payments at checkout with a two-step auth and capture flow, without onchain complexity”
   • [claimed-docs] “Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additiona…”
   • [claimed-docs] “You control auth, capture timing, partial captures, voids”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”

   proof ↗⚑ flag

Chains

1. developerThe platform documents which stablecoins and chains it supports — USDC, USDT and peers across multiple named networks — so I can match what my customers actually hold

   weight 2 · round to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins✓fullprobed8/10

   Docs explicitly enumerate supported stablecoins (USDC, USDP, USDG) and specific chains per coin (Tempo, Ethereum, Solana, Polygon, Base), letting developers match customer holdings to supported networks. Community commentary raises ethical/centralization concerns about Solana but does not dispute the accuracy of the documented coverage. Missing for 10: independent verification of full USDT support (not mentioned in evidence) and confirmation the list is exhaustive/up to date.

   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed4/10

   Docs repeatedly reference USDC support (auto-convert customer USDC, USD treasury payouts in USDC, custom stablecoins backed by USDC) and mention EVM/Solana wallet support, but there is no explicit enumeration of USDT or other stablecoins, nor a clear list of supported chains/networks a developer could match against customer holdings. Missing for 10: explicit multi-stablecoin coverage (USDT, DAI, etc.), a documented list of supported blockchain networks, and any independent confirmation of chain/stablecoin breadth.

   • [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”

   proof ↗⚑ flag

Fiat settlement

1. finance leadTake crypto payments but settle in fiat — a documented option to auto-convert stablecoin receipts into a fiat balance or bank payout so my books never hold crypto

   weight 3 · round drawn
   Stripe Crypto & Stablecoins✓fullprobed8/10

   Stripe's documented crypto product explicitly states customers can pay with crypto that settles as fiat in the merchant's Stripe balance, directly matching the finance-lead need to accept stablecoins without holding crypto on the books, and this is backed by first-party docs on stablecoin payments, refunds, and settlement mechanics. missing for 10: no independent/hands-on accounting confirmation that settlement is always fiat-only (vs. optional stablecoin balance retention), and no explicit mention of bank payout timing/documentation for finance reconciliation.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Refunds / Partial refunds [Yes / Yes](https://docs.stripe.com/payments/stablecoin-payments.md#refunds)”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullclaimed8/10

   Docs explicitly describe auto-crediting custodial accounts with optional auto-liquidation, accepting USDC and auto-converting to USD into a treasury, and sending fiat payouts via ACH/Fedwire/Swift/SEPA — directly matching the finance-lead's request to settle crypto receipts in fiat and avoid holding crypto on the books. Missing for 10: independent/hands-on verification of the auto-liquidation flow in production, and clearer accounting/reconciliation documentation for finance teams.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”

   proof ↗⚑ flag

Agent payments

1. ai-native userAn agent can move stablecoins under scoped authority — documented agent payment flows where an agent initiates a payment or payout with spend controls a human configured

   weight 3 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Stripe documents machine/agent stablecoin payments via the x402 protocol (docs-16, docs-17) and recurring stablecoin withdrawal authorization (docs-4), showing some agent-payment-adjacent capability, but there is no documentation of a human configuring spend controls/limits that scope an agent's authority to move funds. missing for 10: explicit spend-control/authorization-limit configuration by a human, documented agent payout workflow with scoped permissions, and any hands-on or third-party confirmation of this flow working.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [claimed-docs] “Authorize recurring stablecoin withdrawals from your customers’ crypto wallets.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed5/10

   CDP documents agent-native payment flows: x402 lets agents pay for or charge APIs programmatically, and the Wallet MCP lets an AI assistant check balances, send funds and pay via a connected Coinbase Wallet, backed by CDP-managed key custody. However, the pack shows no explicit documentation of human-configured spend limits, allowances, or scoped permission policies constraining what an agent can autonomously spend — the closest control language ('you control auth, capture timing, partial captures, voids') applies to merchant checkout capture, not agent wallet spend caps. missing for 10: documented spend-limit/allowance configuration APIs, explicit human-set policy controls for agent wallets, and independent/hands-on confirmation of scoped-authority enforcement.

   • [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
   • [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
   • [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”

   proof ↗⚑ flag

Agent wallets

1. ai-native userAgents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can move

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Stripe documents stablecoin financial accounts, cards, and support for the x402 machine-payment protocol, hinting at agent/programmatic payment flows, but there is no documentation of agent-specific wallet issuance, scoped API keys, policy controls, or explicit spend limits for autonomous agents. missing for 10: agent-scoped key issuance, policy/permission controls, documented spend limits for agents, independent corroboration of agentic wallet safety.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed5/10

   CDP provides SDK-based wallet issuance where Coinbase secures private keys (coinbase-payments-gh-1) and exposes wallets to AI agents via MCP (coinbase-payments-docs-18) and x402 payments (coinbase-payments-docs-12/13), showing agents can hold and use funds programmatically. However, the evidence never documents scoped keys, granular policy controls, or explicit spend/limit enforcement mechanisms for agent-held wallets—only general custody and signing features. Missing for 10: explicit policy/permission engine docs, documented per-agent spend limits, and independent verification that agents cannot exceed defined bounds.

   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
   • [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
   • [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”

   proof ↗⚑ flag

Protocols

1. ai-native userThe platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins~partialclaimed6/10

   Stripe docs explicitly name and document x402 protocol support for stablecoin payments, including a technical detail (0.01 USDC minimum), which goes beyond blog-level aspiration. However, there is no documented support for ACP, MPP, or AP2 protocols in the evidence pack, so the 'speaks the machine-payment protocols by name' story is only partially fulfilled. Missing for 10: ACP support/endpoints, MPP support/endpoints, AP2 support/endpoints, and independent corroboration of x402 usage in production.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)✓fullprobed9/10

   CDP has dedicated x402 docs with SDK/endpoints for both paying ("Pay for an API or resource with x402 and the CDP SDK") and charging ("Charge for your endpoints with x402 and the CDP SDK"), plus a Coinbase Wallet MCP server enabling agents to pay with x402, and an official CDP CLI/MCP exposing API endpoints as tools — this is concrete named-protocol support with SDKs/endpoints, not just aspirational blog content. Missing for 10: no explicit ACP/MPP/AP2 protocol mentions, so coverage is limited to x402 among the named protocols.

   • [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
   • [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
   • [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
   • [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
   • [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
   • [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”

   proof ↗⚑ flag

Issuance

1. founderIssue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   Stripe's crypto offerings cover payments, onramp, payouts, and stablecoin financial accounts — but there is no evidence of a stablecoin issuance product (minting a branded coin, redemption mechanics, reserve management/attestation). This is a distinct product category (e.g., Bridge/Paxos-style issuance-as-a-service) that Stripe's evidence pack never mentions.

   ⚑ flag

   Coinbase Payments (CDP)~partialclaimed6/10

   Coinbase's docs explicitly describe a custom-stablecoin issuance product ('Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves'), directly matching the story's core ask. However, the evidence pack contains no detail on eligibility/gating requirements, application process, minimum volume, or any independent corroboration of how the program actually works in practice. Missing for 10: honest disclosure of gating/eligibility requirements, independent/hands-on corroboration, and technical detail on minting/redemption mechanics beyond the single overview line.

   • [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”

   proof ↗⚑ flag

Yield

1. finance leadThe economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   Evidence covers stablecoin payment/payout mechanics and financial account features but contains no documentation of reserve composition, attestations, or a yield/rewards program with eligibility and regulatory caveats for held stablecoin balances.

   ⚑ flag

   Coinbase Payments (CDP)—none0/10

   Evidence covers custom stablecoin issuance backed 1:1 by USDC with Coinbase managing issuance/redemption/reserves, but no documentation of reserve composition, attestations, or yield/rewards eligibility and regulatory caveats for finance leads is present.

   • [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”

   proof ↗⚑ flag

Balances

1. finance leadMy business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly

   weight 3 · round to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialcommunity6/10

   Stripe's docs describe Stablecoin Financial Accounts letting eligible businesses hold a stablecoin balance, with explicit gating language ('eligible businesses', 'countries where it's available') and honest disclosure that it's not universally available, plus card issuance against the balance. However, the docs do not enumerate the specific list of supported geographies/countries, and community evidence shows historical exclusion of crypto businesses and confusion over payout mechanics, suggesting real-world gating is stricter/less transparent than the docs alone convey. missing for 10: an explicit published list of eligible countries/geographies, independent confirmation of account availability, and clarity on gating criteria beyond 'eligible businesses'.

   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “Create a virtual or physical card to spend funds”
   • [community] “Just last year Stripe wouldn't even allow any crypto business to be their customers. You could not use Stripe if your business was crypto re…”
   • [community] “Stripe employee: 'Until very recently, we weren't able to support businesses selling crypto. (The regulatory details are complex.) We're now…”
   • [community] “Recipients paid in crypto must be individuals or sole proprietors. Paying companies and non-profits in crypto is not currently supported. 'O…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed4/10

   Docs confirm custodial accounts that hold stablecoin balances (auto-credited addresses, auto-conversion to USD, treasury funding/payout in USDC) — docs-1, docs-19, docs-20 — but nothing in the evidence pack states availability constraints, supported geographies, or KYC/eligibility gating for opening such an account. Missing for 10: documented geographic availability/restrictions, explicit KYC/onboarding gating disclosure, and any stated balance limits or custody terms.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
   • [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”

   proof ↗⚑ flag

Virtual accounts

1. developerIncoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   The evidence describes Stripe's crypto payment acceptance, onramp, stablecoin financial accounts, and payouts, but nowhere mentions per-customer dedicated deposit addresses or named virtual accounts for automatic reconciliation of incoming crypto/stablecoin payments. Payments appear tied to Stripe's standard Checkout/PaymentIntent flow rather than unique wallet addresses per customer.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed6/10

   CDP docs explicitly describe provisioning 'stable onchain addresses' that auto-credit a custodial account (dedicated deposit addresses), and webhooks can watch up to 100 wallet addresses per subscription, which supports per-customer address-based reconciliation. However, there's no explicit documentation of named virtual accounts for fiat, nor clear guidance on mapping addresses to specific customer IDs for reconciliation workflows. Missing for 10: explicit per-customer/customer-ID tagging or named virtual account docs, fiat-side dedicated account numbers, and independent/hands-on confirmation of reconciliation accuracy at scale.

   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
   • [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”

   proof ↗⚑ flag

Wallets

1. developerCreate wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics

   weight 2 · round to Coinbase Payments (CDP)
   Stripe Crypto & Stablecoins—none0/10

   Evidence covers stablecoin payments, onramp, financial accounts, and payouts to connected accounts, but there is no documented API for programmatically creating per-customer or per-purpose wallets/deposit addresses with custody semantics; wallet linking is described as user-driven (Express Dashboard) not developer-provisioned.

   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”

   proof ↗⚑ flag

   Coinbase Payments (CDP)~partialclaimed7/10

   CDP SDK docs confirm programmatic wallet creation for EVM/Solana with CDP securing private keys, plus provisioning of custodial onchain deposit addresses that auto-credit accounts, and a sandbox for testing wallet features without real funds. However, the pack lacks explicit detail on per-customer/multi-tenant wallet architecture or deeper key-custody semantics beyond high-level statements. missing for 10: detailed per-customer wallet provisioning patterns, explicit key custody/security model documentation (MPC, backups, exportability)

   • [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
   • [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
   • [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
   • [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”

   proof ↗⚑ flag