
OUR TEAM
Diana
Senior Associate
Structuring and first steps Response within 24 hours
“Hello, my name is Diana. Get in touch, and I'll help you with your enquiry promptly.”
White Label Banking allows you to offer clients accounts, payments and cards under your own brand using a licensed provider's infrastructure. Regulated United Europe (RUE) helps you choose a model for the EU and the United Kingdom, verify the partner's permissions, agree contracts and prepare the service for launch. The solution combines a software platform with agreed financial services provided by a bank, electronic money institution (EMI) or payment institution (PI). The provider retains its licence. Whether you can operate without your own authorisation depends on your company's functions and the target market.
Prepared by the RUE editorial team · Updated 11 November 2026
White Label Banking suits companies that want to add financial services to an existing product using a partner's infrastructure. This may reduce the amount of in-house development and launch preparation required. Branding, the interface and client service are tailored to the project within the provider's capabilities.
When choosing a partner, monthly payments, transaction fees, product restrictions and advertising approval procedures must be considered. RUE compares offers by total budget and operating terms, including data access and the ability to change providers.

OUR TEAM
Diana
Senior Associate
Structuring and first steps Response within 24 hours
“Hello, my name is Diana. Get in touch, and I'll help you with your enquiry promptly.”
Payment accounts with individual account details and transfers included in the provider's package.
Virtual and physical cards through the issuer's card programme.
A branded client interface and back office for your team.
Accounts and payments are handled by a bank, EMI or PI. We verify its permissions before signing.
White Label Banking is a model for providing a financial service under the customer's brand using a partner's platform and regulated services. Clients interact with your interface, while accounts, payments and cards are serviced by the authorised companies identified in the agreement. Rights relating to technology, data and client relationships are determined by the agreement and the law.
White Label means branding an existing product. Banking as a Service (BaaS) describes access to a provider's financial functions, usually through APIs. Embedded finance means integrating these functions into another product: a marketplace, accounting software or a delivery service. A single project often combines all three. Each participant's legal status is determined by its actual functions and permissions.
|
Provider |
What it may offer |
What matters |
|---|---|---|
|
Bank |
Bank accounts and products under the agreement |
The bank services the account and deposit; deposit protection depends on the product, client and relevant scheme's terms |
|
EMI |
Electronic money and permitted payment services |
Funds are protected through safeguarding, not deposit protection. The brand does not acquire bank status |
|
PI |
Payment services and accounts used to provide them |
A PI cannot independently issue electronic money or accept deposits; available payment services depend on its authorisation |
The term “neobank” describes a digital financial product, but does not, by itself, establish that a banking licence is held. The name, advertising and service descriptions must not misrepresent the company's status. The permissibility of using “bank”, “banking” and related terms is checked for each target market before the brand is approved.
|
Audience |
Typical use case |
|---|---|
|
Fintech companies |
Accounts, payments and cards in their own app |
|
B2B platforms |
Payments to counterparties and expense management |
|
Marketplaces |
Seller payouts and tracking funds by user |
|
Companies with international payments |
Multi-currency accounts and foreign exchange |
|
Services for freelancers |
Receiving payments, cards and withdrawals |
|
Projects with an existing client base |
Financial functions as an additional service |
Cryptocurrency, Forex and gambling projects undergo a separate assessment. Whether they can be served depends on permissions, the provider's risk policy and target market requirements.
Our support results in an agreed launch model: the provider, permitted countries and client categories, functions, contractual terms, budget and setup sequence. Signing agreements and launching depend on the provider's approval of the project and completion of the necessary procedures.
Before setup, rights to the brand, domain and interface, and access to client data and reporting are defined. These terms affect day-to-day service management and future migration.
Wallester pricing example:
EUR 2,495 per month
Published card programme fee for non-financial companies, with no setup fee; the complete package is quoted individually
RUE's support is quoted separately. Scope of work:
The scope depends on the project and is specified in the proposal. A feature shown in a platform presentation may not be available to your project: much depends on the market, client type and provider approval.
|
Component |
What is included |
|---|---|
|
Project analysis |
Countries, B2B or B2C, products, currencies, volumes and the brand owner's role |
|
Provider selection |
Bank, EMI or PI; legal entity, permissions, territory and permissibility of the model |
|
Legal arrangements |
Agreements, client terms, allocation of functions and agent status where required |
|
Platform and branding |
Web portal, design, domain and languages; mobile app depending on the package |
|
Accounts and wallets |
Account type, currencies, recipient of funds and limits; individual or virtual account details |
|
Payments |
Payment systems, destinations, timeframes, fees and restrictions |
|
Card programme |
Issuer, BIN sponsorship, virtual and physical cards, limits and servicing |
|
KYC/KYB and AML |
Individual and corporate checks, sanctions, monitoring and request handling |
|
Back office and API |
Client management, roles, reporting, integrations and transaction reconciliation |
|
Launch and support |
Testing, training, allocation of support responsibilities and incident management |
A virtual IBAN may be used to route and track payments without opening a separate bank account in the client's name. Before launch, it is important to establish the account's legal structure, its holder, the servicing institution and how funds are recorded. Available currencies and account details are specified in the proposal.
IBAN details may also be provided as part of EMI or PI services. Having an IBAN does not, by itself, establish that the provider is a bank.
SEPA, SEPA Instant, SWIFT and local transfers are connected according to the selected package's capabilities. For a UK project, GBP account details and access to Faster Payments or Bacs are checked separately. The agreement discloses the parties in the payment chain, timeframes, limits, FX markups, refunds and procedures for correcting erroneous payments.
For cards, we agree the types and design, issuance, delivery, replacement, blocking and disputed transactions. Apple Pay and Google Pay are not available in every programme, and app store publication requires separate approvals.
|
Option |
In the basic package |
Conditions |
|---|---|---|
|
Additional currencies and markets |
As agreed |
Provider permissions and separate assessment |
|
Separate mobile apps |
As agreed |
Design, publication and support quoted separately |
|
Bulk payouts |
Depends on the package |
Limits, recipient checks and fees |
|
Corporate limits and expense management |
Depends on the package |
Roles, card limits and reporting |
|
Accounting system integrations |
As agreed |
Scope and cost based on the specification |
|
Additional APIs |
Depends on the package |
Access, security and support |
|
Client migration |
As agreed |
Grounds for data transfers, account and card transfers |
Lending, overdrafts, interest-bearing deposits, investment services and crypto services are not automatically included in a payment programme. Each product requires a separate assessment of its legal basis, the provider's permissions and setup terms; it may be provided by the same partner or another authorised company.
Specify the target market, client categories and required functions. RUE will assess available models and prepare provider options for comparison.
A specific bank, EMI or PI provides the regulated services, while you perform the functions permitted under your role. This is what advertising means by “licence included”. There is no licence rental or transfer.
Whether your own licence is required depends on the company's actual activities and market rules. The following roles are possible in a partnership model:
Tied agent and appointed representative statuses are familiar to those who have worked with investment firms, but do not apply to payment services. If actual activities go beyond the chosen role, the model must be changed or the necessary permissions obtained.
A payment agent acts on behalf of a PI or EMI and must be registered under the applicable regime. A distributor distributes or redeems electronic money on behalf of an EMI but does not issue it independently. There is no universal registration requirement for distributors identical to that for agents: national rules, actual functions and cross-border notifications must be checked. Providing payment services requires a separate legal basis.
If the provider is a UK PI or EMI, it must first register you as an agent in the FCA's Financial Services Register before you start operating. This is not appointed representative status under investment regulation. The agent acts on behalf of the principal, not as an independent provider. A model involving a bank is assessed separately.
The client signs the financial services agreement with the regulated provider. The documents must explain who provides which services, what they cost, where to complain, who processes the client's data and how to close the account. Your role as the interface owner is also described.
Protection of funds depends on the product type, provider status and applicable rules. A bank deposit and an e-money balance have different protection mechanisms.
|
Bank |
EMI / PI |
|
|---|---|---|
|
What the client holds |
Bank deposit |
Electronic money or funds for a payment |
|
Protection mechanism |
Deposit guarantee scheme |
Safeguarding: segregation of relevant funds or permitted insurance/guarantee |
|
EU |
For eligible deposits and clients, within the limits of the relevant scheme |
Deposit protection does not apply |
|
United Kingdom |
FSCS for eligible deposits, within applicable limits |
FSCS does not cover electronic money or payment balances |
Safeguarding does not guarantee immediate repayment in full if the provider becomes insolvent. The mandatory safeguarding requirements for UK small payment institutions differ from those for authorised PIs. The specific company's status and the method used to protect the relevant funds must therefore be checked.
Before launch, we establish where funds are recorded, who is responsible for protecting them and what happens if an account is blocked, the provider becomes insolvent or the programme closes. Under the partnership model discussed here, the brand owner does not use client funds to finance its own expenses.
Since Brexit, these are two separate markets with their own rules. Operating in both is possible where the permissions of the specific legal entities allow it. Companies within the same group have different licences, and a UK subsidiary does not serve clients under its European counterpart's licence.
We check the provider in its national regulator's register and, for an EMI or PI, in the EBA register as well. We establish the permitted services, countries covered by cross-border services and required agent notifications. A licence in one EU country does not, by itself, provide access to the others: the provider submits a passporting notification to operate in another member state.
The legal basis for operating in the UK must be established and the provider checked in the FCA Financial Services Register; a bank's banking permissions must also be verified. EUR or GBP accounts, UK account details and access to a payment system do not, by themselves, confer the right to attract clients in the United Kingdom.
Passporting between the United Kingdom and the EEA has ended. Serving both markets therefore usually requires different providers or separate legal entities within one group, separate agreements and separate onboarding. The brand may be shared, but each market has its own authorisations and protection of funds, and clients must be able to see this in the interface.
|
Factor |
EU |
United Kingdom |
|---|---|---|
|
Provider verification |
National regulator; EBA for EMIs/PIs |
FCA Register and banking permissions |
|
Agent model |
Registration and notifications under the applicable model |
Agent registration by the UK PI/EMI provider; bank model assessed separately |
|
Payment functions |
EUR, SEPA / SEPA Instant depending on the package |
GBP, UK account details, Faster Payments / Bacs depending on the package |
|
Protection of funds |
Bank regime or EMI/PI safeguarding |
Bank regime or EMI/PI safeguarding; do not confuse with FSCS |
|
Client documents |
Provider, markets, language, complaints and local requirements |
UK provider or another legal basis, terms and complaints procedure |
Available international transfer destinations depend on the package, sanctions restrictions and the provider's policy. Accounts for individuals and companies may be opened only for agreed countries and client categories.
For each market, we allocate roles under EU GDPR and UK GDPR and agree data transfers, authentication, API access and incident procedures. We assess operational resilience requirements for each participant. Platform certifications do not replace an assessment of each participant's compliance.
The provider first checks your company, then each of your clients. For the initial assessment, prepare:
Registration documents, ownership structure, directors and ultimate owners.
Information and documents on the source of funds for launch and operating costs.
Product, clients and revenue model.
EU, United Kingdom or both; B2B or B2C.
Number of accounts and cards, transaction volumes and payment destinations.
Acquisition channels and advertising materials.
Who is responsible for support and which compliance tasks remain with your company.
The public offers reviewed do not establish a comparable market average for a complete White Label Banking solution for the EU and UK. Packages differ by products, clients and regulated functions. Published indications and cost components are set out below; the final estimate is prepared for the EU, UK or both markets.
|
Service |
Indicative price |
Comment |
|---|---|---|
|
Wallester card programme for non-financial companies |
No setup fee; EUR 2,495 per month |
Published card provider fee; not the price of a universal banking package |
|
Wallester for financial companies / VASPs |
No setup fee; EUR 3,995 / 5,995 per month |
Different client categories; eligibility assessed separately |
|
Complete package for EU clients |
Individual pricing |
Accounts, payments, cards, platform, compliance and agent model |
|
Complete package for UK clients |
Individual pricing |
Verified UK provider, legal model and GBP functions |
|
EU and UK under one brand |
Consolidated estimate |
Separate regulated components, shared technology where possible |
These prices were published in Wallester's article on launching a White Label programme. The current product page invites requests for individual terms; prices are confirmed before signing an agreement.
Wallester states that it operates in the EEA and United Kingdom, but its advertised geographical coverage and pricing do not replace verification of the specific licensee and legal basis for UK operations. The current package, variable fees and availability for the project are confirmed in the proposal. This example does not imply a partnership with RUE.
When comparing offers, we consider the number of markets, client type (B2B or B2C), number of accounts and cards, payment destinations, projected volumes, included compliance services, mobile app and fees beyond the subscription. Prices are stated in the agreement's currency, EUR or GBP.
|
Item |
What to check in the estimate |
|---|---|
|
Client checks |
KYC/KYB, additional documents and repeat checks |
|
Accounts and payments |
Account fees, incoming and outgoing transfers, returns and investigations |
|
Cards |
Issuance, delivery, servicing, replacement, ATMs and transaction disputes |
|
Foreign exchange |
FX spread and conversion fees |
|
Integrations |
Non-standard APIs, new modules, app design and support |
|
Regulated services |
Minimum payments, revenue share, checks and operational functions |
|
RUE and other costs |
Legal support, agent procedures, staff, marketing and taxes |
Consider a hypothetical project in one market. This is not a provider quotation, a market average or an RUE offer. Setup costs EUR 25,000, and servicing costs EUR 3,500 per month. Fixed first-year costs are 25,000 + 12 × 3,500 = EUR 67,000.
If both the EU and UK are required from the outset, we prepare a new estimate: the second market is not included in the first, but the calculation is not simply double the amount either.
|
Package component |
What to specify in the proposal |
|---|---|
|
Setup |
Provider's project assessment, standard branding, portal and fee configuration, integrations, training and testing |
|
Monthly servicing |
Platform access, technical support and updates, back office, reporting and scope of regulated services |
|
Financial products |
Account types, payment destinations and card programme within the provider's permissions |
|
Restrictions |
Countries, B2B/B2C, currencies, number of accounts and cards, limits, support hours and languages |
|
Separate payments |
Transactions, checks, cards, FX, additional modules and RUE's services, if not included |
The proposal must also specify the agreement term, indexation, programme termination, return of funds and migration arrangements. Collateral, reserves and pre-funding are stated separately from expenses: they are neither client funds nor project revenue.
Revenue usually comes from subscription fees, markups on payments and currency conversion, paid plans and a share of card programme revenue where the agreement provides for it. Each provider has its own percentages and fees.
Project revenue consists of fees received and remuneration provided for in the agreement. Client transaction volumes and account balances are not the brand owner's revenue.
|
Step |
Who performs it |
Who decides |
|---|---|---|
|
Registration |
Brand (interface) |
Provider |
|
Identification |
Provider or brand under the agreement |
Provider |
|
Entering into the agreement |
Provider |
Provider |
|
Account opening |
Provider |
Provider |
|
Depositing funds |
Client, provider's payment infrastructure |
Provider |
|
Transfers and cards |
Provider, card issuer |
Provider and issuer |
|
Support and closure |
Brand handles first-line support; provider handles the rest |
Provider |
Outcome: Products, markets, audience and company functions defined
Outcome: Providers, permissions, terms and restrictions compared
Outcome: Documents, agent procedures and responsibilities agreed
Outcome: Platform, brand, APIs, accounts and cards connected according to the package
Outcome: Payments, reconciliation, KYC, support, security and incident handling tested
Outcome: Approvals obtained and operational functions allocated
The launch timeline is determined after the project assessment and includes company checks, agreements, required registrations, integration and testing. Technical readiness of the platform does not replace approval to start serving clients.
|
White Label |
Your own EMI / PI |
Your own bank |
|
|---|---|---|---|
|
Services |
Within the provider's permissions |
PI: permitted payments; EMI: also e-money issuance |
Banking services within permissions and the agreed model |
|
Initial costs |
Setup and platform |
Licence, capital, team and technology |
Highest |
|
Capital |
Collateral, reserves and project funding requirements may apply |
Required |
Required, substantial |
|
Timelines |
Determined by checks and integration |
Lengthy authorisation process |
Longest |
|
Control |
Within the agreement |
Within permissions, the law and agreements |
Within permissions, the law and agreements |
|
Ongoing obligations |
Contractual and agent obligations |
All licensee obligations |
All bank obligations |
|
Exit |
Under the provider agreement |
Subject to obligations to clients and the regulator |
Subject to obligations to clients and the regulator |
Compare complete budgets. The software price for White Label cannot be placed alongside the budget for a licensed institution: they are figures of a different order.
In the agreement, we review rights to the brand and domain, access to data and reports, personal data processing roles, SLAs, procedures for changing fees and contractors, business continuity and programme closure.
Accounts, account details, cards, balances and pending transactions are addressed separately during migration. Retention of IBANs and card details is not guaranteed: new agreements, repeat checks and card reissuance may be required. Data transfer procedures are determined by the agreement and data protection requirements.
|
Party |
Functions |
|---|---|
|
RUE |
Analysis, selection, legal review and coordination |
|
Licensed provider |
Regulated services and controls |
|
Technology contractor |
Software and integrations |
|
Brand owner |
Agreed commercial and operational functions |
RUE acts as a consultant. Our support agreement does not make us a bank, an e-money issuer or a holder of your clients' funds.
+ Mistaking an EMI or PI for a Bank
They offer a different range of services and different protection of funds.
+ Buying Software Alone
Without a regulated provider, the platform cannot serve clients.
+ Promising Worldwide Coverage
You may operate only in markets permitted for the specific provider.
+ Confusing Safeguarding with Deposit Protection
Deposit guarantees and FSCS do not cover electronic money.
+ Overlooking Transaction Fees
The subscription covers only part of the costs; the rest accrue through transactions.
+ Failing to Agree Migration Terms
Without exit terms, changing providers may require replacement accounts and cards.
+ Treating Group Licences as Interchangeable
What matters is the licence of the legal entity that enters into agreements with your clients.
Regulated services are provided by a bank, EMI or PI under its own licence. The provider retains the licence; it is not transferred to you.
Yes, if your role is limited to the functions of a technology partner, agent or distributor and the markets permit this. We check this before setup.
A bank deposit may be covered by a deposit guarantee scheme where its conditions are met and within the applicable limits. For electronic money and funds held by a payment provider, the applicable safeguarding arrangements are reviewed; safeguarding is not equivalent to bank deposit insurance.
The regulated services agreement is entered into with the relevant provider. The arrangements for receiving, recording and protecting funds are set out in client documents. Under the basic model, independent control of client balances is not transferred to the brand owner.
Yes, if the provider's package and card programme allow it. The provider issues the IBANs.
No. Passporting between the EU and United Kingdom has ended; a separate legal basis is needed for each market.
This depends on markets, products and volumes. Wallester's published example for non-financial companies states EUR 2,495 per month. This is a specific card programme's fee, not a minimum price across the market; the complete package is priced individually.
Client checks, transfers, card issuance and servicing, currency conversion, non-standard integrations and minimum payments are most often charged separately.
We provide a timeline after assessing the project: it depends on checks, agreements, agent procedures and integrations.
Yes, but usually through different providers or separate legal entities within a group, with separate agreements and onboarding.
Within the provider agreement and client disclosure rules.
Account closure, return of balances, card reissuance and data transfer procedures must be set out in the agreement in advance.
Tell us about your project, and we will suggest a model, providers and a cost estimate.