How to Launch a Neobank: White Label, BaaS, or Custom Build

Introduction

Updated September 28, 2026.

To launch a neobank, a company defines its target customers and revenue model, chooses how to get the technology (build it from scratch, assemble it on top of BaaS APIs, or start from a white label neobank platform), connects payment, card and KYC providers, tests every money flow end to end, and goes live with support in place. The technology route shapes the timeline, the budget and how much of the product the company controls after launch. In ilink's 1ndex neobank case, starting from a ready modular platform reduced the launch timeline from the traditional 12–18 months to 2–4 months.

This guide compares the routes side by side, lists what a neobank platform has to include, walks through the launch step by step and collects the mistakes that most often slow a launch down.

What Is a Neobank and How Does It Work?

A neobank is a financial company that serves customers only through digital channels, a mobile app and a web platform, without physical branches. Customers open an account, verify their identity, hold balances, send payments and manage cards in the app, while the company runs the product from a back office.

Behind the app, a neobank works as a set of connected modules, each responsible for one part of the product:

• customer onboarding with KYC/KYB verification;

• multi-currency accounts, IBAN and balances;

• payments and transfers, such as SEPA and SWIFT;

• a card module for virtual and physical cards;

• crypto accounts and payments, if the product also serves Web3 users;

• tariffs, commissions and limits;

• a back office for users, accounts, transactions and settings;

• web, iOS and Android apps for customers.

At the center sits the core banking system. It keeps accounts and balances, processes transactions and applies products, tariffs and limits; customer apps, payments and compliance tools all work on top of it. For a broader introduction, see our guide on what a neobank is and how digital-only banks work.

How Do Neobanks Make Money?

Neobanks earn on transactions and services: card interchange fees, premium account subscriptions, interest on loans, currency exchange and international transfer fees, crypto trading fees and commissions from partner products.

• Interchange fees. Every card purchase brings the neobank a small fee from the merchant's side. It is small per transaction but adds up across a large customer base.

• Account fees. Some neobanks keep a basic account free and charge a monthly fee for premium plans with extra features.

• Lending. Loans and credit cards bring interest and fees.

• Currency exchange and international transfers. Fees for converting currencies and for cross-border payments; some neobanks charge them only above a set limit.

• Crypto trading. Fees for trading and exchanging cryptocurrencies.

• Referral and partnership programs. Commissions for referring customers to insurance, investment or other partner services.

For the platform, this means the revenue model has to be configurable in the back office: tariffs, commissions, limits and exchange spreads are set for each product and customer segment. In ilink's VABS core banking platform, for example, the monetization tools include smart tariffs, commission matrices, discount and cap rules, tariff inheritance, rate aggregation, spread management and slippage control. A detailed breakdown of each revenue stream is in our guide to how digital banks make money.

Three Ways to Launch a Neobank: Custom Build, BaaS, or White Label

There are three routes to the technology behind a neobank: build every layer from scratch, take banking services from a Banking-as-a-Service (BaaS) provider through APIs and build the product around them, or start from a ready white label platform and adapt it to your brand. White label platforms are delivered either as a service or with the source code, so in practice the choice is between four options.

When a Custom Build Makes Sense

A custom build fits when the product itself is the differentiator and you need to own every layer, from the ledger to the apps. The price is time and budget: the team builds payment routing, onboarding, the core, the back office and the apps before the first customer arrives. The team can be in-house, which gives more control but requires investment in recruitment and training, or hired from an IT vendor that brings fintech experience and pre-built components.

When BaaS Fits

BaaS fits when the banking services you need are standard and your value is in the customer experience. BaaS providers supply accounts, cards and payments through APIs; your team still builds the apps, the back office, tariffs and compliance workflows around them. When comparing providers, check how they handle compliance, whether they scale with your customer base, how far their features can be customized, which integrations they support and what support and uptime they guarantee. Also check whether every feature you plan is available through the provider's API or only through partners that are not integrated yet.

When a White Label Platform Fits

A white label platform fits when you need a standard neobank feature set under your own brand and want to get to market quickly. Accounts, payments, cards, onboarding, apps and the back office are already built, so your team spends its time on the brand, tariffs, integrations and distribution. Typical tasks it covers: launching a neobank under your brand, adding multi-currency and crypto accounts, running cards and mobile apps, managing clients, tariffs and limits, and building a product that serves both Web2 and Web3 users. One thing a platform does not replace is the people who run compliance day to day: it provides KYC/KYB and AML-ready workflows, but reviewing alerts and making onboarding decisions stays with your team.

SaaS or Source Code: Who Owns the Product

