Stripe Crypto & Stablecoins vs BVNK

Agent access

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

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

   BVNK✓fullprobed8/10

   BVNK hosts a live llms.txt file at docs.bvnk.com/llms.txt confirmed via HTTP 200 probe, containing structured summaries of its API documentation, and individual doc pages are also machine-readable markdown (.md) endpoints. Missing for 10: no independent third-party confirmation of agent usage/adoption of this llms.txt beyond the probe check.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [claimed-docs] “As a partner, you can add a markup fee to your customers' transactions, enabling you to collect additional revenue from your customers.”

   proof ↗⚑ flag

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

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

   BVNK~partialprobed6/10

   BVNK exposes a full REST API with Hawk authentication, webhooks for automated notifications, and a sandbox environment for simulating pay-ins/payouts—all of which support headless, non-interactive automation. There's also a mentioned agent-wallet-cli tool suggesting scriptable/CLI usage. However, there's no explicit documentation of CI pipeline integration, headless auth flows for automated agents, or CI-specific guidance. Missing for 10: explicit CI/automation guide, confirmation the CLI supports non-interactive auth/config for pipelines, and independent evidence of real-world CI usage.

   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”

   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

   BVNK—none0/10

   BVNK is a payments infrastructure product, and while an MCP server is a plausible axis for such an API platform, no evidence shows an official MCP server; only Hawk auth, webhooks, and REST APIs are documented, plus an unrelated CLI mention.

   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”

   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

   BVNK~partialprobed3/10

   A single probe result points to an 'agent-wallet-cli' GitHub repo described as an official CLI, but there is no documentation content, usage examples, or independent corroboration of its functionality. missing for 10: detailed CLI docs, command reference, install/usage examples, independent confirmation of adoption.

   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”

   proof ↗⚑ flag

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

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

   BVNK✓fullprobed8/10

   BVNK publishes a documented public API (Hawk auth, webhooks, wallets, transfers, payment rules) with a dedicated docs site and llms.txt endpoint confirming API-driven access, plus a sandbox for testing. missing for 10: independent third-party corroboration of API robustness/versioning and explicit rate-limit/SLA documentation.

   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”

   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

   BVNK—none0/10

   BVNK's docs only mention Hawk-based API authentication (bvnk-docs-1) and webhooks, with no mention of scoped, least-privilege, or role-restricted API credentials or agent-specific key issuance. No evidence describes creating limited-permission API keys or tokens for AI agents.

   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   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

   BVNK—none0/10

   Evidence shows extensive REST API documentation (auth, webhooks, sandbox, wallets, etc.) and one official CLI tool (agent-wallet-cli), but no evidence of official client SDKs (e.g., Python, JS, Java libraries) that developers could build against. The axis is fair for an API-driven fintech platform, but no SDK evidence is present, so this is 'none' rather than 'na'.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   BVNK✓fullclaimed7/10

   BVNK documents webhook subscriptions for real-time account event notifications, with a dedicated setup guide for creating a webhook listener. Missing for 10: no details on event type filtering/selection, payload signing/verification specifics, or independent hands-on corroboration of webhook reliability.

   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”

   proof ↗⚑ flag

Agentic features

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

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

   BVNK~partialclaimed6/10

   BVNK exposes a rules-based automation API (e.g., POST /payment/v1/rules to auto-link fiat virtual accounts to crypto addresses) and webhooks for real-time automated notifications, plus automatic on-ramp/settlement flows, which together enable background, event-driven automations without manual triggering. However this is payment-domain automation (rules, webhooks) rather than a general agentic/background-task framework, and there's no documentation of scheduling, monitoring dashboards, or broader autonomous workflow orchestration beyond these payment rules. missing for 10: general-purpose scheduling/orchestration beyond payment rules, evidence of monitoring/alerting for autonomous runs, and independent confirmation of reliability of these automations running unattended.

   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”

   proof ↗⚑ flag

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

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

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

   ⚑ flag

   BVNK—none0/10

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

   ⚑ flag

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

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

   BVNK—none0/10

   No evidence BVNK offers a natural-language command interface; its API/CLI (bvnk-probe-2) and docs describe structured REST endpoints and a traditional CLI, not NL-driven interaction. Missing for 10: any chat/NL command interface, agent SDK, or documented natural-language operation mode.

   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   proof ↗⚑ flag

