White-Label Banking for UK Businesses: Providers, Costs and Compliance

How white-label banking works: branded apps versus API platforms

White-label banking lets a business offer a financial service within its own branded experience while a regulated partner provides the underlying account or payment service. Banking-as-a-Service connects the customer-facing product to that infrastructure, commonly through APIs. Depending on the operating model, a business can offer partner-provided accounts without obtaining its own banking licence. Its own activities still need to be assessed for any applicable regulatory obligations.

White labelling describes presentation, not regulatory status. A customer may see your logo while entering an account agreement with a bank or an electronic money institution. A bank deposit and an e-money balance are different legal products, even when both have an account number, sort code and payment functionality. Identify the account provider and the customer's legal rights before describing the product as a bank account.

In a typical account-opening journey, the customer submits business and identity information through the chosen interface. The agreed parties perform verification and acceptance checks; approved customers receive the contracted account or e-money service. Payment instructions pass through the integration to the regulated service provider, while status messages and reports update the application. Your brand may own the first-line relationship, but decision rights and responsibilities follow the programme agreement.

Control over onboarding has several dimensions. You may choose the screen layout while the provider determines mandatory information, eligible customers and approval rules. Likewise, a configurable payments screen does not necessarily allow you to change transaction limits or permitted destinations. Confirm which decisions are yours, which require approval and which are fixed by the product.

Hosting and maintenance also need an explicit boundary. A hosted application may include infrastructure and routine releases but exclude integrations with your CRM, accounting or support systems. With an API build, your team normally maintains the software it creates, while the provider maintains its own service. A hybrid approach can combine hosted onboarding with a custom dashboard and payment workflow.

Evaluate the complete service rather than the label. Request a diagram showing the customer interface, integration layer, regulated account provider, money flows and operational teams. It should make clear what is supplied, what your business must build and who keeps each part working after launch.

UK white-label banking providers: compare account infrastructure and delivery options

Start with the account product and required customer journey, then compare the infrastructure providers capable of supporting them. ClearBank, Griffin and Modulr are relevant candidates to investigate, but their offerings are not interchangeable. None should be assumed to include a complete, ready-made banking app simply because it supports services under another business's brand. Public information below was checked on 4 November 2026.

Sources: ClearBank embedded banking and payments; Griffin embedded accounts, payment schemes and October 2026 Direct Debit rollout update; Modulr platform scope and UK issuer disclosures.

Check release status at product level. Although ClearBank's marketing discusses current accounts, its embedded payment-account documentation identifies that particular solution as not yet live in production. Obtain written confirmation of the account variant and launch availability you would receive. This does not imply that all ClearBank account services are unavailable; it means a broader marketing description should not substitute for programme-specific confirmation.

Ask every candidate to explain what an account identifier represents. A unique number can identify an individual account, a virtual reference or a balance recorded within another structure. Establish the legal holder, the entity owing the balance to the customer, the available statements and the reconciliation data. UK sort codes alone do not establish that the balance is a deposit.

• Account fit: eligible legal entities, supported industries, individual or pooled structure, currencies, account limits and closure processes.
• Payment fit: direction, scheme, transaction limits, cut-offs, Confirmation of Payee, returns and payment-status reporting.
• Interface fit: ready-made app, hosted components, SDKs, APIs or a separate implementation partner, with clear hosting and maintenance responsibilities.
• Operational fit: administrator permissions, reconciliation reports, exception queues, customer support tools and audit history.

Use one demonstration scenario across the shortlist: open an eligible business account, receive funds, make a payment, handle a rejection and reconcile the records. Classify each requirement as included and live, conditional, separately priced or unavailable. That comparison reveals whether a provider supplies the complete delivery route you need or one important part of it.

UK regulation, KYC/AML and customer-funds protection

A white-label banking programme needs a clear legal structure before it needs a launch date. Identify the regulated account or e-money provider, the customer contracting entity and your business's role. Check the firm's current status, permissions and restrictions through the Financial Services Register, using its legal name and reference number rather than relying on the product brand.

UK banks are subject to PRA prudential supervision and FCA conduct regulation. Becoming a bank involves the PRA authorisation process. An electronic money institution operates under a different framework and does not hold a banking licence merely because its accounts support payments. The FCA explains the payment-services and e-money regimes.

