Stripe Crypto & Stablecoins vs MoonPay

Agent access

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

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

   MoonPay✓fullprobed9/10

   MoonPay has a confirmed llms.txt (probe returned HTTP 200 with descriptive content) and dedicated docs on using AI agents, including an official MCP server for searching/retrieving docs. missing for 10: independent third-party confirmation of agent usage beyond MoonPay's own docs/probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://dev.moonpay.com/llms.txt # MoonPay Developer Docs > Integrate MoonPay's on-ramp, off-ramp, and swap pro…”
   • [claimed-docs] “Let new customers buy crypto with Apple Pay or Google Pay without a MoonPay account.”
   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

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

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

   MoonPay~partialclaimed4/10

   MoonPay offers headless APIs/SDKs (build-your-own on-ramp, quote and session endpoints) and a dedicated test mode with testnets/simulated payments that could be scripted in a CI pipeline, but there is no evidence of a CLI, automation-first tooling, or documentation describing running MoonPay flows unattended in CI. Missing for 10: explicit CI/automation guidance, evidence of non-interactive KYC/payment flows, and independent confirmation of headless test-mode usage in pipelines.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   proof ↗⚑ flag

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

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

   MoonPay✓fullprobed7/10

   MoonPay documents an official MCP server for its developer docs that gives AI agents direct access to search and retrieve content, corroborated by a probe confirming the page exists. Missing for 10: independent hands-on verification of the MCP server actually working with an agent, and details on scope/capabilities beyond docs search/retrieval.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

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

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

   MoonPay~partialprobed7/10

   MoonPay publishes detailed API reference docs (quotes, sessions, webhooks, test mode) letting developers programmatically drive on/off-ramp flows, and even documents an MCP server for AI agents to browse docs. However, a probe for standard machine-readable API specs (OpenAPI/Swagger) returned 404s across all candidate paths, suggesting no formal machine-consumable spec exists, which limits fully autonomous/agentic API discovery. missing for 10: a discoverable OpenAPI/Swagger spec, independent/hands-on confirmation that an AI agent can successfully call the API end-to-end.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   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

   MoonPay—none0/10

   Evidence shows API keys and session tokens for general integration (moonpay-docs-15) and a documentation MCP server for search/retrieval (moonpay-docs-6), but nothing about issuing scoped or least-privilege credentials specifically for AI agents acting on a user's behalf. No permissions model, credential scoping, or agent-specific access controls are documented.

   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

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

   MoonPay~partialprobed5/10

   MoonPay's docs explicitly mention building on 'APIs and SDKs' (moonpay-docs-3) and provide a demo integrations repo (moonpay-docs-7) and API reference endpoints (moonpay-docs-14, moonpay-docs-15), indicating some SDK/dev-tooling support. However, there's no direct evidence of language-specific SDK packages, an OpenAPI spec (probe shows 404s for standard OpenAPI paths, moonpay-probe-2), or independent developer corroboration of SDK quality/coverage. Missing for 10: concrete SDK package listings (npm, PyPI, etc.), OpenAPI/spec-driven tooling, and independent hands-on confirmation of SDK usability.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   MoonPay✓fullclaimed7/10

   MoonPay documents webhook events that notify applications of account activity, with specific examples like sell_transaction_requote_required, giving developers a concrete subscription mechanism for events. This directly satisfies the story's core need for event-driven notifications. Missing for 10: a full list/catalog of all webhook event types, subscription management API/UI documentation, and independent third-party confirmation of webhook reliability.

   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”

   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

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

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

   MoonPay—none0/10

   MoonPay's evidence only describes an MCP server that lets external AI agents search/retrieve documentation content (moonpay-docs-6, moonpay-probe-3) — this is a developer-docs tool, not a built-in AI assistant inside the product that end-users can delegate purchase/sell/swap tasks to. No evidence of any in-product assistant, chat interface, or agentic task delegation for users.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   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

   MoonPay—none0/10

   MoonPay's evidence only shows an MCP server for searching/retrieving documentation content, not for operating the actual on-ramp/off-ramp transactions via natural language; there is no evidence of a chat/agent interface that lets a user issue commands like 'buy $50 of ETH' through natural language.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

