A neobank is a customer experience wrapped around someone else’s licence — until it is not. The initial product usually runs on a partner bank, and the strategic question is whether that is a step toward your own authorisation or the permanent shape of the business.
Both are legitimate. What is not legitimate is drifting into the partnership without understanding what you have given up: control of onboarding, control of pricing, and a product roadmap bounded by your partner’s appetite and technology.
We design the model deliberately — partner or own licence, which BaaS or sponsor, how accounts and cards actually work, how customer funds are safeguarded, and whether the unit economics support the growth plan once interchange and partner costs are counted.
- You are launching a digital account or card product and have not settled how it is licensed or banked.
- Your BaaS partnership is constraining the roadmap or the pricing you need.
- You want to migrate from a partner model to your own authorisation and need the pathway.
- Account economics look attractive per user but the model does not fund growth.
Partner or own licence is a strategy decision
The partnership route is faster and cheaper; the owned route is slower and gives you control. Choosing without understanding the trade is how neobanks get stuck.
Safeguarding is not a footnote
How customer funds are held, and under what legal arrangement, is the foundation of the whole product. It is also the first thing a regulator examines.
Unit economics decide survival
Interchange, partner fees, card costs and servicing expense have to leave a margin. A beautiful product with negative contribution per account is not a bank.
- Partner-versus-own-licence analysis with the sequencing and cost of each
- BaaS, sponsor-bank and card-processor selection, including dependency and exit analysis
- Account, card and payment product architecture within the permissions you hold
- Safeguarding and client-money model, with the legal basis documented
- Unit-economics model — interchange, partner fees, servicing and acquisition
- Licensing roadmap and application support where the owned route is chosen
- 01
Define the product and the customer
What the account actually does, who holds the funds, who takes the credit risk, and what the customer is promised. The regulatory answer follows from those facts.
- 02
Choose the operating model
Partner licence, own licence, or a staged path from one to the other — settled with the economics and the control trade-offs explicit.
- 03
Design safeguarding and flow
Where customer money sits, how it is protected, and how it moves between the partner, the processor and you.
- 04
Model the economics
A per-account contribution model built on real interchange and partner pricing rather than hopeful assumptions.
- 05
Launch and, if planned, migrate
Go-live support, then the licensing and migration workstream if the strategy is to own the authorisation.
Model and economics review
A written assessment of partner-versus-own, the safeguarding design and whether the unit economics hold.
Launch programme
Partner selection, product architecture, safeguarding and compliance run through to go-live.
Own-licence pathway
Licensing, capital and substance planning for the migration from a partner model to an owned authorisation.
- Products with no credible path to positive contribution per account at any realistic scale.
- Teams that want the branding of a bank without the safeguarding, reporting and capital obligations that come with one.
Yes — it is a distribution and experience business on top of a licensed partner, and many successful products work that way. What it is not is a bank, and the constraints matter: you will not control onboarding, pricing or the roadmap completely, and you carry concentration risk on a single partner.
When the constraints of the partnership cost more than the licence would — typically when you need control of pricing, a broader product set, or a valuation that reflects owning the regulated business. The right time is usually planned a year or more in advance, because licensing and migration are slow.
Customer funds are held in a way that protects them if the firm fails, typically in segregated accounts or under a safeguarding arrangement, with reconciliation and reporting. The exact regime follows the licence; the principle is that customer money is not the firm’s money.
Rarely. Interchange is a component of the economics, not the whole of them. Products that survive usually add subscriptions, FX margin, lending or business services — which is why the product roadmap and the licence have to be planned together.