BVNK Integration for Payment Firms, PSPs and Treasury Platforms
On BVNK, payment firms, PSPs and treasury platforms book each payout once in their own ledger. They also handle approvals, signed webhooks and a daily report match themselves. Protofire builds those four parts. Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What BVNK does with a payout and what your side decides
BVNK sends the payout, and your side decides which customer a debit belongs to, who approved it and which ledger line it becomes. You have chosen BVNK to pay out stablecoins from a euro, pound or dollar balance. BVNK debits the fiat wallet, converts at send time and sends USDC or another coin to the beneficiary's address (BVNK). So your BVNK integration now has to reach your own ledger.
Three cases show up as breaks at month-end unless your integration handles them. A fiat payout marked COMPLETED can still come back as RETURNED (BVNK). A compliance hold can stop a payout that your client was already told about. And since 30 October 2026, BVNK's Quote API has refused create, estimate and accept calls outside OTC traffic. So a conversion written against the Quote API needs rework.
In the Direct and Embedded models, BVNK converts, screens and holds the custodial wallets and the licenses. Protofire builds the firm's side. Payouts routed over several rails are covered on our stablecoin cross-border payments page.
Who builds and runs each part of a BVNK payout
A payout request starts in the firm's back office and draws on the prefunded BVNK fiat wallet. The payout reaches the beneficiary as stablecoins or a bank payment. It then returns to the firm as a webhook, a booking and a line in BVNK's ledger report.
Payout requests and approvals
Ledger and customer balances
BVNK connector
Webhook receiver and report match
BVNK account
Chains and bank rails
What each BVNK delivery model leaves to your firm
The BVNK delivery model decides who BVNK onboards, whose balance pays and who holds the keys.You pick the model before the build starts.
The firm contracts with BVNK and pays from its own treasury, in the Portal or by API (delivery models). BVNK onboards the firm itself. In standard wallets, BVNK holds the keys as custodian (BVNK). In the Direct model, the payout calls and the webhook receiver are left to the firm. The approval rules and the report match are also left to the firm.
The firm offers BVNK accounts and payouts to its own customers by API, under its brand. BVNK onboards the firm first, then its customers. In the Embedded model, the firm is left with its customers' balances, approvals and KYC records. Booking each debit to the right customer is also left to the firm.
Layer1 is BVNK's self-hosted product. Layer1 runs in the firm's own environment under the firm's licenses. Its Layer1 Vault keeps private keys inside the firm's infrastructure (Layer1). With Layer1, the vault and its approval policies are left to the firm. The screening contract and the export to the general ledger are also left to the firm. This page is written for Direct and Embedded, so a Layer1 build is scoped from Layer1's own documentation.
BVNK ownership, licenses and stablecoins by region
- Owner
- Mastercard completed its acquisition of BVNK on 3 August 2026 (Mastercard).
- European Union
- System Pay Services (Malta) Limited is an electronic money institution regulated by the MFSA (BVNK). ESMA's register lists its MiCA authorization, dated 13 February 2026 (ESMA).
- United States
- Customers in states that BVNK's money transmitter licenses do not cover get fewer coins on BVNK's currency lists. New York and California are among those states (currencies).
- Stablecoins by region
- In November 2026, EEA customers get USDC on nine networks, EURC on Ethereum alone and USDG on Solana. Customers elsewhere and in the US also get USDT and PYUSD (currencies).
Checked November 2026 against BVNK's documentation, ESMA's register and Mastercard's release. Protofire integrates BVNK for firms that have chosen it.
[...] to regard the custody and administration of EMTs as a payment service and the custodial wallet as a payment account under the PSD2, where they allow to send and receive transfers of EMTs to and from third parties
What you get from Protofire's BVNK build
Your firm gets five things from Protofire once BVNK is connected to its books.
Each payout submitted once
After a timeout, the connector resends the request with the same idempotency key and keeps the payout's reference. BVNK refuses that reference a second time as "Duplicate Reference" (BVNK). Protofire builds the connector, with Travel Rule details drawn from your KYC records. Our EU Travel Rule guide lists the tools that pass Travel Rule details between providers.
One booking per movement
A webhook can repeat, so the receiver checks the x-signature header and answers within BVNK's 10 seconds (BVNK). The receiver also drops repeats by event ID and rereads the payment. It posts once per Transaction UUID and status. A fiat COMPLETED remains open, because the beneficiary bank can still reject the payout. A later RETURNED is posted as its own reversal.
A case for each BVNK hold
BVNK can put a payment ON_HOLD for manual review or a request for information. For each hold, Protofire opens a case, attaches the Travel Rule record and switches the client's message from "sent" to "pending".
A daily report match that finance can sign
In production, BVNK's ledger reports run one hour behind, and their download links expire after 24 hours (BVNK). Protofire archives each report file on arrival and matches it on Transaction UUID and Merchant Reference. We book FEE lines as their own entries and flag a report that is late.
Approval rules an auditor can read
A fiat payout waits in PENDING_APPROVAL. If the four-eyes approval is rejected, the payout ends CANCELLED and the funds remain in the wallet. Protofire writes your four-eyes rules as decisions that your staff record. Once BVNK enables its approval action, those decisions are relayed to that action under a Hawk key that the firm can revoke.
BVNK retired three Quote API calls on 30 October 2026
From 30 October 2026, BVNK's Quote API takes no create, estimate or accept calls outside OTC traffic.New conversions run through Transfers v.3 (migration guide). Protofire reads BVNK's migration guides when we scope a build. So the code is changed against the retirement dates that BVNK has published. GET calls for past quotes remain available.
Create and preview
Quote API, retired 30 October 2026: POST /api/v1/quote, with estimate=true
Transfers v.3: POST /payment/v3/transfers, and a dry-run call
Accept
Quote API, retired 30 October 2026: PUT /api/v1/quote/accept/{uuid}
Transfers v.3: An ACCEPT_QUOTE action that includes the quote's digest
Outcome
Quote API, retired 30 October 2026: Two fields, quoteStatus and paymentStatus
Transfers v.3: One status field, the source of truth
Unaccepted quote
Quote API, retired 30 October 2026: Reported as a failure
Transfers v.3: EXPIRED, separate from FAILED
Our record: the Gnosis Safe web app and a Hyperlane route
Public sources show two pieces of Protofire's work: a multisig wallet interface and a cross-chain transfer route.Both bear on two questions that a BVNK payout raises: who must agree before funds move, and what a transfer does on its chain leg.
The Gnosis Safe web app, 2019 to 2021
Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021 (contributors graph). The Safe Ecosystem Foundation wrote in May 2026 that Protofire "has been contributing to Safe since 2018". A four-eyes rule on a BVNK payout asks the same question: who must agree before the payout is sent. Our Safe multisig work has its own page.
A Hyperlane route between Ethereum and Vana, 2024
Hyperlane's public registry records the VANA warp route between Ethereum and Vana as "Deployed by Protofire". The record comes from a pull request merged on 15 December 2024. In 2024, Protofire also built the bridge interface for moving assets onto Vana (Vana case). Our cross-chain integration page describes the service.
How a BVNK project with Protofire runs
- Step 1
Review of your sandbox log before the call
Before the call, an engineer reads your sandbox webhook log and a week of ledger reports against your ledger. A written proposal follows. It sets out findings, a plan in phases and the first step that Protofire recommends. - Step 2
First phase: payouts and bookings
The connector, the webhook receiver and the posting rules are launched first. The approval flow and Travel Rule data are launched with them, so the first live payout is booked once. - Step 3
Next phase: holds, the daily match and the outage runbook
Queued payouts remain pending in your systems until BVNK reports a final status, because a second payout on chain cannot be recalled. BVNK publishes incidents on its status page. The runbook pauses new payouts on the affected rail and tells clients "pending with our payment provider" without a promised time. Afterwards, the runbook checks the next ledger report. - Step 4
Ownership and operation after launch
The code, configuration and runbooks are yours. Your staff generate the Hawk API keys and keep them in your vault. Your team runs the integration, or Protofire operates it under a written scope.
How work with Protofire starts
You send your BVNK delivery model, a sandbox webhook log and a week of BVNK ledger reports.Protofire's first written proposal turns each BVNK status that your flows use into a posting rule. Where Protofire runs the connector, the written scope lists each call that the connector sends to BVNK, including payouts and approval actions.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When a BVNK integration project is more than you need
A full project is more than you need in three cases.
- The Portal handles a few payout batches a month. BVNK's Direct model runs in the Portal or by API, and BVNK's EU payouts page offers CSV upload (BVNK).
- Your payment processor may already give you access to BVNK. Ask the processor before you build.
- You have not picked a rail yet. Our payout rails comparison compares BVNK with zerohash, Bridge and others.
Protofire holds no financial or crypto-asset license. Your firm opens the BVNK account, answers BVNK's compliance reviews and holds the license for customer virtual accounts. Your counsel forms the views on MiCA, PSD2 or US money transmission.
FAQ
What is a BVNK integration?
Who can build a BVNK integration for a payment firm or PSP?
Can EEA customers receive USDT through BVNK?
Can a firm offer its customers virtual accounts through BVNK?
What should happen to queued payouts when BVNK screening or a rail stops?
Can a firm onboard its customers to BVNK with its own KYC?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
