IBAN sponsor
A provider that opens accounts and issues IBANs - often with local country codes - to fintechs under its own EMI, PI or banking licence (IBAN-as-a-service).
If your product holds balances or receives transfers, it needs accounts and IBANs. An IBAN sponsor provides them under its licence: virtual IBANs for reconciliation, safeguarding accounts, SEPA/SWIFT access.
The differentiator is the country code: a German employer may (unlawfully, but routinely) reject a Lithuanian IBAN - the "IBAN discrimination" problem. Sponsors that issue local DE/FR/ES IBANs remove that friction, which is why Fintechnologica tracks exactly which country codes each sponsor can issue.
Primary source: Directive 2009/110/EC (E-Money Directive) · Regulation (EU) 260/2012 (SEPA Regulation)
In the verified data
- 52 live IBAN sponsors issue accounts under their own licence - 9 banks, 35 e-money institutions and 4 payment institutions - across 21 IBAN country codes.
- Rails, as each sponsor documents them: 34 of 51 offer SEPA Instant, but only 15 document SEPA Direct Debit Core and 4 the B2B scheme (Lemonway, Solaris, Swan and Treezor) - and direct debit is where IBAN discrimination bites hardest.
- Account models: 33 offer dedicated accounts, 28 virtual IBANs over a pooled account and 8 named virtual IBANs - the model drives the price.
Recomputed from the catalogue and the official EBA, ESMA and FCA registers on every build — how we verify.
Questions to ask a provider
- Which IBAN country codes can you issue today, and is each IBAN a dedicated account or a virtual IBAN over a pooled account?
- Which rails do you support in production - SEPA Instant, SEPA Direct Debit Core and B2B, SWIFT, UK Faster Payments?
- Is client money held as bank deposits or safeguarded as e-money - and at which credit institution?