# Virtual IBAN (vIBAN) EBA Rules, AML & Pooled Safeguarding

> Structure compliant Virtual IBAN (vIBAN) issuance for EMIs and BaaS platforms: EBA 2024 vIBAN report risks, AMLA cross-border country prefixes, and SEPA Art 9.

Canonical: https://payclearledger.com/rails/virtual-iban-viban-master-pooled-safeguarding-aml-supervision
Last updated: 2026-11-14T19:39:47.187Z

**Publication:** PayClear Ledger
**Category:** Emi Safeguarding Psd2 Psr Accounts
**Published:** 2026-11-14T05:50:25.915Z
**Author:** Claire Beaumont, CAMS, CTP (Certified Anti-Money Laundering Specialist (CAMS), Certified Treasury Professional (CTP))
**Reviewer:** Not recorded

## Answer-first summary

Virtual IBAN (vIBAN) routing engines map thousands of client-unique IBANs onto master pooled safeguarding accounts, triggering strict EBA AML transparency and reconciliation rules.

## Key takeaways

- Virtual IBANs (vIBANs) are programmatic routing numbers mapped onto a Master Pooled Safeguarding Account, eliminating 96%+ of missing-reference suspense breaks vs shared reference IBANs.
- Following the May 2024 EBA vIBAN Report and EU AMLR (2024/1624), issuers and partner banks must link every active vIBAN’s verified end-user identity into centralized national Bank Account Registers (BARs).
- Multi-tier "daisy-chained" vIBAN reselling across nested sub-aggregators without transparent KYCC visibility to the account-holding bank is strictly prohibited across UK and EU supervision.
- Under EPC SEPA Verification of Payee (VoP), vIBAN responders must verify the underlying client’s legal/trading name rather than returning the EMI’s pooled corporate title.

## Related financial entities

- **ISO 20022 pacs.008 Customer Credit Transfer Standard** (PACS-008) — product: Universal financial industry message scheme defining XML data structures for executing customer credit transfers across commercial banks, RTGS networks, and payment systems.
- **Payment Services Directive 3 & PSR Framework** (PSD3-PSR) — license: Comprehensive legislative overhaul of the EU payment services regime separating supervisory licensing rules (PSD3) from directly applicable conduct rules (PSR).
- **Virtual IBAN (vIBAN) Multi-Currency Routing Engine** (VIBAN-SYS) — product: Routing technology that maps dynamically generated individual International Bank Account Numbers to a master pooled safeguarding account.

## Analysis

Modern cross-border B2B platforms, embedded Banking-as-a-Service (`BaaS`) providers, and multi-currency Electronic Money Institutions rely on a [Virtual IBAN (`vIBAN`) routing engine](/corridors/virtual-iban-routing-engine) to issue programmatic `GB`, `DE`, `FR`, `NL`, `IE`, or `LT` collection identifiers that route seamlessly onto a single master pooled safeguarding account (`Master IBAN`). Following the **European Banking Authority (`EBA`) May 2024 Report on Virtual IBANs (`EBA/Rep/2024/08`)** and new EU Anti-Money Laundering Regulation (`AMLR` `2024/1624`) Article 22 mandates, issuers and partner banks must eliminate cross-border supervisory blind spots, report vIBAN-to-master mappings to national central bank Account Registers (`BARs`), and prevent nested sub-ledger commingling.

## Technical Architecture: How vIBANs Map to Master Pooled Safeguarding IBANs

Unlike a physical statutory payment account holding an individual general-ledger row inside a clearing bank’s core mainframe, a **Virtual IBAN** is a routing reference derived from an allocated BIC/bank-code range (`e.g., DE89 3704 ...` at [Deutsche Bank AG](/remitters/deutsche-bank-ag) or `GB29 BARC ...` at [Barclays](/remitters/barclays)). When an external payer sends a SEPA Credit Transfer or SWIFT `pacs.008` wire to `vIBAN #40892`, the clearing bank credits the EMI’s **Master Pooled Safeguarding Account** while passing `vIBAN #40892` untouched inside `<CdtrAcct><Id><IBAN>` of the real-time `camt.054` notification.

