SIXPENCE
Back to Blog
•
5 min read

What Is the Crypto Travel Rule?

The crypto Travel Rule requires regulated providers to share sender and recipient information with certain transfers. Here is how it works across FATF, the EU, and other regimes, and how Sixpence supports it.

Research

What Is the Crypto Travel Rule?

This is general educational information, not legal advice. Obligations depend on your jurisdiction, your licence, and your activity. Confirm your position with a qualified adviser. (Reviewed 2026-06-24.)

Direct answer

The crypto Travel Rule requires regulated crypto businesses to collect and pass on identifying information about the sender (originator) and recipient (beneficiary) when they handle certain transfers. It is the application to crypto of a long- standing anti-money-laundering rule for wire transfers. The exact thresholds and requirements vary by jurisdiction, so there is no single global version.

Why this matters

If you operate a crypto business that moves customer funds, the Travel Rule likely shapes what information you must capture and transmit with transfers, and to whom. Getting it wrong can mean non-compliance with anti-money-laundering obligations. For anyone else, it explains why exchanges increasingly ask for, and share, details about the other side of a transfer.

How it works

At its core, the Travel Rule says that when a regulated provider sends a qualifying transfer, it must include defined information about the originator and beneficiary, and the receiving provider must receive and retain it. The aim is to make transfers traceable so authorities and firms can better detect suspicious activity.

The rule exists at several levels, which are related but distinct:

  • FATF Recommendation 16 is the international standard, set by the Financial Action Task Force. It is guidance that countries implement, not binding law by itself, and it recommends a threshold of around USD or EUR 1,000 for sharing originator and beneficiary information.
  • The EU Transfer of Funds Regulation (Regulation (EU) 2023/1113) is the EU law that applies the Travel Rule to crypto-asset transfers. For crypto-asset service providers it has no de minimis threshold, so it applies regardless of value, and it became applicable on 30 December 2024.
  • Other jurisdictions implement their own versions with their own thresholds.

It is worth separating the Travel Rule from MiCA: MiCA is the EU framework for licensing crypto-asset service providers, while the Transfer of Funds Regulation is the rule about information accompanying transfers. They are different rules. See the related guide on CASPs under MiCA.

Practical example or analogy

The Travel Rule is like the sender and recipient details that must accompany a bank wire. The bank does not just move money; it attaches who is sending and who is receiving, so the transfer can be traced if needed. The crypto Travel Rule extends that same expectation to regulated crypto transfers.

Key steps or considerations

For a regulated provider:

  1. Determine which transfers are in scope under each jurisdiction you operate in.
  2. Capture the required originator and beneficiary information.
  3. Transmit and receive it securely with counterparties.
  4. Retain records to the required standard.
  5. Mind the differences. Thresholds differ; the EU has no de minimis for CASPs, while FATF recommends around 1,000. Do not apply one threshold everywhere.

How LedgerBrain supports Travel Rule compliance

The Travel Rule sits within a wider set of AML controls: monitoring, screening, investigation, and reporting. Sixpence supports that operational side through LedgerBrain.

  • Travel Rule support in reporting. LedgerBrain generates regulator-ready SAR and STR reports with FATF Travel Rule support. This helps a compliance team produce the reporting that sits alongside Travel Rule obligations.
  • Screening and monitoring around transfers. LedgerBrain screens addresses against OFAC, UN, and EU sanctions lists and runs real-time transaction monitoring, which is part of assessing the counterparties and transfers the rule concerns.

LedgerBrain supports these compliance workflows; it does not, by itself, determine your legal obligations or provide legal advice. Whether and how the Travel Rule applies to your business is a matter for your own compliance and legal assessment.

Limitations and compliance considerations

  • There is no single global Travel Rule. Thresholds and details differ by jurisdiction; FATF sets a standard, individual countries set the law.
  • The EU has no de minimis for CASPs. Do not assume a 1,000 threshold applies everywhere.
  • It is distinct from MiCA. Licensing and the Travel Rule are separate obligations.
  • This is general information, not legal advice.

Frequently asked questions

What information does the Travel Rule require? Defined details about the originator and beneficiary of a qualifying transfer, captured, transmitted, and retained by regulated providers.

Is there a single threshold? No. FATF recommends around USD or EUR 1,000, but the EU applies no de minimis for CASPs, and other countries differ.

Is the Travel Rule the same as MiCA? No. MiCA is the EU licensing framework for CASPs; the Travel Rule for crypto in the EU comes from the Transfer of Funds Regulation.

Does it apply to self-custody wallets? Treatment of transfers involving unhosted wallets varies by jurisdiction; check the specific rule that applies to you.

Conclusion

The crypto Travel Rule requires regulated providers to share originator and beneficiary information with certain transfers, applying a long-standing AML principle to crypto. It exists as a FATF standard, as binding EU law in the Transfer of Funds Regulation, and in other national forms, with thresholds that differ. Sixpence supports the surrounding compliance workflow through LedgerBrain, including SAR and STR reporting with Travel Rule support and sanctions screening. To see those capabilities, review the LedgerBrain details at ledgerbrain.io.

Sources

All PostsBack to Home