Virtual IBANs Meet Stablecoins: How Fintechs Bridge Traditional Banking and Digital Dollars

A business in Germany sends a SEPA payment to what looks like a normal bank account number. On the receiving side, a licensed provider converts the euros into USDC and credits the recipient's stablecoin wallet within minutes. The sender never touched crypto. The recipient never opened a European bank account. The bridge between these two worlds is a virtual IBAN: a routing reference that follows the same ISO 13616 format as any traditional IBAN, but connects to stablecoin settlement infrastructure instead of a conventional bank ledger.

This hybrid model is quietly reshaping how global businesses handle cross-border payments. By combining the familiarity and reach of SEPA and SWIFT with the speed and cost advantages of on-chain settlement, virtual IBAN-to-stablecoin providers are building a new category of financial infrastructure. This article explains how the model works, who is building it, and what regulatory frameworks govern it.

What Is a Virtual IBAN?

An International Bank Account Number is a standardized identifier used across more than 80 countries to route payments between banks. A traditional IBAN maps one-to-one to a bank account: each account has exactly one IBAN, and that IBAN is tied to a specific bank, branch, and customer.

A virtual IBAN uses the same format. From a sender's perspective, it is indistinguishable from a regular IBAN. The sending bank processes it through the same clearing and settlement systems. The difference is entirely on the receiving side: instead of mapping to a standalone bank account, a virtual IBAN routes to a pooled or settlement account held by a licensed institution. Multiple virtual IBANs can map to a single underlying master account, with the provider using the unique IBAN reference to identify which customer, invoice, or channel a payment belongs to.

Key characteristics of virtual IBANs

• Follow standard ISO 13616 structure with country code, check digits, and bank identifier
• Pass MOD-97 validation like any other IBAN
• Route through domestic clearing systems (SEPA, Faster Payments, ACH)
• Map to a master safeguarding or settlement account held by a licensed EMI or bank
• Can be issued programmatically via API, without opening a new bank account per customer

Named vs. unnamed: A named virtual IBAN carries the beneficiary's legal name in the payment reference, allowing it to pass Confirmation of Payee checks. An unnamed vIBAN is a generic routing reference. For compliance-sensitive use cases like on-ramp and off-ramp flows, named vIBANs are increasingly required by regulators.

The Hybrid Model: IBAN In, Stablecoin Out

The core innovation is connecting traditional payment rails to stablecoin settlement. A typical flow works as follows:

1. A business is assigned a virtual IBAN denominated in EUR, GBP, or USD
2. A counterparty sends a SEPA transfer or wire to that IBAN
3. The provider receives the fiat into its master settlement account
4. The fiat is converted to a stablecoin (typically USDC or USDT)
5. The stablecoin is credited to the business's wallet or treasury address

The reverse also works: a business holds stablecoins, initiates a payout, and the provider converts to fiat and sends a SEPA or SWIFT payment from the virtual IBAN. This bidirectional flow creates what the industry calls a hybrid account: an instrument that looks like a traditional bank account to the outside world but settles in digital dollars internally.

The stablecoin sandwich

A related pattern used heavily in cross-border B2B payments is the stablecoin sandwich: fiat in on one side, stablecoin settlement across the middle, fiat out on the other. Neither the sender nor the recipient ever holds or sees the stablecoin. This model powers remittance corridors, invoice settlement, and marketplace disbursements across providers like BVNK, Tazapay, and others.

The virtual IBAN is what makes this model work at scale. Without it, the sender would need to use a crypto exchange or wallet interface. With a vIBAN, they can use their existing bank and existing payment workflows. The on-ramp is invisible.

Open vs. closed sandwich: In a closed sandwich, both sides see fiat. In an open sandwich, the recipient keeps the stablecoins and decides when (or whether) to convert. The open model is increasingly popular with businesses that hold stablecoin treasuries or want to make subsequent on-chain payments.

Who Is Building This

Several companies have built or are building virtual IBAN-to-stablecoin infrastructure. They span a range from pure stablecoin-native fintechs to traditional payment processors adding digital asset capabilities.

Monerium: IBAN-linked euro stablecoins

Monerium is an Icelandic company licensed as an Electronic Money Institution under EU law. Its product, EURe, is a euro-denominated stablecoin where each customer receives a personal IBAN. Incoming SEPA payments to that IBAN are automatically minted as EURe in the customer's on-chain wallet. Outgoing payments burn the tokens and send euros through SEPA. Customer funds are held in segregated accounts at licensed EU banks, separate from Monerium's own assets.

What makes Monerium distinct is that EURe is classified as an e-money token under MiCA, meaning holders can redeem at par value at any time. The IBAN linkage means EURe functions as a bridge between legacy banking and on-chain settlement: a euro sent via SEPA becomes a transferable, programmable token without the sender needing to interact with a blockchain.

Clear Junction: vIBANs for licensed crypto firms

