Electronic Money Regulations 2011: What Can UK White-Label Banking Offer?

An EMI partnership can support wallets, payments and cards, but it does not permit every banking feature. Let's examine what UK white-label products offer, where regulatory limits apply and what owners and CFOs should verify.

On this page

In brief

  • An EMI-backed product can support wallets, payments, cards and currency functions only within the issuer's permissions and approved programme.
  • E-money remains a claim on its issuer rather than a bank deposit, with issuance and redemption rights that customer interfaces and fees must respect.
  • Interest linked to holding e-money is prohibited, while deposits, lending, investments, cryptoassets and Open Banking features require separate regulatory assessment.
  • Distributors and payment-services agents have different roles, and neither arrangement independently authorises the white-label business to issue e-money.
  • Safeguarding, financial-crime controls, complaints, records and data responsibilities must be allocated clearly without implying that outsourcing removes accountability.

How Do the Regulations Apply to Your White-Label Model?

The Electronic Money Regulations 2011 apply to the substance of the service behind your brand. E-money is electronically stored monetary value representing a claim against an issuer, created against received funds for payments and accepted by someone other than the issuer, subject to statutory exclusions. The customer-facing app and the entity legally issuing that value may be different businesses.

The EMRs govern e-money issuance and redemption, while the Payment Services Regulations 2017 govern payment services, including relevant transactions performed using e-money. An EMI can provide payment services within its permitted scope without becoming a separate payment institution. That does not give a white-label partner unrestricted permission to perform financial activities in its own right.

Underlying provider

Regulatory position

Implication for your model

Authorised EMI

FCA-authorised e-money institution, subject to its authorised scope and requirements.

Identify the issuer and the services it agrees to provide through your product.

Small EMI

FCA-registered institution subject to eligibility conditions and limits.

Registration is a distinct regime; do not assume identical scale or service permissions.

Bank

Deposit-taking institution with its own permissions; banks can also issue e-money.

Determine whether the specific balance is a deposit or e-money rather than relying on the provider's name.

The FCA's application guidance distinguishes authorisation from registration, and its small-EMI guidance sets out the conditions of that category.

Next classify the white-label business's role. A payment-services agent acts for an EMI principal and must be registered before providing those services. An EMI may distribute or redeem e-money through an agent or distributor, but cannot issue e-money through either intermediary or any other entity acting on its behalf. The EMRs distinguish these functions in regulation 33 and require agent registration under regulation 34. Distributing value is not a substitute for the appropriate arrangement where the business also performs payment services.

An outsourced technology provider may instead supply hosting, interfaces or data processing. The technical-services exclusion depends on the actual activity and requires the provider not to possess transferred funds; it does not cover payment initiation or account information services. A contract describing a firm as a technology partner cannot settle the classification by itself.

Under regulation 36, the EMI retains statutory responsibility for acts and omissions of agents, distributors and outsourced providers carrying out activities on its behalf. Allocating tasks by contract does not remove that responsibility.

Document who contracts with customers, issues value, receives funds, executes instructions and handles redemption. If your company itself undertakes regulated services outside a valid agent, distributor or excluded technical role, assess its own authorisation or registration requirements. The agreed allocation must match the live service, including any additional features introduced after launch.

Which Services Can an EMI-Backed Product Offer?

An EMI-backed product can combine electronic balances with payment functionality, but the available service depends on the institution's regulatory scope and the programme it agrees to support. EMI status is not a standard package of accounts, cards and international payments. Confirm each required function with the issuing institution and identify any separate provider involved.

Customer function

Potential EMI-backed service

What to establish

Hold and use electronic value

A wallet or account recording e-money issued in exchange for funds.

The issuer, account holder, supported currencies and conditions for funding and redemption.

Receive and send payments

Transfers into or out of the product through supported payment arrangements.

Incoming and outgoing rails, beneficiary types, limits, cut-offs and settlement reporting.

Spend using a card

A physical or virtual payment instrument linked to the e-money balance.

The issuer, scheme and processor arrangements, eligible customers and supported transaction types.

Pay other wallet users

Transfers between supported accounts or balances within the programme.

Account ownership, permitted transfers, fees and the records showing each user's entitlement.

Use multiple currencies

Currency balances and conversion associated with supported payment flows.

Which currencies can be held, collected, converted and paid, and who executes each conversion.

The underlying value remains e-money rather than a deposit merely because the app shows an account number or calls the product a current account. The FCA describes e-money as electronically stored value that can be used for payments, including through wallets and prepaid cards. Customer terms should name the issuer and describe the actual account arrangement.

