TL;DR
Written by Maria Skakun (LinkedIn), Partner, Head of Business Development at Bienrock
Helping fintech and crypto companies access banking infrastructure globally.
- Offering IBANs to clients is one of the most commercially valuable capabilities a fintech or payment company can add — and one of the most infrastructure-intensive to build correctly.
- An IBAN is not just a payment reference number. Issuing IBANs to clients means becoming part of the client money chain — which triggers regulatory obligations around safeguarding, AML, and client fund segregation that most companies underestimate.
- The two paths to offering client IBANs are: obtaining an EMI licence and partnering with a bank for safeguarding, or partnering directly with a licensed EMI or bank that issues IBANs on your behalf — each carries different timelines, costs, and compliance obligations.
- The IBAN Partner Selection Framework, used by the team at Bienrock, evaluates IBAN-issuing partners on five criteria: local IBAN availability, safeguarding structure, multi-currency support, technical integration quality, and risk appetite for the client’s business model.
- The single most overlooked selection criterion is local IBAN availability — an IBAN issued in a jurisdiction that does not match the end client’s country of operation creates “IBAN discrimination” problems that block direct debits and reduce transaction acceptance rates.
- Bienrock connects payment companies, fintechs, and crypto businesses to EMI and banking partners that issue IBANs — including dedicated and virtual IBAN structures — globally, with introductions at decision-maker level.
Introduction
For a fintech or payment company, offering IBANs to clients is the difference between being a payment processor and being a financial infrastructure provider. It changes the product, the client relationship, and the commercial model — clients do not just route payments through you; they hold funds with you.
That shift is commercially powerful and operationally complex. The infrastructure required to issue IBANs correctly — including the regulatory framework, the safeguarding structure, the technical integration, and the partner selection — is significantly more demanding than most companies realise when they first decide to add IBAN capability.
This article explains what offering client IBANs actually involves, the two structural paths to getting there, what to look for in an IBAN-issuing partner, and the most common mistakes that cause IBAN programs to underperform after launch.
What Offering Client IBANs Actually Means
An IBAN (International Bank Account Number) is a standardised identifier for a bank or payment account used to route payments across SEPA and international payment networks. When a fintech or payment company offers IBANs to its clients, it is providing each client with a unique account identifier that can receive SEPA transfers, SWIFT payments, and in some cases direct debits — functioning, from the client’s perspective, like a bank account.
The operational reality behind this is that the fintech or payment company has entered the client money chain. Funds received at a client IBAN sit in the company’s infrastructure — either directly in a licensed account or through an EMI or bank partner — until they are transferred onward. This creates regulatory obligations that do not apply to companies that simply route payments without holding client funds.
Specifically: client funds must be safeguarded — held separately from the company’s own operational funds and protected in the event of the company’s insolvency. AML and KYC obligations apply to every client whose funds are received. Reporting obligations to the relevant regulator are ongoing. And the technical infrastructure must maintain accurate real-time records of each client’s balance.
Understanding this upfront changes the entire approach to building IBAN capability — from a feature addition to a regulatory and infrastructure project.
The Two Structural Paths to Offering Client IBANs
Path 1: Obtain an EMI Licence and Partner with a Bank for Safeguarding
The first path is for companies that want to own the full IBAN-issuing capability — issuing IBANs under their own licence, managing client money directly, and controlling the full client experience.
This requires obtaining an EMI (Electronic Money Institution) licence from the relevant national regulator. In the EU, an EMI licence can be passported across all 27 member states from a single jurisdiction — Lithuania, Ireland, Malta, and the Netherlands are common licensing hubs. In the UK, the FCA regulates EMIs separately. Capital requirements for an EMI licence start at around €350,000 in the EU, significantly lower than the €5 million minimum for a full banking licence.
Once licensed, the EMI must partner with a bank for safeguarding — holding client funds in a designated client money account at a licensed credit institution, separate from the EMI’s own funds. Not all banks offer safeguarding services; the pool of institutions willing to provide safeguarding accounts to EMIs, particularly those operating in higher-risk sectors, is smaller than many assume. Obtaining a banking licence takes up to 12 months; an EMI licence typically takes around 6 months. Building and launching the full infrastructure typically adds another 6–12 months.
This path offers the most control and the strongest commercial position — but it is a multi-year project with significant ongoing compliance obligations.
Path 2: Partner with a Licensed EMI or Bank That Issues IBANs on Your Behalf
The second path is for companies that want to offer IBAN capability without obtaining their own licence — by partnering with an existing licensed EMI or bank that issues IBANs under its own regulatory framework, with the partner company acting as the distributor of those accounts.
In this model, the IBAN-issuing partner holds the licence, manages the safeguarding, and bears the primary regulatory obligations. The partner company handles the client relationship, the product experience, and the commercial terms with its own clients. The IBAN appears to the end client as part of the partner company’s product — but the underlying account is held at the licensed EMI or bank.
This path is significantly faster — operational in 3–6 months rather than 2–3 years — and requires no upfront capital for licensing. The trade-off is dependency on the partner’s infrastructure, risk appetite, and commercial terms. If the partner changes its risk appetite, is subject to regulatory action, or exits the relationship, the IBAN program is disrupted. Selecting a partner with financial stability, a strong safeguarding structure, and genuine risk appetite for the company’s client base is therefore the most consequential decision in this path.
For most fintechs and payment companies outside the largest tier, Path 2 is the practical starting point — with Path 1 as a future option once the business has the scale and regulatory infrastructure to justify it.
The IBAN Partner Selection Framework — Five Criteria That Actually Determine Program Success
The IBAN Partner Selection Framework is the approach used by the team at Bienrock to evaluate and select IBAN-issuing partners for fintech and payment company clients. The framework assesses five criteria in sequence — because failure at any level makes the subsequent criteria irrelevant.
Criterion 1: Local IBAN Availability
The most commercially damaging and most commonly overlooked criterion in IBAN partner selection is whether the partner can issue IBANs in the jurisdictions where the end clients actually operate.
A Lithuanian IBAN issued to a client in France, Germany, or Spain creates a problem called IBAN discrimination — where the receiving institution (an energy company, a landlord, a supplier) refuses to process a direct debit or payment because the IBAN does not correspond to a local account. This practice is technically illegal under SEPA rules, but it occurs regularly in practice. A client who cannot use their IBAN for direct debits has an account that is operationally incomplete.
The ability to issue local IBANs — with country codes matching the client’s jurisdiction — is a functional requirement for any program serving clients in markets where IBAN discrimination is common. Not all EMI partners can provide this; it depends on the partner’s own banking relationships and licence passporting. This criterion should be assessed before any other.
Criterion 2: Safeguarding Structure
The safeguarding structure of the IBAN-issuing partner determines whether client funds are genuinely protected — and how that protection is communicated to end clients.
EMI partners safeguard client funds either through segregation (holding funds in designated client money accounts at one or more banks) or through insurance/guarantee. The segregation method is more common and more verifiable. The strength of the safeguarding structure depends on which banks the EMI uses, whether those banks are themselves financially stable, and whether the EMI maintains safeguarding across multiple banking partners rather than relying on a single one.
A well-connected EMI that safeguards across multiple banking partners provides meaningful resilience — if one safeguarding bank exits the relationship, client funds remain protected through the others. A poorly connected EMI with a single safeguarding partner at a smaller institution carries structural fragility that is not immediately visible but becomes critical if the safeguarding bank encounters problems. Bienrock’s approach to EMI selection for clients specifically prioritises partners with diversified, well-connected safeguarding structures — providing the onboarding speed of an EMI with stability comparable to traditional banking.
Criterion 3: Multi-Currency Support
For payment companies and fintechs serving international clients, single-currency IBAN programs are operationally insufficient — multi-currency account support is a baseline requirement, not a premium feature.
The ability to receive, hold, and transfer funds in multiple currencies — EUR, USD, GBP, and others relevant to the client base — determines whether the IBAN program can serve the company’s actual client needs or only a subset of them. Partners vary significantly in their currency coverage: some offer EUR only, some offer a handful of major currencies, and a smaller number offer genuinely broad multi-currency support.
Currency coverage should be assessed against the company’s specific client geography and transaction types — not against a generic list of “supported currencies” that may include currencies with restricted functionality.
Criterion 4: Technical Integration Quality
The quality of the partner’s API and technical infrastructure determines whether the IBAN program can be built and operated efficiently — or whether it becomes a permanent operational burden.
Key technical requirements include: real-time or near-real-time balance and transaction data via API; webhook notifications for incoming payments; the ability to issue virtual IBANs programmatically at scale; and accurate reconciliation between client IBAN balances and the underlying safeguarded funds. Partners with well-documented, stable APIs and responsive technical support enable a program to be built in weeks; those with poor documentation, unreliable uptime, or slow support create development delays and ongoing operational issues.
Criterion 5: Risk Appetite for the Client’s Business Model
An IBAN partner that does not genuinely accept the company’s sector and client profile will restrict, delay, or exit the relationship — regardless of what it says during the commercial negotiation.
This is particularly relevant for payment companies and fintechs serving crypto clients, forex businesses, iGaming operators, or other higher-risk sectors. Partners that publicly state openness to these sectors but impose restrictive transaction monitoring rules, low volume limits, or frequent compliance holds effectively do not serve these sectors. Understanding a partner’s actual — not stated — risk appetite requires current network knowledge of how that partner operates in practice with similar clients.
Dedicated vs Virtual IBANs — Choosing the Right Structure
Dedicated IBANs assign a unique IBAN to a specific client or purpose — funds received at that IBAN are clearly attributed and segregated at the individual account level. This is the stronger structure for regulatory compliance and client experience, but it requires individual account setup and creates more administrative overhead at scale.
Virtual IBANs are unique payment reference numbers that route to an underlying master account held by the program operator. Each client receives a unique virtual IBAN that identifies their transactions, but funds are pooled at the master account level and reconciled by the program operator. Virtual IBANs are the standard mechanism for platforms, exchanges, and payment processors that need to assign unique payment references to large numbers of clients without individual account setup overhead.
The choice between dedicated and virtual IBANs depends on the regulatory environment, the client profile, and the volume of accounts required. For programs issuing IBANs to hundreds or thousands of clients, virtual IBANs are the practical structure. For programs where individual fund segregation is a regulatory requirement or a commercial differentiator, dedicated IBANs are the correct choice.
How the IBAN Partner Selection Framework Works Inside Bienrock’s Process
Bienrock is not a bank or EMI. It is an intermediary that connects payment companies, fintechs, and crypto businesses to the right IBAN-issuing partners — and structures the partner relationship for long-term operational stability.
The IBAN Partner Selection Framework is applied at the start of every IBAN infrastructure engagement: assessing the company’s client geography, currency requirements, volume profile, and sector to identify which partners genuinely meet all five criteria. The introduction is made at decision-maker level — not through a general enquiry — which changes both the onboarding timeline and the commercial terms available.
Critically, Bienrock’s partner selection specifically prioritises EMIs with strong, diversified banking connections — so clients get the onboarding speed of an EMI partnership with the structural stability of a well-connected institution. This is Bienrock’s core approach to EMI positioning: not all EMIs are equivalent, and the difference between a well-connected and a poorly-connected EMI only becomes visible when the banking environment changes.
Bienrock’s network covers IBAN-issuing partners across EU, UK, MENA, and other jurisdictions, with both dedicated and virtual IBAN structures available — including partners with genuine risk appetite for crypto, fintech, forex, and iGaming client bases.
Find out more about Bienrock’s IBAN and payment infrastructure services at bienrock.ch/bank-accounts.
The Most Common Mistakes That Cause IBAN Programs to Underperform
Selecting the wrong jurisdiction for the IBAN. Issuing IBANs with a country code that does not match the client’s operating jurisdiction creates IBAN discrimination problems that no amount of post-launch adjustment can fully resolve. This decision needs to be made before the partner is selected, not after.
Underestimating the safeguarding compliance obligations. Companies that add IBAN capability without understanding the safeguarding requirements — or that assume the partner handles everything — often find themselves with compliance gaps when the regulator or the safeguarding bank requests documentation. Even in a partner model, the company distributing the IBANs has compliance obligations.
Selecting a partner based on the lowest fee rather than the strongest structure. IBAN partner pricing varies — but the lowest-cost partner is rarely the most stable one. Fee differences that look significant in a spreadsheet become irrelevant if the partner is subject to regulatory action or exits the relationship.
Building a single-partner dependency. A single IBAN-issuing partner with no backup creates the same operational vulnerability as a single banking relationship. Building in a secondary option — even as a standby — reduces the exposure to partner disruption significantly.
Frequently Asked Questions
What does it mean to offer IBANs to clients as a fintech or payment company? Offering IBANs to clients means providing each client with a unique account identifier that can receive bank transfers and in some cases direct debits — effectively providing a bank account-like capability. It also means entering the client money chain: the funds received at those IBANs sit within the company’s infrastructure and must be safeguarded, with AML and KYC obligations applying to every client. The infrastructure required is significantly more complex than adding a payment processing capability.
Do I need an EMI licence to offer IBANs to my clients? Not necessarily. There are two paths: obtaining your own EMI licence (which takes around 6 months for the licence alone, plus additional time to build the infrastructure), or partnering with an existing licensed EMI or bank that issues IBANs on your behalf. For most companies outside the largest tier, partnering with a licensed EMI is the faster and more practical starting point — operational within 3–6 months without the capital and compliance burden of holding a licence.
What is IBAN discrimination and why does it matter for partner selection? IBAN discrimination occurs when a receiving institution — an energy company, a landlord, a payment processor — refuses to accept a direct debit or payment because the IBAN does not correspond to a local account in the client’s country. For example, a Lithuanian IBAN used by a client in France may be rejected for French direct debits even though this practice is illegal under SEPA. Local IBAN availability — IBANs with a country code matching the client’s jurisdiction — is the most important functional criterion in IBAN partner selection.
What is the difference between a dedicated IBAN and a virtual IBAN? A dedicated IBAN is a unique account identifier assigned to a specific client, with funds held separately at the individual account level. A virtual IBAN is a unique reference number that routes to a master account, with reconciliation handled by the program operator. Dedicated IBANs provide stronger individual fund segregation; virtual IBANs are the standard mechanism for platforms issuing IBANs to large numbers of clients at scale without individual account setup overhead.
How should I evaluate the safeguarding structure of an EMI partner? Assess which banks the EMI uses for safeguarding, whether it maintains accounts at multiple banks rather than a single institution, and the financial stability of those banks. An EMI that safeguards across multiple well-connected banking partners provides meaningful resilience; one with a single safeguarding partner at a smaller institution carries structural fragility that becomes visible when the banking environment changes. Request the EMI’s latest safeguarding audit report as part of due diligence.
How long does it take to launch an IBAN program through a partner EMI? With the right partner selected, compliance documentation prepared, and a complete technical integration plan, an IBAN program can go live in 3–6 months. Programs with complex technical requirements — multi-currency virtual IBAN issuance at scale, custom reconciliation logic, or crypto-to-fiat balance integration — take longer. The onboarding timeline depends heavily on the partner’s own processes and the readiness of the company’s compliance documentation.
Key Takeaways
- Offering IBANs to clients means entering the client money chain — triggering safeguarding, AML, and regulatory obligations that go significantly beyond standard payment processing.
- There are two structural paths: obtaining an EMI licence (a 6–12 month regulatory project with ongoing compliance obligations) or partnering with a licensed EMI or bank (operational in 3–6 months, with partner dependency as the primary risk).
- The IBAN Partner Selection Framework, used by Bienrock, evaluates partners on five criteria in sequence: local IBAN availability, safeguarding structure, multi-currency support, technical integration quality, and risk appetite for the client’s business model.
- Local IBAN availability — the ability to issue IBANs with a country code matching the client’s jurisdiction — is the most commercially important and most commonly overlooked criterion in partner selection.
- Bienrock’s approach to EMI selection specifically prioritises partners with diversified, well-connected safeguarding structures — providing onboarding speed with stability comparable to traditional banking.
- Virtual IBANs are the standard mechanism for platforms issuing unique payment references to large numbers of clients; dedicated IBANs provide stronger individual segregation for programs where that is a regulatory or commercial requirement.
- A single-partner dependency for IBAN issuance creates the same operational vulnerability as a single banking relationship — building in a secondary option is a baseline resilience measure, not an optional upgrade.
Conclusion
Offering client IBANs is not a feature — it is an infrastructure commitment. The companies that build this capability successfully are those that understand the regulatory obligations upfront, select the right partner based on the five criteria that actually determine program success, and structure the relationship for long-term stability rather than fastest time to market.
The IBAN Partner Selection Framework exists because the default approach — identifying an available EMI and negotiating a contract — frequently produces programs that underperform due to IBAN discrimination issues, safeguarding gaps, or partner instability that was not assessed at the selection stage.
If your company is building or expanding IBAN capability, start with a partner assessment — not a commercial negotiation.
Start at bienrock.ch.