The U.K. to U.S. Money Transfer Corridor: FCA Licence on One End, MSB on the Other

Moving money between the United Kingdom (“U.K”) and the United States (“U.S”) looks simple to the customer. A user opens an app, enters an amount, confirms the exchange rate, and expects the money to arrive. However, for the fintech operator, it is a regulated financial service on both sides.

The U.K. to U.S. corridor may involve U.K. payment services regulation, U.K. e-money rules, U.S. federal money services business registration, U.S. state money transmitter licensing, anti-money laundering controls, sanctions screening, foreign exchange disclosures, consumer protection, and banking partner requirements. Its more than a payment feature.

A Financial Conduct Authority licence or registration in the U.K. does not automatically authorise the U.S. side. A U.S. Money Services Business registration does not automatically solve the U.K. side. This article explains why founders must analyse both ends of the corridor before launch.

Why this corridor needs careful structuring

The U.K. and U.S. are both mature financial markets which can make founders assume the rules are straightforward. They are not.

A U.K.-based fintech may need authorisation or registration from the Financial Conduct Authority (FCA) if it provides payment services or issues electronic money. The FCA explains that firms may need to apply if they want to provide payment services, issue electronic money, or operate as certain account information or payment initiation service providers.

On the U.S. side, a business that transfers funds may be treated as a money transmitter and therefore as a Money Services Business (MSB). Financial Crimes Enforcement Network (FinCEN) states that no activity threshold applies to money transmission, meaning a person engaged as a business in transferring funds can be an MSB regardless of transaction amount.

For a fintech operator, this means the legal analysis should begin before launch. You should not wait until banks, investors, or regulators ask how the corridor is licensed.

Start with the actual money flow

Before asking which licence is needed you should map the transaction.

A U.K.-to-U.S. corridor may involve several steps:

A customer in the U.K. funds a transfer;
The platform receives or initiates payment in pounds sterling;
The platform or its partner converts pounds into U.S. dollars;
Funds are settled through a bank, payment processor, or correspondent arrangement;
The U.S. recipient receives a bank deposit, card payout, wallet credit, or cash equivalent.

Each step matters because regulators will look at what the business actually does, not only what the product is called.

You want to ask who contracts with the customer, who receives and holds customer funds, and who controls the exchange rate. Also, probe who decides whether a transaction is accepted or rejected, who delivers funds to the U.S. recipient, and who manages failed transactions and refunds.Then, highlight accountability by asking who is responsible for anti-money laundering checks and who ultimately owns the customer relationship.

If your company only provides software to a licensed provider, your licensing position may be different. But if your company controls the customer experience, receives funds, moves money, sets fees, or markets itself as the transfer provider, you may be carrying on regulated activity.

The U.K. side: payment institution or EMI?

In the U.K., the first question is whether your business provides payment services, issues electronic money, or does both.

The FCA states that payment services are listed under the Payment Services Regulations 2017. In summary, they include services connected to payment accounts, execution of payment transactions, issuing payment instruments, acquiring payment transactions, money remittance, account information services, and payment initiation services.

For a U.K.-to-U.S. remittance product, “money remittance” is often the starting point. In simple terms, money remittance means taking money from one person and sending it to another person without opening a payment account for the customer.

However, the analysis may change if your product also holds value for users. If customers can hold balances in the app, spend from those balances, or keep wallet value before making a transfer, the product may be considered electronic money.

The FCA explains that firms applying to become electronic money institutions may apply as an authorised electronic money institution or register as a small electronic money institution, depending on their model and thresholds.

The practical distinction is important:

A payment institution model may fit a business that executes transfers but does not issue stored wallet value.
An electronic money institution model may be needed where the business issues electronic value that users can store and use.
A hybrid model may involve both payment services and e-money issuance.

Founders should avoid choosing the licence label first. The better approach is to define the product, then classify the regulated activity.

Authorised institution or small institution?

Some U.K. fintechs may qualify for a smaller registration category. Others will need full authorisation.

The FCA’s application guidance indicates that firms providing payment services or issuing e-money should determine whether they need to be authorised or registered. The FCA also notes that small electronic money institutions have transaction limits and cannot provide certain services such as account information services or payment initiation services.

