Oliver / Questions

How should crypto firms handle unhosted wallets?

UKChecked answer · verified 30 October 2026 · next review 30 April 2027

Oliver, in short

Under regulation 64G of the Money Laundering Regulations, a UK crypto business may ask its own customer for originator or beneficiary details on a transfer to or from an unhosted wallet, based on risk. It must weigh purpose, value, frequency and relationship length. If requested information doesn't arrive, it must not make the crypto available.

An unhosted wallet (also called self-hosted or self-custody) is software or hardware where the user holds their own private key. No crypto business stands behind it, so there is no counterparty firm to exchange travel rule data with. The Money Laundering Regulations deal with this in regulation 64G, part of the travel rule rules in force since 1 September 2023.

What the law requires

  • The rule applies to transfers from an unhosted wallet to your customer, or from your customer to an unhosted wallet.
  • You may ask your own customer for the details you don't already hold: names and account number or transaction identifier. For incoming transfers of £800 or more (with linked transfers), you may also ask for the extra originator details, such as address or date of birth. The threshold was 1,000 euros until 30 June 2026.
  • Whether to ask is risk-based. Consider your firm-wide risk assessments and the risk of the transfer: its purpose and nature, value and linked transfers, how often the customer transfers, and how long you've known them.
  • If you ask and don't get it, you must not make the crypto available to the beneficiary.

What JMLSG guidance adds (Annex 22-I)

  • Ask for more information where your risk assessment shows higher risk.
  • In higher-risk cases, consider checking the source of funds in the wallet. Only consider allowing the transfer if the customer can show control of the wallet, for example with a micro-deposit or a cryptographic signature.
  • Work out whether a wallet is hosted or unhosted. Use blockchain analysis, your travel rule provider's lookup tools, your own address book, or ask the beneficiary. Document the steps.
  • Submit a suspicious activity report where appropriate.

Common mistakes

  • Treating every unhosted wallet as forbidden, or every one as fine. The law expects a documented, risk-based decision.
  • Assuming a wallet is unhosted without trying to identify the counterparty.
  • Not linking repeat small transfers when deciding whether the £800 threshold is reached.

Note: JMLSG's Sector 22 text, updated December 2025, still refers to a 1,000 euro threshold in places. The Regulations have used £800 since 30 June 2026.

This is general information, not legal advice.

Sources

  1. MLR 2017, regulation 64B (definition of unhosted wallet) (source updated 3 July 2026)
  2. MLR 2017, regulation 64G(1)–(4) (Part 7A, in force 1 September 2023; £800 from 30 June 2026) (source updated 3 July 2026)
  3. JMLSG Guidance Part II (June 2023, updated December 2025), Annex 22-I Cryptoassets transfers, paragraphs 34 and 36, Annex 22-I, paras 34, 36
  4. JMLSG Part II, Annex 22-I, paragraph 39 (wallet attribution), Annex 22-I, para 39

Researched from primary sources and checked by a separate fact-checker. General information, not legal advice.

Still have a question?

Ask Oliver in your own words, or send it to the AML Buddy team and we’ll use it to add a checked answer.

Ask Oliver Email the team
Ask Oliver a follow-upHe has read this page too