Working with a regulated partner can support a branded product without your business becoming a bank, but the partner's permissions do not automatically cover your own activities. Establish whether you are a technology supplier, an e-money distributor, a payment-services agent or a firm requiring its own authorisation. These roles have different boundaries. Assess the proposed activities and contracts with the partner and qualified UK advisers before enabling transactions.

If you act as an agent of a payment institution, the principal must register you on the Financial Services Register before you provide payment services. An agent of a bank permitted to provide payment services in the UK is not required to register as an agent under the Payment Services Regulations 2017, although other applicable obligations remain. Confirm the requirements for your specific arrangement using the FCA's agent guidance.

Define KYC, business verification and anti-money-laundering responsibilities across the full customer lifecycle. Business onboarding should address the legal entity, authorised representatives, beneficial ownership, nature of the business and expected account use, with additional evidence where the risk assessment requires it. Ongoing monitoring and review are separate from the initial identity check. The FCA Financial Crime Guide provides the relevant risk-based context.

• Name the party collecting documents, performing checks and making the final acceptance decision.
• Agree who handles enhanced due diligence, sanctions alerts, unusual transactions and suspicious-activity escalation.
• Specify who may restrict an account or stop a payment, and how customer communication is controlled.
• Assign record retention, quality assurance, staff training and access for audits or regulatory enquiries.
• Document complaint handling, fraud investigations, payment disputes and any applicable reimbursement responsibilities.

Mandatory authorised push payment (APP) scam reimbursement applies to qualifying UK transfers through Faster Payments and CHAPS, protecting eligible individuals, microenterprises and charities. The mandatory maximum is GBP 85,000 per claim, subject to the applicable eligibility rules and exceptions. Reimbursement is normally due within five business days, with permitted extensions for investigation. Specify who receives claims, gathers evidence, communicates decisions and makes reimbursement payments. The sending and receiving payment service providers generally share the reimbursement cost equally; programme contracts should also clearly allocate any financial exposure borne by your business without reducing customers' statutory protections. See the PSR's APP reimbursement guidance.

Explain customer-money protection according to the legal product. Eligible bank deposits are subject to the standard FSCS limit of GBP 120,000 per eligible person, per authorised firm, effective from 1 December 2025. Accounts held under different brands sharing a banking licence are aggregated. Confirm eligibility and the actual deposit-taking entity; the limit does not apply separately to each app or account.

E-money and non-bank payment services use safeguarding where required, rather than FSCS compensation for the failure of the e-money or payment institution itself. The FCA describes protection through permitted segregation or insurance/guarantee arrangements and notes that insolvency recovery may take time and involve deductions. Holding safeguarded funds at a bank does not make the branded e-money balance a bank deposit.

The supplementary safeguarding regime took effect on 7 May 2026. Ask the responsible institution for evidence of the reconciliation, oversight, reporting and assurance arrangements applicable under the current FCA requirements. Your programme should provide the records and operational cooperation needed to support those controls.

Customer terms, onboarding screens and support scripts should consistently identify the provider, account type, protection arrangements and complaints route. Assess data-protection duties and any applicable Consumer Duty responsibilities alongside the financial-services perimeter. A signed responsibility matrix makes these obligations concrete and exposes operational work that a generic promise of included compliance may leave unresolved.

Costs, revenue potential and realistic launch timelines

Build the commercial case around the complete service: the account infrastructure, the branded experience and the team operating it. Separate one-off implementation from recurring commitments and volume-based fees. Then add customer acquisition, expected losses, applicable taxes and any cash tied up in contractual reserves or settlement prefunding. Customer funds are not working capital available to finance your business.

As a public reference checked on 4 November 2026, Griffin's platform-banking page lists onboarding from GBP 15,000 and minimum monthly packages of GBP 4,000, GBP 6,000 or GBP 10,000, with enterprise terms available. Accounts, payments and onboarding draw down the package. A GBP 15,000 setup fee plus twelve GBP 4,000 minimums would total GBP 63,000, but this arithmetic is not an all-in quote: excess usage, excluded services, your app and internal delivery remain to be priced.

Distinguish drawdown minimums from additive subscriptions. Under a drawdown structure, eligible usage offsets the minimum; under an additive model, usage is charged on top of the licence. Request sample invoices at your expected launch and growth volumes. Compare like-for-like 12- and 36-month forecasts, including fee increases and internal work.

