IBAN Assignment for Offshore Fintechs: A Practical Guide

How IBAN assignment works for offshore fintechs, why your own IBAN range matters, and the licensing, sponsor-bank and compliance realities behind it.

For a young fintech, few things feel more validating than the moment your customers can receive money into an account that carries your brand rather than a third party's. That moment usually hinges on one technical detail: IBAN assignment. Get it right and you control the payment experience, the float and the data. Get it wrong and you inherit a fragile dependency that can be switched off with little notice.

IBAN assignment sits at the intersection of banking infrastructure, licensing and anti-money-laundering obligations. It is also one of the most misunderstood topics in the offshore and cross-border fintech world, where founders are routinely promised "your own IBANs" without being told what actually underpins them.

This guide explains how IBAN assignment really works, the structures behind it, and the questions every founder should ask before building a product on top of someone else's licence.

What an IBAN actually is

An IBAN, the International Bank Account Number, is a standardised format for identifying an individual account at a financial institution. It encodes a country code, check digits and a domestic account identifier, often including a bank or institution code. It is an addressing standard, not a licence and not a guarantee of anything.

The common misconception is that holding an IBAN means holding a bank account in the traditional sense. In practice, many IBANs issued to fintech customers today are accounts at an electronic money institution or payment institution, not a deposit-taking bank. Funds may be held as electronic money or safeguarded client money rather than as bank deposits. That distinction matters for how the money is protected, how it is reported, and what the customer is actually buying.

When we advise clients, we are careful to separate three things that often get conflated: the IBAN format, the institution that issues it, and the regulatory permission that allows that institution to hold and move customer funds.

Who can assign IBANs, and from whose range

Only a regulated institution with the appropriate permissions and access to a payment scheme can originate IBANs. That is typically a licensed bank, an electronic money institution (EMI) or a payment institution, often connected to a domestic clearing system or to SEPA in the European context.

Offshore fintechs generally reach IBANs through one of a few routes. The first is direct licensing, where the fintech itself obtains an EMI, payment institution or banking licence and is allocated its own IBAN range by the scheme or central infrastructure. This gives the most control but is the slowest and most capital-intensive path.

The second is a sponsor or principal arrangement, where a licensed institution issues IBANs and the fintech operates as an agent, distributor or programme manager on top. The fintech's customers may see branded accounts, but the regulatory perimeter, and frequently the IBAN range itself, belongs to the sponsor.

The third route is banking-as-a-service, a packaged version of the second, where IBAN issuance, ledgering and compliance tooling are delivered through APIs. This is fast to integrate, but the fintech is one link in a chain that runs from a sponsor bank through a BaaS provider to the end customer.

A recurring pitfall we see is founders believing they have "their own IBANs" when in reality they hold a slice of a sponsor's range under contract. The IBANs can look bespoke while remaining entirely dependent on a relationship the founder does not control.

Dedicated versus shared ranges

There is a meaningful difference between a dedicated IBAN range allocated to your programme and shared or virtual IBANs that map back to a pooled account. Dedicated ranges generally give cleaner reconciliation, stronger branding and more resilience if a single relationship ends. Pooled or virtual structures are cheaper and quicker but can raise questions from receiving banks and from regulators about who truly holds the funds.

The right choice depends on volume, the regulatory framework you operate under, and how much continuity risk you can tolerate.

The offshore dimension

Choosing an offshore or non-traditional jurisdiction for the issuing entity can be sensible, but it changes the IBAN conversation in concrete ways.

First, the country code in the IBAN reflects the issuing institution's jurisdiction, and counterparties form judgements based on it. Some receiving banks apply enhanced scrutiny, or decline, to IBANs from certain jurisdictions, regardless of how robust the underlying institution is. This is sometimes called IBAN discrimination, and while rules in some regions prohibit it for domestic schemes, cross-border practice is uneven.

Second, scheme access is not automatic. Being licensed in one jurisdiction does not, by itself, grant access to another region's clearing system or to SEPA. Many offshore fintechs therefore pair an offshore holding or operating structure with an onshore licensed issuer or sponsor to obtain usable IBANs.

Third, substance and governance expectations have risen sharply. Regulators and correspondent banks increasingly expect genuine local presence, qualified management and real decision-making in the jurisdiction of licensing. A letterbox arrangement is now a liability rather than a shortcut.

Compliance is the real product

It is tempting to treat IBAN assignment as a plumbing problem. In our experience the binding constraint is almost always compliance, not technology.

Whoever issues the IBAN carries obligations around customer due diligence, ongoing monitoring, sanctions screening and transaction reporting. If you operate as an agent or programme manager, those obligations flow to you contractually even when the licence sits elsewhere. Sponsors will audit your onboarding, your monitoring rules and your handling of suspicious activity, and they will offboard programmes that create risk.

Information-sharing regimes such as the Common Reporting Standard and, for US persons, FATCA can also reach accounts identified by these IBANs, depending on the nature of the institution and the account holder. Founders who assume offshore issuance means invisibility are mistaken; transparency is now the default direction of travel.

The practical lesson is to build compliance capability as a first-class part of the business, not as an afterthought bolted on to satisfy a sponsor. The programmes that endure are the ones that treat the sponsor's risk appetite as their own.

Continuity, control and exit risk

The single most important commercial question is what happens if a relationship ends. Sponsor banks change strategy, BaaS providers lose their own banking partners, and de-risking events can arrive with little warning.

Before committing, we encourage clients to map the dependency chain in full: who issues the IBAN, who safeguards the funds, who provides scheme access, and what notice and portability rights exist at each link. A programme that can migrate its customers and their IBANs, or at least their balances, to an alternative issuer is far more resilient than one that cannot.

Where continuity is critical, the calculus may favour pursuing your own licence over time, or maintaining more than one issuing relationship, even at higher cost. The cheapest path to launch is rarely the cheapest path to survive.

How HPT helps

We help founders and established operators design IBAN and payment structures that match their risk appetite, growth plans and regulatory reality, from selecting the right licensing route and jurisdiction to assessing sponsor and BaaS relationships and stress-testing exit and continuity risk. We coordinate the corporate, licensing, banking and compliance workstreams so that the structure you launch is one you can defend and one you can keep.

If you are weighing how to obtain dependable IBANs for your fintech, we would welcome a confidential conversation.