What Is a Virtual IBAN
A virtual IBAN is a unique international bank account number assigned to a business or individual that functions like a real bank account number for receiving payments, but routes funds to a master account held by a payment institution rather than a separate physical bank account. To anyone sending money to it, it looks and behaves identically to a standard IBAN. To the company receiving through it, it is a flexible collection tool that can be issued in multiple currencies, across multiple jurisdictions, without opening a new bank account in each one.
It is the infrastructure that makes it possible to collect payments locally in markets where a company has no physical banking presence, and to know exactly which payment came from which counterparty without manually matching references afterwards.
What a Virtual IBAN Actually Is
A standard IBAN, International Bank Account Number, is the identifier tied to a specific bank account at a specific financial institution. It is unique, it routes payments, and it belongs to one account. Opening one requires a banking relationship in the relevant country, which typically means incorporation, documentation, and in some cases physical presence.
A virtual IBAN shares the structure and function of a standard IBAN; it passes validation checks, works in SEPA transfers, accepts SWIFT payments, and appears on invoices without raising any flags, but it sits in front of a master account rather than a standalone bank account. The payment institution that issues the virtual IBAN holds the underlying master account. The virtual IBAN routes inbound payments into that master account, tagged with the unique identifier, so the receiving company knows which virtual IBAN the payment came through.
The practical effect is that a company can issue a unique virtual IBAN to each counterparty, each supplier, each client, each subsidiary, and every inbound payment arrives pre-labelled with its origin. No reference codes to match, no manual reconciliation against bank statements. The routing does the identification work automatically.
How It Works in a Real Treasury Operation
A UK-based software company sells to enterprise clients across Europe and the US. Under a traditional model, collecting euro payments means either accepting SWIFT wires, slow, expensive for the sender, and difficult to reconcile, or maintaining a euro bank account in an EU jurisdiction, which requires a banking relationship the company may not have or want to maintain.
With virtual IBANs, the company issues each EU client a unique euro-denominated virtual IBAN. The client pays as if sending to a local European bank account, a SEPA transfer, in euros, with no cross-border wire fees. The payment arrives in the company's master account within the SEPA settlement window, tagged to the specific virtual IBAN the client paid into. The treasury team can see immediately which client paid, how much, and when, without touching a bank statement or matching a reference number.
The same model extends to US dollar collections through virtual account numbers, and to markets where local payment rails support equivalent functionality. The company collects locally in multiple currencies without maintaining local bank accounts in each market, and without asking international clients to absorb the cost and friction of sending a SWIFT wire.
Why Virtual IBANs Matter for Enterprise Collections
The reconciliation problem in enterprise treasury is underappreciated from the outside. A company receiving hundreds of inbound payments monthly, from clients in multiple countries, in multiple currencies, against multiple invoices, spends significant time matching what arrived to what was expected. Reference numbers get truncated in the SWIFT network. Payments arrive in amounts that don't correspond cleanly to a single invoice. Currencies convert at rates that produce rounding differences. The bank statement shows a credit. The accounts receivable ledger shows an open item. Connecting the two is manual work.
Virtual IBANs solve the identification problem structurally. Each counterparty has a unique inbound account number. Every payment that arrives is already attributed to a specific client before anyone looks at it. The reconciliation layer still needs to match amounts to invoices, but the hardest part, knowing who paid, is handled by the routing infrastructure itself.
For treasury teams processing high volumes of international collections, this is not a minor convenience. It is the difference between a reconciliation process that takes hours and one that is largely automated.
Beyond reconciliation, virtual IBANs also improve the client experience. Asking an international counterparty to send a SWIFT wire in a foreign currency is asking them to absorb fees, navigate correspondent banking complexity, and wait days for settlement. Giving them a local account number to pay into, in their own currency, through their own domestic payment infrastructure, removes all of that. The payment is easier to send. It arrives faster. It costs less. And it reconciles automatically on receipt.
The Compliance Layer Underneath
Virtual IBANs are issued by regulated payment institutions, EMIs in the UK and EU, and the compliance framework that governs them is the same one that governs any payment account. The institution issuing the virtual IBAN is responsible for KYC on the account holder, AML monitoring on inbound transactions, and sanctions screening on counterparties making payments into the account.
For enterprise clients, this means the compliance obligation sits with the platform rather than requiring the treasury team to build it independently. Each inbound payment is screened before it is credited. The transaction record is maintained by the issuing institution in accordance with regulatory record-keeping requirements. And the audit trail, which virtual IBAN received what, from whom, at what time, is available without needing to reconstruct it from multiple bank statements.
For regulated businesses whose own compliance teams need to sign off on collections infrastructure, this matters. The virtual IBAN isn't just an operational convenience; it is a compliant collection mechanism backed by a licensed institution's regulatory framework.
How Merge Uses Virtual IBANs
Merge issues virtual IBANs as part of its cross-border collections infrastructure, allowing enterprise clients and fintech builders to collect local currency payments in multiple markets without maintaining physical bank accounts in each jurisdiction. Merge handles the conversion from locally collected fiat into stablecoin for onward settlement, and Merge Reconcile maps each inbound payment, identified automatically by its virtual IBAN, to the corresponding receivable in the client's ledger.
FAQ
What is a virtual IBAN, and how is it different from a regular IBAN?
A virtual IBAN is a unique account number that routes inbound payments to a master account held by a payment institution, rather than a standalone bank account. It works identically to a standard IBAN for anyone sending money, passing validation, accepting SEPA and SWIFT transfers, but can be issued across jurisdictions without opening physical bank accounts in each one, and automatically identifies the source of every inbound payment by its unique routing number.
Why do companies use virtual IBANs for international collections?
Because they allow local currency collection in multiple markets without maintaining local bank accounts, and because each unique virtual IBAN identifies its counterparty automatically on receipt, eliminating the manual reconciliation work of matching inbound payments to invoices. They also remove friction for international clients, who pay into what appears to be a local account rather than sending an expensive cross-border wire.
Are virtual IBANs regulated the same way as real bank accounts?
Virtual IBANs are issued by regulated payment institutions, EMIs in the UK and EU, and are subject to the same KYC, AML, and sanctions screening obligations as any regulated payment account. Client funds received through virtual IBANs are safeguarded under the issuing institution's regulatory framework. They are not bank accounts in the deposit-taking sense, but they operate within an equivalent compliance structure for payment purposes.
