Stripe Crypto & Stablecoins vs Paxos

Agent access

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

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

   Paxos✓fullprobed9/10

   Paxos hosts an llms.txt at docs.paxos.com/llms.txt, confirmed live by a direct probe returning HTTP 200 with structured documentation links, and the docs also advertise AI-assistance built into the documentation for contextual help. missing for 10: independent third-party confirmation of an agent successfully consuming the llms.txt beyond the first-party probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.paxos.com/llms.txt # Paxos Documentation - [Build with Paxos](https://docs.paxos.com/welcome.md): …”
   • [claimed-docs] “Sign Up for access to the Sandbox environment.”
   • [claimed-docs] “Get contextual help with Paxos APIs using AI assistance built into our documentation.”

   proof ↗⚑ flag

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

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

   Paxos~partialclaimed6/10

   Paxos is API-first with client credentials, auth tokens, and a Sandbox environment explicitly designed for automated end-to-end integration testing (faucets, mock flows, transfers), which supports headless/CI-style automation. However, there is no explicit mention of CI/CD pipeline examples, SDKs, or automation tooling tailored for AI-native/headless workflows. Missing for 10: explicit CI/CD integration guides, official SDK/CLI support for headless automation, and independent confirmation of running in CI.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”

   proof ↗⚑ flag

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

   weight 3 · round to Stripe Crypto & Stablecoins
   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

   Paxos—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

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Crypto & Stablecoins
   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

   Paxos—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

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

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

   Paxos✓fullprobed8/10

   Paxos provides extensive documented public APIs covering authentication (Client ID/Secret, tokens), sandbox testing, identity onboarding, payments, conversions, crypto brokerage (REST v2.0, FIX, WebSocket), and webhooks — clearly enabling programmatic/agentic control of the platform. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (probe found only 404s) and evidence of official SDKs, which would strengthen AI-native automation.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [claimed-docs] “Leverage the Paxos FIX API to trade crypto.”
   • [claimed-docs] “Stream order book updates and executions in real time using the Smart Order Routing WebSocket API”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.paxos.com/llms.txt # Paxos Documentation - [Build with Paxos](https://docs.paxos.com/welcome.md): …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   proof ↗⚑ flag

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

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

   Paxos~partialclaimed5/10

   Paxos supports API credentials (Client ID/Secret) with configurable allowed scopes to restrict access to specific endpoints, which supports least-privilege credential issuance [paxos-docs-2]. However, there is no explicit documentation of an 'agent' use case, dynamic/programmatic credential issuance for AI agents, or fine-grained per-action scoping beyond endpoint-level access. Missing for 10: agent-specific credential provisioning workflow, evidence of granular per-resource scopes beyond endpoint-level, and independent/hands-on confirmation of scope enforcement.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe Crypto & Stablecoins
   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

   Paxos—none0/10

   The evidence pack details Paxos's REST/FIX/WebSocket APIs, sandbox, webhooks, and docs, but never mentions official client SDKs or libraries in any language; the openapi.json probe also 404s, suggesting no even machine-readable spec is exposed for SDK generation.

   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [claimed-docs] “Leverage the Paxos FIX API to trade crypto.”
   • [claimed-docs] “Stream order book updates and executions in real time using the Smart Order Routing WebSocket API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   Paxos✓fullclaimed7/10

   Paxos documents a dedicated Webhooks feature allowing registration of endpoints to receive asynchronous platform events, with configurable event types, auth, and RPS via the Dashboard. Missing for 10: independent/hands-on corroboration of webhook reliability, payload schema examples, and no OpenAPI spec confirming event types programmatically.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”

   proof ↗⚑ flag