For operators, a key question is whether the business is being built as a limited U.K. product or as a cross-border payments company that can grow. If the product is designed for growth, institutional partnerships, or large transaction volume, a small registration category may not be enough.

You should consider:

Assessing the expected monthly transaction volume and whether users will hold balances.

Whether the product includes business customers and whether it supports multiple corridors.

A licence strategy should match the business plan, not just the launch plan.

The U.S. side: MSB registration is only the beginning

In the U.S, a money transfer business usually starts with federal MSB analysis.

FinCEN states that, with limited exceptions, each MSB must register with the Department of the Treasury. The registration is generally filed within 180 days after the MSB is established and must be renewed every two years.

The Internal Revenue Service, summarising Bank Secrecy Act requirements, also states that anyone who,as a business,transfers funds is an MSB as a money transmitter, no matter how little money they send..

In practical terms, if your company is receiving funds for transmission to another person in the U.S., or is otherwise participating in the transfer of funds as a business, you should assess whether MSB registration is required.

However, this is where many fintechs make costly mistakes. FinCEN registration is not the same as state licensing.

A federal MSB registration tells the U.S. Treasury that the business is operating as an MSB. It does not automatically give the company permission to transmit money in every U.S. state. Many states have their own money transmitter licensing regimes. Depending on the model, a company may need state-by-state licences, an exemption, or a licensed partner.

So the U.S. side should be analysed at two levels:

Federal MSB registration and Bank Secrecy Act compliance.
State money transmitter licensing or Partnership coverage.

MSB registration is an important compliance step, but it is not a complete licensing strategy.

FinCEN explains that MSBs must register, renew registration every two years, and retain a copy of the registration and supporting documentation in the U.S for five years. The registration supports federal supervision and anti-money laundering oversight. It does not answer every commercial question.

Banks, payment processors, card networks, and enterprise customers typically demand clear answers on compliance and responsibility. They will ask whether you are licensed in the U.S., where you operate and if you are using a licensed money transmitter partner. They want to know who the regulated entity of record is, who holds customer funds, and who performs KYC and sanctions screening. They may also inquire about who files suspicious activity reports, who handles consumer complaints, and who is liable for failed or delayed transfers. This is to establish the regulatory and operational accountability expected in financial services.

Partnership models can work, but only if the roles are clear

Many fintechs do not obtain every licence themselves at the beginning. Instead, they work with licensed partners. This can be a practical route, especially for early-stage operators testing a corridor.

A U.K.-to-U.S. corridor may involve:

An FCA-authorised payment institution or EMI in the U.K.
A U.S. licensed money transmitter or bank partner
A sponsor bank
An FX provider
A payment processor
A compliance technology provider

The contract must spell out responsibilities exactly. The fintech should know exactly which party provides regulatory cover for each activity. A weak contract might simply state, “Partner will handle compliance,” whereas a stronger one should clearly identify who is the regulated provider for the U.K. part and for the U.S. part, who performs customer due diligence, and who screens sanctions lists. It should also specify who monitors transactions, who files regulatory reports, and who handles chargebacks, refunds, and failed transfers.

In addition, it must define who owns customer complaints, who keeps transaction records, and who responds to regulator requests. By addressing each of these points, the contract ensures clarity, accountability, and resilience in the partnership. The more regulated the product, the less room there is for vague operational language.

AML and sanctions compliance must cover both jurisdictions

A U.K.-to-U.S. transfer product will be expected to have strong anti-money laundering and sanctions controls.

For the U.S. side, MSBs are treated as financial institutions under the Bank Secrecy Act framework. FinCEN and IRS materials explain that MSBs have registration, recordkeeping, reporting, and AML programme obligations. The IRS states that MSBs must develop and implement an AML compliance programme designed to prevent the business from being used for money laundering or terrorist financing.

In practical terms, a fintech should establish robust controls across key compliance and risk areas. These include customer identification and beneficial ownership checks for business customers, as well as sanctions screening and politically exposed person checks. Strong fraud monitoring mechanisms, transaction limits, and escalation procedures for unusual activity are also essential.

