IBAN Assignment for Offshore Fintechs: How It Works and Who Provides It

Why IBANs Matter for Fintechs

The International Bank Account Number (IBAN) is the standard account identifier for payments across the Single Euro Payments Area (SEPA) and much of the global banking system. For a fintech business offering account-like services — whether a neobank, a payment platform, a corporate expense management tool, or a crypto on-ramp — the ability to assign IBANs to customers is a core product requirement.

Without an IBAN, a customer cannot receive SEPA credit transfers, set up direct debits, or be identified within the European payment infrastructure. For offshore fintechs targeting European customers, IBAN assignment is therefore not a technical detail — it is a fundamental product capability that determines whether the fintech can compete with incumbent banks.

How IBANs Are Assigned

The IBAN Structure

An IBAN consists of:

• Country code (2 letters): Identifies the country of the account-holding institution (e.g., LT for Lithuania, MT for Malta, IE for Ireland, DE for Germany)
• Check digits (2 numbers): A validation mechanism calculated from the rest of the IBAN
• Basic Bank Account Number (BBAN): The domestic account number, which includes the bank/institution code and the individual account number

The country code in the IBAN corresponds to the country where the issuing institution is licensed, not the country where the customer resides. A Lithuanian EMI assigns LT-prefix IBANs to its customers regardless of whether those customers are in Germany, France, or Spain.

Who Can Assign IBANs

Only institutions with a Bank Identifier Code (BIC) registered with SWIFT and a SEPA participant status can assign IBANs. In practice, this means:

• Credit institutions (banks): Can assign IBANs directly through their own BIC
• Electronic money institutions (EMIs): Can assign IBANs either through their own BIC (if they are direct SEPA participants) or through a sponsoring bank's BIC
• Payment institutions (PIs): Generally cannot assign IBANs directly; they must rely on a banking or EMI partner

For an offshore fintech, this means that IBAN assignment requires either:

1. Obtaining an EMI licence in an EU member state and securing SEPA connectivity, or
2. Partnering with a licensed institution that provides IBAN assignment as a service (the BaaS model)

The Two Routes to IBAN Assignment

Route 1: Own EMI Licence

An offshore fintech that obtains its own EMI licence in an EU member state can assign IBANs to its customers. The process involves:

Step 1: EMI licensing Obtain an EMI licence from a national competent authority (e.g., Bank of Lithuania, MFSA, Central Bank of Ireland). The EMI licence authorises the issuance of electronic money and the provision of payment services.

Step 2: SEPA participant status Connect to the SEPA payment infrastructure. This can be achieved through:

• Direct participation: Becoming a direct participant in a SEPA-compliant clearing and settlement mechanism (e.g., STEP2 operated by EBA Clearing, or TARGET Instant Payment Settlement operated by the Eurosystem). Direct participation requires significant investment in technology infrastructure and is typically only viable for larger institutions
• Indirect participation: Accessing SEPA through a sponsor bank that is a direct participant. The EMI routes its SEPA transactions through the sponsor bank's infrastructure. This is the standard approach for most EMIs
• CENTROlink: The Bank of Lithuania's payment system provides Lithuanian-licensed EMIs with SEPA access, acting as a technical intermediary. This is one reason Lithuania is popular for EMI licensing

Step 3: BIC registration Register a Bank Identifier Code with SWIFT. The EMI can use its own BIC or, in some cases, operate under the BIC of its sponsor bank.

Step 4: IBAN range allocation Obtain an IBAN range from the national IBAN allocation authority. In Lithuania, for example, the Bank of Lithuania allocates IBAN ranges to licensed EMIs.

Step 5: IBAN issuance to customers The EMI assigns individual IBANs from its allocated range to each customer upon account opening.

Cost and timeline:

• EMI licence: €150,000-€500,000 (total including advisory fees and capital)
• SEPA connectivity: €20,000-€80,000
• BIC registration: €5,000-€15,000
• Timeline: 6-12 months from EMI licence application to live IBAN issuance

Route 2: BaaS Partnership

An offshore fintech that does not hold its own EMI licence can assign IBANs through a Banking-as-a-Service partner. The BaaS provider holds the EMI or banking licence and assigns IBANs from its own range to the fintech's customers.

How it works: The fintech integrates with the BaaS provider's API to:

• Create customer accounts (triggering IBAN assignment)
• Process incoming and outgoing SEPA transfers
• Manage account balances and transaction history

The IBAN assigned to the customer carries the BaaS provider's country code and institution code, not the fintech's. A fintech using a Lithuanian BaaS provider will assign LT-prefix IBANs; one using an Irish BaaS provider will assign IE-prefix IBANs.

Key BaaS providers offering IBAN assignment:

• Banking Circle (Luxembourg): LU-prefix IBANs
• Modulr (UK): GB-prefix sort code/account numbers (not SEPA IBANs) and EUR IBANs
• Swan (France): FR-prefix IBANs
• ClearBank (UK): GB-prefix sort code/account numbers
• Solaris (Germany): DE-prefix IBANs
• Paynetics (Bulgaria): BG-prefix IBANs

Cost:

• Setup: €10,000-€50,000
• Per-IBAN fee: €0.50-€3.00 per active account per month
• Per-transaction fee: €0.05-€0.50 per SEPA transfer
• Timeline: 2-4 months from BaaS agreement to live IBAN issuance

Dedicated IBANs vs Virtual IBANs

The distinction between dedicated (structural) IBANs and virtual IBANs is critical and frequently misunderstood:

Dedicated IBANs

A dedicated IBAN corresponds to a unique, segregated account at the issuing institution. Each customer has their own account with their own IBAN. Funds sent to that IBAN are credited to that specific customer's account.

• Regulatory treatment: Each dedicated IBAN represents a distinct payment account under PSD2
• Safeguarding: Funds held in dedicated IBAN accounts must be safeguarded in accordance with EMD2 Article 7
• SEPA compliance: Fully compliant with SEPA scheme rules
• Customer experience: The customer owns their IBAN and can share it for incoming payments

Virtual IBANs (vIBANs)

A virtual IBAN is an IBAN that routes incoming payments to a pooled or master account, where they are credited to the correct customer based on the vIBAN reference. Multiple vIBANs map to a single underlying account.

• Regulatory treatment: vIBANs do not necessarily represent distinct payment accounts. The regulatory treatment depends on the specific structure and the regulator's interpretation
• Use case: vIBANs are commonly used for payment reconciliation — each customer receives a unique reference number (formatted as an IBAN) that identifies their payments within a pooled account
• Risks: Some regulators have expressed concern about vIBAN structures, particularly where the vIBAN creates the appearance of a dedicated account while funds are held in a pooled arrangement
• EBA guidance: The European Banking Authority has examined vIBAN structures and identified potential risks related to AML/CFT (difficulty in identifying the true account holder), consumer protection (customer perception vs. legal reality), and prudential treatment

Regulatory Scrutiny of vIBANs

In 2024, the EBA published an Opinion on the prudential treatment of virtual IBANs, identifying several concerns:

• vIBANs may be used to circumvent AML/CFT requirements if the true account holder is not properly identified
• Customers may believe they hold a dedicated account when they are actually part of a pooled structure
• The country code in a vIBAN may not correspond to the jurisdiction where the underlying account is held, creating potential confusion about the applicable regulatory regime

Fintechs using vIBAN structures should ensure:

• Clear disclosure to customers about the nature of the vIBAN
• Proper AML/CFT procedures applied to the vIBAN holder
• Compliance with the regulator's specific guidance on vIBAN usage

The IBAN Country Code Issue

The country code in an IBAN can affect customer acceptance:

• German customers receiving a Lithuanian (LT) IBAN may face issues with certain direct debit originators or employers who only accept DE-prefix IBANs
• Regulation (EU) No 260/2012 (SEPA Regulation) Article 9 prohibits IBAN discrimination — payors and payees cannot require that a payment be made to or from an account in a specific member state. However, enforcement varies, and practical discrimination persists
• Customer perception: Some customers perceive IBANs from established financial centres (DE, FR, NL, IE) more favourably than IBANs from newer fintech jurisdictions (LT, BG)

For fintechs concerned about IBAN discrimination, options include:

• Obtaining an EMI licence in a jurisdiction whose IBAN prefix is well-accepted (Germany, France, or Ireland)
• Using a BaaS provider licensed in a major jurisdiction
• Educating customers about IBAN portability and their rights under the SEPA Regulation

SEPA Instant Credit Transfers

Regulation (EU) 2024/886 requires all EU payment service providers that offer SEPA credit transfers to also offer SEPA Instant Credit Transfers (SCT Inst) from January 2025. This affects IBAN issuers because:

• Customers expect that their IBAN supports instant payments (funds received within 10 seconds)
• The EMI or BaaS provider must have SCT Inst capability through its SEPA connectivity
• Pricing for instant payments may differ from standard SEPA credit transfers

Fintechs planning IBAN issuance should confirm that their licensing and BaaS arrangements support SEPA Instant from the outset.

Key Takeaways

• IBAN assignment requires either an EMI licence with SEPA connectivity or a BaaS partnership with a licensed provider — payment institutions alone cannot assign IBANs
• The own-licence route costs €170,000-€600,000 and takes 6-12 months but provides maximum control and margin; the BaaS route costs €10,000-€50,000 setup and takes 2-4 months but involves ongoing per-account and per-transaction fees
• Dedicated IBANs represent distinct customer accounts with clear regulatory treatment; virtual IBANs route to pooled accounts and face increasing regulatory scrutiny from the EBA
• The IBAN country code can affect customer acceptance despite the SEPA Regulation's prohibition on IBAN discrimination — fintechs should consider this when selecting their licensing jurisdiction or BaaS provider
• SEPA Instant Credit Transfer capability is now mandatory for EU PSPs offering credit transfers, and must be factored into IBAN infrastructure planning
• Lithuania (via CENTROlink) offers the most streamlined path from EMI licence to IBAN issuance, while Germany, France, and Ireland offer IBANs with stronger customer acceptance
• The distinction between dedicated IBANs and virtual IBANs is a regulatory and product design question that must be addressed early in the planning process