Money Service Business registration and fiat remittance routes
A Money Service Business (MSB) registration is the primary regulatory route for remittance providers, currency exchange operators, and money transmitters in jurisdictions outside the EU/EEA, where PSD2/EMD2 do not apply. MSB frameworks are registration-based (rather than full authorisation) in most jurisdictions, with mandatory AML and financial crime controls as the central compliance obligation.
What an MSB registration covers
The definition of an MSB varies by jurisdiction. The following activities are consistently captured by MSB frameworks across the UK (HMRC), US (FinCEN), Canada (FINTRAC), and Australia (AUSTRAC).
- Money transmission — sending or receiving money domestically or cross-border on behalf of customers.
- Currency exchange — exchanging one national currency for another (spot and some forward transactions).
- Cheque cashing and money orders — converting cheques, money orders, or stored-value instruments to cash.
- Prepaid access — issuing, selling, or redeeming prepaid access instruments (jurisdiction-specific definition).
- Hawala and informal value transfer — operating value transfer systems outside the traditional banking system.
- Payment processing — where the processor accepts funds and transmits value, crossing the MSB threshold.
Providing MSB services without registration is a criminal offence in most jurisdictions. FinCEN in the US, HMRC in the UK, FINTRAC in Canada, and AUSTRAC in Australia all maintain active enforcement programmes targeting unregistered MSBs.
What this route does not cover
MSB registration is a fiat-focused route and carries significant limitations relative to EU payment institution frameworks.
- MSB registration does not confer EEA passporting rights — each jurisdiction requires separate registration or licensing.
- MSB registration does not authorise deposit-taking or lending — banking or credit institution authorisation is required for those activities.
- In jurisdictions where PSD2 applies (all EEA member states), MSB registration is not sufficient — PI or EMI authorisation is required.
- Crypto-specific money transmission (e.g. virtual asset exchange, VASP activities) typically requires a separate crypto/VASP registration in addition to, or instead of, the fiat MSB route — see the route scope section below.
- MSB registration does not provide investor protection, deposit guarantee, or segregation obligations equivalent to EMI safeguarding.
Fiat MSB vs Crypto MSB — route scope
The MSB framework captures both fiat and crypto activities in several jurisdictions, but the regulatory treatment differs. Ensure you identify the correct route for your model.
- Fiat MSB (this page)Covers: Remittance, currency exchange, and fiat money transmission. Regulated by HMRC (UK), FinCEN (US), FINTRAC (Canada), AUSTRAC (Australia). Core compliance obligation is AML/CTF. No mandatory capital in many jurisdictions.Not for: Businesses whose primary activity is virtual asset exchange, crypto custody, or crypto-to-fiat conversion — those activities typically trigger VASP/crypto-specific registration requirements.
- Crypto MSB / VASPCovers: Virtual asset service providers — exchanging virtual assets for fiat or other virtual assets, transferring virtual assets, or providing custody. Subject to FATF Travel Rule and jurisdiction-specific VASP frameworks.Not for: Pure fiat remittance or currency exchange businesses with no virtual asset element.
MSB vs PI vs EMI — decision matrix
Use this matrix to determine whether a fiat MSB registration or an EU payment institution authorisation better fits your business model and target markets.
| Criteria | MSBRegistration (non-EEA) | PIEEA Authorisation | EMIEEA Authorisation |
|---|---|---|---|
| Money remittance | |||
| Currency exchange (spot) | |||
| Issue e-money / stored value | |||
| Accept deposits | |||
| EEA passport | |||
| Minimum prescribed capital | Varies (often none) | €20k–€125k | €350k |
| Safeguarding / segregation obligation | |||
| AML/CTF obligation | |||
| Typical authorisation timeline | 1–6 mo | 3–12 mo | 6–18 mo |
Permitted and excluded activities — fiat MSB
The MSB activity scope differs by jurisdiction. The following reflects the combined scope across major frameworks (UK, US, Canada, Australia).
Covered by this licence
- Domestic money transmission
- Cross-border remittance
- Spot currency exchange
- Cheque cashing and money orders
- Prepaid access issuance and redemption (US FinCEN definition)
- Informal value transfer (hawala)Must be registered; unregistered hawala is illegal
Not covered — separate licence required
- Accepting deposits repayable on demandBanking licence required
- Extending credit or loansConsumer credit or banking authorisation required
- Virtual asset exchange or custodySeparate VASP/crypto MSB registration required in most jurisdictions
- Payment services within the EEAPI or EMI authorisation required — PSD2 applies within the EEA
MSB compliance obligations
AML/CTF compliance is the defining obligation of an MSB registration. The following framework applies across all major MSB jurisdictions, with jurisdiction-specific variations noted.
Written AML/CTF policies and procedures, risk assessment, CDD procedures, enhanced due diligence for high-risk customers, and MLRO designation.
Systems to detect suspicious activity, threshold-based reporting, and filing of Suspicious Activity Reports (SARs) / Suspicious Transaction Reports (STRs) with the financial intelligence unit.
Identity verification for all customers above threshold; ongoing due diligence for higher-risk profiles; PEP and sanctions screening.
Retention of transaction records, customer identification records, and compliance documentation for the prescribed period (typically 5 years).
If operating any virtual asset activities, the Travel Rule requires originator and beneficiary information to accompany transfers above threshold.
Annual AML/CTF training for all relevant staff; documented training records.
Most MSB frameworks require annual registration renewal and periodic reporting of transaction volumes to the supervisory authority.
Is an MSB registration right for your project?
MSB registration suits businesses operating outside the EEA in money transmission and currency exchange. Evaluate the alternatives if your market includes EEA customers.
Best for
- Remittance operators targeting corridors entirely outside the EEA — e.g. US to LATAM, UK to Africa, Australia to South-East Asia.
- Currency exchange bureaux operating physical or online exchange services in non-EEA jurisdictions.
- Hawala and informal transfer networks seeking to regularise their operations under the AML framework.
- FinTech businesses targeting the US market where FinCEN MSB registration is the primary federal payment framework.
- Businesses that need a rapid, lower-burden regulatory entry point while preparing for EU PI/EMI authorisation.
Not for
- Businesses with EEA customers — PSD2 applies and PI/EMI authorisation is required regardless of where the business is registered.
- Wallet providers holding customer balances — EMI authorisation provides safeguarding and consumer protection that MSB registration does not.
- Businesses seeking EEA market access through passporting — MSB registration provides no passporting rights.
- Crypto-first businesses — VASP/MiCA frameworks are more directly applicable than fiat MSB registration.
Jurisdiction-specific MSB guidance
MSB requirements differ substantially across jurisdictions. Detailed country-level pages covering UK (HMRC), US (FinCEN), Canada (FINTRAC), Australia (AUSTRAC), Singapore (MAS), and UAE (VARA/CBUAE) are under development.
Related authorisation routes
If your business model includes EEA customers or requires e-money issuance, one of the following EU routes is likely necessary.
Businesses with EEA customers needing PSD2-compliant payment services. EEA passport, safeguarding obligations, and €20k–€125k minimum capital.
PI requires full NCA authorisation and a more extensive compliance framework than a fiat MSB registration.
Businesses that need to hold customer balances as stored value in addition to executing payment transactions across the EEA.
EMI carries €350k minimum capital and ongoing own-funds requirements — significantly more demanding than MSB registration.
Businesses whose services include virtual asset exchange, conversion, or custody as part of their MSB-adjacent model.
Crypto MSB/VASP frameworks are separate from fiat MSB registration in most jurisdictions and carry additional FATF Travel Rule obligations.
MSB registration — frequently asked questions
MSB registration is a notification-based framework in non-EEA jurisdictions (UK, US, Canada, Australia) focused primarily on AML compliance. A Payment Institution (PI) licence is a full authorisation under EU PSD2 that provides EEA passporting, safeguarding obligations, and a more comprehensive regulatory framework. If your customers are in the EEA, you generally need a PI licence rather than MSB registration.
Yes. In the UK, businesses providing money transmission or currency exchange services must register with HMRC as an MSB (Money Service Business) under the Money Laundering Regulations. Some activities also trigger FCA payment institution authorisation requirements — the two regimes can overlap.
No. FinCEN MSB registration is a federal requirement but does not substitute for state-level money transmitter licences (MTLs). Most states require separate MTL applications, and the US patchwork of state licensing is a significant operational burden for new entrants.
The FATF Travel Rule applies to virtual asset transfers. Fiat-only MSBs are generally subject to wire transfer rules requiring originator and beneficiary information, which are the fiat equivalent of the Travel Rule. If an MSB handles any virtual asset transactions, the FATF Travel Rule explicitly applies.
This page provides general educational information about MSB registration routes. Requirements differ materially by jurisdiction. Engage a licensed compliance adviser before commencing operations.