Api quality

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

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

   MoonPay~partialprobed4/10

   MoonPay's dev docs include structured API reference pages (e.g., quotes/get, sessions/create) and a separate GitHub repo of clone-able demo integrations, but there's no evidence of an interactive, in-browser 'try it now' console — a probe for standard OpenAPI/swagger endpoints returned 404s, suggesting no exposed spec powering live runnable examples. Missing for 10: in-docs interactive request builder/console, publicly exposed OpenAPI spec, and confirmation that example code snippets are directly executable from the reference pages.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   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

   MoonPay—none0/10

   No evidence of a downloadable OpenAPI/Swagger spec; a direct probe of common OpenAPI paths (openapi.json, swagger.json, etc.) returned 404 across the board, and docs only mention API reference pages and an MCP server for agent content retrieval, not a machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   proof ↗⚑ flag

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

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

   MoonPay✓fullclaimed7/10

   MoonPay explicitly documents a test mode using testnet blockchains and simulated payments so no real assets are transferred, directly matching the sandbox story, and this is reinforced by clone-able demo integrations for testing before production use. Missing for 10: independent/hands-on confirmation that the sandbox fully mirrors production behavior and more detail on how test-mode credentials/environments are provisioned.

   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
   • [claimed-docs] “Create a session token to initialize a connection”

   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

   MoonPay—none0/10

   No evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; openapi spec probe 404s, and no changelog/versioning page is cited. missing for 10: versioning scheme documentation, deprecation policy/timeline, changelog or migration guides.

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

   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

   MoonPay—none0/10

   No evidence of bulk/batch operations across many items (e.g., batch quotes, bulk transaction processing) in MoonPay's API or docs; endpoints shown are single-item (single quote, single session).

   ⚑ flag

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

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

   MoonPay~partialclaimed4/10

   MoonPay exposes webhook events (e.g., transaction status, requote-required) that notify an application when activity occurs, which developers can use to build their own automated actions, but there is no evidence of a built-in rules/automation engine where users define conditional triggers within MoonPay itself. missing for 10: a native rule-builder or automation configuration UI/API, evidence of conditional logic or multi-step workflows tied to events, independent confirmation of automation use in production.

   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”

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

   MoonPay~partialprobed5/10

   MoonPay's docs describe KYC as a built-in, hosted part of its on-/off-ramp widget and API flow (session creation, quotes, webhooks) and note that returning users can skip re-onboarding, but there is no documented standalone KYC/KYB endpoint or explicit 'counterparty cleared' status API that an ops team could call programmatically before initiating a transfer — KYC is embedded in the transaction flow rather than exposed as an independent compliance-check service. missing for 10: explicit KYC/KYB API/endpoint documentation, a way to query verification/clearance status independent of a transaction, and any B2B/KYB (business) onboarding flow.

   • [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Connect existing MoonPay usersSkip re-onboarding. Plug into the existing MoonPay account base.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “Millions of users have previously purchased cryptocurrencies using MoonPay, having stored their payment and KYC details, leading to maximize…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   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

   MoonPay—none0/10

   No evidence pack item names MoonPay's licensed/registered legal entities, regulatory licenses, or jurisdictional coverage; documentation is entirely product/API focused, and community items concern fee transparency and an unrelated scam-fund allegation, not entity/licensing disclosure.

   ⚑ 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

   MoonPay—none0/10

   MoonPay's docs mention generic 'KYC and compliance' and 'payments' but never name specific machinery like sanctions screening, wallet risk scoring, or travel-rule data sharing — the exact named-not-waved-at requirement of this story. Missing for 10: any documentation naming sanctions/OFAC screening process, wallet address risk-scoring methodology, or travel-rule protocol implementation (e.g., Notabene/Sygna/TRISA integration).

   • [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Millions of users have previously purchased cryptocurrencies using MoonPay, having stored their payment and KYC details, leading to maximize…”

   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

   MoonPay~partialprobed6/10

   MoonPay's docs show a conventional REST API (quotes, sessions, webhooks) and widgets/SDKs that abstract on-chain mechanics like fees and rate-locking, letting developers build fiat-to-crypto flows without running nodes (moonpay-docs-3, moonpay-docs-14, moonpay-docs-15, moonpay-docs-11). However, there's no evidence of concrete multi-language client libraries or a public OpenAPI spec (probe found 404s at all candidate spec URLs), so the 'client libraries in my language' part of the story is unsupported. Missing for 10: enumerated SDK languages/repos, published OpenAPI/swagger spec, independent confirmation of ease-of-use across languages.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

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

   MoonPay✓fullclaimed7/10

   MoonPay documents a dedicated test mode using testnet blockchains and simulated payments where no real assets are transferred, directly matching the sandbox/testnet rehearsal story for buy/sell/conversion flows. Missing for 10: explicit documentation of deterministic test values (e.g., specific test card numbers or fixed exchange rates) and independent/hands-on confirmation that payouts and conversions behave predictably in test mode.

   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

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

   MoonPay~partialclaimed5/10

   MoonPay docs confirm a webhook system that notifies apps of account activity and give an example event (sell_transaction_requote_required), supporting event-driven state tracking. However, there is no evidence of cryptographic signing/verification of webhooks, nor documentation of specific 'payment confirmed', 'payout settled', or 'conversion executed' event types the story describes. missing for 10: signature verification details, full enumerated list of transaction lifecycle events (buy/sell/swap completion, payout settlement), independent confirmation of webhook reliability.

   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”

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

   MoonPay~partialclaimed6/10

   MoonPay documents a Quotes endpoint returning locked rate, fees, and a signature for fiat-to-crypto buys, plus off-ramp requote webhooks for sell price changes, giving developers programmatic access to rates/fees for fiat↔stablecoin conversion. However, stablecoin-to-stablecoin 'swap' conversion is only mentioned as a marketing feature (docs-18) without a documented quotes/fees API for that path, and no settlement-time documentation appears anywhere in the pack. missing for 10: documented quote/fee API for stablecoin-to-stablecoin swaps, explicit settlement-time guarantees, independent confirmation of rate accuracy.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
   • [claimed-docs] “Trade between tokens, even if they're on different chains (we make bridging seamless too).”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”

   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

   MoonPay✓fullclaimed8/10

   MoonPay documents a widget and API/SDK approach for embedding fiat-to-stablecoin (and crypto) onramp flows, supporting card, Apple Pay, Google Pay and bank transfers, with customization, prefill, webhooks, quotes and session tokens, plus test mode for development. missing for 10: no independent/hands-on developer corroboration of the integration experience, and no explicit confirmation of stablecoin-specific (vs generic crypto) purchase support in the widget docs.

   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “You can customize the widget to feel like a native part of your site or application by adjusting button and background colors. You can also …”
   • [claimed-docs] “Improve your customers' experience and speed up the buying process by pre-filling information such as their wallet address, email, selected …”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”

   proof ↗⚑ flag

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

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

   MoonPay~partialprobed6/10

   MoonPay documents a full build-your-own API/SDK path (quotes, sessions, webhooks, prefill, wallet creation, requote handling) that mirrors much of what the hosted widget UI offers, suggesting broad but not explicitly total parity. However, no OpenAPI/swagger spec was found (404s on all probed paths), and there's no explicit documentation stating 100% feature parity between API and UI, with a community question even asking if the API/webhook list is public at all. Missing for 10: explicit statement of full UI/API parity, a published OpenAPI spec, and independent developer confirmation that all UI features are API-accessible.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Improve your customers' experience and speed up the buying process by pre-filling information such as their wallet address, email, selected …”
   • [claimed-docs] “Users don't have a digital wallet? We can create one for them using just their email address as they go through the purchase flow.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
   • [community] “Wow, Congrats to MoonPay! I was curious about their fee structure, and after digging was able to find the following chart... Is the API publ…”

   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

   MoonPay—none0/10

   MoonPay's docs describe single-transaction on-ramp/off-ramp flows (quotes, sessions, webhooks) for individual end-user purchases/sells, but there is no evidence of a batch/bulk payout API, mass disbursement endpoint, or per-item status reporting for many payouts in one operation.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

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

   MoonPay~partialclaimed5/10

   MoonPay documents off-ramp (sell) rails paying out to bank account or card, with build-your-own or hosted options and sell-specific webhooks (requote), showing the payout mechanism exists and is documented for developers. However, there is no evidence of a published, itemized list of supported fiat currencies or countries for the off-ramp, which the story specifically requires. Missing for 10: published currency/country coverage table for off-ramp, independent confirmation of payout rails working across those markets.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your 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 Stripe Crypto & Stablecoins
   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

   MoonPay—none0/10

   MoonPay's docs describe on-ramp/off-ramp widgets and APIs for individual users buying/selling crypto (quotes, sessions, webhooks for sell/requote), but there is no evidence of a payouts API that lets a developer programmatically disburse stablecoins to a wallet address or stored recipient list with settlement status tracking — that is a distinct payouts/disbursement capability not shown in the pack.

   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”

   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

   MoonPay—none0/10

   The evidence pack shows webhooks, quotes with locked rates/fees, and test mode, but nothing documents settlement timing (payment to available balance), a published fee schedule per rail, or accounting-consumable statements/reports. A community comment even asks whether MoonPay's fee structure/API is publicly available, suggesting no clear published fee documentation exists. Missing for 10: settlement timing documentation, per-rail fee schedules, downloadable statements/reports for accounting.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [community] “Wow, Congrats to MoonPay! I was curious about their fee structure, and after digging was able to find the following chart... Is the API publ…”

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

   MoonPay—none0/10

   MoonPay's documented capabilities are consumer-facing on-ramp/off-ramp/swap widgets and APIs (buy, sell, quote, webhooks) for end users converting fiat to crypto and back — there is no evidence of an internal treasury/balance system, account-to-account transfers, or rebalancing API/dashboard aimed at a finance lead managing platform-held fiat and stablecoin balances. Missing for 10: any documentation of internal ledger/balance accounts, transfer-between-balances API, or treasury dashboard for rebalancing fiat vs stablecoin holdings.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”

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

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

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

   MoonPay—none0/10

   The evidence pack shows general on-ramp/off-ramp and cross-chain swap capabilities but contains no documentation listing specific supported stablecoins (USDC, USDT, etc.) or named blockchain networks. Missing for 10: an explicit supported-assets/networks list, stablecoin-specific documentation, and named chain coverage.

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

   MoonPay~partialclaimed4/10

   MoonPay's off-ramp product (docs-17, docs-3) lets crypto be converted to cash paid to a bank account or card, and this can be built into a business's own flow via APIs/webhooks (docs-11, docs-14). However, this is framed as a consumer/end-user cash-out feature, not a documented merchant treasury/settlement product for automatically converting incoming stablecoin payments into a fiat balance so a business's books never hold crypto. Missing for 10: explicit merchant/business settlement documentation, stablecoin-specific auto-conversion mechanics, fiat balance/ledger concept, and accounting-oriented guarantees that crypto is never held.

   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”

   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

   MoonPay—none0/10

   MoonPay's MCP server (moonpay-docs-6, moonpay-probe-3) only gives agents access to search/retrieve documentation content, not to initiate payments. There is no evidence of an agent payment flow with human-configured spend controls, scoped authority, or delegated transaction limits — the API docs describe quotes/sessions for human-driven checkout flows, not autonomous agent-initiated payouts.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   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

   MoonPay—none0/10

   Evidence covers MoonPay's on/off-ramp widget, API, and MCP docs-server for content retrieval, but there is no mention of programmatic wallet issuance for AI agents, scoped API keys, policy controls, or documented spend limits governing what an agent can move. The comm-1 item is off-topic (fraud allegation, not agent wallet controls) and ignored.

   ⚑ 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

   MoonPay—none0/10

   Evidence shows MoonPay has an MCP server for docs search and standard fiat on/off-ramp APIs, but no mention of named machine-payment protocols like x402, ACP, MPP, or AP2 anywhere in the docs, 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

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

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

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

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

   MoonPay—none0/10

   Evidence describes MoonPay purely as an on-ramp/off-ramp/swap payment rail (buy/sell/bridge crypto, webhooks, quotes, session tokens) with no documented custodial account product for holding a business stablecoin balance, nor any stated availability, geography, or gating for such a balance. This is a plausible axis for a crypto payments platform to address, but no supporting evidence exists.

   • [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
   • [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “Trade between tokens, even if they're on different chains (we make bridging seamless too).”

   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

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

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

   MoonPay—none0/10

   MoonPay's docs mention it can auto-create a wallet for users via email during the on-ramp purchase flow, but this is a widget-embedded convenience feature, not a documented developer API for programmatically provisioning per-customer/purpose wallets or deposit addresses, and there is no documentation of key custody semantics.

   • [claimed-docs] “Users don't have a digital wallet? We can create one for them using just their email address as they go through the purchase flow.”

   proof ↗⚑ flag