Within milliseconds, the EMI’s core ledger parses the inbound `camt.054`, attributes the exact credit to sub-customer `#40892`, and updates its Relevant Funds Requirement (`RFR`) ahead of next-morning [D+1 internal and external safeguarding reconciliations](/rails/daily-internal-external-safeguarding-reconciliation-d-plus-one)—anchored to our [UK & EU EMI safeguarding and PSD3/PSR guide](/rails/uk-eu-emi-safeguarding-segregated-accounts-psd3-psr-guide).

## Fighting SEPA Article 9 IBAN Discrimination vs Cross-Border AML Blind Spots

Why did Lithuanian, Irish, and Dutch EMIs ask German, French, and Spanish partner banks to issue local `DE`, `FR`, and `ES` vIBANs? Primarily to bypass illegal **IBAN Discrimination**—where legacy utility, tax, and payroll portals violated Article 9 of the SEPA Regulation (`260/2012`) by rejecting non-domestic `LT` or `IE` IBANs! However, the EBA’s 2024 investigation exposed a severe supervisory gap: when a Lithuanian EMI issued a `DE` vIBAN backed by a pooled Master IBAN in Frankfurt to an Italian corporate, German FIU queries against the BaFin central account register saw only the EMI’s name on the Master IBAN, while Lithuania’s FIU had no automatic visibility into the `DE` prefix.

Under **EU AMLR (`Regulation 2024/1624`)**, any credit or financial institution issuing vIBANs MUST obtain and verify the identity of the natural or legal end-user of every vIBAN and feed real-time end-user identity + Master IBAN linkage into centralized national **Bank Account Registers (`BARs`)** within 5 working days.

![Compliant Virtual IBAN routing, Master Pooled Safeguarding Account settlement, and EU BAR AML reporting flow](/api/figure?type=flow&title=EU%2FUK%20Compliant%20vIBAN%20Routing%20%26%20BAR%20Reporting%20Flow&subtitle=Sub-second%20camt.054%20attribution%2C%20SEPA%20VoP%20end-user%20matching%2C%20and%20Central%20Register%20sync&steps=1.%20Onboard%20%26%20Sync%20BAR%3A%3AComplete%20KYB%2FKYC%3B%20push%20vIBAN%20-%3E%20End-User%20ID%20to%20national%20BAR%7C2.%20Expose%20VoP%20Responder%3A%3AReturn%20end-merchant%20legal%20name%20%28not%20EMI%20pool%29%20on%20VoP%20check%7C3.%20Settle%20Master%20Pool%3A%3AReceive%20cash%20in%20acknowledged%20DRFBA%3B%20parse%20vIBAN%20in%20camt.054%7C4.%20Credit%20Wallet%20%26%20D%2B1%3A%3AUpdate%20client%20e-money%20sub-ledger%20%26%20verify%20100%25%20RFR%20coverage&metrics=EBA%20Benchmark%3A%3ARep%2F2024%2F08%3A%3A12%20supervisory%20risk%20controls%7CBAR%20Upload%20SLA%3A%3AReal-Time%20%2F%20%3C5d%3A%3AEU%20AMLR%20Art%2022%20register%7CDaisy-Chaining%3A%3AProhibited%3A%3AMax%201-hop%20KYCC%20visibility%7CAuto%20Attribution%3A%3A99.7%25%3A%3AEliminates%20missing-ref%20cash)

## Banning Unlicensed "vIBAN Reselling" (Daisy-Chaining / Nested BaaS)

The #1 enforcement trigger flagged in `EBA/Rep/2024/08` is **multi-tier vIBAN daisy-chaining**: Bank A issues a vIBAN block to EMI B, EMI B allocates a sub-range to Foreign MSB C, and MSB C hands individual vIBANs to end-merchants D without Bank A knowing D exists! Both the FCA and EU supervisors (`BaFin`, `ACPR`, [Central Bank of Ireland](/licensing/cbi)) treat unapproved multi-hop vIBAN nesting as a critical AML and safeguarding violation.

