Virtual IBAN vs Virtual Bank Account: Key Differences
Understand the difference between virtual IBANs and virtual bank accounts — how they work, use cases, issuer requirements, compliance, and product design implications.
A virtual IBAN (International Bank Account Number) is a unique account identifier formatted to the IBAN standard, mapped to a real bank account behind it. Incoming transfers to the virtual IBAN are routed to the master account and matched by the virtual IBAN reference. A virtual bank account is a broader term for a ledger account that represents a balance for a user or entity within a platform — it may or may not be backed by a real bank account or IBAN.
The terms "virtual IBAN" and "virtual bank account" are often used interchangeably, but they describe different things. Understanding the distinction matters for product design, compliance, and what your banking partner actually provides.
What is a Virtual IBAN?
A virtual IBAN is an IBAN-formatted account number that points to a specific physical bank account (the "master account"), but routes incoming transfers to a sub-account or reconciliation reference within that master account. The virtual IBAN follows the standard IBAN format (e.g. GB29 NWBK 6016 1331 9268 19) and can be used on any payment form that accepts IBANs.
When a payer sends a SEPA Credit Transfer or other bank transfer to the virtual IBAN, the payment is received into the master account. The bank's system uses the IBAN to identify which customer or ledger account should be credited. From the payer's perspective, it looks like a normal bank transfer.
What Virtual IBANs Are Used For
- Marketplace seller accounts — each seller gets a unique virtual IBAN for receiving buyer payments
- B2B invoice payment matching — each invoice has a virtual IBAN; payment identifies the invoice automatically
- Escrow and trust structures — funds are received into a pooled master account, tracked per virtual IBAN
- Multi-tenant SaaS — each tenant receives payments via their own virtual IBAN within a shared bank account
- International payment collection — virtual IBANs in multiple countries collect local payments from different regions
How Virtual IBANs Work Technically
The banking partner issues a range of IBAN numbers that all route to the master account. The platform assigns one virtual IBAN per user or entity via API. When a transfer arrives, the bank's reconciliation system fires a webhook to the platform with the matched virtual IBAN. The platform credits the corresponding user ledger.
What is a Virtual Bank Account?
A virtual bank account is a broader concept — it is a ledger account within a platform that represents a balance for a user. It may be backed by a virtual IBAN (for bank transfer acceptance), a different account reference, or simply be a platform-internal ledger with no direct bank account equivalent.
In many fintech products, "virtual bank account" describes the full account experience: a balance, a payment reference or IBAN, transaction history, and outbound payment capability. The "virtual" in this context means the account exists in software and is not a traditional bank passbook account — even if it is backed by real banking infrastructure.
Types of Virtual Bank Accounts
- Virtual IBAN-backed account — a ledger account with a unique IBAN for receiving SEPA/SWIFT transfers
- Virtual account number-backed — a unique sort code and account number (UK), routing/account number (US), or equivalent for local markets
- Platform-internal ledger only — balance exists only in the platform ledger; no external payment address
- E-money account — regulated e-money institution issues payment accounts with real account numbers and IBAN
Virtual IBAN vs Virtual Bank Account: Key Differences
A virtual bank account in a fintech product often includes a virtual IBAN as one of its components — along with a balance ledger, transaction history, and outbound payment functionality.
| Dimension | Virtual IBAN | Virtual Bank Account |
|---|---|---|
| Scope | A specific account identifier (the IBAN number) | A full account concept (balance, history, payments in/out) |
| Standard | Formatted to ISO 13616 IBAN standard | No specific format standard; platform-defined |
| Geography | Primarily European (SEPA); also used in MENA and some Asian markets | Any market; format matches local banking standards |
| Backed by | Master bank account at a regulated institution | May be backed by a bank account, or purely a ledger entry |
| Regulation | Provided by a regulated bank or e-money institution | Depends on the platform structure and jurisdiction |
| Outbound payments | Virtual IBANs are receive-only references | Accounts can support outbound payments if the platform provides this |
| Use in product | Used as payment instruction for receiving transfers | Used as a full account experience in-product |
Provider and Regulatory Requirements
Virtual IBANs are issued by regulated entities — typically banks with BIC/SWIFT codes, or e-money institutions authorized to issue IBANs in their jurisdiction. To offer virtual IBANs to end users, you need a banking partner that provides virtual IBAN issuance via API.
Common providers: Banking Circle, ClearBank, Modulr, Railsr (formerly Railsbank), Currencycloud, and regional bank partners. The platform integrates via API to provision accounts, receive payment webhooks, and initiate outbound transfers.
Who Needs a License?
If the platform holds client funds (customer balances) and provides payment services to third parties, this typically constitutes e-money or payment institution activity requiring authorization in most jurisdictions (FCA in UK, national regulator in EU member states under PSD2/EMD2).
The platform can often operate under the banking partner's regulatory umbrella as a technical provider rather than a regulated entity — but this depends on the exact product structure and geography. Legal advice is required to determine the applicable regulatory framework.
Product Design Implications
When designing a virtual account product, key decisions include:
Account model: Is each user assigned one account or can they have multiple (e.g. one per currency)? Does the account persist long-term or is it payment-specific?
Balance model: Does the platform hold balances in the banking partner's ledger, or is there an internal platform ledger with the banking partner used only for settlement?
Outbound payments: Can users initiate payments from their virtual account? What limits and approval flows apply?
Multi-currency: Does each currency need a separate virtual IBAN? Some providers issue multi-currency IBANs; others require separate accounts per currency.
Compliance: KYC for the account holder before a virtual IBAN is assigned. Transaction monitoring on received and outbound payments.
FAQ
Can a virtual IBAN receive payments from any country?
How are virtual IBANs provisioned in a product?
What is the difference between a virtual account and an e-money account?
Can Gizmolab build a virtual IBAN product?
Building a Virtual Account or IBAN Product?
Gizmolab builds virtual account platforms with virtual IBAN integration, balance management, and payment reconciliation for fintechs and marketplaces.