How to Launch a Money Transfer Business in the UK: 2026 Complete Guide

Who this is for

This guide is for founders preparing a UK remittance operation or putting an approved business model into practice. It focuses on payment-institution routes, application preparation, funds responsibilities and software readiness. It does not determine your eligibility or cover every regulatory model.

Define the operating model before committing to software: permissions, providers, customer funds and operational controls determine the requirements.

1. SPI or API: services, eligibility and volume

The appropriate route depends on your services and eligibility, not transaction volume alone.

SPI eligibility includes a limit of €3 million in average monthly payment transactions, as well as other conditions. Being below that threshold does not itself grant eligibility or permission to trade. Check your services and circumstances against PERG 15.4 and the FCA applicant guidance.

Two consequences people miss:

• Small PIs cannot provide account information services or payment initiation services. AIS-only businesses may use the registered account information service provider route; PIS requires the appropriate authorisation. See the FCA's AIS/PIS guidance.
• Small PIs have no initial capital requirement. The FCA’s capital chapter states plainly that it “is not relevant to small PIs” (Our Approach, 9.1). You will still need working capital to run the business — that is a commercial question, not a regulatory one.

Initial capital applies to authorised PIs, and the amount depends on what you do: €20,000 for money remittance, €50,000 for payment initiation services, €125,000 for the services in Schedule 1 Part 1(1)(a) to (e). Where more than one applies, you hold the greater amount. Our Approach, 9.7–9.8.

If you are close to €3m, model it honestly. Registering as a small PI and outgrowing it means applying for authorisation later anyway, with the disruption landing exactly when the business is working.

2. The application pack, document by document

The FCA publishes separate API and SPI application requirements. Use the current list for your route; the preparation areas include:

• Programme of operations — the payment services you intend to provide, and how.
• Details of the individuals responsible for the payment services business and for managing the firm.
• Anyone with a qualifying holding.
• Control mechanisms to meet your obligations under the Money Laundering Regulations.
• Your measures to safeguard payment service users’ funds, where applicable.
• Procedures for incident reporting, data management and business continuity.
• A security policy, and a policy for security-related customer complaints.
• MLR registration details, where applicable.
• Outsourcing arrangements and any plans to use agents.

Check financial information for either route. API applicants also need the applicable capital evidence, governance and risk-management material, including a wind-down plan. AIS/PIS applicants must address applicable insurance or comparable-guarantee requirements. Use the separate checklists in FCA, Payment institution applicants, rather than treating this summary as the submission pack.

Everyone with a qualifying holding must be a fit and proper person “having regard to the need to ensure the sound and prudent conduct” of the business, and directors and managers must be of good repute with appropriate knowledge and experience. Nobody managing or operating the business may have been convicted of offences relating to money laundering, terrorist financing, the payment services regulations, or financial crime. The firm must have its head office or registered office in the UK and carry on payment services business here. PERG 15.4.

3. Safeguarding, mechanically

Safeguarding is an operational obligation where it applies, not a software label. The supplementary rules effective from 7 May 2026 add requirements around reconciliation, reporting, records and oversight. Check the current FCA safeguarding guidance and applicable CASS/SUP rules alongside the principles below.

There are exactly two methods: the segregation method, or the insurance or comparable guarantee method. You may use one for some relevant funds and the other for the rest. Our Approach, 10.36.

Segregation is not a book entry. The FCA is explicit: “It would not be sufficient to segregate funds in the institution’s books or records; if held electronically, the funds must be held in a separate account at a third party account provider, such as a credit institution. Funds held in banknotes and coins must be physically segregated.” (10.39)

The mechanics:

• Segregate as soon as funds are received — not at end of day, not at reconciliation. (10.39)
• If funds are still held at the end of the business day following receipt, deposit them in a separate account with an authorised credit institution or the Bank of England, or invest them in secure liquid assets the FCA approves and place those with an authorised custodian. (10.38)
• Mixed receipts — where a customer pays relevant funds and your fees together — must be split “as frequently as practicable throughout the day”, and “in no circumstances should such funds be kept commingled overnight”. (10.40)
• Agents and distributors holding funds on your behalf do not transfer the obligation. You remain responsible for ensuring they segregate. (10.41)

Small PIs are not required to safeguard. A small PI that chooses to can offer users the same protection an authorised PI must provide. Whichever you decide, record the decision and the reasoning — and confirm the current position with the FCA before you rely on it.

Plan account onboarding early and confirm your chosen method with your advisers and account provider. Remitz does not open safeguarding accounts or hold the funds; software records do not constitute safeguarding.

4. HMRC money service business registration

Confirm who supervises your business for anti-money-laundering purposes and whether HMRC registration is required for your activities. Do not assume FCA status removes that requirement, or that every business needs duplicate registration. Check applicability, current fees and the application process directly with HMRC. Where applicable, the FCA asks for your HMRC registration or application details.

5. Timelines, and what actually causes delay

The rule that governs everything:

The clock does not start when you submit. It starts when the FCA agrees your pack is complete. Where an application is incomplete they ask in writing for more, then “confirm the date from which we consider the application to be complete” — and the three months runs from that date. (3.17)

