Here is the problem virtual IBANs were invented for. A firm publishes one bank account and asks clients to write their account number in the payment reference. Some do. Some write their own name. Some write nothing. Some send from a company account with a different name entirely. At fifty deposits a week that is an annoyance handled by one person and a spreadsheet. At five hundred it becomes a queue, and every unmatched payment is a client waiting to trade with money the firm already holds.
A virtual IBAN, often written vIBAN, removes the reference from the equation. Each client gets their own IBAN. Money arriving on that IBAN can only have come from that client, so attribution happens on receipt with no text parsing at all.
What is actually happening at the bank
The vIBAN is a routable account identifier issued by a licensed institution, usually an electronic money institution or a bank with a virtual account product. It passes IBAN validation, it appears in the payment scheme as a normal beneficiary, and payments to it clear like any other credit transfer.
Behind the scenes it is generally a pointer. Funds settle into a physical account held by the issuing institution, and the vIBAN is recorded as the identifier the payment arrived on. Some products give the firm a real segregated ledger position per vIBAN, others give a reporting line only. That distinction is the first question to ask a provider, because it determines what happens if the institution fails, how the balance is treated for client fund segregation purposes, and whether the arrangement satisfies a regulator that expects client money in named accounts.
Why brokers and prop firms want them
The obvious win is reconciliation speed. Deposit is credited to the client record automatically, the trading account is funded, and nobody opens a bank statement. The less obvious wins matter as much.
Third party payment detection becomes easy. If a payment lands on Ana's vIBAN but the sender name on the transfer is a company nobody has documented, the mismatch is visible immediately rather than after the money has been traded. That is a direct AML control, and it is far harder to run when everything arrives in one pooled account with free text references.
Refunds and withdrawals get cleaner too. Sending funds back to the exact account they came from is the default policy in most compliance manuals, and a per client identifier makes the return path unambiguous. The mechanics of routing that back through the client record are covered in the deposit methods guide.
A vIBAN does not perform KYC. It tells you which client the money is attributed to, not whether that client is who they claim to be or whether the source of funds is acceptable.
Where vIBANs break
The most common failure is name matching. Payment schemes and national services increasingly check the beneficiary name a payer types against the name registered on the account. If a client's vIBAN is registered in the firm's name, the payer typing their own name gets a warning or a rejection. If the vIBAN is registered in the client's name, the sending bank may be satisfied while the receiving institution is not, because the client is not its customer. Providers handle this differently, and the answer determines what instruction text the firm shows on its deposit page.
The second failure is the country prefix. A German client asked to send euros to an IBAN starting LT or BE sometimes finds their bank's form rejecting it, or their payroll system refusing to store it. That behaviour is unlawful within SEPA and remains common anyway, which is the whole subject of IBAN discrimination. Firms serving several EU markets often solve it by holding local prefixes in the largest markets rather than arguing with sending banks.
The third is scheme coverage. A euro vIBAN reachable on SEPA credit transfer is not automatically reachable on SEPA instant, and a GBP virtual account may support Faster Payments but not CHAPS. Ask which schemes each identifier is addressable on, in both directions, before promising anything on the deposit page. The SEPA and SWIFT comparison covers what changes when a payment leaves the euro area entirely.
Buying the right product
Providers price vIBANs in a mix of monthly platform fee, per identifier fee and per transaction fee. The per identifier cost is the one that catches firms out, because the natural design is to issue an IBAN to every registered user, including the ones who never deposit. Issuing on first deposit intent, and recycling identifiers after a long dormancy, keeps that line sane.
The questions worth asking before signing anything: is the identifier permanent or per transaction, whose name is registered on it, which schemes it is reachable on, whether webhooks fire on credit, how returns and recalls are handled, and what the notice period is if the provider decides your sector is no longer within appetite. That last one is not theoretical, and the reasons behind it are set out in banking for trading firms.
On the software side, the value only materialises if the identifier is stored on the client record and the credit webhook posts straight into the ledger. A broker CRM that treats a vIBAN credit as a first class deposit event, with the sender name captured for review, converts the banking product into an actual reduction in manual work. Without that link the firm has simply bought a longer list of account numbers.
"The vIBAN is not the interesting part. The interesting part is that an unexpected sender name now lands in a review queue on the same day, instead of six weeks later in an audit."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- A vIBAN is a routable identifier that maps deposits to one client, usually settling into a single underlying account.
- Automatic attribution kills reference matching and makes third party payments visible on arrival.
- Name checking services and foreign country prefixes are the two failure modes that reject otherwise valid payments.
- Ask whose name is registered, which schemes are reachable, and whether the balance is a real ledger position or a reporting line.
Frequently Asked Questions
Is a virtual IBAN a real bank account?
It is a real routable IBAN, but usually not a separate account. Funds credited to a vIBAN settle into an underlying account held by the provider or the firm, with the vIBAN acting as the identifier that says who the money came from.
Can each client keep their own virtual IBAN permanently?
Most providers allow a vIBAN to be assigned to one client for the life of the relationship, which is what makes reconciliation automatic. Some issue them per transaction instead, so confirm the model before designing the deposit flow.
Why do some banks reject payments to a virtual IBAN?
Two common reasons. The sending bank blocks a country prefix that does not match the beneficiary's stated country, which is the IBAN discrimination problem, or a name checking service flags a mismatch between the account holder name on the vIBAN and the name the payer typed.