Neobank Launch: The Regulatory Pathway Explained

The word "neobank" suggests a clean, app-first banking experience built from scratch. The reality behind the interface is rarely so clean. Almost every neobank rests on a particular regulatory architecture, and the choices made there determine what the business can offer, how fast it can launch, how much capital it consumes and how durable it will prove.

The most consequential decision a founder makes is not the brand or the app design. It is the regulatory pathway: whether to obtain a licence directly, to build on top of a licensed partner, or to combine approaches over time. Each route carries a different balance of cost, speed, control and risk.

This guide maps the principal pathways to launching a neobank and the obligations that follow whichever you choose. The specifics differ by jurisdiction, so treat the structure here as a framework to apply with local advice rather than a single rulebook.

First, define what your neobank actually does

Before choosing a pathway, it helps to be precise about the activities. "Banking" in common usage bundles together several regulated functions that are treated very differently in law.

Holding customer money and providing payment accounts and IBANs is one function. Issuing cards is another. Lending, including overdrafts and consumer credit, is a third, often the most heavily regulated. Taking deposits in the legal sense, where customer money becomes the institution's own and is protected by a deposit-guarantee scheme, is the function that genuinely defines a bank and triggers the most demanding requirements.

Many products marketed as neobanks are not banks at all. They are payment or electronic money businesses offering accounts, cards and payments, sometimes partnering with a licensed bank for the deposit-taking and lending elements. Clarifying which functions you truly need is the first and most clarifying step, because it narrows the viable pathways.

Pathway one: your own banking licence

Obtaining a full banking licence gives the most control and the broadest permissions, including deposit-taking and lending, and it allows the business to own its customer relationships and infrastructure outright.

It is also the hardest path. Banking authorisations demand substantial capital, an experienced board and management team, sophisticated risk and capital management, extensive systems, and a long, intensive engagement with the regulator. The timelines are measured in many months to years, and supervisory scrutiny continues throughout the institution's life.

For most early-stage founders this route is premature. It tends to suit well-funded ventures with seasoned banking leadership and a clear case for deposit-taking and lending at scale. We generally advise founders to be honest about whether they need a bank or merely want the label.

Pathway two: an EMI or payment institution licence

A middle path is to obtain an electronic money institution or payment institution licence. This permits payment accounts, IBANs, transfers and card issuance, and in the European framework allows passporting across the single market from one authorisation.

The capital and substance requirements are materially lighter than for a bank, while still demanding genuine governance, a real compliance and money-laundering reporting function, safeguarding of customer funds, and a credible business plan. Crucially, an EMI or payment institution cannot take deposits in the banking sense and must safeguard customer money rather than lend it freely.

For a large share of neobank propositions, those focused on accounts, payments and cards rather than deposit-funded lending, this pathway offers the best balance of capability, cost and control. Where lending is part of the plan, it is often delivered through a separate credit permission or a partner.

Pathway three: build on a licensed partner

The fastest route to market is to build on top of someone else's licence, operating as an agent, distributor or programme manager of a licensed bank or EMI, frequently delivered through banking-as-a-service APIs.

This lets a founder launch branded accounts, cards and payments without holding the licence directly. The trade-off is dependency: the regulatory perimeter, and often the customer funds and IBAN range, sit with the partner. Compliance obligations still flow to the programme manager contractually, and the partner can audit, constrain or, in adverse circumstances, terminate the programme.

The build-versus-rent decision is rarely permanent. Many successful neobanks launch on a partner to prove the model, then pursue their own licence once volume and capital justify the investment and the dependency risk becomes uncomfortable. Designing for that eventual migration from the outset is wise.

The obligations that follow every pathway

Whichever route you choose, a common spine of obligations applies, varying in intensity rather than in kind.

Capital and prudential requirements. Licensed entities must hold initial capital and maintain ongoing own funds. The amounts differ sharply between a bank and an EMI, and the calculation methods evolve, so we confirm the current position with the relevant regulator at planning stage.

Safeguarding and protection of customer funds. Non-bank models must keep customer money segregated and protected from the firm's creditors. Banks operate under deposit-guarantee schemes instead. How customer money is held and reconciled is a central supervisory concern in every model.

Anti-money-laundering and sanctions controls. Risk-based onboarding, ongoing monitoring, sanctions screening, transaction monitoring and suspicious-activity reporting are non-negotiable. For programme managers on a partner's licence, these duties flow through contractually and are actively policed by the partner.

Governance and substance. Regulators and partners expect real management, experienced compliance leadership and genuine local decision-making. Nominal arrangements no longer pass.

Consumer protection and conduct. Clear terms, fair treatment, complaint handling, transparent fees and resilient operations all attract scrutiny, particularly as a neobank scales into the mass market.

Sequencing the launch

A pragmatic neobank plan usually unfolds in phases. Define the precise activities and target market; choose the pathway that fits the activities, capital and risk appetite; secure the licence or partner and the supporting banking and safeguarding arrangements; build compliance as a core capability rather than an afterthought; and plan in advance for the migration or upgrade you may want later.

The most common failure mode we see is choosing a pathway based on launch speed alone, without weighing continuity, control and the cost of unwinding a dependency. The cheapest route to launch is frequently the most expensive route to scale.

How HPT helps

We help founders translate a neobank vision into a defensible regulatory structure, clarifying which functions are genuinely needed, comparing the licence and partner pathways, selecting jurisdictions, and coordinating the corporate, licensing, banking, safeguarding and compliance workstreams. Where a phased approach makes sense, we help design a launch that can grow into its own authorisation rather than being trapped by early shortcuts.

If you are planning a neobank and want clarity on the right regulatory pathway, we would welcome a confidential conversation.