Crypto Travel Rule Compliance: FATF Recommendation 16 for VASPs

The phrase "Travel Rule" makes it sound like a single rule that either applies or doesn't. In practice it is FATF Recommendation 16, a standard written for fiat wire transfers and then extended to virtual assets, and the hard part is operational: the de minimis threshold differs from one jurisdiction to the next, and the "sunrise issue" routinely leaves the originator and beneficiary data with nowhere to land. This guide covers what the rule actually obliges a VASP to do, why the threshold is not a single number, and where cross-border transfers break down. AML obligations are strictly jurisdiction-specific, so treat everything here as a starting point for a compliance-counsel conversation, not a substitute for one.

What the Travel Rule comes down to

• The Travel Rule is FATF Recommendation 16 applied to virtual assets: a VASP must collect, verify and transmit originator and beneficiary information to the counterpart VASP.
• FATF recommends a de minimis threshold of USD/EUR 1,000, but jurisdictions diverge. The EU applies its requirements with no threshold; others set their own figures. There is no single global number.
• The sunrise issue is structural friction: a compliant VASP sending to a counterpart in a jurisdiction that has not yet implemented the rule cannot complete the data exchange.
• Treatment of self-hosted (unhosted) wallet transfers is complex and jurisdiction-specific; no universal rule is stated here.
• The rule is implemented through national legislation, so thresholds, scope, data fields and timelines vary, and global adoption is still uneven.
• This area is strictly jurisdiction-specific and evolving. Confirm current rules in every relevant jurisdiction with compliance counsel. This is not legal or compliance advice.

What the Travel Rule actually requires

FATF Recommendation 16, originally a wire-transfer rule for fiat, has been extended to virtual assets. A Virtual Asset Service Provider (VASP) must:

1. collect and verify the originator information;
2. collect the beneficiary information;
3. transmit that information to the counterpart VASP.

It is an AML/CFT obligation implemented through national legislation, so the precise requirements depend on the jurisdiction; confirm with compliance counsel and treat it as part of the practical AML/KYC baseline.

The threshold is not one number

There is no single global threshold. The applicable figure depends entirely on the jurisdictions involved and must be checked against current local law, not assumed from the FATF standard.

The sunrise issue

The sunrise issue comes from uneven global adoption. When a compliant VASP in a regulated jurisdiction sends to a counterpart VASP in a jurisdiction that has not yet legislated or implemented the rule, the receiving VASP may be unable to receive or return the required data. This is structural friction in cross-border virtual-asset transfers, and compliance design has to account for non-uniform counterpart readiness rather than assume it.

Self-hosted wallets: deliberately not a universal rule

Treatment of transfers involving self-hosted (unhosted) wallets is one of the most complex and jurisdiction-specific aspects, and approaches differ between jurisdictions and over time. This guide does not state a universal rule, because there isn't one; it is exactly the point to determine under the specific applicable law with compliance counsel.

Jurisdiction comparison: how the Travel Rule is implemented in key markets

The following illustrates how jurisdictional divergence plays out in practice. This is informational only — confirm current rules per jurisdiction with compliance counsel:

The EU zero-threshold is the most demanding and affects every CASP authorized under MiCA. For a CASP with EU authorization — including through the AMF in France — compliance with the TFR's zero-threshold Travel Rule is not optional.

Practical guidance

1. Identify every VASP-to-VASP leg and the jurisdictions on both sides.
2. Apply each jurisdiction's threshold; never assume the FATF USD/EUR 1,000 universally (the EU is zero).
3. Design for the sunrise issue, since counterpart readiness is not uniform.
4. Treat self-hosted-wallet transfers as a counsel question, with no universal rule.
5. Apply each relevant jurisdiction's rules for a cross-border VASP, not a single global assumption.
6. Confirm current rules per jurisdiction with compliance counsel. This is evolving and not legal or compliance advice.

Choosing a Travel Rule solution

A Travel Rule tool has to do two distinct jobs: identify the counterparty VASP and exchange the originator and beneficiary data with it in a format the receiving side can accept. Providers such as Chainalysis and Elliptic offer blockchain analytics and screening that feed those workflows, and several specialist messaging protocols handle the data exchange itself. Before relying on any of them, check that it:

• applies the correct threshold for each jurisdiction on a transfer, rather than a single global default (the EU zero threshold is the one most often missed);
• has a workable answer to the sunrise issue, so a transfer to a counterpart in a not-yet-implemented jurisdiction is handled by policy rather than silently dropped;
• reflects the current rules of each relevant jurisdiction, since thresholds and data requirements change.

Whatever the tool does, the legal obligation, the threshold determination and the jurisdictional analysis stay with the VASP and its compliance counsel.

Where Wag3s fits

Wag3s is not a Travel Rule or screening provider, and it does not perform the originator/beneficiary data exchange. What Wag3s HR and the wider finance OS do is keep the auditable financial record around transfers and counterparties, so the underlying data feeding a VASP's Travel Rule and AML/KYC workflow is reconciled and evidenced. The Travel Rule obligation itself stays with the VASP and its compliance counsel under the applicable jurisdictions; Wag3s supports that work rather than discharging it.

Further reading

• AML & KYC for Crypto Businesses
• FATF VASP Guidance
• OFAC Crypto Sanctions Compliance
• DAC8 Compliance Guide
• Crypto Company Jurisdiction Guide
• Crypto Security for Finance Teams

Sources

• FATF — Virtual assets: the standards applying Recommendation 16 (the Travel Rule) to virtual assets, requiring VASPs to obtain, hold and transmit originator and beneficiary information when transferring virtual assets.
• FATF — Targeted Update on Implementation of the FATF Standards on Virtual Assets and VASPs: jurisdictional adoption status and the persistence of the "sunrise issue" from uneven global implementation.
• FATF — FATF updates Standards on Recommendation 16 on Payment Transparency (June 2025): the June 2025 revisions to R.16 and how they interact with the VASP framework.
• The FATF standard sets a recommended de minimis threshold of USD/EUR 1,000, but the Travel Rule is implemented through each jurisdiction's own legislation, with thresholds, scope, data fields and timelines that differ (the EU applies its Transfer of Funds Regulation with no threshold). Self-hosted-wallet treatment is jurisdiction-specific. Confirm the current rules of each relevant jurisdiction with qualified compliance counsel; this is not legal or compliance advice.