Issuance and redemption are central to the service. Under regulations 39 to 44 of the Electronic Money Regulations 2011, the issuer must issue e-money at par on receipt of funds and redeem it at par on the holder's request, subject to the statutory conditions. Redemption fees are permitted only in specified circumstances, must be disclosed in the contract before the holder is bound by it, and must be proportionate and commensurate with the issuer's actual costs. Regulation 44 allows contractual redemption arrangements for non-consumers who accept e-money, disapplying the fee and redemption-amount rules in regulations 41 and 42 for those persons; this is not a blanket exception for all business customers. A cash-out screen should implement the applicable rights rather than inventing unrestricted withdrawal charges or treating redemption as a discretionary product feature.

For a GBP wallet, a representative journey is funding, issuance of the corresponding electronic value, a permitted payment and redemption of the remaining balance. Test how rejected transfers, fees and pending card authorisations affect the amount available to spend. A successful instruction and a completed external payment are different events; the interface and statements must reflect the provider's actual transaction states.

Check the institution's category as well as its advertised features. The FCA's EMI applicant guidance distinguishes authorised EMIs from small EMIs and states that small EMIs cannot provide account information or payment initiation services. Do not infer Open Banking coverage from a general API offering. A product specification should classify every function as included, separately contracted or unavailable, with the responsible legal entity beside it.

Which Features Are Prohibited or Need Separate Regulatory Assessment?

An EMI-backed product can support useful payment functions, but EMI status is not a general permission to offer banking, credit, investment or cryptoasset services. Assess each proposed feature against the issuer's permissions, the Electronic Money Regulations and any other applicable regime before adding it to the roadmap.

Feature

Regulatory boundary

Interest on an e-money balance

Interest and other benefits linked to the length of time e-money is held are prohibited.

Savings deposits

An EMI permission does not authorise deposit-taking; a separate appropriately authorised deposit product is needed.

Loans or overdrafts

Assess the permitted credit conditions and any separate consumer-credit requirements; safeguarded funds cannot finance lending.

Investments, insurance or cryptoasset services

Assess the relevant activity and permissions separately rather than relying on the payments arrangement.

Open Banking services

Account information and payment initiation require the appropriate regulatory route and cannot be assumed included.

Regulation 45 makes the interest restriction explicit. Renaming a time-based return as a bonus or reward does not remove the need to assess its substance. A benefit based on spending is a different proposition, but still requires review of its design, customer value and contractual terms.

Credit needs particular care. EMR regulation 32 permits credit subject to the applicable payment-services credit conditions. Such credit must be ancillary and granted exclusively in connection with executing a payment transaction, must not be funded from money received or held for executing customer payments, and must satisfy applicable own-funds requirements. E-money safeguarding funds must not finance it either. Do not treat these provisions as a general lending licence or use customer safeguarded money as working capital. Obtain a feature-specific assessment, including any separate consumer-credit requirements, before offering repayment plans or credit limits.

Distribution and agency also have limits. Under regulation 33, an EMI may distribute or redeem e-money through an agent or distributor, but cannot issue e-money through either intermediary or any other entity acting on its behalf. Providing payment services on the principal's behalf requires the appropriate registered-agent arrangement; a technology contract cannot substitute for it.

Finally, distinguish legal permissibility from programme availability. The issuer may prohibit sectors, currencies, customer types or transaction flows that are not inherently unlawful. Record both the regulatory conclusion and the partner's written approval for each material feature. Changes to marketing, fees or account behaviour should follow the same review process rather than being treated as cosmetic app updates.

What Customer Protection and Compliance Duties Apply?

An e-money customer holds a claim on the issuer, not a bank deposit merely because the app displays a GBP balance and account details. The issuer and the customer-facing business should describe that relationship consistently in terms, onboarding and support communications.

Relevant funds must be safeguarded under the applicable arrangements. The FCA explains that safeguarding differs from FSCS compensation for a non-bank provider's failure: returning funds after insolvency can take time and involve deductions. Do not imply that placing safeguarded money at a bank makes the customer's e-money an FSCS-protected deposit.

The safeguarding Supplementary Regime, effective from 7 May 2026, adds requirements including daily safeguarding reconciliations, monthly reporting to the FCA and safeguarding audits where applicable. Your programme must supply the identifiers, transaction evidence and operational cooperation the responsible institution needs, even where the institution performs the calculation itself.

Area

Allocation to document

Onboarding

Identity and beneficial-owner checks, eligibility decisions, enhanced review and retained evidence.