Compliant BaaS contracts enforce **1-Hop End-User KYC Parity**, programmatic API sync of Ultimate Creditor (`<UltmtCdtr>`) identities, and full compatibility with EPC **SEPA Verification of Payee (`VoP`)** so payers checking a vIBAN verify the end-merchant’s legal name—not the EMI’s pooled corporate name!

| Supervisory Risk Area (EBA 2024) | Non-Compliant BaaS / vIBAN Pattern | Compliant PSD3 / AMLR Architecture | Enforcement / Operational Impact |
| :--- | :--- | :--- | :--- |
| Central Account Register (`BAR`) | Only EMI corporate name visible on Master IBAN | Automated API feed linking each vIBAN to verified end-user | Prevents FIU subpoena blind spots across borders |
| SEPA Verification of Payee (`VoP`) | Returns `"PayTech EMI Safeguarding Pool"` (`NMTC`!) | EMI VoP API resolves exact vIBAN sub-holder legal name | Prevents payer abandonment after Oct 2025 / Apr 2027 |
| Sub-Allocator Nesting (`N-Tier`) | Wholesale vIBAN blocks resold to offshore sub-PSPs | Contractual ban on nested allocation without bank KYCC | Eliminates BaFin/FCA BaaS cease-and-desist orders |
| Safeguarding Status Disclosure | Marketing "German Bank Account" implying EUR 100K DGS | Explicit disclosure: e-money vIBAN (Safeguarded, no DGS) | Complies with [PSD3/PSR](/corridors/eu-psd3-psr-framework) marketing clarity |
| Home vs Host AML Jurisdiction | LT EMI issuing ES vIBAN with unclear STR filing FIU | Dual-FIU suspicious transaction coordination protocol | Closes host-state AMLA / national FIU gap |

## Safeguarding & Outbound POBO Attribution on vIBAN Rails

On outbound disbursements from a vIBAN wallet, the EMI populates the vIBAN or Master IBAN consistently alongside structured [ISO 20022 Ultimate Debtor POBO tags](/rails/iso-20022-ultimate-debtor-ultimate-creditor-on-behalf-of-pobo) and [Lithuania LB and Dutch DNB vIBAN governance controls](/rails/lithuania-lb-dutch-dnb-emi-safeguarding-centro-link-supervision) so correspondent banks never suspect disguised third-party clearing. Model pooled account funding carry in our [Nostro SOFR prefunding carry calculator](/calculators/nostro-sofr-prefunding-carry-calculator) and browse the [EMI safeguarding & PSD3 topic cluster](/topics/emi-safeguarding-psd2-psr-accounts).

![Annual account infrastructure and unapplied suspense cost per 10,000 B2B merchants across collection models](/api/figure?type=bars&title=Annual%20Collection%20Cost%20per%2010%2C000%20B2B%20Sub-Merchants&subtitle=Bank%20ledger%20fees%2C%20BAR%2FVoP%20API%20compliance%2C%20and%20manual%20missing-reference%20reconciliation&steps=Physical%20Bank%20Sub-Accts%3A%3AEUR%202.40M%20%2F%20yr%20%E2%80%94%20EUR%2020%2Fmo%20bank%20ledger%20fee%20x%2010%2C000%20accts%7CShared%20IBAN%20%2B%20Text%20Ref%3A%3AEUR%20485K%20%2F%20yr%20%E2%80%94%208.4%25%20payers%20omit%20ref%20-%3E%20manual%20pacs.004%2FAR%7CCompliant%20Direct%20CSM%20vIBAN%3A%3AEUR%2092K%20%2F%20yr%20%E2%80%94%20own%20BIC8%20range%20%2B%2099.7%25%20zero-touch%20match%7CPartner%20Bank%20BaaS%20vIBAN%3A%3AEUR%20168K%20%2F%20yr%20%E2%80%94%20EUR%201.40%2Fyr%20per%20active%20vIBAN%20%2B%20BAR%20sync&metrics=Missing-Ref%20Cut%3A%3A-96.4%25%3A%3AvIBAN%20vs%20Shared%20IBAN%20%2B%20ref%7CSEPA%20Art%209%20Rule%3A%3ANo%20IBAN%20Block%3A%3AIllegal%20to%20reject%20EEA%20prefixes%7CVoP%20Responder%3A%3ASub-Second%3A%3AResolves%20end-user%20vs%20pool%7CAMLA%20Supervision%3A%3A2026%20-%202028%3A%3AHarmonized%20EU%20BAR%20technicals)

