---
title: "Virtual account vs virtual IBAN vs real bank account: what's the difference?"
seoTitle: "Virtual account vs virtual IBAN vs bank account"
description: "A real account holds funds for one holder. A virtual account routes deposits into a master account. A virtual IBAN is the IBAN version. When to use each."
date: "2026-08-04"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "Is a virtual IBAN the same as a virtual account?"
    a: "A virtual IBAN is one kind of virtual account. Both are unique receiving details that route into a master account and identify who a deposit belongs to. A virtual IBAN uses the IBAN format and mostly receives SEPA and other IBAN-based transfers. A US virtual account uses a routing and account number and receives ACH, wire, and sometimes SWIFT."
  - q: "Are funds in a virtual account protected?"
    a: "It depends on the structure behind it, not on the word virtual. The money sits in a master account at a bank or licensed payment institution, and protection depends on how that account is titled and what records the provider keeps. Ask the provider in writing who holds the funds, in whose name, and what happens if the provider fails. Stablecoins are not bank deposits."
  - q: "Can virtual accounts receive international payments?"
    a: "Some can. It depends on the rails the account supports. A US virtual account that accepts SWIFT can receive wires from foreign banks, and a virtual IBAN can receive SEPA transfers from anywhere in the SEPA zone. Before telling a foreign payer how to pay, confirm the account supports their rail and that the beneficiary name matches what they expect."
  - q: "Do virtual accounts have their own balance?"
    a: "Not at the bank. The bank sees one master account with one balance. The provider's ledger tracks how much of it belongs to each virtual account. Some providers show that per-account balance in their API; others sweep each deposit onward, for example converting it into a stablecoin and sending it to a linked wallet, so there is no balance to show."
  - q: "What is an omnibus account?"
    a: "An omnibus account is a single bank account that holds funds belonging to many customers, titled to the provider or to the provider for the benefit of its customers (an FBO account). Pooled virtual accounts usually route into one. The provider's ledger, not the bank, records which customer owns which part of the balance."
---

A real bank account is opened by a bank for one account holder and holds its own balance. A virtual account is a unique set of receiving details that routes deposits into a master account and identifies who they belong to. A virtual IBAN is a virtual account in IBAN format, used mainly for SEPA and other IBAN-based transfers.

Same goal, different plumbing. The one that fits depends on who pays you, over which rail, and whose name needs to be on the account.

## Key takeaways

- Only a real bank account holds its own balance at the bank. Virtual accounts and virtual IBANs route into a master account.
- A virtual IBAN is a virtual account with an IBAN. The difference is format and rails, not concept.
- Named accounts carry your customer's name. Pooled accounts carry the provider's. That choice drives what the payer sees and what compliance asks for.
- Terminology varies by provider and country. Ask what the product actually does, not what it's called.

## What is the difference at a glance?

The three differ in who holds the funds, whose name is on them, and how they're issued.

| | Real bank account | Virtual account | Virtual IBAN |
| --- | --- | --- | --- |
| Holds funds | Yes, its own balance at the bank | No, routes into a master account | No, routes into a master account |
| Account holder name | The account holder | The provider (pooled) or the end customer (named) | The provider (pooled) or the end customer (named) |
| How it's issued | Bank application and onboarding, one at a time | API call from a provider | API call from a bank or licensed payment institution |
| Identifier | Account number (plus routing number, or an IBAN) | Account number plus routing number (US), or local equivalent | IBAN: country code, check digits, bank and account identifier |
| Typical rails | Everything the bank offers | ACH and wire in the US, sometimes SWIFT | SEPA, domestic IBAN rails, SWIFT |
| Reconciliation | By reference or amount | By the receiving account number | By the receiving IBAN |
| Best for | Operating cash, treasury, full banking | High-volume collections, per-customer attribution | Collecting euros and other IBAN currencies at scale |

## What is a real bank account?

A real bank account is an account a bank opens for a specific account holder, after its own KYC or KYB, with its own balance on the bank's books. The holder can usually send and receive payments, get statements, and access every service the bank offers.

The trade-off is scale. Opening one is slow and manual. Opening 10,000 of them, one per customer, isn't realistic for most businesses.

## What is a virtual account?

A virtual account is an identifier, usually an account number and routing number in the US, that routes incoming payments into a master account while telling the provider exactly who the payment is for. Payers send to it like any account. The provider's ledger records which customer each deposit belongs to.

The full breakdown of how the routing and matching work is in [what is a virtual account](/resources/more/what-is-a-virtual-account).

## What is a virtual IBAN?