Ongoing controls

Sanctions alerts, transaction monitoring, suspicious-activity escalation and account restrictions.

Customer support

Complaints, unauthorised payments, fraud claims, redemption requests and escalation deadlines.

Financial records

Customer balances, fees, safeguarding inputs, discrepancy investigation and approved corrections.

Technology and data

Access permissions, authentication, incident response, privacy roles and supplier oversight.

Agree who performs each task and who makes the final decision. Outsourcing a verification check does not make accountability disappear, and the white-label business remains responsible for the duties it accepts and those arising from its own activities.

Customer terms should explain issuance, redemption, charges, restrictions and the complaints route. The FCA conduct guidance connects the EMR requirements with payment-services information and conduct duties. Review redemption fees against the applicable rules rather than treating them as unrestricted income.

For relevant payment-services and e-money complaints, firms must normally provide a final response within 15 business days. In exceptional circumstances beyond their control, they must explain the delay within that period and provide a final response within 35 business days. Eligible customers can refer unresolved complaints to the Financial Ombudsman Service if they are dissatisfied with the final response or the applicable response deadline has passed. Explain this route in customer communications, consistent with the FCA's complaints guidance.

Distinguish payments the customer did not authorise from authorised push payment (APP) fraud, where the customer was tricked into authorising a transfer. Unauthorised payments are subject to separate statutory refund rules; the APP reimbursement limit does not cap those rights. For eligible UK Faster Payments and CHAPS APP fraud claims, mandatory reimbursement protection covers losses up to £85,000 per claim, subject to the applicable eligibility conditions and exceptions. Assign responsibility for assessing and handling each type of claim, and explain the relevant protection accurately using the FCA's fraudulent-payment guidance.

Assess Consumer Duty where the product and customers fall within scope, including relevant business customers. Keep staff training and customer messages aligned with the actual arrangement, and retain evidence that complaints, restrictions and financial discrepancies reach an accountable team promptly.

What Should You Verify Before Launch?

Approve launch against a documented programme, not a general claim that the platform is compliant. The legal structure, contracted service and customer journey should agree on who issues e-money, who provides payments and what the branded business is permitted to do.

  1. Verify the entities. Check the issuer's exact legal name, status, permissions and restrictions through the Financial Services Register, and confirm any required agent registration.
  2. Confirm the product. Record eligible customers, currencies, payment rails, cards, limits and redemption routes, separating live functions from roadmap promises.
  3. Approve the role allocation. Obtain a signed responsibility matrix covering acceptance, monitoring, safeguarding support, complaints, incidents and reporting.
  4. Review disclosures. Ensure customer terms and marketing identify e-money correctly and do not promise deposit protection, interest or services the programme cannot lawfully deliver.
  5. Test the financial journey. Demonstrate funding, payment, rejection, return, fee deduction and redemption with expected balances and traceable records.

Test difficult cases as well as successful transactions. A repeated request must not produce a second payment; delayed notifications must not overwrite a valid later state. An unresolved response needs investigation before a replacement instruction is submitted. Reconcile internal records to provider evidence and assign every difference an owner.

Confirm access controls, payment approvals, audit logging and recovery procedures. Identify personal-data processing roles and contractual duties. Check that support staff can distinguish a pending payment from a completed transfer and can escalate fraud or account restrictions without inventing assurances.

Review the full commercial schedule, including manual reviews, failed verification, dormant accounts, disputes, support and exit. Establish billing start dates, service levels, liability allocation, data exports and transition assistance. Price the work retained by your team as well as the provider's fees.

Agree a customer-funds wind-down plan for the end of the partnership or failure of the issuer. Assign responsibility for stopping new funding, reconciling balances, resolving pending payments and communicating with customers. Set out how customers can redeem balances during an orderly closure and how records and operational support will enable funds to be returned through the applicable insolvency process if the issuer fails. Customer communications should explain the relevant process without promising immediate access or guaranteed recovery.

Set release gates with named finance, operational, technical and compliance approvers. Missing permissions, misleading disclosures or unexplained customer balances should block live activity. Start within agreed customer and transaction limits, then expand only when reconciliation, support and incident handling meet the acceptance criteria.

Maintain a change process after launch. A new customer group, credit feature, payment route or provider relationship can alter the original assessment, so require approval before enabling it rather than relying indefinitely on the initial programme sign-off.

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.

Next stepTurn your UK product requirements into a practical implementation plan.Discuss the infrastructure, partners and operating model for your use case.Book a discovery call