The framework must cover suspicious activity reporting, thorough recordkeeping, employee training, and independent testing. These controls should be built into the product flow and should not sit in a policy folder that no one uses.

For example, if a user sends five transfers to five unrelated recipients in one hour, the product should flag that pattern. If a business customer suddenly changes its transfer behaviour, the system should raise an alert.

FX disclosure is not just a pricing issue

Most U.K.-to-U.S. transfers involve currency conversion. That makes foreign exchange disclosure important.

Users should have a clear understanding of the key elements of their transfer. Many customer complaints arise because users do not understand the difference between a fee and an exchange rate spread.

They need to know the amount they are sending in pounds, the exchange rate applied, and any transfer fee or FX markup. Transparency also requires showing the amount the recipient will receive in U.S. dollars and the expected delivery time. In addition, users should be informed about what happens if the rate changes before settlement and how refunds are calculated.

A clear product flow should show all key information before the user confirms the transfer. The company should also store a transaction receipt showing the rate, fee, payout amount, and timestamp.

Consumer protection and error handling should be designed early

Cross-border payments fail for ordinary reasons. A user enters the wrong account number. A recipient bank rejects the payment. A compliance review delays the transaction. A customer wants a refund after the FX conversion has already occurred.

These issues should not be solved informally after launch. They should be built into the product and contracts.

Your user terms should clearly set expectations for when a transfer becomes final, when the company may delay or reject it, how refunds are handled, and whether FX losses or gains affect those refunds. They should also explain how customers can complain, how long investigations may take, and what happens if a payout partner fails.

Operational resilience matters

Payments businesses are judged not only by licensing, but also by reliability. If the corridor fails, users may not care which partner caused the problem. They will blame the brand they used.

A U.K.-to-U.S. operator should be prepared for a range of operational and compliance challenges. These include bank downtime, processor outages, and rejected payouts, as well as liquidity shortages. The operator must also anticipate risks such as FX provider failure, cybersecurity incidents, and sudden surges in customer support demand. Addressing these early helps ensure resilience and continuity in cross-border payment operations.

The FCA has placed continuing emphasis on operational resilience for payments and e-money firms, and its application materials direct firms to consider operational resilience as part of their broader regulatory obligations.

For founders, the practical question is: can the product keep working safely when something goes wrong?

A practical launch checklist

Before launching a U.K.-to-U.S. money transfer corridor, fintech operators should complete a corridor-specific checklist.

First, map the money flow. Identify who collects funds, holds funds, converts currency, transmits value, and pays out the recipient.
Second, classify the U.K. activity. Decide whether the product involves payment services, money remittance, e-money issuance, or a combination.
Third, confirm the FCA route. Determine whether the business needs authorisation, registration, variation of permission, or a licensed partner.
Fourth, classify the U.S. activity. Assess whether the business is a money transmitter and MSB under federal rules.
Fifth, review state licensing. Do not stop at FinCEN registration. Confirm whether state money transmitter licences, exemptions, or partner coverage are needed.
Sixth, document the partner model. Identify the regulated entity for each part of the corridor and allocate compliance duties clearly.
Seventh, build AML and sanctions controls. These should be product-level controls, not just written policies.
Eighth, design customer disclosures. Show fees, FX rates, delivery timelines, recipient amounts, and refund rules before confirmation.
Ninth, prepare records. Keep evidence of licences, partner due diligence, transaction receipts, customer checks, monitoring alerts, and complaints.
Tenth, review the corridor regularly. Regulatory expectations, partner permissions, and product features can change.

Conclusion

The U.K.-to-U.S. money transfer corridor can be commercially attractive, but it should be treated as a regulated corridor from day one.

On the U.K. side, the business may need to consider FCA payment institution or electronic money institution requirements. On the U.S. side, the business may need FinCEN MSB registration, Bank Secrecy Act compliance, and potentially state money transmitter licensing or licensed partner coverage.

The safest approach is to build the corridor around the actual money flow. Identify the regulated activities, confirm who is licensed for each leg, allocate compliance duties in writing, and make the user experience transparent. For further information or assistance with corridor compliance and advisory services, please fill out our Contact Us Form.