Virtual Account
A virtual account is an account number — an IBAN, a local account number — that holds no funds itself but routes payments into one real account while identifying who paid and for what, so a company can give each customer, invoice or subsidiary its own number and reconcile automatically. Fintechs use virtual IBANs to collect, to offer local account details abroad and to run multi-currency treasury; regulators watch who is behind each number.
- Also known as
- Virtual IBAN, vIBAN, Virtual account number, Reference account
- Used at
- collections and reconciliation (each payer's transfers arrive tagged by their virtual account), marketplaces and PSPs (a vIBAN per merchant), fintechs offering "local accounts" in many countries, corporate treasury (virtual accounts per subsidiary under one physical account), and neobanks and e-money institutions issuing IBANs to customers on a partner bank's rails
- Binding
- banking and payments regulation on who may issue account numbers and in whose name; AML rules on knowing the beneficial owner behind each virtual account; scheme and correspondent-bank policies, which have tightened on vIBANs since 2020 because of misuse; in the EU, the 2024 AML package and payment-system rules address them explicitly
- Typical mechanics
- the bank or e-money institution holds one physical account and issues virtual numbers from its range; an incoming transfer to a virtual number is credited to the physical account and tagged; the issuer's ledger allocates it to the customer
- Typical risks
- a payment to a vIBAN in a country different from the issuer's regulator ("IBAN discrimination" cases and sanctions-screening blind spots), correspondent banks refusing traffic to virtual ranges, and fraudsters using vIBANs to receive proceeds under a plausible local number
- Parties
- the issuing bank or institution, the fintech or corporate using the numbers, the payers, the correspondent and receiving banks, and the regulators and screening systems that must see through the number to the owner
How a virtual account works in practice
A B2B platform collects payments from 5,000 customers by bank transfer into one account, and its finance team spends two days a week matching transfers to invoices by amount and reference — half of which are wrong. It obtains virtual IBANs from its bank: each customer is given its own IBAN; all route into the platform's real account; every incoming transfer arrives with the customer's identity built into the account number. Reconciliation becomes automatic; the two days become an exception queue of twenty items a week. The same mechanism, run by an e-money institution, gives each of its customers an IBAN in the institution's country, on the institution's partner bank's rails, so the customer can receive salary and pay bills without the institution being a bank.
The regulatory attention is about visibility. A payment to a virtual IBAN looks, to the sending bank and to the sanctions screen, like a payment to the issuing institution in its country — not to the fintech's customer, who may be anywhere. Correspondent banks have cut off vIBAN ranges they could not see through; regulators have required that the ultimate holder be identifiable and that screening apply to them; and the EU's 2024 AML rules require issuers to be able to identify the holder of every virtual account on request. A fintech built on vIBANs from a partner bank is built on that bank's willingness to keep issuing them.
For a buyer of a fintech whose product is "a local account in twelve countries", the diligence is which bank issues each range, on what terms, and how the fintech identifies the holder behind each number.
Example
A payments fintech gives its 40,000 SME customers vIBANs in three countries through two partner banks, and runs collections for marketplaces through them: €2bn a year. One partner bank's correspondent, screening a spike of incoming transfers from a high-risk jurisdiction to the range, asks the bank to explain the beneficial owners behind 300 vIBANs; the bank asks the fintech, which produces KYB files for 290 in two days and closes the other 10. The correspondent keeps the range. A competitor, asked the same question by another bank, cannot map its virtual numbers to customers in under a week; the bank withdraws the range, and 12,000 of its customers lose their account details with thirty days' notice. The first fintech is later bought for its two bank relationships and its ledger; the second is bought for its customer list.
Common mistakes
- Issuing virtual accounts without a ledger that maps every number to a verified holder in seconds. - Treating a vIBAN as a bank account; it is a routing label on someone else's account. - Screening incoming payments at the physical-account level and missing the virtual holder. - One partner bank's range as the whole product. - Assuming payers' banks will accept a vIBAN in a country where the payer's regulator has seen misuse.