The Travel Rule for crypto: a practical compliance guide.
The FATF Travel Rule requires identifying information to travel alongside crypto transfers between service providers. The principle is simple; the thresholds and obligations vary by market, and that's what trips products up.
What the Travel Rule is
The "Travel Rule" applies FATF Recommendation 16 to virtual-asset transfers. In plain terms, when crypto moves between service providers, certain verified information about the sender and recipient must travel with the transaction — so that transfers carry the same transparency expected of traditional wires. It exists to help detect and prevent illicit finance across borders.
Thresholds differ by market
The FATF standard sets a baseline around a USD/EUR 1,000 threshold for exchanging originator and beneficiary information, but jurisdictions diverge. The EU requires full originator and beneficiary information on every crypto transfer regardless of amount; the US applies its recordkeeping threshold; and other markets set their own limits. A product operating across regions can't assume one threshold — it has to apply the rule per jurisdiction.
What data has to travel
Typically the originating provider must transmit the originator's verified name, an account or wallet identifier, and either a physical address or an alternative identifier such as a national ID number, customer number, or date and place of birth. Beneficiary information generally includes the beneficiary's name and account or wallet identifier. The receiving provider must verify what it gets and apply risk-based controls when the information is incomplete or the counterparty can't be confirmed.
Who carries the obligation
The obligations fall on Virtual Asset Service Providers (VASPs) — exchanges, custodians, and similar regulated entities. As of 2026 the rule is enforced across more than 50 jurisdictions, including the EU's Transfer of Funds Regulation, the UK, Singapore, and the US. For a platform, the key point is that the regulated VASP in the flow carries the Travel Rule duty — but the platform has to be built so that the required data is collected, attached, and verifiable.
How Axora handles it
Axora is the orchestration layer, not a VASP. For crypto-enabled workflows, regulated activity is delivered through MiCA-authorised CASP infrastructure in the EEA and through regulated entities and partners in other markets where authorised — and those regulated entities carry the Travel Rule obligation. Axora's role is to make compliance operable: ensuring onboarding, identity data, screening, and Travel Rule support are part of the workflow where required, so the regulated route has what it needs and every transfer is evidenced.
Building crypto transfer workflows?
Tell us your markets and asset types. Axora can help you design crypto workflows that route through regulated providers with Travel Rule support where required.
Request Access