At a glance
A virtual IBAN (vIBAN) is an IBAN-format account number that routes incoming payments to an underlying account, so a platform can give every client its own number without opening a separate bank account for each. Payers see a normal IBAN. The provider uses the number to attribute each payment to the right client.
Key distinction: what sits behind the number decides how client funds are protected. A pooled vIBAN points to a master account in the platform's or provider's name, with ownership tracked in a ledger. A named vIBAN maps to an account in the client's own name.
Virtual IBANs are now standard infrastructure for payment service providers, marketplaces, payroll platforms and FX businesses that collect money from many payers. Regulators have noticed. In May 2024 the European Banking Authority reported that national authorities apply the rules on vIBANs differently, and that the full extent of vIBAN issuance in the EU is not known.
What is a virtual IBAN?
An IBAN (International Bank Account Number) is the standard format for identifying an account across borders. It starts with a two-letter country code and two check digits, followed by a country-specific account number, up to 34 characters. A UK IBAN has 22; a Dutch one has 18.
A virtual IBAN uses the same format and passes the same validation checks. The difference is what happens after a payment arrives. A standard IBAN identifies one account. A virtual IBAN is a routing identifier: payments sent to it are redirected to another account that carries its own IBAN. The EU's Anti-Money Laundering Regulation defines it in almost exactly those terms.
A simple example: a marketplace with 10,000 sellers issues each seller a unique vIBAN through an API. Buyers pay the seller's number. Every payment lands in accounts the marketplace controls, already tagged to the right seller, without 10,000 bank account openings.
Why virtual IBANs exist
Virtual IBANs solve operational problems that every platform collecting money at scale runs into:
- Reconciliation. Matching thousands of transfers by the free-text reference field is slow and error-prone, because payers mistype references or leave them blank. A unique number per client makes the number itself the reference.
- Local collection. A platform can collect EUR over SEPA or GBP over Faster Payments with local account details, so payers avoid international transfer fees and delays.
- Speed of issuance. Opening a real bank account per client means onboarding and paperwork at the bank. Issuing a vIBAN is an API call.
- Visibility by client. Each client's inflows are identifiable from the moment they arrive, which supports safeguarding and client money reporting.
These benefits explain why vIBANs spread quickly through PSPs, e-money institutions and marketplaces. They also explain the regulatory attention: a structure built for routing can obscure who the end client actually is.
How a virtual IBAN works
A payment to a virtual IBAN passes through five steps:
- Issuance. The provider assigns a vIBAN to the platform's client and records which underlying account it routes to.
- Payment. The payer sends a transfer to the vIBAN over the relevant scheme, such as SEPA, SEPA Instant or Faster Payments.
- Name check. Before the payment leaves, the payer's bank checks the payee name against the number. In the euro area, Verification of Payee has been mandatory since 9 October 2025. In the UK, Confirmation of Payee covers over 99% of Faster Payments, Bacs and CHAPS.
- Routing. The payment settles into the underlying account the vIBAN points to.
- Attribution. The provider, or the platform's ledger, records the payment against the client the vIBAN belongs to.
Step 3 is where the structure behind the number becomes visible to payers. If the vIBAN is registered to the platform or provider, a payer who enters the client's name can see a partial match or no match, and may stop the payment. If the vIBAN is held in the client's own name, the check returns a match.
Step 5 is where protection is decided. In a pooled model, the only record of which client owns which funds is a ledger, while the account itself belongs to someone else. In a named model, the account and the client are the same. The wider trade-off is covered in pooled accounts and the US equivalent, the FBO account.
Virtual IBAN vs IBAN vs named account
| Dimension | Standard IBAN | Pooled virtual IBAN | Named virtual IBAN |
|---|---|---|---|
| Whose name is on the account | The account holder | The platform or provider | The end client |
| Where funds sit | In that account | In a master account, attributed by ledger | In an account mapped to that client |
| Name check result | Match | Can return a partial or no match | Match |
| Opening at scale | Slow, one account at a time | Instant by API | Instant by API |
| Attribution if a provider fails | Direct | Depends on ledger quality | Direct |
| Typical use | Corporate and retail accounts | High-volume collections | Client money programmes, marketplaces, payroll |
The format is identical in all three columns. What differs is the legal and operational structure behind the number, and that is what a regulator, an auditor and an insolvency practitioner examine first.
Where pooled virtual IBANs fall short
Pooled vIBANs work well for collections where the platform is the true owner of the funds. The limits appear when the money belongs to someone else:
- Attribution depends on a ledger. If the ledger and the master account balance diverge, clients cannot prove what they own. Reconciliation becomes the control that everything rests on.
- Counterparty risk concentrates. Client funds sit behind one provider's licence, and that provider often reaches local rails through nested correspondent relationships of its own.
- End clients can be invisible. The EBA found that vIBAN users may be unknown to the payment service providers in the chain. From July 2027, the EU's new AML rules require institutions to identify the people using a vIBAN, and national account registers will record vIBANs alongside their underlying accounts.
- Safeguarding rules are tightening. The UK's CASS 15 regime requires daily reconciliation of safeguarded funds, and PSD3 moves the EU toward strict segregation at receipt.
None of this makes virtual IBANs the wrong tool. It makes the account structure behind them the decision that matters, especially for platforms holding client money.
From reference numbers to named accounts
Virtual IBANs solved the first problem platforms faced: reconciling payments at scale. The next problem is proving, continuously, whose money is whose. That depends on what the number points to. A vIBAN that maps to an account in the client's name passes name checks cleanly, keeps attribution out of a single ledger, and turns a safeguarding audit into a check of account structures.
Lorum issues named virtual IBANs that receive USD, EUR, GBP and AED, each mapped to a specific account within an account hierarchy the platform designs. Lorum is the correspondent institution for banks and fintechs, providing access to global clearing, named accounts, and treasury, on a non-lending, 100% reserve model.
For platforms comparing providers, the guide to virtual IBAN providers sets out the main options, and the fintech and PSP page shows how the account structure fits a payments business.
Frequently asked questions
Is a virtual IBAN a real IBAN?
Yes. A virtual IBAN uses the standard IBAN format and passes the same validation checks, so payers can send SEPA, SEPA Instant or Faster Payments transfers to it like any other IBAN. The difference is that it routes payments to an underlying account rather than identifying a standalone account.
What is the difference between a virtual IBAN and an IBAN?
A standard IBAN identifies one account held in one name. A virtual IBAN is an identifier that redirects payments to another account with its own IBAN, which lets a platform give each client a unique number without opening a separate account for each.
Who uses virtual IBANs?
Payment service providers, e-money institutions, marketplaces, payroll and employer-of-record platforms, FX businesses and trading platforms use virtual IBANs. They suit any business that collects payments from many payers and needs to attribute each payment to a specific client automatically.
Are virtual IBANs safe for client funds?
It depends on the structure behind them. With pooled vIBANs, client ownership is recorded in a ledger while funds sit in a master account in another name. With named vIBANs, each number maps to an account in the client's own name, which makes attribution direct and name checks return a match.
How much does a virtual IBAN cost?
Pricing varies by provider. Common models combine a fee per active vIBAN, fees on inbound payments, and a platform fee tied to volume. Compare the total against the reconciliation work it removes and the account structure it gives your clients.