Revenue can come from paid account plans, disclosed service fees or contractually available revenue shares. Card, FX or balance-related income depends on the actual product and commercial agreement; do not assume it is available or fixed. Model revenue after the provider's revenue share and refunds, then deduct variable costs and expected variable losses to calculate contribution. Payment throughput and balances held for customers are not revenue.

For an illustrative calculation, assume GBP 10 of monthly revenue per active account after provider revenue-sharing and refunds, but before variable costs. Deduct GBP 4 per account for variable costs and expected variable losses, giving a monthly contribution of GBP 6 per account. With GBP 18,000 of fixed monthly costs, operating break-even is 3,000 active accounts. At 5,000 accounts, monthly operating surplus is GBP 12,000. An assumed GBP 90,000 launch investment would take 7.5 months to recover at that steady run rate, before earlier losses, acquisition spending, tax and financing. These are hypothetical figures, not market rates or a forecast.

Launch estimates require the same discipline. Griffin advertises a six-to-eight-week onboarding route on its pricing page; this should not be treated as a universal deadline for a complete branded proposition. Confirm the starting point, eligibility, prerequisites and scope behind any quoted period. Your critical path may include due diligence, contracts, compliance design, interface development, payment testing and production approval.

Model a slower customer ramp and a delayed launch. Include charges that become payable before revenue starts, and distinguish technical readiness from operational readiness. The investment decision should follow verified scope, a cash-flow forecast and measurable launch gates, with sufficient funding for a plausible downside case.

How to select a partner and launch

Start with a short product brief that makes the intended service concrete. Define the business customers you will serve, the problem the account solves, the required money flows and the experience you want to control. Specify whether a bank deposit is essential or whether an e-money account meets the need. This decision narrows the provider shortlist before commercial comparisons begin.

1. Set mandatory requirements. List eligible customer types, account ownership, UK account details, required payment schemes and directions, cards if needed, currencies and support expectations. Separate launch essentials from later enhancements. Mark any feature dependent on a roadmap or third-party supplier.
2. Confirm the delivery structure. Identify the regulated entity, customer contract and your business's role. Establish whether the proposal supplies a branded app, embedded components, APIs or a combination. Allocate hosting, maintenance, compliance operations and first-line support explicitly.
3. Request comparable commercial proposals. Give each candidate the same active-account, onboarding, payment and card forecasts. Ask for itemised setup costs, minimums, usage rates, exclusions, revenue shares and sample invoices. Include internal delivery costs in your comparison.
4. Validate the complete journey. Use the sandbox to test onboarding, account creation, incoming funds, outgoing payments, failures, returns and reconciliation. Request evidence that the required functions are available for your approved programme in production.
5. Agree contractual and operational gates. Confirm acceptance criteria, change control, service levels, incident escalation, record access, liability allocation and exit assistance. Assign an owner to each unresolved requirement before approving launch.
6. Launch within controlled limits. Begin with an agreed customer cohort and appropriate transaction limits. Monitor customer outcomes and financial controls before expanding the programme.

Use a scorecard only after mandatory eligibility and product checks have passed. Compare total cost, customer experience, implementation effort, operational reliability and contractual flexibility. Record the evidence behind each score and distinguish verified functionality from promises. A low price cannot compensate for an unavailable payment function or an operating model that does not fit your activities.

Production acceptance should cover financial integrity as well as usability. Check duplicate requests, delayed status notifications, timeouts and interrupted processing. Demonstrate that application balances and transaction records can be reconciled to the provider's reports, with an owned process for exceptions. Train support teams to distinguish pending, failed and completed payments and to escalate account restrictions correctly.

Agree the initial monitoring measures in advance: onboarding completion and manual-review rates, payment completion and return rates, reconciliation exceptions, support response times, complaints, fraud losses and contribution per active account. Set escalation thresholds and conditions for pausing expansion. A technically successful launch can still require changes to pricing, staffing or customer journeys.

Protect the ability to change partners. Confirm how historical records are exported, what transition assistance costs and whether customers would need new account details, cards or agreements. Test assumptions about portability before committing to a long contract. The FCA's outsourcing guidance reinforces that regulated firms remain accountable for their applicable obligations when using third parties.

A useful enquiry should therefore contain the target customers, legal account type, mandatory capabilities, money-flow diagram, volume forecast, integration environment, budget and desired launch window. Ask the provider to return a scoped proposal, responsibility matrix and milestone plan. That gives your business a reviewable basis for selecting a partner and funding a controlled launch.