Clear Junction is dual-licensed by the UK Financial Conduct Authority as both an EMI and a virtual asset service provider. In July 2025, it extended its named virtual IBAN service to VASP-licensed businesses, a capability previously restricted to banks and EMIs. Each named vIBAN is tied to a single end customer, supporting travel rule compliance and automated reconciliation.

Clear Junction also launched an on-chain stablecoin transfer service for regulated institutions, targeting crypto exchanges, fintechs, EMIs, and remittance providers. The dual-license structure lets it operate across both the fiat and digital asset sides of a transaction without relying on third-party banking partners for either leg.

BVNK: stablecoin-native payment infrastructure

BVNK connects fiat rails (SWIFT, SEPA, UK Faster Payments, ACH) to stablecoins across more than 130 countries. Merchants and platforms receive stablecoins through unique channel addresses and can automatically convert to USD, EUR, or GBP via named virtual IBANs. By the end of 2025, BVNK was processing roughly $30 billion in annualized stablecoin payment volume.

In March 2026, Mastercard agreed to acquire BVNK for up to $1.8 billion, a signal that traditional card networks view the virtual IBAN-to-stablecoin model as strategically significant. The deal reflects a broader trend of incumbents acquiring stablecoin infrastructure rather than building it from scratch.

OpenPayd and BCB Group

OpenPayd offers a single API for multi-currency accounts, named virtual IBANs, and fiat-to-stablecoin conversion. Regulated under both UK and EEA electronic money institution licenses, it serves over 750 enterprise clients. In 2025, OpenPayd integrated with Fireblocks to become the first UK payments provider on its network, and partnered with Circle to give crypto exchanges like VALR fiat-stablecoin infrastructure through dedicated virtual IBANs.

BCB Group operates the BLINC Network for instant settlement among institutional clients. Its product suite includes virtual IBANs for fiat custody and stablecoin trading services. In February 2026, BCB and Zodia Markets launched instant settlement and institutional liquidity through BLINC integration.

Traditional IBAN vs. Virtual IBAN vs. Stablecoin-Only

Each model involves different tradeoffs around speed, cost, compliance, and accessibility. The following table compares the three approaches for receiving and settling a cross-border payment.

The Regulatory Framework

Virtual IBAN-to-stablecoin providers sit at the intersection of two regulatory regimes: payment services regulation and digital asset regulation. In Europe, this means navigating both the Electronic Money Directive (EMD2) and MiCA simultaneously.

E-money institution licensing

To issue virtual IBANs and handle customer funds in the EU or UK, a provider typically needs an e-money institution license or a payment institution authorization under PSD2. EMIs can issue electronic money, hold customer funds in safeguarded accounts (segregated from their own assets), and participate in payment schemes. Unlike bank deposits, customer funds at an EMI are not covered by deposit insurance schemes, but they are legally ring-fenced.

SEPA participation

Participating in SEPA (and therefore issuing IBANs that can receive SEPA payments) requires either direct or indirect membership in the SEPA payment schemes. Direct participants settle through central bank systems like TARGET2 or TIPS and must hold a central bank cash account. Historically, only credit institutions had direct access. Recent regulatory changes now allow EMIs and payment institutions to apply for direct SEPA participation, though most still access SEPA indirectly through a sponsor bank.

This indirect model is how most virtual IBAN providers operate: a licensed EMI partners with a SEPA-direct bank, issues virtual IBANs under its own BIC, and routes incoming payments through the bank's settlement infrastructure. The EMI handles the customer relationship, compliance, and conversion; the bank provides the payment rail access.

MiCA and stablecoin classification

Under the EU's Markets in Crypto-Assets Regulation, stablecoins pegged to a single fiat currency are classified as e-money tokens (EMTs). EMT issuers must be licensed as credit institutions or EMIs, maintain reserves in the same currency as the token, hold a significant share of reserves in bank deposits (at least 30% under draft EBA technical standards), and allow holders to redeem at par value at any time.

This classification directly affects the virtual IBAN-to-stablecoin model. A provider that converts incoming SEPA payments to a MiCA-compliant EMT like EURC or Monerium's EURe is operating within the regulated framework. Converting to an EMT that lacks authorization (or to a stablecoin not classified as an EMT) creates regulatory risk. As of mid-2026, only a handful of stablecoins meet the full EMT requirements. A Circle-affiliated source claims only USDC, EURC, and USDG are fully compliant among the top 50 stablecoins by market cap, though this figure should be treated with appropriate skepticism given the source.

Regulatory comparison by jurisdiction

Use Cases for the Hybrid Model

The virtual IBAN-to-stablecoin bridge addresses several concrete problems that neither traditional banking nor pure stablecoin solutions solve alone.

Cross-border B2B settlement

A company in Southeast Asia invoices a European client. The client pays via SEPA to a virtual IBAN. The provider converts to USDC and settles to the company's wallet, bypassing correspondent banking chains that would add 2-4 intermediaries, each taking fees and adding days to the settlement timeline. The stablecoin sandwich model can reduce total cross-border costs to 0.5-2.5% compared to the 3-7% typical of SWIFT corridors, though these estimates come from vendor sources and actual costs depend on volume, corridor, and conversion spread.

