Do You Need an EMI Licence for a UK Payment or Banking Product?

Does Your Product Need EMI, Payment Institution or Bank Permissions?

The UK regulatory route depends on what your business does with customer money and which entity provides each service. A wallet, prepaid card, payment account or banking app does not determine the permissions required by its name alone. Start by mapping who receives the funds, who owes the customer money, how payments are executed and whether balances fund lending or other business activities.

E-money is electronically stored monetary value issued on receipt of funds for making payment transactions, representing a claim on the issuer and accepted by someone other than that issuer. It includes value stored magnetically. For example, a customer loading GBP 100 into a wallet for spending with independent merchants may be purchasing e-money. A wallet that merely stores card credentials does not issue e-money simply because it enables payments. The legal definition and contractual arrangements determine the outcome.

Use the following funds-flow decision table to identify the starting regulatory route. These routes assume the relevant activity is carried on in the UK as a business and no applicable exclusion or exemption applies.

An "EMI licence" generally refers to FCA authorisation under the Electronic Money Regulations 2011. Small EMI registration is a separate route for eligible businesses, including those with average outstanding e-money no higher than EUR 5 million. Other conditions apply, including limits on unrelated payment services. Small EMIs cannot provide account-information or payment-initiation services. An EMI can also provide payment services within its permitted scope without obtaining separate payment institution authorisation.

Unlike a bank savings account, e-money cannot earn interest from its issuer or carry benefits linked to how long it is held, under regulation 45. This restriction matters when designing savings-like features.

Not holding customer funds does not automatically remove the need for regulation. An app providing consolidated information about payment accounts may provide an account-information service; an app initiating payments from accounts held elsewhere may provide a payment-initiation service. These activities are expressly outside the technical-service exclusion. A business providing only account-information services can generally use the registered account information service provider route, while payment initiation requires the relevant authorisation.

Likewise, a restricted-use card is not automatically exempt. The limited-network exclusion can cover qualifying instruments usable within a limited merchant network or for a very limited range of goods or services. A general-purpose wallet does not qualify merely because participating merchants sign agreements. Providers relying on the relevant exclusion must notify the FCA when transaction value exceeds EUR 1 million in any 12-month period; this is a notification threshold, not a general exemption for smaller businesses. See the FCA's Payment Services and Electronic Money Approach Document for guidance on these regulatory boundaries.

UK authorisation does not provide EEA passporting rights. Serving customers outside the UK requires a separate assessment of local rules and any authorisation requirements, as explained in the FCA's post-Brexit guidance.

Adding lending does not automatically require bank authorisation. Assess the funding model and the credit activity separately: lending may require additional FCA consumer-credit permissions, while accepting deposits raises a distinct regulatory question. Before committing a launch budget, document the funds flow, customer contractual claims and responsible legal entities. That assessment establishes the permissions the product needs and provides the basis for deciding whether your business or a regulated partner will perform each activity.

Can You Launch Through a Regulated Partner Instead?

Yes. A UK business can often launch a wallet, prepaid card or payment account through an authorised electronic money institution, or another appropriately authorised issuer, rather than first obtaining its own EMI authorisation. The partner model works only when the regulated firm genuinely carries on the regulated activities and the programme remains within its permissions, risk appetite and approved operating model. A label such as white label, embedded finance or banking as a service does not create a legal exemption.

The first question is who issues the e-money and who provides each payment service. The regulated EMI must remain the issuer: an EMI may use an agent or distributor to distribute or redeem e-money, but it cannot issue e-money through either of them. If the programme business acts as the EMI's payment-services agent, it must be entered on the Financial Services Register before providing those services. A distributor can distribute or redeem e-money but cannot use that status to provide payment services. Distribution alone does not require agent registration, but the principal EMI should notify the FCA of its use of the distributor. A business supplying software only may be an outsourced technology provider, but the analysis changes if it controls payment execution, customer funds or regulated decisions.

The EMI is responsible under the Electronic Money Regulations for acts and omissions of its agents and distributors as if they were its own. That explains why partner onboarding is detailed. Expect scrutiny of owners, directors, business model, customer types, funds flow, financial-crime controls, marketing, complaints, operational resilience, data security and financial forecasts. The partner may reject a product, impose limits, require reserves or prefunding, approve every material change and audit the programme.

