BVNK

• Name: BVNK
• URL: https://bvnk.com/
• Category: stablecoin payments / wallet / virtual-account infrastructure
• Tags: ethereum-ecosystem
• Summary: BVNK is a regulated stablecoin money-movement stack: wallets, virtual accounts, compliance packaging, and payout plumbing in one vendor surface. The delivery-model menu is secondary. This is operator plumbing, not a new rail.
• What it does:
  • Offers managed payments for businesses that want BVNK to handle more of the licensing, custody, compliance, and payment execution stack
  • Supports direct and embedded delivery models so companies can use BVNK for their own treasury/payment flows or embed stablecoin capabilities into customer-facing products
  • Provides self-managed / Layer1-style infrastructure for teams that want to connect their own licences, custodians, and liquidity partners while keeping BVNK in the operational stack
  • Exposes REST APIs, sandbox accounts, API keys, webhook flows, and an OpenAPI specification for integrating payments, channels, and wallet operations
  • Supports fiat rails plus a narrower set of supported crypto/stablecoin assets and networks documented in the currencies reference
  • Publishes uptime / incident-handling expectations and a public status page, which is useful for evaluating it as an operational vendor rather than just a marketing brand
• Key claims:
  • The homepage positions BVNK as “enterprise-grade payments infrastructure for stablecoins” and says customers can send, receive, convert, and store funds across 130+ countries
  • Official docs present multiple delivery models, centered on whether the customer wants BVNK to handle custody/compliance or prefers to run more of the stack themselves
  • The API overview describes BVNK as infrastructure for payments, channels, and digital-wallet operations, with separate sandbox and production environments
  • The currencies reference shows that the supported-asset universe is operationally curated rather than a broad long-tail token catalog; the emphasis is on key fiat rails and payment-oriented assets such as USDC and USDG on selected networks
  • BVNK’s uptime page commits to 99.90% availability and describes continuous monitoring, on-call engineering, status-page communications, and post-mortem practices
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were BVNK’s official site and documentation portal; see ../whitepapers/bvnk-primary-sources-2026-04-23.md.
• Sources:
  • https://bvnk.com/
  • https://docs.bvnk.com/
  • https://docs.bvnk.com/llms.txt
  • https://docs.bvnk.com/bvnk/get-started/get-started-w-bvnk
  • https://docs.bvnk.com/bvnk/get-started/delivery-models
  • https://docs.bvnk.com/bvnk/api-explorer/api-overview/overview
  • https://docs.bvnk.com/bvnk/references/currencies
  • https://docs.bvnk.com/bvnk/references/uptime-and-incident-handling

Internal linkages

• Strongest upward reads: bridge-xyz, coinflow, and openpayd.

• Last reviewed: 2026-06-04 UTC