White label as a licensed service
In the first sense, a bank, an electronic money institution or a card issuer provides the regulated service, and a second company puts its brand on the app and the card. The customer's contract for the regulated part is with the licensed firm, which holds the funds and answers to the regulator.
The brand owner usually acts as an agent, a distributor or a programme manager. It reaches the market without a licence of its own, and in exchange accepts the licensed firm's rules, pricing and approval of what it launches.
White label as software
In the second sense, a vendor supplies a finished platform, such as a banking app, an exchange or a payment gateway, and the buyer operates it under its own brand, design and domain. No licence comes with the software: the operator holds its own authorisation or arranges a licensed partner separately.
What varies is depth. Some products allow a logo and colours on a shared system, and others are deployed for one operator, with its own configuration, integrations and data.
What white label changes for a company launching a product
White label trades control for time. A launch is faster and cheaper than a build, and the questions move to the contract: who owns the customer relationship and the data, what can be changed, what happens on exit, and who answers to the regulator for each function.
The brand on the screen does not change who the regulated provider is, and the terms a customer accepts name that firm.
White label, banking as a service or custom build?
- Banking as a service
- A licensed firm's accounts, payments and cards offered through APIs for another company to build on. White label in the first sense, often without a ready-made app.
- Custom build
- Software written for one company, which owns and maintains it. Slower and costlier, with full control over every decision.
- Embedded finance
- A financial service placed inside a non-financial product. The term says where the service appears, not who built or licensed it.
Where white label shows up in a platform
Modules that do the work
- BackofficeOne console to run the platform: customers, money, risk, content and staff permissions.
- Card issuingVirtual and physical cards, wallets and controls, on the issuer processor you choose.
- Accounts & IBANsCustomer accounts with their own IBANs, on the partner bank and the rails you choose.
- LedgerThe double-entry book of record behind every balance, fee and transfer.
Platforms that need it
Guides that go deeper
- White-label vs custom fintech platform: build, rent or buyCustom build, SaaS licence or white-label with the source code: how the three routes compare on time, cost, ownership and lock-in, and the outsourcing rules regulators apply to each.
- White-label crypto banking: the software, the two licences and who holds whatHow a crypto banking app works: an IBAN account, crypto wallets, conversion and a card, the two licences behind them, who holds the money and the coins, and SaaS, API or source code.
- How to launch a neobank without a banking licenceYour own e-money licence, an EMI's agent, a partner bank or a bank licence: how each route works, who holds the money, and what safeguarding and deposit protection cover.