Before signing, verify the legal entity on the FCA Financial Services Register, its e-money status, payment services, requirements, restrictions and any agents. A familiar trading name or platform interface is not enough. Obtain written confirmation of which entity contracts with customers, issues e-money, receives funds, safeguards them, executes payments and handles redemption. E-money safeguarded by an EMI is not a bank deposit and is not protected by the Financial Services Compensation Scheme; customer disclosures should not imply otherwise.

Create a responsibility matrix covering:

• KYC or KYB, sanctions screening, transaction monitoring, suspicious activity escalation and account restriction.
• Safeguarding, settlement, reconciliations, liquidity, fees, refunds, chargebacks and shortfall escalation.
• Customer terms, financial promotions, consent, complaints, vulnerable customers and regulatory reporting, including clear complaint escalation and access to the Financial Ombudsman Service for eligible complainants.
• Consumer Duty, where applicable: target-market assessment, fair value, customer understanding, support and monitoring of outcomes, with EMI oversight of delivery through agents and distributors.
• Security, access control, incident notification, business continuity, subcontractors and data-protection roles.
• Product changes, new countries or currencies, approval rights, audit access, termination and customer migration.

Commercially, compare implementation fees, recurring minimums, per-customer and per-transaction charges, scheme and card costs, foreign-exchange sharing, reserve requirements and exit costs. The contract should also address service levels, liability, regulatory change, ownership of customer data and the practical ability to export records and transfer customers if the relationship ends.

A partner route can reduce initial regulatory lead time, but it creates dependency on the issuer's permissions, systems and continued willingness to support the programme. It does not remove the programme company's own obligations under contract, data protection, consumer law, financial promotions or any separately regulated lending or credit activity. Map the actual funds flow and customer journey with UK regulatory counsel before treating the model as outside direct authorisation.

What Does Your Own EMI Authorisation Require?

Obtaining your own authorised electronic money institution status means the applicant, not a sponsor, becomes responsible for issuing e-money and for every regulated payment service within its authorisation. The FCA assesses whether the firm can satisfy the Electronic Money Regulations at authorisation and on an ongoing basis. A detailed business plan is not enough unless the people, capital, controls and operational evidence show that the firm is ready to operate safely.

The applicant must meet the corporate and UK-presence conditions. A body corporate formed under UK law must have its head office, and any registered office, in the UK. The regulations also provide a route for some overseas bodies with a UK branch. In either case, at least part of the e-money and payment services business must be carried on in the UK, and group or overseas links must not prevent effective FCA supervision.

The EUR 350,000 figure is regulatory capital, not an application fee or a launch budget. An authorised EMI must maintain own funds equal to at least EUR 350,000 or the calculated ongoing own-funds requirement, whichever is greater. Method D normally requires 2% of average outstanding e-money, subject to FCA adjustment; unrelated payment services generate additional capital requirements. The financial model should cover three years, explain revenue and cost assumptions, include balance-sheet forecasts and show stress scenarios. Capital must be available in an eligible form; borrowed cash or unverified future investment should not be presented as committed regulatory resources without analysis.

Safeguarding is a central operating obligation. The firm must identify relevant funds and protect them through segregation or eligible insurance or guarantee arrangements. Since 7 May 2026, applicable firms must also comply with CASS 15, CASS 10A and related reporting and audit requirements, including internal and external safeguarding reconciliations at least once each reconciliation day and applicable monthly safeguarding returns. Discrepancies must be investigated and resolved. Safeguarded funds are not working capital, and safeguarding is different from deposit protection: e-money is not a bank deposit and is not covered by the Financial Services Compensation Scheme as a deposit.

Customer terms and systems must support issuance at par without delay on receipt of funds and redemption at par on request, subject to the statutory conditions. Redemption fees are permitted only in specified circumstances and must be disclosed in advance.

The application should contain tailored, internally consistent evidence, including:

• A precise programme description, customer journey and end-to-end funds-flow diagrams for issuance, payments, redemption, fees and settlement.
• A three-year business plan, forecasts, stress tests, capital calculation, liquidity plan and wind-down triggers, plus a separate business plan for any unrelated payment services.
• Governance maps, role descriptions, staffing plans, controller information and evidence of relevant competence.
• Policies for safeguarding, AML, sanctions, fraud, security, operational resilience, complaints, outsourcing, data and regulatory reporting.
• Evidence of Consumer Duty compliance for in-scope retail business, including product governance, fair-value assessments and monitoring of customer outcomes.
• Professional indemnity insurance or a comparable guarantee where account-information or payment-initiation services are proposed.
• Contracts or advanced arrangements with banks, processors and material suppliers, with responsibilities and audit access clearly allocated.