## vIBAN vs Physical Sub-Account Treasury Cost & Cash-Match Formula

Opening 25,000 physical statutory commercial bank accounts for B2B marketplace sellers is economically impossible (`EUR 15–40/month/account`), whereas programmatic vIBAN allocation atop a single safeguarded Master IBAN achieves 99.6% automated payer attribution at fractions of a euro.

Below is the unit-economics and reconciliation comparison model.

```formula
Net_vIBAN_Savings = [ M_merchants * V_inbound_m * (p_miss_shared - p_miss_viban) * C_suspense_fix ] - (M_merchants * c_viban_yr)

Where:
 M_merchants = Active B2B platform sellers / corporate wallets (15,000 accounts)
 V_inbound_m = Average annual inbound bank transfers per merchant (48 wires/yr -> 720,000 total)
 p_miss_shared = Missing/garbled reference rate on single shared IBAN (0.084 = 8.4%)
 p_miss_viban = Unmatched rate on dedicated per-merchant vIBAN (0.003 = 0.3%)
 C_suspense_fix = Ops support + pacs.004 return cost per unallocated wire (EUR 11.50)
 c_viban_yr = Partner bank + BAR/VoP registry cost per active vIBAN (EUR 2.20/yr)

Worked Platform Reconciliation Payback:
 Eliminated Suspense Wires = 720,000 * (0.084 - 0.003) = 58,320 wires/year
 Ops & Return Cost Avoided = 58,320 * EUR 11.50 = EUR 670,680/year
 Net_vIBAN_Savings = EUR 670,680 - (15,000 * EUR 2.20) = EUR 637,680/year
```

## Frequently asked questions

### Does holding a German DE or British GB Virtual IBAN from an EMI provide deposit insurance?

No. Even when a vIBAN carries a DE or GB bank sort prefix hosted at a tier-1 commercial bank, the end-user’s legal claim is an electronic-money/payment claim against the EMI protected by 100% safeguarding—never sovereign EUR 100K DGS or GBP 85K FSCS deposit insurance.

### Why did the EBA flag cross-border country-prefix vIBANs in its May 2024 report?

When an EMI licensed in Member State A issued vIBANs carrying the country prefix of Member State B to customers in Member State C, unclear host-vs-home AML jurisdiction delayed law-enforcement Bank Account Register lookups and STR routing.

### How does SEPA Verification of Payee (VoP) work when paying into an EMI Virtual IBAN?

When a payer enters a vIBAN and the merchant’s name, the Master-IBAN bank either delegates the VoP API lookup in sub-second real time to the EMI’s sub-ledger or queries a synchronized hashed directory so the merchant’s exact name returns MTCH.

### How can an EMI issue domestic vIBANs without relying on a partner commercial bank?

By becoming a direct participant in Eurosystem TIPS / EBA STEP2-T (under amended EU SFD rules) or UK Faster Payments/CHAPS with its own national bank/sort code allocation, an EMI issues first-party native IBANs directly.


## Source URLs

- https://www.eba.europa.eu/regulation-and-policy/payment-services-and-electronic-money
- https://www.europeanpaymentscouncil.eu/what-we-do/other-schemes/verification-payee
- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R0886

## Citation

- APA: Claire Beaumont, CAMS, CTP. (2026). Virtual IBAN (vIBAN) Issuance Under EBA and PSD3: Cross-Border IBAN Discrimination and Pooled Safeguarding. PayClear Ledger. https://payclearledger.com/rails/virtual-iban-viban-master-pooled-safeguarding-aml-supervision
- Canonical article: [Virtual IBAN (vIBAN) Issuance Under EBA and PSD3: Cross-Border IBAN Discrimination and Pooled Safeguarding](https://payclearledger.com/rails/virtual-iban-viban-master-pooled-safeguarding-aml-supervision)
- Site research index: [PayClear Ledger](https://payclearledger.com/llms-full.txt)
