On this page
In brief
- Fiat accounts hold balances in government-issued currencies such as GBP, but those balances may be bank deposits or e-money with different customer-fund protections.
- White-label banking lets businesses offer branded financial services through technology providers and regulated partners without becoming licensed banks themselves.
- A ready-made branded interface and API-led BaaS provide different starting points, so confirm whether customer-facing software is included.
- Compare providers by account structure, UK payment capabilities, customer eligibility and integration requirements.
- Assess commercial viability using total launch costs, recurring commitments and realistic revenue assumptions, rather than provider setup fees alone.
This guide compares four UK-focused banking and BaaS providers, explains the difference between bank deposits and e-money, and outlines the costs, compliance responsibilities and implementation work to assess before choosing.
How white-label fiat accounts work
The term "fiat account" describes an account denominated in a government-issued currency, such as GBP, EUR or USD; it does not identify a specific legal category of account. Depending on the account terms and the underlying regulated service, a GBP balance may represent a bank deposit or electronic money issued by an electronic money institution (EMI). These products can offer similar payment functions, but they have different legal structures and customer-fund protections.
White-label banking allows a business to offer account services through an interface carrying its own branding, using infrastructure supplied by other organisations. Customers can view balances, receive funds and initiate payments within that branded experience. The business can therefore introduce financial services without developing core banking infrastructure itself.
The arrangement typically combines three roles, although one provider may perform more than one:
- The customer-facing business manages the brand, product experience and customer relationship. It may collect onboarding information and provide first-line support under the agreed operating model.
- The technology provider supplies the software connecting the customer interface to account and payment services. This may include application programming interfaces (APIs), transaction reporting and account-management tools.
- The regulated bank or EMI provides the underlying deposit account or issues the e-money balance and delivers the associated regulated services. The account terms should identify the relevant legal entity and the nature of the product.
For example, Framnex's white-label banking solution provides configurable software for branded accounts, payments and multi-currency wallets, connecting customer journeys with selected banks, EMIs and compliance providers. Businesses can integrate an existing application through APIs or include a branded web or mobile interface in the implementation scope. Framnex supplies the technology layer, while applicable regulated services are delivered by licensed partners. For a UK launch, GBP account details, Faster Payments availability and customer-fund protection should be confirmed for the chosen partner and account structure.
In a typical UK account journey, the customer submits identity or business information through the branded service. Once the required checks and approval are complete, an account is opened and payment details are assigned. Depending on the product, these can include a UK sort code and account number.
In a pooled-account arrangement, funds for multiple customers are held together, while ledger records track each customer's balance. Virtual account details are payment identifiers that allow incoming funds to be attributed to a particular customer; they do not necessarily represent a separate bank account. UK sort codes and account numbers alone do not establish that a balance is a bank deposit, since e-money accounts can also have these details.
When an incoming payment arrives, the provider records the transaction against the relevant account and makes the updated balance available to the application. For an outgoing transfer, the application submits a payment instruction; the provider processes it through the supported payment scheme and returns status information. Faster Payments can support domestic GBP transfers, but availability depends on the provider and account configuration. Payment records and status updates also support reconciliation between the business's systems and the provider's records.
White-label interfaces and API-led Banking-as-a-Service (BaaS) describe different parts of this model. A white-label interface is an existing application that can be adapted to the business's brand. API-led BaaS exposes account and payment capabilities for integration into software the business builds or commissions. An account API does not necessarily include a ready-made customer application, although providers may offer both approaches.
The underlying account structure determines the applicable customer-fund protections, while each participant's activities determine its regulatory responsibilities.
Regulation, compliance and protection of customer funds
White-label banking is a commercial arrangement, not a regulatory status. Offering branded fiat accounts does not make a business a licensed bank or automatically allow it to conduct regulated activities. UK-incorporated banks are authorised by the Prudential Regulation Authority (PRA) and regulated by both the PRA and the Financial Conduct Authority (FCA). Electronic money institutions (EMIs) operate under a separate FCA authorisation or registration regime; EMI status does not permit deposit-taking.
The customer-facing business must establish its own regulatory position based on what it actually does. Depending on the arrangement, it may supply technology, introduce customers, distribute e-money or act as a registered payment services agent. These roles are not interchangeable. An EMI must register agents providing payment services on its behalf and remains responsible for their acts and omissions. A partnership agreement alone does not extend the provider's permissions to every activity the business wishes to offer. Verify the contracting entity, permissions, restrictions and relevant agent registration on the FCA Financial Services Register.
Compliance responsibilities should be documented between the business, technology provider and regulated institution. Outsourcing onboarding or monitoring does not remove the regulated provider's accountability. The operating model should specify who performs each control, who approves exceptions and how concerns reach the responsible compliance team.
- Customer due diligence: Know Your Customer (KYC) and business verification procedures should establish customer identity, beneficial ownership, the purpose of the account and the expected transaction profile. Higher-risk relationships require enhanced due diligence.
- Ongoing monitoring: Anti-money laundering (AML) controls should identify unusual activity, keep customer information current and define escalation routes for suspicious transactions. Passing onboarding checks does not end the monitoring obligation.
- Financial sanctions: Screening and escalation procedures must address applicable sanctions separately from AML checks. Relevant checks can extend to beneficial owners, directors and payment recipients.
- Strong Customer Authentication (SCA): Payment service providers must apply SCA to online payment-account access, electronic payment initiation and certain other remote actions carrying a fraud risk, unless an exemption applies. The operating model should specify how the branded customer interface supports these requirements.
- Customer treatment and complaints: Allocate responsibility for complaints, fraud reports and support during account restrictions. For complaints covered by the payment services and e-money complaints rules, the responsible provider must normally issue a final response within 15 business days. In exceptional circumstances beyond its control, it must explain the delay within that period and provide a final response within 35 business days of receiving the complaint. Eligible complainants can refer the matter to the Financial Ombudsman Service if they are dissatisfied with the final response or the applicable response deadline has passed. Where the Consumer Duty applies, the product and service arrangements must support good customer outcomes.
Authorised push payment (APP) scams occur when a customer is deceived into authorising a transfer to a fraudster. Mandatory reimbursement rules cover qualifying UK Faster Payments and CHAPS transfers made by individuals, microenterprises and eligible charities, subject to scheme conditions and exclusions, with a maximum mandatory reimbursement of GBP 85,000 per claim. The sending payment service provider handles the claim, while reimbursement costs are generally shared equally between the sending and receiving providers. A white-label agreement should specify how the customer-facing business receives and escalates claims, supports investigations and bears any contractually allocated costs, without displacing the providers' regulatory obligations. This protection concerns scam losses and is separate from FSCS deposit protection.
Protection of customer funds depends on the underlying legal product, not the branding, GBP denomination or presence of a UK sort code.
Account structure | Protection mechanism | Key limitation |
Eligible deposit with a UK-authorised bank | The Financial Services Compensation Scheme (FSCS) generally protects up to GBP 120,000 per eligible depositor, per authorised institution, following the bank's failure. This limit took effect on 1 December 2025. | Eligible balances across brands sharing the same banking licence are aggregated. A separate branded account does not create an additional protection limit. |
E-money balance issued by an EMI | Relevant customer funds must be safeguarded through segregation or qualifying insurance or a comparable guarantee. | FSCS compensation does not cover the EMI's own failure. Safeguarding aims to return customer funds, but recovery can involve delays and deductions for insolvency costs. |
A separate protection scenario arises if the bank holding an EMI's safeguarded funds fails. Eligible underlying customers may qualify for FSCS compensation, subject to the scheme's eligibility rules, aggregation requirements and applicable deposit protection limit. This protection relates to the failure of the safeguarding bank; it does not provide FSCS cover against the EMI's own failure.
Business deposits can qualify for FSCS protection, but eligibility requires checking: most regulated financial services companies are excluded. A limited company generally has a separate entitlement from its owners, whereas a sole trader's business and personal deposits at the same institution are aggregated.
For EMI arrangements, assess the safeguarding controls as well as the contractual promise. FCA rules effective from 7 May 2026 strengthen reconciliation, reporting, audit and resolution-planning requirements, subject to applicable exemptions. Customer terms and marketing should identify the regulated provider, explain whether the balance is a deposit or e-money, and describe the applicable protection accurately. FCA authorisation and safeguarding should never be presented as a guarantee that customers cannot lose money.
Compare UK white-label banking and BaaS providers
Compare providers by the account product, payment capabilities and customer interface your business needs. A bank offering embedded deposit accounts, an EMI providing payment accounts and a platform specialising in cross-border transfers solve different problems. The label "white label bank" is therefore less useful than a clear specification: who holds customer funds, which transactions are supported and who supplies the branded application.
The following comparison summarises published capabilities as of November 2026. Availability depends on the contracting entity, customer eligibility and agreed product configuration.
Provider | Account model | Currencies and UK payments | Interface and integration |
ClearBank | A bank offering embedded current and savings accounts, with FSCS protection for eligible deposits. Its embedded banking proposition targets established businesses offering financial products under their own brand. | Currencies: GBP accounts; multi-currency and FX services depend on the agreed product scope. Incoming GBP credit transfers: Faster Payments, Bacs Direct Credits and CHAPS. Outgoing GBP credit transfers: Faster Payments and CHAPS. Confirm any requirement to originate Bacs Direct Credits separately from receiving them. | API-led infrastructure with testing facilities and webhook notifications. The partner designs the customer experience; a ready-made branded application should not be assumed. |
Griffin | A bank providing separate embedded accounts owned by each end customer, with unique account numbers, sort codes and interest-bearing functionality. Eligible deposits receive FSCS protection. | Currencies: GBP accounts. Incoming GBP credit transfers: Faster Payments, Bacs Direct Credits and CHAPS. Outgoing GBP credit transfers: Faster Payments. Its published payment documentation lists Bacs Direct Credits and CHAPS as inbound-only services. | APIs embed accounts into an existing customer application or operational workflow. This suits businesses developing their own account experience or automating payments and reconciliation. |
Modulr | UK account services are provided by Modulr FS Limited, an FCA-authorised EMI. Customer balances are e-money subject to safeguarding, rather than bank deposits. | Currencies: GBP, EUR, USD and additional supported currencies, subject to the agreed account offering. Incoming GBP credit transfers: Faster Payments and Bacs credits; CHAPS requires enablement. Outgoing GBP credit transfers: Faster Payments and CHAPS, subject to service availability and routing rules. Confirm any requirement to originate Bacs Direct Credits separately. | Accounts are accessible through APIs and a portal. Assess the portal's intended users and branding options separately from the APIs needed to embed services into your product. |
Currencycloud | Its UK entity, The Currency Cloud Limited, is authorised to issue e-money and provide payment services. The proposition centres on currency collection, conversion and cross-border payments. | Currencies: Multi-currency balances and FX, with collection, holding and payout capabilities varying by currency. Incoming GBP credit transfers: Local third-party collections through Faster Payments. Bacs and CHAPS funding use separate instructions; confirm their suitability for the intended customer flow. Outgoing GBP credit transfers: Faster Payments for local payments and CHAPS for priority payments to UK accounts. | Offers both APIs and an explicitly advertised white-label cross-border platform. This is relevant when a branded FX and transfer interface is required, rather than assuming every account API includes an application. |
Direct Debit support requires a separate comparison: paying a Direct Debit from a customer's account is different from collecting money from accounts held elsewhere. Griffin supports Direct Debits taken from its customer accounts but does not support collecting Direct Debits from accounts at other banks. Modulr documents both outgoing Direct Debit payments and incoming Direct Debit collections, with additional onboarding requirements for collections.
Based on these capabilities, ClearBank and Griffin are candidates for propositions requiring customer bank deposits. Modulr is a candidate for embedded payment accounts and payment automation, while Currencycloud is a candidate for branded multi-currency collection, FX and international transfers. These are starting points for a shortlist, rather than a ranking: suitability depends on the precise account structure and transaction flows.
Use the same requirements when evaluating each proposal:
- Account ownership and eligibility: Establish whether each customer receives an account in their own name, virtual payment details linked to a pooled account or another structure. Confirm supported customer types, countries and business sectors.
- Payment coverage: Separate incoming from outgoing Faster Payments, Bacs and CHAPS capabilities. Check transaction limits, cut-off times, Confirmation of Payee and whether Direct Debit support means paying mandates, collecting funds or both.
- Currency functionality: Request a currency-by-currency matrix covering collection, holding, conversion and payout. A supported payout currency does not necessarily come with local receiving details.
- Technology and service levels: Compare API documentation, sandbox access, payment-status notifications, reconciliation exports and account-management controls. Request contractual availability commitments, incident escalation procedures and capacity limits.
- Delivery scope: Confirm whether the proposal includes a customer application, an administrative portal or APIs alone. Separate technical integration estimates from the time required for commercial approval, compliance review and production access.
- Commercial comparability: Obtain quotations using the same projected account numbers, balances, payment volumes and FX activity. Identify minimum commitments and chargeable extras before comparing headline prices.
Launch costs, operating expenses and commercial viability
The cost of offering white-label fiat accounts extends beyond the provider's setup fee. A viable budget must cover the customer interface, integration, compliance operations and ongoing account servicing, together with sufficient working capital to support the business while customer revenue grows. Distinguish upfront expenditure, recurring commitments and usage-based charges before comparing proposals.
Cost category | What to budget for | What to clarify |
Provider onboarding and setup | Commercial onboarding, programme configuration and any implementation or white-label software fees. | Deliverables included, payment milestones, refund conditions and when monthly billing begins. |
Product development and launch preparation | API integration, interface development or customisation, security testing, legal review and operational preparation. | Whether the proposal includes a branded customer application, an administrative portal or APIs alone; responsibility for maintenance and upgrades. |
Recurring provider charges | Platform subscriptions, minimum monthly spend, account charges, payment processing, verification checks and FX charges where applicable. | Included allowances, volume tiers, inactive-account fees, unsuccessful verification charges and payment-return or investigation fees. |
Internal operating expenses | Engineering support, hosting, customer service, reconciliation, fraud operations and compliance work allocated to the business. | Expected staffing requirements, manual-review volumes, service coverage and contractual liability for losses. |
Published pricing provides a reference point, but it is not a complete launch budget. As checked on 3 November 2026, Griffin advertises platform banking onboarding from GBP 15,000 and a minimum monthly package starting at GBP 4,000, against which account, payment and onboarding usage is drawn down. At those starting figures, onboarding plus 12 monthly minimums totals GBP 63,000, before additional usage, internal costs and any applicable taxes. This calculation describes one provider's published structure, not a market-wide price or binding quotation.
Minimum-spend arrangements require careful modelling. Where eligible usage counts towards the minimum, the relevant monthly charge is generally the greater of the minimum commitment and eligible usage charges, plus separately billed items. Adding the full minimum to all usage would double-count expenditure. Confirm whether unused allowances expire, which services qualify and whether volume discounts apply to all transactions or only those above a threshold.
Illustrative launch and first-year operating budget
Using the GBP 63,000 provider-fee illustration above as a starting assumption, a business could build the following planning scenario. All additional figures are hypothetical internal budget allowances, not supplier quotations or market averages.
Budget item | Illustrative amount |
Provider onboarding and 12 monthly minimum commitments | GBP 63,000 |
One-off integration and interface development | GBP 30,000 |
Initial legal review and compliance preparation | GBP 10,000 |
Staff allocation for customer support, compliance operations and technical maintenance over 12 months | GBP 72,000 |
Hosting, monitoring and software tools over 12 months | GBP 12,000 |
Customer acquisition and launch marketing | GBP 18,000 |
Usage charges above the monthly minimums and separately billed services | GBP 10,000 |
Contingency reserve | GBP 20,000 |
Total illustrative funding requirement | GBP 235,000 |
This scenario covers launch preparation and 12 months of operation before offsetting customer revenue. Usage included within the provider's monthly minimums is not charged again in the additional-usage allowance. The contingency is a funding buffer, not an expense already incurred. Any applicable irrecoverable VAT, contractual security deposits or prefunding requirements would need to be added separately. Actual funding needs depend on the delivery scope, staffing model and timing of payments and receipts.
A ready-made white-label interface can reduce the amount of software your business must build, while an API-led product requires its own customer experience. Currencycloud explicitly offers these alternative approaches. Compare the full cost of customisation, hosting, maintenance and future changes before treating the packaged interface as the cheaper option over the contract term.
Revenue assumptions must also match the contractual model. Potential income includes permitted subscriptions or account fees, payment fees, FX margins and contractually agreed balance-related commission. None should be assumed automatically. For example, the March 2024 Sponsored Standards for The Currency Cloud Limited restricted certain account and collection fees while permitting specified payment fees and FX spreads under that sponsored model. These dated, model-specific provisions should not be treated as universal current terms: confirm the fees and margins permitted by your proposed agreement before including them in revenue forecasts.
Evaluate commercial viability using contribution margin: revenue less the variable costs attributable to serving customers. Calculate revenue and costs across the same customer population, allowing for inactive accounts, payment frequency, verification failures and support demand.
Illustrative operating break-even
The following standalone example uses different assumptions from the first-year budget above and illustrates operating break-even only. Assume monthly revenue of GBP 10 per active customer, variable servicing costs of GBP 4 per active customer and fixed monthly operating costs of GBP 12,000. Each active customer contributes GBP 6, so operating break-even requires 2,000 active customers: GBP 12,000 divided by GBP 6. These are hypothetical assumptions, not provider prices. The example excludes recovery of upfront launch expenditure and assumes fixed fees are separate from variable charges; a usage-credit minimum requires a different calculation.
Operating break-even means that ongoing revenue covers ongoing operating costs; it does not mean the initial investment has been recovered. Investment payback occurs when cumulative net cash inflows have covered the upfront expenditure and any operating cash deficits incurred during the launch period. Assess payback using a monthly cash-flow forecast that reflects customer growth, churn and the timing of receipts and payments.
Test the forecast under slower customer acquisition, lower payment activity, higher support costs and reduced balance-related income. Include customer acquisition expenditure and churn when assessing payback, and model cash requirements through the point of sustained positive cash flow. Any contractual prefunding, security deposit or reserve should be shown separately from fees: it may tie up liquidity without being an immediate expense. Customer balances must not be counted as the business's operating cash.
Before committing, obtain a complete fee schedule covering minimum terms, annual price increases, VAT treatment, termination charges and migration assistance. A commercially sustainable proposition should recover its launch investment and service costs at a credible level of customer adoption, with enough cash available to withstand a slower start.
Implementation: from provider selection to live accounts
Launching white-label fiat accounts requires commercial approval, a defined compliance model and a tested customer service operation alongside the technical integration. Manage these as coordinated workstreams, with named owners and clear acceptance criteria. Access to a sandbox demonstrates that development can begin; it does not mean the provider has approved your business or customers for live accounts.
1. Define the launch scope and confirm provider suitability. Specify the customer types, jurisdictions, currencies and transaction flows the initial product must support. For a UK GBP proposition, confirm account ownership, sort codes and account numbers, inbound and outbound Faster Payments, payment limits and reconciliation data. Establish whether you are implementing bank deposits or e-money accounts, and whether the supplier provides a branded application or APIs requiring your own interface. Obtain written confirmation that the provider supports your business model and intended customers.
2. Complete business due diligence and agree responsibilities. Prepare company and beneficial ownership information, financial forecasts, expected payment volumes and relevant compliance policies. Agree the service contract, data-processing arrangements, service levels, incident escalation and exit provisions. Document who performs customer due diligence, sanctions screening, transaction monitoring, complaints handling and regulatory reporting. Resolve any required authorisation or agent registration before commencing the relevant regulated activity. Provider onboarding can involve several teams: Griffin, for example, requests director and ownership verification, contractual documentation and compliance assessments alongside technical development.
3. Build the customer onboarding and account-opening journey. Collect the identity, business and beneficial ownership information required by the agreed KYC process. Present the account terms, fees, privacy information and applicable customer-fund protection clearly, and retain evidence of acceptance. Handle applications requiring additional information or manual review, as well as approvals and rejections. Open accounts only once the applicable approval conditions are satisfied, and link each provider customer identifier and account identifier to the correct internal record. Modulr's documented workflow, for example, signals customer approval before the first payment account is created.
4. Integrate payments, account records and reconciliation. Implement secure authentication, appropriate staff permissions and controls for protecting production credentials. Integrate the customer authentication flows agreed with the regulated provider, including SCA where required. Test successful, failed and abandoned authentication attempts, account recovery and any permitted exemptions. Keep customer authentication separate from API authentication: securing the connection between systems does not by itself authenticate the customer authorising a payment.
Connect account creation, balance retrieval, payment initiation and transaction reporting. Process webhook notifications safely, including repeated deliveries, and follow the provider's retry and duplicate-prevention rules. A successful API acknowledgement should not automatically appear to customers as a completed transfer: track the provider's payment statuses and subsequent returns. Reconcile internal records against provider transactions and balances, with an exception queue for discrepancies.
For online payment accounts subject to third-party access requirements, agree who provides and maintains access for appropriately authorised or registered account-information and payment-initiation providers. Verify the associated customer consent and authentication journeys. A partner-facing BaaS API does not, by itself, demonstrate compliance with these access requirements.
5. Test complete journeys and operational failures. Use synthetic customer data to test onboarding, account issuance, incoming payments, outgoing transfers, account recovery and access to current and historical statements. Test account closure and the return of remaining funds, including how pending payments or account restrictions affect the closure process. Include insufficient funds, rejected payments, account restrictions, duplicate requests, delayed notifications and outages. Test payment limits, access permissions and anticipated transaction volumes. Record which scenarios the sandbox cannot reproduce and agree how they will be validated. Sandbox behaviour can differ materially from production: Griffin documents simulated checks and payments, separate credentials and product access restricted by live approval.
6. Obtain production approval and launch a controlled pilot. Complete the provider's required assurance checks and secure internal sign-off from product, engineering, operations, compliance and finance. Where required by the partnership model, obtain the regulated provider's approval of customer journeys, account terms, fee disclosures, fund-protection wording and marketing materials before launch. Include this review in the delivery schedule and retain the approved versions. ClearBank's published integration process, for example, moves from simulation testing through provider quality assurance before production access. Start with a limited customer group and agreed transaction limits. Validate real account details, payment processing, customer communications and reconciliation, with a documented procedure to pause new onboarding or payment initiation if material problems emerge.
7. Expand against measured operating performance. Monitor onboarding completion, manual-review rates, payment failures, unresolved reconciliation differences, fraud alerts and support response times. Assign owners to exceptions and review provider incidents and API changes. Increase customer numbers and transaction limits only when the pilot meets the agreed acceptance criteria and the support team can handle the additional workload.
Set the launch date around these dependencies rather than an API integration estimate alone. Griffin states an onboarding aim of eight weeks where checks proceed smoothly; this is a conditional provider estimate, not a universal implementation timetable. Bespoke interfaces, complex ownership structures, compliance remediation or additional payment schemes can change the delivery scope. Maintain a schedule that distinguishes contract approval, technical readiness, production access and the first successful live customer transactions.
Sources: UK regulatory and customer-protection information is based on the FCA’s guidance on payment services and e-money, safeguarding requirements, Strong Customer Authentication and complaints handling, together with the FSCS deposit protection limits, Bank of England guidance on protection for safeguarded funds and PSR guidance on APP fraud reimbursement. Provider capabilities are drawn from ClearBank’s UK documentation, Griffin’s payment documentation, Modulr’s payment documentation, and Currencycloud’s GBP payment guide and white-label platform description. Commercial examples reference Griffin’s published pricing and onboarding guidance; the historical Currencycloud fee example refers specifically to its March 2024 Sponsored Standards. Illustrative budgets and break-even assumptions are editorial examples, not provider quotations.
Independent research
Ask AI whether Framnex fits your business.
Research Framnex with your preferred AI assistant and see where the platform may fit your client base, product and launch model.
The prompt will be prefilled. Review it before sending.