A virtual IBAN (vIBAN) is an International Bank Account Number that routes into a master account instead of standing as its own account. It has the same structure as any IBAN: a two-letter country code, two check digits, and the bank and account identifier, up to 34 characters in total, following the format [Swift publishes in the IBAN registry](https://www.swift.com/standards/data-standards/iban-international-bank-account-number).

Because the country code comes from the issuing bank, a business can collect euros on, say, a Lithuanian or Irish IBAN while being based elsewhere. Inside the euro area, [EU Regulation 260/2012](https://eur-lex.europa.eu/eli/reg/2012/260/oj) prohibits payers from refusing to pay an account because of the country it's held in. In practice some companies still reject foreign IBANs, so ask your payers before assuming it's a non-issue.

## Named vs pooled virtual accounts: why does the name matter?

A named virtual account is titled to your end customer, so the payer sees your customer as the beneficiary. A pooled virtual account sits under an account in the provider's name, often an omnibus or "for benefit of" (FBO) account, so the payer sees the provider.

The name matters for two reasons:

- **The sender experience.** Payers increasingly get a name check before they send. In the euro area, payment providers must verify that the payee's name matches the IBAN for SEPA credit transfers, a requirement introduced by the [Instant Payments Regulation](https://eur-lex.europa.eu/eli/reg/2024/886/oj). The UK runs Confirmation of Payee. A pooled account in the provider's name can trigger a "name doesn't match" warning when the payer typed your customer's name, and a scared payer doesn't send.
- **Compliance.** Regulators want to know whose money it is. With a named account, the account title answers that. With a pooled account, the provider's ledger has to prove, deposit by deposit, which customer owns what. Both are legitimate. Pooled just puts more weight on the provider's records.

| | Named virtual account | Pooled virtual account |
| --- | --- | --- |
| Beneficiary the payer sees | Your customer | The provider |
| Payee name checks | Usually match | May show a mismatch |
| Who proves ownership of funds | The account title, plus the ledger | The provider's ledger |
| Typical setup time | Longer: compliance and bank review | Shorter: often instant |
| Outgoing payments from the account | Can go out under the customer's name | Go out under the provider's name |

## Does the terminology mean the same thing everywhere?

No, and it's worth being honest about. "Virtual account" in one provider's docs can mean a ledger-only sub-account with no external details. In another it means a fully named account with its own routing number. Some banks call vIBANs "dedicated IBANs" or "named IBANs." In some countries, "virtual account" is the common name for bank collection references that aren't accounts at all.

Three questions cut through it:

1. Can a payer outside the provider send money directly to it?
2. Whose name will the payer see as the beneficiary?
3. Where does the money actually sit, and in whose name?

If the answers are "yes, my customer's, a regulated bank," you have a named virtual account, whatever the page calls it.

## When should you choose each?

Choose by who pays you, how many payers there are, and whose name the payer needs to see.

- **Choose a real bank account if** you need full banking for your own company: operating cash, treasury, payroll out, a relationship with a bank. You won't need thousands of them.
- **Choose a virtual account if** you receive many payments from many payers in the US, need each one attributed without reading references, and want accounts issued by API as customers sign up.
- **Choose a virtual IBAN if** your payers are mostly in the SEPA zone or other IBAN countries and pay in euros or another IBAN currency.
- **Choose named over pooled if** payers are businesses that run payee name checks, if outgoing payments must show your customer's name, or if your compliance team wants the account title to prove ownership.
- **Choose pooled over named if** you need accounts instantly, payers are consumers who won't be confused by a provider name, and you trust the provider's ledger.

## How does BlindPay handle virtual accounts?

[BlindPay virtual accounts](/virtual-accounts) are named US accounts. Each one is issued in a single customer's name, with its own routing and account number, and receives ACH, wire, and SWIFT depending on the account type. Deposits convert automatically to USDC or USDT and settle to one blockchain wallet.

A few specifics from the [virtual accounts docs](/docs/virtual-accounts):

- **One customer per account.** Each account belongs to one onboarded customer who has passed KYC or KYB.
- **Several accounts per customer.** A customer can hold more than one to separate funds by purpose, with one active account per banking partner for most partners.
- **Named payouts.** Payouts that originate from the account go out under the end customer's name, not a pooled name.
- **Reviewed, not instant.** Production accounts go through compliance review and bank review, with SLAs of 24 hours or 3 to 5 business days depending on the account type. Development accounts are approved instantly.

BlindPay's virtual accounts use US routing and account numbers, not IBANs. For euros, BlindPay pays out over SEPA rather than collecting on virtual IBANs.

If you're new to how the stablecoin side works, [stablecoin virtual accounts explained](/resources/more/stablecoin-virtual-accounts-explained) walks through approval, deposits, and settlement.

## What to do next

List your top 20 payers and write down three things for each: their country, the rail they'd use, and whether their bank checks payee names. If most are US businesses on ACH or wire, you want named US virtual accounts. If most are in the SEPA zone, you want virtual IBANs. Then create a test account on a free BlindPay development instance with [create a virtual account](/docs/virtual-accounts-create) and see what your payers would see.

*This article is for general information only and is not legal, tax, or financial advice.*