Join our Newsletter — 33% off our NHI Course
Home› Guides› Crypto Travel Rule Compliance Guide: FATF, EU and…
Guide Fraud Prevention

Crypto Travel Rule Compliance Guide: FATF, EU and UK Obligations Explained

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 15 min read
On this page

Every crypto-asset transfer between regulated providers now has to carry verified information about who sent it and who receives it, and a provider that cannot send, receive, check and protect that data cannot lawfully move the asset. The "Travel Rule" began as FATF Recommendation 16 for wire transfers and was extended to virtual asset service providers (VASPs) when FATF updated Recommendation 15 and its Interpretive Note in 2019. In the EU it is binding law through Regulation (EU) 2023/1113, the recast Transfer of Funds Regulation (TFR), and in the UK through Part 7A of the Money Laundering Regulations 2017. This guide explains who is covered, the data and timing obligations, the current status, penalties, what it means for the machine identities and automated systems that move crypto-assets, and how to build a compliant and secure programme. It is written for compliance, security and engineering leads at exchanges, custodians, brokers and wallet providers. It goes deeper than the Web3 and Crypto Security Guide, which covers the wider security picture.

Status checked 27 October 2026: the EU TFR has applied since 30 December 2024. UK Part 7A has applied since 1 September 2023, and the UK cross-border threshold in regulation 64C(4) was substituted with effect from 30 June 2026. FATF published its seventh targeted update on virtual assets on 16 July 2026. Rules and supervisory expectations continue to change, so confirm the current texts before relying on any detail here.

Key takeaways

  • It is a data obligation with a security core. FATF says VASPs must obtain, hold and securely transmit originator and beneficiary information, and the EU TFR requires it to be submitted in a secure manner and in line with GDPR.
  • The EU has no minimum amount. Article 14 of Regulation (EU) 2023/1113 applies to crypto-asset transfers of any value, with extra ownership checks for self-hosted addresses above EUR 1,000.
  • The UK rule depends on the route. Where every business in the chain is in the UK, names and account numbers travel and more detail is supplied on request; on routes involving non-UK businesses, transfers of at least £800 must carry the fuller set.
  • Missing data must stop or hold the asset. Beneficiary and intermediary providers must detect missing information and either reject, return or request it, and report counterparties that repeatedly fail.
  • Automation carries the risk. Travel Rule messaging runs between systems, so the API keys, certificates and service accounts that sign and exchange these messages hold sensitive personal data and become regulated controls.

Scope: who and what is covered

FATF sets the global standard; countries legislate it. FATF's 2025 targeted update reported that 99 jurisdictions had passed, or were in the process of passing, Travel Rule legislation, and that jurisdictions with materially important VASP activity account for about 98 per cent of the global virtual asset market. The two texts most practitioners in Europe work with are below.

ElementEU: Regulation (EU) 2023/1113UK: MLR 2017 Part 7A
WhoCrypto-asset service providers (CASPs) of the originator and beneficiary, and intermediary CASPsCryptoasset businesses: cryptoasset exchange providers and custodian wallet providers, including intermediaries
Applies from30 December 2024 (Art. 40)1 September 2023
ThresholdNone for inter-CASP transfers; EUR 1,000 triggers ownership assessment for self-hosted addressesReduced data on all-UK chains; fuller data on non-UK routes at £800 or more, including linked transfers (reg 64C(4))
Self-hosted / unhosted walletsObtain and hold information; above EUR 1,000 assess ownership or control (Arts. 14(5), 16(2))Business may request information on a risk basis; must not make the asset available if requested information is not received (reg 64G)
Supervisor for failuresNational AML/CFT competent authorityFinancial Conduct Authority (repeated failures reported to the FCA)
ExclusionsSee Article 2 of the RegulationTransfers within reg 64A(2) and (3), including where both parties are cryptoasset businesses acting on their own behalf

The UK regulation defines an unhosted wallet as software or hardware that lets a person store and transfer cryptoassets where the private cryptographic key is administered by that person. The EU text uses "self-hosted address" for the same idea.