Api quality

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

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

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   BVNK's docs describe endpoints and a sandbox simulation environment, but there is no evidence of an interactive API reference (e.g., a Swagger/OpenAPI explorer or 'try it' console) with runnable code examples embedded in the docs.

   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”

   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

   BVNK—none0/10

   The evidence pack shows extensive API documentation (docs.bvnk.com, llms.txt) and endpoint references, but nowhere is an OpenAPI/Swagger spec or other machine-readable spec file mentioned or linked for download. missing for 10: explicit OpenAPI/Swagger JSON or YAML file, a documented spec download link, any mention of spec format.

   ⚑ flag

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

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

   BVNK✓fullclaimed7/10

   BVNK explicitly documents a sandbox environment that simulates pay-ins and payouts consistently across accounts, letting developers test without touching production data. Missing for 10: no explicit statement of how sandbox data/credentials are isolated from production, no independent/hands-on confirmation, and no detail on how to switch environments via API.

   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”

   proof ↗⚑ flag

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

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

   BVNK~partialclaimed3/10

   There is evidence of API versioning practice (Transfers v.3 replacing the legacy Quote API), showing BVNK does version and migrate APIs, but no documented deprecation policy, sunset timeline, or versioning scheme is provided. missing for 10: explicit deprecation policy documentation, versioning scheme details, sunset/EOL timelines, migration guarantees beyond one example.

   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”

   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

   BVNK—none0/10

   No evidence of bulk/batch endpoints (e.g., batch payouts, bulk wallet creation, or bulk transfer APIs); documentation covers single-item operations (single wallet, single rule, single transfer) with no mention of batch processing or multi-item requests. missing for 10: bulk/batch API endpoints, batch job status tracking, documentation of multi-item request payloads.

   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
   • [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”

   proof ↗⚑ flag

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

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

   BVNK~partialclaimed6/10

   BVNK exposes a documented Rules API (POST /payment/v1/rules) that automatically links a fiat virtual account to a crypto address, and webhooks provide real-time event notifications that could trigger downstream automation. This shows genuine rule/event-driven automation, but only for a narrow, specific use case rather than a general-purpose rules engine covering arbitrary triggers/actions. Missing for 10: evidence of broader rule types (e.g., conditional logic across multiple event types), a general rules/automation dashboard, and third-party corroboration of rule reliability at scale.

   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”

   proof ↗⚑ flag

Kyc

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

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

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   Evidence pack covers wallets, payments, webhooks, embedded wallets, and API auth, but no documented KYC/KYB endpoints or onboarding/counterparty-clearance flows are mentioned anywhere in the docs list.

   ⚑ 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

   BVNK—none0/10

   The evidence pack contains only API/product documentation (webhooks, wallets, transfers, sandbox) and no published disclosure of the specific licensed or registered legal entities behind BVNK or the jurisdictions each covers. No regulatory/licensing page, entity list, or legal disclosures are cited anywhere in the evidence.

   ⚑ 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

   BVNK—none0/10

   None of the evidence names sanctions screening, wallet risk scoring/checks, or travel-rule handling—docs cover authentication, wallets, webhooks, transfers, and embedded partner features only. Absence of any specific compliance-machinery documentation means this axis is unmet.

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

   BVNK~partialprobed5/10

   Docs show BVNK exposes a REST API for wallets, transfers, channels and payouts that hides on-chain mechanics (e.g., wallet, rule, and transfer endpoints), so nodes/gas are clearly abstracted. However, evidence only shows a Hawk-authenticated REST API and one CLI repo, not official client libraries/SDKs in multiple languages as the story specifies. Missing for 10: documented multi-language SDKs/client libraries, explicit statement that developers never touch node/gas mechanics.

   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
   • [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”

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

   BVNK~partialclaimed5/10

   BVNK documents a dedicated sandbox ('payment-sim') that simulates pay-ins and payouts consistently across accounts, which covers part of the story, but there is no explicit documentation of sandbox coverage for currency conversions (Transfers v3) or of deterministic test values/testnet behavior for those flows. missing for 10: sandbox coverage for conversions/Transfers API, explicit deterministic test-value behavior, and independent developer confirmation of sandbox fidelity.

   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”

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

   BVNK~partialclaimed5/10

   Docs confirm BVNK webhooks deliver real-time, automated notifications for account changes (bvnk-docs-2), which supports event-driven state tracking without polling. However, the evidence never confirms webhook payloads are cryptographically signed/verifiable, nor does it enumerate specific event types like payment confirmed, payout settled, or conversion executed. Missing for 10: explicit signature/verification mechanism for webhooks, documented list of event types matching the story (payment/payout/conversion events), and any independent confirmation of reliability.

   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

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

   BVNK~partialclaimed5/10

   BVNK exposes a dedicated Transfers v3 API for wallet-to-wallet currency conversion (replacing a legacy Quote API), plus fiat/stablecoin flows (fund in stablecoin, pay out in fiat) and partner markup-fee controls, indicating conversion is an API-first primitive. However, the pack lacks concrete documentation of quote request/response fields showing rates, fee breakdowns, or settlement-time SLAs for these conversions. missing for 10: explicit quote endpoint schema with rate/fee/settlement fields, independent confirmation of conversion accuracy or timing.

   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
   • [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
   • [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
   • [claimed-docs] “As a partner, you can add a markup fee to your customers' transactions, enabling you to collect additional revenue from your customers.”
   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in 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 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

   BVNK~partialclaimed5/10

   BVNK documents API-driven fiat-to-crypto conversion (linking fiat virtual accounts to blockchain addresses, automated on-ramp to crypto) and embedded wallets/virtual accounts that a developer could use to build an onramp flow, but there is no documented pre-built onramp widget, and no explicit mention of end users paying via card to buy stablecoins — the flow described is bank/virtual-account based automation rather than a card-based consumer buy widget. Missing for 10: a documented embeddable UI/widget component, explicit card-payment support for the onramp, and end-user-facing checkout flow evidence.

   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
   • [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
   • [claimed-docs] “Embedded Wallets provide partners with seamless payment and fund management capabilities directly within their platform while maintaining th…”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”

   proof ↗⚑ flag

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

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

   BVNK~partialprobed7/10

   BVNK's docs show broad API coverage across core UI functions—wallet creation (fiat/crypto), transfers, payouts, rules, embedded wallets, webhooks—and explicitly note wallets can be managed 'through the Portal or API' (bvnk-docs-4), suggesting strong UI/API parity. However there is no explicit statement or independent audit confirming every UI feature (e.g., rewards, virtual cards, markup fee configuration) has a full API equivalent. Missing for 10: explicit parity documentation stating all UI actions are API-accessible, and independent/hands-on verification that no UI-only features exist.

   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
   • [claimed-docs] “Embedded Wallets provide partners with seamless payment and fund management capabilities directly within their platform while maintaining th…”
   • [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”

   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

   BVNK—none0/10

   Evidence shows individual payout, wallet, and transfer APIs (e.g., bvnk-docs-11, bvnk-docs-13, bvnk-docs-6) but nothing documenting a batch/bulk payout endpoint, mass-disbursement operation, or per-item status reporting for multiple payouts in one call. This is a fair axis for a payments platform, so absence of evidence means 'none' rather than 'na'.

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

   BVNK~partialclaimed6/10

   BVNK docs describe fiat payout rails (payout-overview, virtual accounts in USD/EUR/GBP, stablecoin-to-fiat settlement flows) confirming that off-ramp to local bank accounts is supported, but there is no single published table enumerating all supported countries or the full currency corridor list beyond USD/EUR/GBP mentions. missing for 10: a published country/currency coverage matrix, confirmation of local payout rails outside USD/EUR/GBP, and independent verification of settlement speed/coverage claims.

   • [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
   • [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
   • [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”

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

   BVNK~partialclaimed6/10

   BVNK's docs confirm programmatic stablecoin sending via API (bvnk-docs-13, bvnk-docs-14, bvnk-docs-18), wallet creation/management via API (bvnk-docs-4), and webhook-based notifications for account changes (bvnk-docs-2), plus a sandbox simulation for payouts (bvnk-docs-3). However, there is no explicit documentation of a 'stored recipient' object, dedicated payout endpoint with status-lifecycle documentation (e.g., pending→settled states), or confirmation that webhooks specifically track payout-to-settlement status. missing for 10: dedicated payout API/status-tracking docs, stored-recipient object documentation, explicit settlement-state webhook events.

   • [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
   • [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
   • [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”

   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

   BVNK—none0/10

   No evidence pack items document settlement timing SLAs (payment to available balance), a published fee schedule per rail, or exportable statements/reports for accounting reconciliation; evidence only covers API mechanics like wallets, webhooks, transfers, and embedded partner features.

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

   BVNK✓fullclaimed8/10

   BVNK documents crypto/fiat wallet creation, the Transfers v3 API for wallet-to-wallet currency conversion, fiat-to-crypto automation rules, on/off-ramp flows, and messaging like 'use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat' — covering both API and dashboard rebalancing between fiat and stablecoin balances end to end. Missing for 10: an explicit worked example/tutorial showing a full internal transfer+rebalance flow with request/response payloads, and independent (non-vendor) confirmation of dashboard UX.

   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
   • [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
   • [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
   • [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
   • [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”

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

   BVNK✓fullclaimed8/10

   BVNK's docs describe creating payment channels (unique repeated-use blockchain addresses) to accept stablecoin payments, converting to fiat, plus webhook notifications for settlement confirmation and a sandbox for testing pay-ins programmatically. This covers create → present address → confirm settlement end-to-end via documented API, though evidence is docs-only without independent hands-on confirmation. Missing for 10: independent/hands-on verification of the checkout flow working in practice, and more detail on the specific 'create payment' endpoint/response schema.

   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
   • [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   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

   BVNK—none0/10

   The evidence pack shows BVNK supports generic 'stablecoins' and 'crypto' wallets, but nowhere does it name specific stablecoins (USDC, USDT, etc.) or specific blockchain networks/chains supported. missing for 10: named stablecoin list (USDC, USDT, etc.), named supported chains/networks, any coin-to-chain compatibility matrix.

   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
   • [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
   • [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
   • [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
   • [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”

   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 to BVNK
   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

   BVNK✓fullclaimed9/10

   BVNK explicitly documents accepting stablecoin payments and receiving fiat currency in the account (bvnk-docs-9), with marketing and docs confirming 'Accept payments globally in stablecoins. Settle in fiat' and 'fund in stablecoins and pay out in fiat' (bvnk-docs-18, bvnk-docs-19), plus payout mechanisms to bank accounts (bvnk-docs-11) and fiat virtual accounts in major currencies (bvnk-docs-12). missing for 10: independent/hands-on confirmation of the auto-conversion accounting flow beyond vendor docs.

   • [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
   • [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
   • [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”
   • [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”

   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

   BVNK—none0/10

   Evidence shows general wallet/payment/API capabilities (wallets, rules automation, transfers) but nothing describing an 'agent' actor, scoped spend authority, or human-configured spend limits governing agent-initiated payments. The lone 'agent-wallet-cli' repo mention has no accompanying documentation of spend controls or agent payment flows, so this doesn't establish the capability.

   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
   • [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
   • [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”

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

   BVNK~partialprobed3/10

   BVNK documents general programmatic wallet creation (crypto/fiat) via API/Portal and Hawk-based API authentication, and a probe references an 'agent-wallet-cli' repo, suggesting some agent-oriented wallet tooling exists. However there is no documentation of scoped API keys per agent, policy/permission controls, or explicit spending/movement limits tailored to autonomous agents. Missing for 10: scoped-key issuance mechanics, policy engine/spend-limit configuration, and agent-specific governance documentation.

   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”

   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

   BVNK—none0/10

   No evidence of x402, ACP, MPP, or AP2 protocol support anywhere in the docs pack; BVNK documents Hawk auth, webhooks, wallets, and fiat/crypto conversion APIs but never mentions these machine-payment protocols by name or provides endpoints/SDKs for them.

   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”

   proof ↗⚑ flag

Issuance

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

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

   BVNK—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 to BVNK
   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

   BVNK~partialclaimed2/10

   Marketing copy mentions a rewards program ('Put idle balances to work with built-in rewards') implying some yield mechanism, but there is no documentation of reserve composition, attestation reports, eligibility criteria, or regulatory caveats for held stablecoins. Missing for 10: reserve composition disclosure, third-party attestation reports, yield program eligibility rules, regulatory/risk caveats for the rewards program.

   • [claimed-docs] “Put idle balances to work with built-in rewards.”

   proof ↗⚑ flag

Balances

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

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

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed5/10

   BVNK docs and marketing confirm you can create and hold crypto/stablecoin wallets/balances (bvnk-docs-4, bvnk-docs-15, bvnk-docs-13, bvnk-docs-17, bvnk-docs-19), but there is no documentation on custodial account structure, licensing, geographic availability, or any gating/eligibility disclosures for holding stablecoin balances. missing for 10: explicit custodial/regulatory documentation, stated geographic availability, and honest disclosure of any gating or KYC/jurisdiction restrictions for balance holding.

   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
   • [claimed-docs] “Spin up stablecoin and fiat wallets for your customers.”
   • [claimed-docs] “Put idle balances to work with built-in rewards.”
   • [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”

   proof ↗⚑ flag

Virtual accounts

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

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

   BVNK✓fullclaimed7/10

   BVNK docs show both named virtual accounts (USD/EUR/GBP) for businesses/customers and 'channels' — unique, repeated-use blockchain deposit addresses that never change per customer — plus webhooks for real-time notification of incoming funds, directly enabling attribution without manual matching. missing for 10: explicit documentation tying a specific virtual account/address to a customer ID in transaction payloads, and independent/hands-on confirmation of reconciliation workflow.

   • [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”

   proof ↗⚑ flag

Wallets

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

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

   BVNK~partialclaimed6/10

   Docs confirm crypto/fiat wallet and virtual-account creation via API or Portal (bvnk-docs-4, bvnk-docs-12), per-customer wallet provisioning (bvnk-docs-15), and reusable deposit addresses/'channels' for receiving crypto (bvnk-docs-10), which together demonstrate programmatic wallet/address provisioning. However there is no documentation of key custody semantics (custodial model, key management, signing responsibility) anywhere in the pack. Missing for 10: explicit key custody/ownership documentation, independent confirmation of API wallet creation workflow beyond docs snippets.

   • [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
   • [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
   • [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
   • [claimed-docs] “Spin up stablecoin and fiat wallets for your customers.”

   proof ↗⚑ flag