Launching a bank takes years and capital most founders do not have. Launching something that behaves like a bank takes weeks, because the licence and the core belong to somebody else.
That is the whole idea behind white-label neobanking. What follows is what you actually get, what stays outside your control, and when the model stops making sense.
Contents
- What you are actually buying
- What the platform includes
- Where the licence draws the line
- How long a launch takes
- What it costs
- Your own BIN or the provider’s
- Where neobanks earn
- When the model does not fit
- What to check in a provider
- Who launches neobanks, and why
- The path from decision to launch
- Short answers
- Where to start
What you are actually buying
A banking product under your brand: accounts with IBANs, cards, transfers and an app. The licence, the ledger and the compliance perimeter come from the provider.
You own the brand, the customers, the pricing and the margin. You do not own the permission to hold client money — that stays with the licensed institution behind you.
For most launches that trade is the point. Building the other half means a banking licence, capital requirements and a compliance department.
What the platform includes
- Accounts — personal and business euro IBANs, multiple currencies
- Payments — SEPA and SWIFT outbound, instant transfers between your own customers
- Cards — virtual and physical, issued on your BIN or the provider’s
- App — mobile and web under your brand, or your own build on the API
- Compliance — KYC, AML, transaction monitoring, reporting and audit trails
- Back office — customer management, limits, fees, reconciliation
Where the licence draws the line
The provider’s rules apply to your customers. Who can be onboarded, which countries are accepted, which activities are excluded — none of that is yours to redefine.
Check this against your target audience before design work starts. A neobank aimed at an audience the licence does not cover is a project that dies after the build.
Ask for the restricted list in writing at the first meeting. It is the single most useful document in the whole process.
How long a launch takes
In the cloud, two to four weeks for the technical side. On your own infrastructure, two to three months depending on customisation.
The real timeline is set elsewhere: company documents, the compliance questionnaire, and decisions about your product that nobody has made yet.
Teams that have those ready launch in weeks. Teams that start them after signing launch in months.
What it costs
Three parts: a setup fee, a monthly platform fee, and a share of transaction volume. Card issuing, crypto and advanced risk tooling are priced on top.
The monthly fee starts before your first customer does. That is the number to model against your acquisition plan, not the percentage.
Your own BIN or the provider’s
On the provider’s BIN you launch faster and cheaper, with no scheme agreement of your own.
Your own BIN gives freedom over pricing and rules, at the cost of certification, a direct scheme agreement and months of lead time.
At launch the provider’s BIN is almost always the right answer. Revisit it when volume justifies the overhead.
Where neobanks earn
Interchange on card payments, subscription fees for premium tiers, and the spread on currency conversion.
Understanding this matters, because it decides your own pricing. A free account that earns nothing from either interchange or conversion is a cost centre with users attached.
When the model does not fit
If you need lending, deposits or anything requiring a balance sheet, white label will not get you there. That is a licensed bank’s business.
If your audience sits outside the provider’s permitted markets, no amount of product work will fix it.
And if you have no users yet, the monthly fee arrives before the revenue. Validate demand first.
What to check in a provider
- Which licence covers you and in which countries it is valid
- Where client funds are held and whether they are segregated
- The restricted activities and markets list, in writing
- Whether API documentation is public before you sign
- Exit terms: data export, card tokens, notice period
Who launches neobanks, and why
Four patterns come up again and again, and they want different things from the platform.
Fintech startups. A first product, usually aimed at a niche the large banks serve badly: freelancers, a diaspora, a profession. They need speed and a low entry cost more than anything.
Companies with an existing audience. A marketplace, a telecom, a retail chain. The customers already exist; accounts and cards are an added service rather than the product itself.
Crypto platforms. They need fiat rails next to the crypto side, so users can move between the two without leaving.
Payment businesses expanding. An acquirer or a PSP adding accounts and cards to what it already sells.
The path from decision to launch
- Define the audience and the market. This decides which licence you need, so it comes first, not after the design
- Check the restricted list. Make sure your audience is actually permitted before anything is built
- Agree the product scope. Accounts, cards, currencies — each module carries a monthly cost
- Company documents and compliance questionnaire. The longest item, so start it in week one
- Integration and testing. Sandbox access, scenarios, edge cases
- Pilot with real users. A small group before the public launch
The order matters more than the speed. Teams that build first and check the licence later rebuild.
Short answers
Will my customers know it is not my own bank?
The brand is yours
throughout. The licensed institution is named in the terms, as regulation requires.
Can I move to my own licence later?
Yes, and some do once volume
justifies it. Plan for it in the contract rather than discovering the exit terms later.
Who handles customer support?
You do, for everything your customers
see. The provider supports you, not them.
What happens if the provider closes?
Client funds are segregated at
a partner bank, not on the provider’s balance sheet. Ask how that is arranged and get it
in writing.
Where to start
Describe the market, the product and where your customers come from. We will say which parts you need and which you can skip.
The platform and the commercial model are described on the white label page.