A small EMI registration can be an alternative only if its conditions are met. These include a EUR 5 million ceiling for average outstanding e-money and, where applicable, a EUR 3 million monthly average for payment transactions unrelated to e-money issuance, measured over the preceding 12 months. The latter is not a cap on payments made using the firm's e-money. A small EMI cannot provide account-information or payment-initiation services.

Small EMI registration is not necessarily capital-free: where actual or projected average outstanding e-money is EUR 500,000 or more, initial capital is generally at least 2% of that amount, with an ongoing own-funds requirement. Safeguarding e-money funds is mandatory, while safeguarding funds for unrelated payment services is optional for small EMIs. Growth assumptions and the intended service set should determine the route from the outset.

EMI authorisation does not authorise deposit-taking. It also does not automatically cover every credit or lending activity, which may require separate permissions under consumer-credit or other regimes. Define the permission perimeter service by service, then build governance and systems around the regulated activities actually proposed. Once authorised, the firm must continue to meet its capital, safeguarding, conduct, reporting and notification obligations as the product and supplier network change.

What Are the Application Steps, Costs and Timelines?

An EMI application is a regulatory readiness project, not a form-filling exercise. The business normally needs a preparation phase to define the permission perimeter, recruit accountable people, secure capital and produce operating evidence. Budget for preparation, regulatory assessment and any post-authorisation work needed before customer launch.

A practical sequence is:

• Scope the model: document customers, products, jurisdictions, e-money issuance, payment services, funds flows, outsourcing and any lending or credit activity. Decide whether authorised EMI or small EMI status fits the forecast.
• Build the applicant: establish the required UK presence, appoint competent directors and managers, identify controllers, secure eligible capital and agree material banking and technology arrangements.
• Prepare evidence: complete tailored policies, three-year forecasts, stress tests, governance maps, safeguarding method, AML framework, security and resilience plans, complaints process and wind-down plan.
• Preflight the submission: reconcile every form, policy, contract, forecast, customer journey and funds-flow diagram. Explain items that do not apply rather than leaving unexplained gaps. The FCA may reject a submission without assessing it if minimum required information is missing.
• Submit through Connect: provide the correct application and individual or controller forms, nominate an internal main contact and pay the non-refundable fee.
• Respond to assessment: answer the case officer's questions promptly, update evidence where facts change and be ready for calls or meetings with the FCA.

The FCA application fee is only a small part of the total funding need. There is no official standard total project cost because scope, staffing, outsourcing and technology differ materially. Prepare a cash budget that separates regulatory capital, safeguarded customer funds, settlement liquidity, supplier reserves, one-off implementation expense and recurring operating cost. Safeguarded funds cannot finance payroll or product development.

Illustrative budget only: assume an authorised EMI uses an outsourced platform, with a small internal team and combined staffing, supplier and overhead costs of GBP 50,000 a month. Twelve months of operating runway would cost GBP 600,000; adding GBP 150,000 for one-off implementation and advice and GBP 150,000 contingency gives GBP 900,000, before the application fee, regulatory capital, settlement liquidity and reserves. These are hypothetical inputs, not market benchmarks; replace them with hiring plans and supplier quotes.

For timing, the Electronic Money Regulations require the FCA to determine a complete authorisation application within three months. An incomplete application may be determined earlier, but must in any event be determined within 12 months of receipt. These are determination periods, not promises of approval. The FCA usually has follow-up questions and may ask an applicant that is not ready, willing and organised to withdraw and reapply. Its current published timeframe to allocate an EMI case officer is a maximum of 20 working days, which should not be confused with the determination deadline.

Illustrative planning timeline only: a firm with key managers identified, committed funding and an established technology supplier might allocate three to six months to preparation and one to three months to final implementation after authorisation, alongside the applicable FCA assessment period. These preparation and implementation ranges are assumptions, not FCA service standards. Recruitment, safeguarding-bank onboarding or system remediation may extend them, and a 12-month operating budget may need additional runway.

Use the FCA's pre-application support service where useful, but do not treat a pre-application discussion as approval of the eventual model. After submission, keep forecasts, ownership, key people, suppliers and product scope current; material changes can require revised evidence and further assessment. Do not commit to an unconditional public launch date until authorisation is effective, required agents are registered, safeguarding and operational controls are live, and all partner approvals have been obtained.

For a CFO, the forecast should show separate preparation, assessment and launch-readiness stages, with contingency for delays and additional operating costs. Current fees and rules should be checked again immediately before submission, and specialist UK advice should confirm the permission scope.