Key obligations

Originator provider

Data itemEU TFR Article 14UK reg 64C
Originator nameRequired (14(1)(a))Required (64C(5))
Originator address or accountDistributed ledger address and crypto-asset account number where used (14(1)(b)); account number if not on DLT (14(1)(c))Account number, or a unique transaction identifier if there is none
Further originator identifierAddress including country, official personal document number, customer identification number, or date and place of birth (14(1)(d))On non-UK routes at £800 or more, or on request in all-UK chains: identifiers listed in 64C(6)
Legal entity identifierCurrent LEI or equivalent, where the field exists and the originator provides it (14(1)(e))Registered or trading name for firms; customer identification number or address
BeneficiaryName, ledger address and account number, LEI where provided (14(2))Name and account number or unique transaction identifier
VerificationVerify originator information before the transfer; no transfer until full compliance (14(6) to 14(8))Verify from a reliable, independent source (64C(8)); no transfer before full compliance (64C(9))
  • Timing: the EU requires the information "in advance of, or simultaneously or concurrently with" the transfer, and it does not have to be attached to the on-chain transaction itself (Art. 14(4)). That is why the industry uses off-chain messaging between providers.
  • Secure transmission: Article 14(4) requires secure submission in line with Regulation (EU) 2016/679 (GDPR). The data is personal data about customers and counterparties, so confidentiality, integrity and authenticated delivery are legal requirements, not just good practice.
  • On request in the UK: where all businesses are UK-based, the originator's business must provide the further details within three working days of a request (reg 64C(3)).
  • Batches: both texts make specific provision for batch transfers; the UK exemption in reg 64C(7) applies only where the beneficiary's business is wholly outside the UK and the batch carries the required information.