Marketplace and platform disbursements

Platforms that operate globally often struggle to pay out to sellers, freelancers, or service providers across multiple countries. Virtual IBANs let the platform collect in local fiat, while stablecoin settlement on the back end enables near-instant payouts to recipients in countries where local banking infrastructure is limited or slow. The recipient can hold stablecoins or convert to local currency through a local off-ramp.

Crypto-native treasury operations

Companies that hold stablecoin treasuries need a way to receive payments from clients who operate in fiat. A virtual IBAN gives the company a "normal" bank account number for invoicing, while the received funds settle directly into their stablecoin treasury. This eliminates manual conversion steps, reduces float, and simplifies accounting by keeping settlement in a single denomination.

Remittance corridors

The model also applies to consumer remittances. A worker in Europe sends euros to a virtual IBAN. The provider converts to USDC, transfers on-chain, and a local partner in the destination country converts to local currency for cash pickup or mobile money deposit. This is the stablecoin sandwich at its simplest, and it can operate through existing remittance corridors without requiring the sender to install a crypto wallet or understand blockchain mechanics.

Risks and Limitations

The hybrid model is not without its challenges, and businesses evaluating it should understand the tradeoffs.

Counterparty risk

Virtual IBAN accounts are not bank deposits. Funds held at an EMI are safeguarded but not covered by deposit insurance schemes like the EU's €100,000 guarantee. If the EMI becomes insolvent, customer funds should be segregated and returned, but the process is not instant and outcomes depend on the insolvency regime and how well the provider actually maintained segregation. This is a meaningful difference from holding funds at a regulated bank.

Conversion spread and slippage

The fiat-to-stablecoin conversion is where providers earn most of their margin. Spreads can range from 0.1% to over 1% depending on the provider, currency pair, and volume. For large or frequent transactions, these spreads compound. Businesses should compare effective rates across providers rather than relying on advertised headline fees, which often exclude the FX or conversion spread.

Regulatory fragmentation

A provider licensed as an EMI in Lithuania can passport across the EU but cannot issue virtual IBANs in the UK without a separate FCA authorization. The US has no federal equivalent of the EMI license, requiring state-by-state money transmitter licensing. This fragmentation means that a provider's geographic coverage depends heavily on its licensing footprint, and businesses need to verify that their specific corridors are supported.

Stablecoin risk

The model inherits the risks of whichever stablecoin is used for settlement. A depeg event, a regulatory freeze, or a blacklisting action on the stablecoin layer can disrupt the entire flow. Multi-stablecoin support (allowing businesses to choose between USDC, USDT, and others) mitigates this but adds operational complexity.

Where Spark Fits In

Virtual IBAN-to-stablecoin bridges represent one end of the on-ramp spectrum: they convert traditional bank payments into digital dollars. But once funds exist as stablecoins, they need a settlement layer that is fast, low-cost, and capable of handling programmable payments.

Spark provides exactly this kind of infrastructure. As a Bitcoin Layer 2 that supports native stablecoin issuance (including USDB), Spark can serve as the settlement rail after the fiat-to-stablecoin conversion. Transfers on Spark settle instantly, cost fractions of a cent, and preserve self-custody. For businesses that receive fiat through virtual IBANs and want to hold or transfer the resulting stablecoins without high on-chain fees or slow confirmation times, Spark offers a natural next step.

The Spark SDK enables developers to build wallets and payment flows that connect to this infrastructure. For an example of a consumer-facing wallet built on Spark, see General Bread, which demonstrates how stablecoin settlement can be delivered through a simple mobile interface. For a deeper comparison of how different settlement layers handle stablecoin payments, see our research on payment finality across blockchains and embedded finance and Banking-as-a-Service.

What Comes Next

The virtual IBAN-to-stablecoin hybrid is still early. Several developments will shape its trajectory over the next few years.

PSD3, the EU's next Payment Services Directive, is expected around 2028 and will merge EMI and payment institution licensing into a single framework. This could simplify the regulatory path for hybrid providers. At the same time, MiCA's evolving technical standards (including reserve requirements and supervisory expectations for significant EMTs) will determine how much flexibility issuers have in structuring their products.

In the UK, the FCA is consulting on a stablecoin regulatory framework that could create a parallel to MiCA's EMT category. And in the US, the GENIUS Act and related proposals would establish federal requirements for stablecoin issuers, potentially opening the door for US-based virtual IBAN-to-stablecoin services.

Meanwhile, Mastercard's acquisition of BVNK signals that the legacy payment networks see this infrastructure as a strategic asset, not a niche experiment. As more providers launch and more corridors open, the line between a "bank account" and a "stablecoin wallet" will continue to blur, until the distinction matters only to regulators and compliance teams, not to the businesses and individuals using these accounts to move money.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.