White label platforms come in two delivery models. With SaaS/PaaS, the vendor runs the infrastructure, which is the fastest route to an MVP. With a source code license, you receive the code itself: on-premises deployment, no vendor lock-in and full control over how the product scales.

The difference shows up later, not at launch. When a neobank depends on a single vendor, switching becomes costly and slow, and the vendor gains pricing power. Before signing, ask any vendor five questions:

1. Can we change ledger rules, workflows and integrations ourselves?

2. Can we replace the KYC provider, payment provider or card issuer without rewriting the core?

3. Who holds the ledger data, and can we export customer, transaction and audit records?

4. Which products are already live on the platform, not only in a demo?

5. What will the platform cost over three years, not only in year one?

ilink's white label neobank platform is available both ways: SaaS/PaaS for a fast MVP, or under a Source Code License for companies that need full control.

Weighing white label against a custom build?

ilink can walk you through the working 1ndex platform, delivered as SaaS/PaaS or under a Source Code License.

Request a Demo

What a Neobank Platform Includes

A neobank platform includes customer apps, a core that keeps accounts and processes transactions, payment and card modules, compliance and security tools, and a back office where the team runs the product. Here is what each layer covers, using ilink's 1ndex neobank and VABS core banking platforms as the reference.

Accounts, Payments and Financial Products.

1ndex covers multi-currency accounts, IBAN and SEPA/SWIFT routing on a core that manages users, accounts, balances, tariffs, commissions and limits. The VABS core adds a payment engine with nine payment scenarios: SWIFT, SEPA, BSB, IFSC, internal transfers, B2B, P2P, recurring and bulk payments, with cascading limits. Underneath is a core ledger with synthetic and analytical accounts, multi-currency accounting and automatic reconciliation. The same core supports deposit products, automated underwriting, lending schedules and overdue control. More on this layer is on our white label core banking platform page.

Cards.

The card module works in the same back office as accounts and transactions. In VABS it covers virtual and physical cards, PIN management, velocity limits, card freezing and territorial restrictions.

Onboarding, Compliance and Security.

1ndex includes KYC/KYB verification flows, AML-ready processes, 2FA, granular admin roles, configurable limits and tools for fraud and operational risk control. VABS adds Maker-Checker approval logic, sanctions screening, PEP and adverse media checks, periodic rescreening, KYT monitoring, real-time alerts, scoring models and temporary blocking of suspicious activity.

Crypto and Web3.

Custodial and non-custodial modules, crypto processing, invoice generation, crypto payments and blockchain integrations run alongside fiat accounts. A customer's accounts, cards and crypto balances live in the same app, and the team manages all of them from the same back office.

Apps and Back Office.

1ndex comes with ready web interfaces, native iOS and Android apps and a unified back office for users, accounts, transactions, notifications, fees, limits and business settings. VABS adds a 360° client view, support tickets, mass onboarding through XLSX/CSV and an agent network with invite links and automated rewards.

APIs for Embedded Finance.

A BaaS API lets a company embed accounts and payments into a product it already runs. 1ndex is built API-first, so modules can be added as the product grows.

How to Launch a Neobank Step by Step

A neobank launch goes through eight steps: define the audience, choose the revenue model, pick the technology route, fix the MVP scope, set up providers, configure the product and compliance workflows, test every flow, then launch and support. On a ready platform, the launch timeline in ilink's 1ndex case is 2–4 months, compared with the traditional 12–18.

1. Define Your Audience and Value Proposition.

Decide who the neobank is for and what problem it solves that existing banks do not: freelancers, small businesses, students, underserved communities or crypto users. The audience defines the features. A neobank for freelancers, for example, needs invoicing tools and automated tax savings. Study the neobanks already serving that segment, their features and their weak spots.

2. Choose the Revenue Model.

Decide how the product will earn: subscriptions, transaction fees, card interchange, currency exchange or lending. The model defines which modules and tariff settings you need on day one and which can wait.

3. Pick the Technology Route.

Choose between a custom build, BaaS and a white label platform, and, for white label, between SaaS/PaaS and a source code license (see the comparison above). The route affects the timeline, the budget and how much of the product you control after launch.

4. Fix the MVP Scope.

Write down which features are must-have for launch and which are nice-to-have for later phases. Going to market with an MVP and adding products afterwards is the fastest way to revenue. Agree on the list with your partners early: changing requirements in the middle of implementation is a common cause of delays.

5. Select Providers and Plan Integrations.

List the banking, payment, KYC and crypto providers the product will connect to, and check that each feature you need is available through their APIs. A white label platform connects to the providers you choose; with a custom build, your team writes each integration itself.

6. Configure the Product and Compliance Workflows.