Agentic features

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

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

   Paxos—none0/10

   Paxos evidence covers APIs, webhooks, orchestrations (mint/redeem) and sandbox testing, but none of it describes a mechanism for setting up automations or agents that run autonomously in the background (e.g., scheduling, workflow triggers executed by Paxos itself, or an automation builder). Webhooks are reactive event notifications requiring external systems to act, not autonomous background execution.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   proof ↗⚑ flag

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

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

   Paxos~partialclaimed3/10

   Paxos docs mention only a documentation-embedded AI assistant for contextual API help (paxos-docs-18), not a built-in assistant capable of executing platform tasks like payments, conversions, or identity onboarding on the user's behalf. Missing for 10: evidence of an in-product AI agent that can perform actions (transfers, KYC, order execution) rather than just answer doc questions, and any first-party or independent confirmation of agentic task delegation.

   • [claimed-docs] “Get contextual help with Paxos APIs using AI assistance built into our documentation.”

   proof ↗⚑ flag

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

   weight 2 · round to Stripe Crypto & Stablecoins
   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

   Paxos—none0/10

   Paxos is a financial/stablecoin API platform with developer docs, REST/FIX APIs, and an AI-assisted docs search helper, but there is no evidence of natural-language command operation of the product itself (e.g., no chat-driven transaction execution or NL-to-API interface). The 'AI assistance built into our documentation' (paxos-docs-18) is a doc-search helper, not a way to operate the product via NL commands.

   ⚑ 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

   Paxos—none0/10

   The evidence pack shows Paxos has a Sandbox environment, docs with AI assistance, and various API guides, but nothing describing an interactive API reference (e.g., Swagger/OpenAPI explorer or 'try it' console) with runnable code examples; the probe for standard OpenAPI spec paths returned 404 across all checked locations, reinforcing the absence of such a feature.

   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”
   • [claimed-docs] “Get contextual help with Paxos APIs using AI assistance built into our documentation.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos—none0/10

   Direct probing of common OpenAPI/Swagger paths returned 404s, and the docs pack contains no link to a downloadable machine-readable spec despite extensive API documentation.

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

   proof ↗⚑ flag

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

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

   Paxos✓fullclaimed8/10

   Paxos provides a dedicated Sandbox environment with signup, credentials, test crypto asset faucets, and explicit guidance to mock flows, execute transfers, and test integrations without touching production data. missing for 10: independent/hands-on corroboration beyond vendor docs, and detail on data isolation guarantees between sandbox and production.

   • [claimed-docs] “Sign Up for access to the Sandbox environment.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”

   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

   Paxos—none0/10

   Evidence only shows a passing reference to 'Paxos API v2.0' (paxos-docs-19) with no changelog, versioning scheme, or deprecation/sunset policy documented anywhere in the pack; the OpenAPI/spec probes also returned 404s, suggesting no discoverable machine-readable API version metadata either.

   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   proof ↗⚑ flag

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

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

   Paxos—none0/10

   The evidence pack shows individual API operations (single mint/redeem, single identity creation, single transfers) but no batch or bulk endpoints for processing many items in one call. Bulk operations across many items are a fair ask for a financial API platform, but no documentation mentions batch processing, bulk uploads, or multi-item transactions.

   ⚑ flag

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

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

   Paxos~partialclaimed4/10

   Paxos offers webhooks that push asynchronous platform events to a user-defined endpoint (paxos-docs-16, paxos-docs-17), which lets a developer build custom automation externally, but there's no evidence of a built-in rules/automation engine where actions are defined and triggered directly within Paxos itself. Missing for 10: native rule-definition UI/API, conditional action triggers, and any AI-native automation tooling beyond raw webhook events.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”

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

   Paxos✓fullprobed7/10

   Paxos docs explicitly describe programmatic KYC/KYB flows: creating a person identity and handling onboarding decisions, creating an institution identity with required members and onboarding decisions, and collecting/transmitting beneficiary info for above-threshold transfers — directly matching counterparty clearance before money moves. missing for 10: X, Y — no visible OpenAPI/endpoint spec (openapi probe 404) and no independent/hands-on corroboration of these onboarding APIs.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Collect and transmit beneficiary information for above-threshold crypto transfers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

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

   Paxos—none0/10

   The evidence pack is entirely API/developer documentation about sandbox, onboarding, payments, and webhooks; none of it addresses the legal/regulatory entities behind Paxos, their licensing status, or jurisdictional coverage. No trust/compliance/licensing page, entity disclosure, or regulatory registration info is cited anywhere.

   ⚑ 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 Paxos
   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

   Paxos~partialclaimed4/10

   Travel-rule handling is explicitly documented ('Collect and transmit beneficiary information for above-threshold crypto transfers') and identity onboarding decisions are named, but sanctions screening and wallet risk checks are never named as distinct compliance mechanisms — only vague 'onboarding decision' language. missing for 10: explicit sanctions screening documentation, explicit wallet/address risk-scoring documentation, and independent corroboration of these compliance mechanisms.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Collect and transmit beneficiary information for above-threshold crypto transfers.”

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

   Paxos~partialprobed6/10

   Docs show Paxos exposes stablecoin mint/redeem, transfers, and conversions via REST-style orchestration endpoints with sandbox/auth, effectively hiding chain mechanics and gas from developers (paxos-docs-8, paxos-docs-9, paxos-docs-10, paxos-docs-22). However, there's no mention of official client libraries/SDKs in specific languages, and the probe found no discoverable OpenAPI spec, so the 'client libraries in my language' part of the story is unevidenced. missing for 10: language-specific SDKs/client libraries, published OpenAPI/swagger spec, independent confirmation of no direct chain exposure.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

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

   Paxos~partialclaimed6/10

   Docs confirm a dedicated Sandbox environment with test credentials, faucets for test crypto assets, and ability to 'mock flows, execute transfers and test integrations' (paxos-docs-1,4,22), which covers the general intent of rehearsing without real funds. However, there is no explicit documentation tying the sandbox to deterministic test values, nor confirmation that payouts/conversions (mint/redeem orchestrations) are specifically testable in sandbox mode rather than just payments. Missing for 10: explicit deterministic test-value behavior, sandbox coverage confirmation for conversions/payouts orchestrations, and independent/hands-on corroboration.

   • [claimed-docs] “Sign Up for access to the Sandbox environment.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

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

   Paxos~partialclaimed6/10

   Docs confirm Paxos Webhooks deliver asynchronous events for platform activity (configurable endpoint, event types, auth type of API Key or OAuth) which covers state tracking without polling, but there is no explicit mention of cryptographic signing/signature verification for webhook payloads, nor specific event-type names like 'payment confirmed' or 'payout settled'. Missing for 10: explicit payload-signing/signature-verification mechanism, and confirmation of exact event types matching payment/payout/conversion lifecycle.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”

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

   Paxos~partialclaimed6/10

   Paxos documents concrete conversion orchestrations (USD→stablecoin mint, stablecoin→USD redeem, and 'execute conversions between supported assets') plus held-rate quote execution in its crypto-brokerage API, showing conversion is a first-class, callable API surface. However, the evidence pack lacks explicit documentation of fee schedules or settlement-time SLAs tied to these conversion endpoints. missing for 10: documented fee tables/rate-spread disclosure, explicit settlement-time guarantees, and confirmation that quote/held-rate functionality extends to fiat↔stablecoin (not just crypto-brokerage trading pairs).

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”

   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 to Stripe Crypto & Stablecoins
   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

   Paxos~partialclaimed5/10

   Paxos provides APIs to convert USD to stablecoins and back (mint/redeem orchestrations) and identity onboarding flows, which are the backend building blocks for a fiat-to-stablecoin onramp, but the evidence describes a backend API/orchestration platform rather than a documented pre-built embeddable widget or turnkey onramp UI for end users to buy stablecoins via card/bank transfer. missing for 10: an explicit end-user-facing widget/UI component, card payment support (evidence only shows wire/CUBIX bank transfers, not card rails), and independent confirmation of a ready-to-embed onramp product.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   proof ↗⚑ flag

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

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

   Paxos~partialprobed6/10

   Paxos exposes a broad API surface (identity onboarding, transfers, conversions, payments, brokerage, webhooks) that mirrors most Dashboard functionality, suggesting strong API/UI parity for core workflows. However, evidence explicitly notes account/user management ('manage your platform and users') is documented as a Dashboard-only guide, webhook configuration is described as done via Dashboard login rather than API, and no OpenAPI spec was discoverable to verify full API coverage. missing for 10: confirmed API equivalents for Dashboard-only admin/user-management tasks, API-based webhook configuration, discoverable OpenAPI/swagger spec proving full endpoint parity, independent verification beyond vendor docs.

   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”
   • [claimed-docs] “Learn how to use the Paxos Dashboard to manage your platform and users.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”
   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”

   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

   Paxos—none0/10

   Evidence shows single-operation APIs (mint, redeem, convert, transfer) and payment acceptance flows, but nothing describing a batch/bulk payout endpoint that processes many payouts in one call with per-item status reporting. missing for 10: batch/bulk disbursement endpoint docs, per-item status/response schema, evidence of multi-recipient payout support.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

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

   Paxos~partialclaimed5/10

   Paxos documents converting stablecoins to USD and settling directly to a bank account (redeem, settle-to-bank, auto-convert-to-fiat), which covers the core off-ramp-to-bank-transfer mechanic, but all evidence is USD/wire-transfer specific with no published list of supported fiat currencies or countries for payouts. missing for 10: published multi-currency/country coverage list, evidence of non-USD bank rails, independent confirmation of international payout reach.

   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Settle USD directly to your bank account.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

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

   Paxos~partialprobed6/10

   Paxos docs show programmatic stablecoin transfer/conversion orchestrations (mint/redeem, asset transfers), beneficiary/recipient handling for crypto transfers, and webhooks for asynchronous event tracking that could support payout status monitoring. However, there is no explicit documentation of a dedicated 'pay to wallet address or stored recipient' payout endpoint with full status-to-settlement tracking, and the OpenAPI spec probe failed (404), limiting confirmation of endpoint-level detail. Missing for 10: explicit payout-to-wallet/stored-recipient API reference, confirmed OpenAPI schema, and independent/hands-on verification of settlement status tracking.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Collect and transmit beneficiary information for above-threshold crypto transfers.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos—none0/10

   Docs describe settlement mechanics (mint/redeem orchestrations, wire transfer/CUBIX, direct bank settlement) but nowhere document payment-to-available-balance timing, publish a fee schedule per rail, or provide statements/reports formatted for accounting consumption.

   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”
   • [claimed-docs] “Settle USD directly to your bank 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 Paxos
   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

   Paxos✓fullclaimed7/10

   Paxos docs describe end-to-end orchestrations for converting USD↔stablecoins in one API call (mint/redeem), moving USD on/off platform via wire/CUBIX, and general conversions between supported assets, plus a Dashboard for platform management, giving a finance lead both API and dashboard paths for treasury operations. Missing for 10: explicit dashboard UI screenshots/steps for initiating a fiat/stablecoin transfer or rebalancing (dashboard docs are generic), and independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”
   • [claimed-docs] “Learn how to use the Paxos Dashboard to manage your platform and users.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”

   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

   Paxos✓fullprobed7/10

   Paxos has a dedicated Payments API documented to accept PYUSD/USDC/USDP on-chain transfers, auto-convert to fiat or hold in stablecoin, settle to bank, issue refunds, and receive async settlement confirmation via webhooks — covering create/present/confirm end-to-end. Missing for 10: no independent hands-on developer integration report, no OpenAPI spec exposed (404s), and no explicit example of presenting a checkout address/UI flow to an end customer.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Settle USD directly to your bank account.”
   • [claimed-docs] “Issue refunds to the original Buyer via stablecoin on-chain transfers.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos~partialclaimed5/10

   Docs explicitly list supported stablecoins for payments (PYUSD, USDC, USDP) and mention conversions between 'supported assets,' showing some named-coin documentation, but USDT is not mentioned anywhere, and no specific blockchain networks (e.g., Ethereum, Solana) are named in the evidence pack. missing for 10: USDT support, explicit multi-chain network list, and a consolidated supported-assets/chains reference page.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   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

   Paxos✓fullclaimed8/10

   Docs explicitly describe accepting PYUSD/USDC/USDP payments with an option to automatically convert stablecoin to fiat or settle USD directly to a bank account, matching the finance-lead's no-crypto-on-books requirement, plus a redeem orchestration to convert stablecoins to USD and withdraw to bank in one call. Missing for 10: independent/hands-on confirmation of the auto-convert toggle in production and clearer accounting/reporting detail on how converted balances appear in books.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Settle USD directly to your bank account.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   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 Stripe Crypto & Stablecoins
   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

   Paxos—none0/10

   Evidence shows generic API credentialing with scopes (paxos-docs-2) and various payment/transfer/orchestration endpoints, but nothing documents an agent-specific payment flow, delegated spend limits, or scoped authority configured by a human for an autonomous agent to initiate stablecoin payments. Missing for 10: any mention of AI agents, agent-specific spend controls, or delegated payment authority workflows.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   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 Stripe Crypto & Stablecoins
   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

   Paxos—none0/10

   Paxos docs show API credentials with configurable scopes (paxos-docs-2), sandbox testing, and identity onboarding, but there is no evidence of agent-specific wallet issuance, scoped keys tied to autonomous agents, or documented spending/policy limits governing what an agent can move.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”
   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”

   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 Stripe Crypto & Stablecoins
   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

   Paxos—none0/10

   No evidence names or documents x402, ACP, MPP, or AP2 protocols; Paxos documentation covers stablecoin issuance, payments, brokerage, and webhooks but never references these specific machine-payment protocols by name with endpoints or SDKs.

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

   Paxos—none0/10

   The evidence pack shows Paxos APIs for minting/redeeming existing stablecoins (mint.md, redeem.md) and payment flows, but nothing documenting a distinct 'issue your own branded stablecoin' program, its reserve-management practices, or the eligibility/gating requirements (e.g., minimum volume, regulatory vetting) stated honestly. Missing for 10: dedicated issuance-product docs, reserve/attestation disclosure, and explicit gating/eligibility criteria for founders wanting a new branded coin.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   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

   Paxos—none0/10

   The evidence pack covers API/developer documentation for minting, redeeming, payments, and sandbox testing, but contains no mention of reserve composition, attestation reports, or any yield/rewards program with eligibility or regulatory caveats for held stablecoins.

   ⚑ 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

   Paxos~partialclaimed5/10

   Docs describe custodial-style flows (person/institution identity onboarding, USD-to-stablecoin conversion, holding balances, wire/CUBIX movement) implying an account structure for holding stablecoin balances, but nowhere do they state specific geographies served, eligibility/gating criteria, or availability constraints as the story requires. Missing for 10: explicit geographic availability list, stated eligibility/gating (e.g., institutional-only, jurisdictional restrictions), and independent confirmation of custodial account terms.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”

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

   Paxos—none0/10

   Paxos docs describe payment acceptance (PYUSD/USDC/USDP on-chain transfers), auto-conversion to fiat, and webhooks for event notifications, but nowhere mention per-customer virtual accounts or dedicated deposit addresses for automatic reconciliation of incoming funds. missing for 10: any documentation of per-customer/dedicated deposit addresses or virtual account assignment, reconciliation tooling tying incoming transfers to specific customers.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Issue refunds to the original Buyer via stablecoin on-chain transfers.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”

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

   Paxos—none0/10

   The evidence pack covers identity onboarding, fiat/crypto conversions, payments, webhooks, and brokerage trading, but contains no mention of programmatic wallet creation, per-customer deposit address provisioning, or documented custody/key-management semantics. Missing for 10: wallet/deposit-address creation API docs, custody model documentation, evidence of per-customer wallet provisioning.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   proof ↗⚑ flag