.jpg)
Most guides to virtual IBAN providers are written for startups that need a EUR account quickly. This one is written for the segment in the middle: regional and community banks, established EMIs, PSPs, and scaling fintechs that move real volume but sit below the threshold where global banks compete for their business.
That segment is re-evaluating its account infrastructure for three reasons:
The buying decision therefore looks less like "which provider issues IBANs" and more like "which institution should sit between our clients' money and the clearing system." This guide compares the leading options through that lens.
One note on perspective: Lorum publishes this guide and appears in it. The comparison is built on structural criteria that any institution can verify in due diligence.
What a virtual IBAN is, and where it falls short
A virtual IBAN is an account number that routes payments to an underlying master account, allowing a platform or institution to give each client a unique reference without opening individual bank accounts. It solves a reconciliation problem elegantly, and for many use cases it works well.
The limits show up at institutional scale. In pooled setups, the name behind the IBAN is the provider's rather than the client's. That creates friction under Verification of Payee and makes fund attribution dependent on the provider's internal ledger.
Funds also sit behind the provider's licence, so counterparty risk concentrates in one intermediary, often itself operating through nested correspondent relationships. For a mid-market bank or fintech holding client funds, these are the questions a regulator, an auditor, and an insolvency practitioner will ask first. The structural background is covered in named accounts vs pooled accounts.
That is why this comparison weighs structure as heavily as coverage. Some providers below issue virtual IBANs in the client's name, and some replace the virtual layer with named accounts altogether.
How the providers were evaluated
Six criteria, weighted for mid-market financial institutions rather than early-stage startups:
The regulatory direction of travel is examined further in PSD3 and the end of commingled funds in Europe.
1. Lorum
Lorum sits at the structural end of this list. Rather than issuing virtual references against a master account, Lorum operates as a globally licensed specialist correspondent institution built around Named Account Custody, a structure that gives each account holder a legal and operational relationship to the custody framework, reducing the opacity and chain risk of nested clearing models.
Clients receive genuinely named accounts with multi-currency clearing across 30+ markets, cash management, and FX through a single API. Lorum does not operate a lending book and holds all client funds in 100% reserve. The firm filed for a US national trust bank charter with the OCC in April 2026.
For mid-market banks and fintechs, two characteristics matter most:
The trade-off is fit. Lorum is built for financial institutions and platforms moving institutional volume, not for a company that needs a single EUR IBAN by Friday.
2. Currencycloud
Currencycloud, acquired by Visa in 2021 and now part of Visa Cross-Border Solutions, is an FX-first platform providing multi-currency wallets, conversion, and payment execution through a well-established API. For fintechs whose core need is embedding currency accounts and FX into their product, it is one of the most widely integrated routes in the market.
The account infrastructure is built around multi-currency wallets rather than named accounts, which shapes how fund attribution and name verification behave at scale. A structure-level breakdown is available in Lorum vs. Currencycloud.
3. Banking Circle
Banking Circle provides bank-grade infrastructure with direct UK and EU scheme access, safeguarding accounts, and account structures designed for client-level separation. It is a strong fit for payments businesses processing high volumes that want named separation without building bank relationships market by market.
Onboarding is institutional rather than self-serve, which mid-market buyers should treat as a feature rather than a drawback. See Lorum vs. Banking Circle for the detailed comparison.
4. ClearBank
ClearBank is a UK clearing bank offering fully regulated accounts with direct UK scheme access, plus embedded banking for fintechs that want client-named accounts backed by a banking licence. For UK EMIs and payment institutions preparing for CASS 15 audits, a clearing bank counterparty is a defensible answer.
Coverage is concentrated in the UK, which institutions with broader settlement needs should assess carefully. The structural differences are covered in Lorum vs. ClearBank.
5. OpenPayd
OpenPayd issues multi-currency IBANs in the client's name through a modular API covering accounts, payments, and FX, and is among the more developer-friendly routes to named IBANs. Coverage centres on the UK and EU, with further regions served through partners.
Institutions evaluating OpenPayd for global flows should map the partner chain, since every added intermediary reintroduces some of the nesting that a named model is meant to remove.
6. LHV Bank
LHV has built a substantial business providing banking infrastructure to fintechs, with accounts, UK and European scheme access, and a banking licence behind them. For fintechs that specifically want a bank as their counterparty without the onboarding thresholds of a global bank, it is a credible option.
Product breadth beyond core accounts and payments is narrower than the infrastructure specialists above.
A structural comparison
The infrastructure decision
The choice between these providers is less a question of which is better and more a question of what the institution's primary need is. A fintech embedding FX conversion into a consumer product has different requirements from a regional bank that must hold client funds in named, segregated structures across multiple jurisdictions.
Three questions separate the contenders faster than any feature list:
As regulatory frameworks converge on stricter fund segregation and custody requirements, the distinction between pooled, client-named, and fully named architectures becomes more consequential. The answers to these questions will determine which infrastructure is the right fit.
