BVNK Flow Simulator
Step through BVNK's stablecoin payment flows as animated sequence diagrams — Payment Link pay-ins with locked quotes, reusable Channel top-ups at spot rate, and two-step payouts from a fiat wallet — with every API call, status transition, and webhook annotated.
A customer tops up a platform account with stablecoins via a BVNK Payment Link: the platform creates a payment with a live quote, BVNK generates a unique deposit address, the customer sends funds on-chain, and BVNK converts and settles into the platform's wallet — in fiat, a different stablecoin, or the same one.
"Deposit $10 in crypto"
Customer picks stablecoin at the platform's cashier or checkout.
A trading platform, neobank or e-commerce site offers stablecoins as a deposit / payment option next to cards and bank transfers. The customer chooses the amount in the display currency; everything after this is orchestrated through BVNK.
What the BVNK platform does
BVNK is stablecoin payment infrastructure: a single API layer through which a platform can accept stablecoins from customers, hold balances across fiat and digital currencies, and pay out stablecoins to any wallet — while BVNK handles quotes, conversion, blockchain monitoring, gas, and settlement. In August 2026 the company became part of Mastercard, the first major card network to own stablecoin settlement infrastructure outright (a deal of up to $1.8 billion announced in March 2026, closed August 3, 2026, bringing roughly $30 billion in annualised payment volume).
The simulator covers the three flows that make up most integrations: single-use Payment Links with a locked quote and unique deposit address, permanent per-customer Channels converted at spot rate, and two-step payouts where a fiat wallet funds a stablecoin transfer after an explicit quote confirmation. For the underlying stablecoins themselves — issuers, reserves, and chains — see the Stablecoin Reference.
How it compares to protocol-level rails
BVNK is a platform, not an open protocol: the counterpart of a PSP or acquirer for stablecoin rails, reachable over an authenticated REST API with signed webhooks. That places it between two things covered elsewhere on this site — the x402 protocol, where the payment lives inside the HTTP request itself with no intermediary holding funds, and card-rail settlement flows (clearing & settlement), where value moves T+1 through scheme netting. A BVNK payout is closer to a real-time gross settlement: one on-chain transfer, final in minutes, with no recall.
Common questions
Does the platform ever hold crypto?
Not necessarily. A platform can run entirely on fiat wallets: pay-ins convert to fiat on settlement, and payouts convert fiat to stablecoins at a locked rate when created. Holding USDT/USDC wallets is equally supported for crypto-to-crypto flows.
What stops a payout being sent twice?
Each payout requires a unique reference (duplicates are rejected), and the two-step flow adds an explicit confirm gate on a quote that expires after one hour. Once broadcast, on-chain transfers are final — BVNK's docs warn to never re-issue an API call for an already-finalised withdrawal.
How does the platform know a payment completed?
Signed webhooks (HMAC-SHA256 in the x-signature header) fire on every status change, with retries backing off up to 100 attempts. The recommended pattern is: verify the signature, acknowledge with 200 fast, then re-fetch the payment by UUID before crediting — amounts can differ from the request (e.g. UNDERPAID).
What networks and coins are supported?
Typically USDT and USDC across Ethereum (ERC-20), Tron (TRC-20), Solana, Polygon and others — a pay-in response returns alternative deposit addresses per network. Around 16 cryptocurrencies are accepted for deposits; fiat sides settle in USD, EUR, GBP and more.
Flows follow BVNK's public API documentation (docs.bvnk.com, Stablecoin Payments guides). The simulator is illustrative — no network requests are made and nothing runs outside your browser. Also see the BVNK platform guide for architecture, status models, and the Mastercard context.