Apply your brand to the web and mobile apps, then set up tariffs, limits, commissions, roles and payment scenarios in the back office. Build compliance in parallel with the product, not after it: KYC rules, monitoring thresholds, approval flows and alerts written after the features ship lead to rework.

7. Test Every Flow End to End.

Test payments, onboarding, roles and limits end to end, together with reconciliation and reporting. A neobank handles money, so every transaction must add up in the ledger before real customers arrive.

8. Launch, Support and Scale.

Launch the web, iOS and Android apps and the back office. After launch, monitor performance, set up support channels such as chat, email or phone, collect user feedback and ship regular updates. Plan the next modules, products and markets early, so that adding them does not require rebuilding the core.

Planning your neobank launch?

ilink can show you the platform and discuss which modules fit your launch.

Leave a request

Common Mistakes When Launching a Neobank

Most launch delays come from decisions made too late: a scope that keeps changing, compliance left for later and no plan for the day a provider changes its terms. These are the mistakes that come up most often:

1. Choosing software before deciding how much control you need. A platform picked for its demo may not let you change a payment provider, card issuer or market rules without a rewrite.

2. Changing the scope during implementation. Agree on a must-have list for the MVP before implementation starts: changes to requirements after the partners have aligned lead to delays.

3. Treating compliance as phase two. KYC and AML rules written after the features are built lead to rework before launch.

4. Leaving reconciliation until after launch. The first customers expose gaps in the ledger faster than any feature checklist.

5. Counting only year-one costs. Per-transaction provider fees, compliance staff and the cost of migrating to another provider appear in years two and three.

6. Having no exit plan. If you cannot say what happens when a provider raises prices or ends the relationship, you are buying launch speed, not a platform.

7. Targeting everyone. The target segment is one of the first decisions, and it should follow research of the market: product-market fit depends on it.

8. Not planning for new markets. Expanding to another geography later means repeating KYC, reporting and data storage work if the architecture was built for one market only.

Why Launch Your Neobank with ilink

ilink has 14 years of experience and 60+ IT specialists, and starts neobank projects from its own platforms rather than from an empty repository.

• 1ndex neobank. In the 1ndex case, the launch timeline was reduced from the traditional 12–18 months to 2–4 months. Fiat banking, crypto operations, payment processing and Web3 tools run on one infrastructure, with ready web, native iOS and Android apps and a unified back office. Delivery as SaaS/PaaS or under a Source Code License reduces vendor lock-in.

• VABS core banking. A white label core ledger and back office, with deployment measured in weeks instead of long custom development timelines, in the cloud or on-premise. The platform is designed to support different financial models, including classic banking and Sharia-compliant banking.

• Adaptation to your product. ilink's team handles branding and UI/UX design, adapts the mobile apps, builds custom modules, connects banking, payment, KYC and crypto providers, and supports and scales the product after launch, including with a dedicated team.

See the white label neobank platform, the white label core banking platform and the 1ndex case study.

FAQ

How can I start my own neobank?

Define your target customers and revenue model, choose the technology route (custom build, BaaS or a white label platform), fix the MVP scope, connect payment, card and KYC providers, configure the product, test every flow and launch with support in place. Starting from a white label platform shortens the technical part: in ilink's 1ndex case, the launch timeline is 2–4 months instead of the traditional 12–18.

How long does it take to launch a neobank?

It depends on the route. A traditional custom build takes 12–18 months, while ilink's 1ndex white label platform reduces the launch timeline to 2–4 months. The exact timeline depends on the modules and integrations the product needs.

Should I build a neobank from scratch or use a white label platform?

Build from scratch if the product itself is unique and you need to own every layer and can afford a long build. Choose a white label platform if a standard feature set is enough and speed matters. If you need both speed and control, take a white label platform under a source code license: you get the code, on-premises deployment and no vendor lock-in.

How does a neobank make money?

Neobanks earn on transactions and services: card interchange fees, premium account subscriptions, interest on loans, currency exchange and international transfer fees, crypto trading fees and commissions from partner products. The platform has to let the team configure tariffs, commissions and limits for each product and customer segment.

What does a white label neobank platform include?

Customer web, iOS and Android apps, a core that keeps accounts and processes transactions, multi-currency accounts and IBAN, SEPA and SWIFT payments, a card module, KYC/KYB and AML-ready workflows, and a back office for tariffs, commissions and limits. Some platforms, such as ilink's 1ndex, also include crypto modules and a BaaS API for embedded finance.

Can a white label neobank platform integrate with existing systems?

Yes, if it is built API-first. ilink's platforms connect to payment providers, KYC and screening vendors, blockchain infrastructure and a company's internal systems, and 1ndex includes a BaaS API for embedding accounts and payments into an existing product.