There is an outer limit. For an incomplete application the FCA “must make a decision within 12 months of receipt”, and they say plainly that if discussions have not produced everything they need within that window, “it is likely that the application will be refused” — because they will not have been able to satisfy themselves the requirements are met. (3.200)

A statutory decision period does not ensure approval or establish your launch date. Plan for application preparation as well as assessment and separate provider onboarding. Potential dependencies include:

• The safeguarding account. Bank onboarding for a pre-authorisation payments firm is slow and outside your control.
• Fitness and propriety evidence for individuals, particularly anyone overseas.
• A programme of operations that describes ambition rather than operations. If it does not match your actual flows, expect questions.
• AML documents written to be filed rather than used. A risk assessment that does not reflect your corridors is visible immediately.
• Provider contracts — the FCA may ask to see drafts.

6. Further information requests, and refusal

The FCA can require further information before determining an application. A request may identify a material gap, so assess it with your advisers and respond within the stated deadline. (3.17)

Refusal has a defined process, and it is worth knowing it exists before you need it:

• The FCA can refuse “when the information and evidence provided does not satisfy the requirements” of the PSRs 2017. (3.206)
• They must give a warning notice setting out the reason, and allow 28 days to make representations. (3.206)
• Representations may be oral or written. For oral representations, notify within two weeks of the warning notice so a meeting can be arranged inside the 28 days. (3.207)
• If refusal stands, a decision notice follows, and the firm may refer the matter to the Upper Tribunal (Financial Services). If no referral is made within 28 days, a final notice is issued. (3.208)

If you receive a notice, seek professional advice on its specific grounds and deadlines. This summary is not advice on representations or an appeal.

7. Choosing payout, KYC and gateway providers

These are commercial decisions with regulatory consequences, and they are yours to make directly.

Payout partners determine available services under your agreement. Check your actual corridors and delivery methods, not just a network's headline reach. Ask what happens when a payout fails, who holds the funds while it is investigated, and what reconciliation records are available.

KYC and screening providers need to match your customer base, not a generic average. Document coverage for the nationalities you actually serve matters more than headline pass rates, and you will need sanctions and PEP screening with a defensible tuning and review process.

Payment gateways support customer funding through the agreed services. Map receipt, entitlement, settlement and refunds with your provider and advisers to establish when safeguarding applies to your actual funds flow. Do not infer the legal treatment from a software status.

With Remitz, you hold your own provider agreements, accounts and credentials. Other arrangements must be evaluated on their actual contracts and responsibilities; a software integration alone does not give access to financial services.

8. Software

Once you know the operating requirements, test the software against them. Financial records, provider failures and reconciliation deserve as much attention as customer-facing screens.

What matters:

• Does it produce the evidence a regulator asks for? Audit trails, transaction monitoring output, and the returns your permission requires — small PIs file the FSA057 Small Payment Institution Return (SUP 16 Annex 28D).
• Does it integrate the providers you chose, rather than the providers it resells?
• Can you leave? Data export, and whether the provider relationships are in your name.
• Build or buy. Building means the compliance surface is yours to maintain forever, not just to write once.

Remitz is one option among several, and this guide is usable without it. To evaluate the technology, book a demo with your provider shortlist and operating requirements. Remitz's typical 15–30-day implementation is subject to authorisation, provider readiness, credentials, configuration and testing; it is not the time needed to obtain permission or accounts.

Your Pre-Launch Checklist

Adapt this checklist to your firm with your advisers. Each applicable requirement needs evidence and an accountable owner; an inapplicable item needs a documented reason. Completing a website checklist does not grant permission to launch.

• ☐ FCA SPI registration or API authorisation granted and published on the Financial Services Register
• ☐ AML supervisory body confirmed and HMRC registration completed where required
• ☐ MLRO appointed, named in FCA application, and operationally ready
• ☐ AML/KYC policy approved and staff trained
• ☐ Applicable capital requirements assessed and evidenced
• ☐ Safeguarding obligations and any opt-in arrangements assessed, documented and implemented
• ☐ Software platform configured and white-labelled
• ☐ KYC provider integrated and tested
• ☐ Sanctions and PEP screening live
• ☐ Payout partners contracted in every launch corridor
• ☐ FX rates and corridor margins configured
• ☐ Agreed customer channels tested and ready for the approved launch scope
• ☐ Agreed notification channels tested, with required customer and provider information retained
• ☐ Terms of service, privacy policy, and customer agreements published
• ☐ Required report inputs/exports tested, with review and submission responsibilities assigned
• ☐ Complaints-handling process documented
• ☐ Business continuity and disaster recovery tested

Further Reading Across the Launch Journey

• How to Start a Money Transfer Business in the UK — the long-form explainer version of this playbook.
• Agent Network Management for Remittance Businesses — hierarchy, commission, settlement, agent-level compliance.
• Money Transfer Business Software: Build vs Buy 2026 — the technology decision.
• Ready-Made SPI Licence UK — should you buy a pre-authorised firm?
• White-Label eWallet Software: Buyer's Guide 2026 — adding a wallet to your launch.