A virtual IBAN routes payments to a master account. Learn how vIBANs work, their use cases, and the FCA and EBA rules that apply to UK firms.

If you collect payments from many customers, you have probably wished every incoming transfer arrived with a clear label saying who sent it and what it was for. Virtual IBANs are one of the tools that try to solve this. They give each customer, invoice, or business unit its own account number, while the money all lands in a single underlying account you control.
The idea sounds simple, but the detail matters. A virtual IBAN is a real, valid IBAN in technical terms, yet it does not sit on top of a separate bank account the way a normal IBAN does. That difference shapes how reconciliation works, how funds are safeguarded, and how regulators view the arrangement.
This guide explains what a virtual IBAN is, how it maps to a master account, the main use cases, and the regulatory considerations that UK payment and e-money firms should keep in view. It draws on primary sources from the standards body behind IBANs, the European Banking Authority, and the Financial Conduct Authority.
An IBAN, or International Bank Account Number, is an internationally agreed way of identifying bank accounts across borders. It is defined by the standard ISO 13616, and SWIFT acts as the Registration Authority for that standard, publishing the registry of national IBAN formats.
An IBAN can be up to 34 alphanumeric characters. It always begins with a two letter country code, taken from the ISO 3166-1 alpha-2 list, followed by two check digits. Those check digits are calculated using the MOD 97-10 method from ISO/IEC 7064, which lets systems detect common errors such as a mistyped, omitted, or transposed character before a payment is sent.
After the country code and check digits comes the Basic Bank Account Number, or BBAN. The BBAN is country specific and can be up to 30 characters. It packages the domestic account details, which may include a bank identifier, a branch code, and the account number itself, into the format each national authority has defined. Each country fixes its own IBAN length, so a UK IBAN and a German IBAN differ in length but follow the same overall pattern.
Understanding this structure is the key to seeing what a virtual IBAN does and does not change. A virtual IBAN keeps the exact same anatomy. It still starts with a valid country code, still carries correct check digits, and still ends with a compliant BBAN. Nothing about the number itself tells a payer, or their bank, that it is virtual. The novelty lies entirely in how the receiving provider interprets and routes the identifier once a payment reaches it.
A virtual IBAN, often shortened to vIBAN, looks like a regular IBAN but does not represent its own payment account. Instead, as the European Banking Authority puts it, it is linked to a master payment account, which has a separate IBAN, and allows payments to be routed to that account.
In practice, a payment institution or e-money firm can generate many vIBANs and assign them to different customers, invoices, or purposes. All of these vIBANs point back to one underlying master account. When money arrives addressed to a vIBAN, the provider's systems recognise the identifier and credit the master account, while recording which vIBAN the payment came in on.
Because a vIBAN is still a structurally valid IBAN, it passes the same check digit validation as any other IBAN and can be used by a payer exactly like a normal account number. The payer usually has no way of knowing that the identifier is virtual. The difference is entirely on the receiving side, in how the provider maps the identifier to an account it controls.
The clearest way to understand a virtual IBAN is to compare it with a physical, or standard, IBAN. A physical IBAN is tied one to one with an actual account at the account servicing institution. A virtual IBAN is one of potentially many identifiers that all resolve to a single underlying account.
This has consequences beyond reconciliation. Ownership, the way client funds are protected, and even which rules apply can differ depending on whether the identifier is physical or virtual, and on how the arrangement is structured. The table below summarises the main contrasts.
| Feature | Physical IBAN | Virtual IBAN |
|---|---|---|
| Underlying account | Its own dedicated account | Points to a shared master account |
| Ownership | Held by the account holder | Master account held by the provider; end user is often not the master account holder |
| Typical use case | A single account for a person or business | Per customer, per invoice, or per unit collection and routing |
| Reconciliation | Payments matched by reference or manual review | Payments matched automatically by the vIBAN they arrive on |
| Safeguarding | Depends on the account holder's own arrangements | Provider must still safeguard relevant client funds under FCA rules |
The mapping between a vIBAN and its master account is the heart of the concept. Each vIBAN acts as an intermediary identifier. The provider maintains a lookup that connects every issued vIBAN to the single master account and to the customer or purpose it represents.
One point the European Banking Authority draws attention to is that a vIBAN and its master account do not have to share the same country code. A firm might issue vIBANs with one country's prefix while the master account sits in another country. That mismatch is useful commercially, because it can present a local looking account number to customers in several markets, but it also creates questions about how the payer's firm should report the transaction and which jurisdiction's rules apply.
This is why the mapping is not just a technical convenience. It determines where the money really sits, who legally holds it, and which authority supervises the arrangement. For a business choosing a provider, it is worth asking exactly where the master account is held, under whose authorisation, and how the provider keeps the vIBAN to customer mapping accurate over time.
It is also why the arrangement can look deceptively simple from the outside. A payer sees an ordinary account number and sends money in the usual way. Behind that number, though, the provider is running a lookup, crediting a shared account, and recording an attribution. If that lookup is wrong, or if the provider fails, the questions of who owns the funds and how they are protected become very real. Those questions are the reason regulators have taken an interest, which the next sections address.
Virtual IBANs earn their keep wherever a business needs to receive many payments and attribute each one accurately. The most common driver is reconciliation. When each customer or invoice has its own vIBAN, an incoming payment identifies itself automatically, so the finance team spends far less time matching bank credits to open items.
Collections and marketplaces are a natural fit. A marketplace can give each seller a dedicated vIBAN so that buyer payments are attributed to the right seller before being routed to the platform's master account. Subscription and lending businesses use the same pattern to track who has paid.
Per customer account experiences are another use. A business can offer each end customer what looks like their own account number without opening a separate bank account for every one of them. This scales far more cheaply than provisioning thousands of physical accounts, which is a large part of why virtual IBANs have become popular in modern payments platforms.
If your priority is faster, cleaner collections, our payments platform is built around exactly these reconciliation and routing patterns.
Illustrative view of typical drivers, based on the use cases described in this article. Not survey data.
The reconciliation benefit is worth spelling out because it is where most businesses see immediate value. Instead of trying to match a bank statement line to an invoice using a reference the payer may have typed incorrectly, you match on the vIBAN itself, which the payer cannot get wrong because it is the destination of the payment.
A typical flow looks like this.
Virtual IBANs are convenient, but they do not remove regulatory obligations. In May 2024 the European Banking Authority published its Report on virtual IBANs, reference EBA/Rep/2024/08, after finding that firms across the EU issue vIBANs in different ways and that national authorities interpret the rules differently. The report identifies issues across four areas: money laundering and terrorist financing, consumer and depositor protection, authorisation and passporting, and regulatory arbitrage.
Two themes stand out. First, attribution. Because many customers can sit behind one master account, and because a vIBAN can carry a different country code from that account, it can be harder to see who is really behind a transaction and which jurisdiction's anti money laundering rules apply. The EBA recommends clarifying how a payer's firm should report transactions to a vIBAN when it has a different country code to the master account.
Second, protection of the end user. The EBA notes that where end users are not the master account holders, they may not benefit from certain protections and may suffer detriment due to a lack of transparency, particularly around complaints procedures and deposit guarantee protection. That is a direct prompt to be clear with your own customers about how their funds are held.
For UK payment and e-money firms, safeguarding sits at the centre of this. The Payment Services Regulations 2017 and the Electronic Money Regulations 2011 require firms to protect relevant customer funds, under regulation 23 of the PSRs and regulation 20 of the EMRs, either by segregating those funds from the firm's own money or by covering them with an insurance policy or comparable guarantee. Detailed requirements sit in the FCA's Client Assets Sourcebook, at CASS chapters 10A and 15, and in the Supervision Manual. The FCA strengthened this regime, with new rules taking effect on 7 May 2026, so firms using virtual IBANs should confirm their safeguarding stands up under the current framework. If you want to talk this through, book a demo.
A virtual IBAN is a valid IBAN that does not carry its own account. It routes incoming payments to a master account and lets a business attribute each payment to a customer, invoice, or unit automatically. For reconciliation, collections, marketplaces, and per customer account experiences, that is a genuine operational gain, and it scales far more cheaply than opening a physical account for every customer.
The trade off is that the convenience sits on top of real obligations. Because many parties can share one master account, and because a vIBAN can carry a different country code from the account it points to, questions of attribution, jurisdiction, and fund protection become sharper rather than softer. The EBA's 2024 report and the FCA's safeguarding rules both make that clear. Choose a provider that is transparent about where the master account sits and how client money is safeguarded, and you get the benefits of virtual IBANs without losing sight of the responsibilities that come with them.
Yes, in technical terms. A virtual IBAN is structured like any other IBAN, with a country code, two check digits, and a Basic Bank Account Number, and it passes the same MOD 97-10 validation. The difference is that it does not represent its own account. As the European Banking Authority explains, it is linked to a master payment account with a separate IBAN and routes payments to that account.
A physical IBAN is tied to its own dedicated account. A virtual IBAN is one of potentially many identifiers that all resolve to a single underlying master account held by the provider. This affects ownership, reconciliation, and how funds are safeguarded, even though the two look identical to a payer.
The main use cases are automated reconciliation, collections, marketplaces, and giving each customer an individual account number without opening a separate bank account for every one. Assigning a unique vIBAN per customer or invoice means incoming payments identify themselves, which removes most manual matching.
No. UK payment and e-money firms must still protect relevant customer funds under the Payment Services Regulations 2017 and the Electronic Money Regulations 2011, either by segregating those funds or covering them with insurance or a comparable guarantee. The FCA sets out detailed rules in CASS and the Supervision Manual, and strengthened these rules with effect from 7 May 2026.
In May 2024 the European Banking Authority published a report, EBA/Rep/2024/08, finding that firms issue virtual IBANs in different ways and that national authorities interpret the rules differently. It identified issues around money laundering and terrorist financing, consumer and depositor protection, authorisation and passporting, and regulatory arbitrage, particularly where a vIBAN carries a different country code from its master account.
Yes. The EBA notes that a vIBAN and its master account do not have to share the same country code. This can be commercially useful for presenting a local looking account number in several markets, but it raises questions about transaction reporting and which jurisdiction's anti money laundering rules apply.
Nasara Pay helps UK firms send and control payments with lower fees, better rates and full visibility.
Practical guides and updates for UK firms, straight to your inbox.