Beneficiary and intermediary providers

  • Detect: effective procedures, including monitoring where appropriate, to detect missing or incomplete information (EU Art. 16(1); UK reg 64D(1) requires checking the information was received and matches the business's own verified records).
  • Verify before release: verify beneficiary information before making the crypto-assets available (EU Art. 16(3)).
  • Act on gaps: reject or return the transfer, or request the information before making the assets available (EU Art. 17(1)); in the UK, request the information and consider delaying or returning if it is not resolved within a reasonable time (reg 64D(2)).
  • Escalate repeat offenders: for counterparties that repeatedly fail, issue warnings and deadlines, then reject future transfers or restrict or end the relationship, and report to the authority (EU Art. 17(2)); report repeated failures to the FCA (UK reg 64D(5)).
  • Treat gaps as a risk signal: missing or incomplete information is a factor when deciding whether a transfer is suspicious and should be reported to the financial intelligence unit (EU Art. 18).
  • Intermediaries: pass all received information on with the transfer and keep records (EU Arts. 19 to 21; UK regs 64E and 64F).
  • Records: keep the Article 14 to 16 information for five years, then delete personal data unless national law says otherwise (EU Art. 26). UK businesses must also respond "fully and without delay" to written law enforcement requests (reg 64H).

Timeline and current status

DateEvent
2019FATF updates Recommendation 15 and its Interpretive Note to cover virtual assets and VASPs
28 October 2021FATF updated guidance for a risk-based approach to VAs and VASPs, including Travel Rule implementation
1 September 2023UK MLR Part 7A (transfer of cryptoassets) applies
30 December 2024EU Regulation (EU) 2023/1113 applies, alongside MiCA
18 June 2025FATF announces revised Recommendation 16 (payment transparency), to be implemented by the end of 2030
26 June 2025FATF sixth targeted update: 99 jurisdictions have passed or are passing Travel Rule legislation
30 June 2026UK reg 64C(4) threshold wording substituted by S.I. 2026/621
16 July 2026FATF seventh targeted update on VAs and VASPs

FATF's 2026 update says jurisdictions have made progress, including implementing the Travel Rule, but gaps remain in turning risk assessments into mitigation, operationalising licensing and registration, identifying people conducting VASP activity, and risk-based supervision and enforcement. It names emerging risks including the industrialisation of virtual asset enabled fraud by organised crime groups, misuse of stablecoins, peer-to-peer transfers through unhosted wallets, offshore VASPs outside effective oversight, and decentralised finance. The revised Recommendation 16 is a payments standard; FATF's announcement notes that Recommendation 16 is also referred to as the Travel Rule for virtual assets, but it does not set out VASP-specific changes, so watch for follow-up guidance.

Enforcement and penalties

  • EU: Member States set penalties that are "effective, proportionate and dissuasive" (Art. 28), and legal persons can be held liable. Article 29 lists breaches that must attract at least the sanctions in Article 59(2) and (3) of Directive (EU) 2015/849, including repeated or systematic failures to include required information, record-keeping failures under Article 26 and serious failures by intermediaries. Article 30 requires sanctions to be published. Exact amounts are set in national law.
  • UK: Part 7A is part of the Money Laundering Regulations, so the FCA's supervisory and enforcement powers under those regulations apply. Counterparty failures are reported to the FCA under regs 64D(5) and 64E(5).
  • Commercial consequence: a provider repeatedly reported as non-compliant can find counterparties restricting or ending the relationship, which in practice cuts it off from regulated liquidity.

The threat behind the rule is real. FATF's 2025 update cited the theft of USD 1.46 billion from the exchange Bybit, which it attributed to the DPRK, with 3.8 per cent of the funds recovered. Laundering at that scale depends on moving assets through providers whose controls are weak, which is exactly the gap the Travel Rule targets.

What it means for AI agents and non-human identities

Travel Rule compliance is almost entirely machine to machine. A withdrawal triggers a service that builds the originator payload, discovers the counterparty provider, authenticates to it, sends the message, waits for a response and then releases the on-chain transaction. Each step is performed by a non-human identity.

Machine identityRiskControl
API keys or OAuth clients for a Travel Rule messaging providerTheft exposes customer personal data and lets an attacker send forged counterparty messagesStore in a secrets manager, scope per environment, rotate, alert on use from new networks. See the Secrets Management Guide
TLS client certificates and message signing keys used between providersSpoofed counterparty, tampered beneficiary dataMutual TLS, keys in an HSM or managed KMS, certificate inventory with expiry alerts
Service accounts that release withdrawals after a successful exchangeA compromised account bypasses the check and releases fundsSeparate the compliance decision from the signing service; signing requires a recorded compliance result. See the Crypto Exchange Identity and Key Security Guide
Screening and analytics integrationsOver-broad data sharing with third partiesData minimisation, contracts, access logs
AI agents that initiate transfers for customersThe agent supplies, or is tricked into supplying, wrong beneficiary data, or acts outside its mandateBind the agent to a customer account, limit destinations, keep the Travel Rule check outside the agent's control, and log the delegation. See the AI Agent Crypto Wallet Security Guide

The data model used by most Travel Rule messaging is the industry's IVMS101 standard, and many providers use third-party networks to exchange it. Whatever the protocol, the legal duty stays with the CASP: treat the messaging provider as a critical supplier and its credentials as privileged.

Compliance steps

  1. Map your flows. List every way crypto-assets leave or enter: customer withdrawals and deposits, internal treasury, OTC, staking and batch payouts. Mark which counterparties are regulated providers and which are self-hosted addresses.
  2. Confirm your legal regime per route. EU, UK and other jurisdictions differ on thresholds, data items and self-hosted rules. Record the rule applied to each route and the date you checked the text.
  3. Choose a messaging approach. Decide between a third-party network, an open protocol run in-house, or both, based on counterparty coverage. Most providers need more than one to reach all counterparties.
  4. Build counterparty due diligence. Before sending personal data, confirm the counterparty is a licensed or registered provider and can protect the data. Keep the evidence.
  5. Secure the pipeline. Encrypt in transit and at rest, authenticate counterparties, sign messages, restrict who can read payloads, and log every access. Run a data protection impact assessment, because the GDPR applies. See the GDPR Compliance Guide for Security Teams.
  6. Gate the release. Make the signing service refuse to broadcast a transfer that lacks a successful Travel Rule result, so a fault fails closed. Test this in a staging chain before production.
  7. Handle self-hosted addresses. For EU transfers above EUR 1,000, assess ownership or control with a method you can evidence, such as a signed message from the address or a small test transfer; apply your UK risk policy under reg 64G.
  8. Operate the exceptions queue. Define who reviews missing-data cases, the deadlines for requesting information, when to return assets, and how repeat offenders are warned, restricted and reported.
  9. Retain and delete. Keep records for five years in the EU and delete afterwards unless national law requires otherwise.
  10. Roll out safely. Start with monitoring only on incoming transfers to measure data quality, then enforce for outgoing, then incoming, keeping a documented manual fallback for counterparties that cannot yet message.

Detection and measurement

  • Percentage of outgoing transfers with a successful Travel Rule exchange before broadcast (target 100 per cent where required).
  • Percentage of incoming transfers with missing or mismatched information, by counterparty.
  • Median time to resolve a missing-information case.
  • Number of counterparties under warning, restricted or reported for repeated failure.
  • Credential health for messaging integrations: secrets past rotation date, certificates within 30 days of expiry.
  • Alerts for transfers released without a recorded compliance result (should be zero).

Framework mapping

Travel Rule activityNIST CSF 2.0NIST SP 800-53 Rev 5
Map transfer flows and legal requirementsGV.OCPM-11
Protect personal data in messagesPR.DSSC-8, SC-13
Manage messaging keys and certificatesPR.AASC-12, IA-5
Monitor missing data and released transfersDE.CMSI-4, AU-6
Retain records for five yearsPR.DSAU-11

Common failure patterns

  • Compliance check that fails open: the messaging call times out and the withdrawal is released anyway, so the control exists on paper only.
  • Personal data sent to anyone who asks: no counterparty due diligence, so customer names and identifiers go to unregulated or fake providers.
  • Messaging credentials treated as ordinary config: API keys in environment files or shared across staging and production, readable by every engineer.
  • One rule for every route: applying the EU no-threshold approach or the UK £800 threshold everywhere, rather than the rule that applies to each counterparty.
  • Exceptions queue with no owner: incoming transfers with missing data sit unresolved, assets are released by default, and repeat offenders are never reported.
  • Self-hosted ownership not evidenced: a checkbox in which the customer asserts ownership with nothing recorded to show how it was assessed.

Practitioner checklist

  • Document every transfer route and the Travel Rule regime that applies to it, with the date each text was checked.
  • Confirm data items per regime against Article 14 of Regulation (EU) 2023/1113 and reg 64C of the UK MLR.
  • Make broadcast of an outgoing transfer depend on a recorded Travel Rule result, and test that it fails closed.
  • Run counterparty due diligence before sending personal data, and keep the evidence.
  • Hold messaging API keys, certificates and signing keys in a secrets manager or HSM, with owners, rotation and expiry alerts.
  • Define the self-hosted address ownership method and record its outcome for every EU transfer above EUR 1,000.
  • Staff the missing-information queue, with deadlines, return rules and a repeat-offender reporting path.
  • Set five-year retention and deletion for Travel Rule records, and complete a data protection impact assessment.
  • Track the six metrics above monthly and report them to the MLRO and CISO.
  • Review FATF updates and national texts at least twice a year; the next changes may come from the revised Recommendation 16.

Standards and references

Related NHI Mgmt Group resources: Web3 and Crypto Security Guide · MiCA and DORA for Crypto-Asset Service Providers Guide · Crypto Exchange Identity and Key Security Guide · Identity Proofing and KYC Guide. This guide summarises the FATF Travel Rule and its EU and UK implementations as of 27 October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.