Crypto Travel Rule Compliance: FATF Recommendation 16 for VASPs

The "Travel Rule" sounds like one rule. It is FATF Recommendation 16 — a fiat wire-transfer standard extended to virtual assets — and its real-world difficulty is that the threshold differs by jurisdiction and the sunrise issue routinely breaks the data exchange. This guide is the mechanic, hedged, because AML obligations are strictly jurisdiction-specific and a compliance-counsel question.

TL;DR

• Travel Rule = FATF Recommendation 16 extended to virtual assets: a VASP must collect, verify and transmit originator + beneficiary info to the counterpart VASP.
• FATF threshold = USD/EUR 1,000 — but jurisdictions diverge: the EU applies it at no threshold (zero); others differ. No single global figure.
• Sunrise issue: a compliant VASP sending to a counterpart in a not-yet-implemented jurisdiction cannot complete the data exchange — structural friction.
• Self-hosted-wallet treatment is complex and jurisdiction-specific — no universal rule stated here.
• Implemented via national legislation — different thresholds/scope/data/timelines; adoption still uneven.
• Strictly jurisdiction-specific, evolving — confirm current rules per jurisdiction with compliance counsel. Not legal/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 (the practical AML/KYC baseline).

The threshold is not one number

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

The sunrise issue

The sunrise issue: uneven global adoption. When a compliant VASP in a regulated jurisdiction sends to a counterpart VASP in a jurisdiction that has not yet legislated/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 — compliance design must account for non-uniform counterpart readiness, not 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 — it is exactly the point to determine under the specific applicable law with compliance counsel.

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 (EU = zero).
3. Design for the sunrise issue — counterpart readiness is not uniform.
4. Treat self-hosted-wallet transfers as a counsel question — no universal rule.
5. Apply each relevant jurisdiction's rules for a cross-border VASP — no single global assumption.
6. Confirm current rules per jurisdiction with compliance counsel — evolving; not legal/compliance advice.

How vendor tools handle the Travel Rule

Chainalysis and Elliptic provide blockchain analytics and screening that support Travel Rule and counterparty-risk workflows. They support the process — the legal obligation, threshold determination and jurisdictional application remain the VASP's and its compliance counsel's, not the tool's. Confirm any tool reflects the current rules of each relevant jurisdiction.

How Wag3s helps

Wag3s is not a Travel Rule or screening provider. Wag3s HR and the finance OS keep the auditable financial record around transfers and counterparties, so the data feeding a VASP's Travel Rule and AML/KYC process is reconciled and evidenced — while the obligation itself stays with the VASP and compliance counsel under the applicable jurisdictions. See the HR product page.

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 Recommendation 16 (the Travel Rule), originally a fiat wire-transfer rule, extended to virtual assets — a VASP must collect/verify originator info, collect beneficiary info, and transmit it to the counterpart VASP; implemented via national legislation
• FATF-recommended de minimis threshold USD/EUR 1,000; jurisdictional divergence — the EU applies Travel Rule requirements to crypto-asset transfers with no threshold (zero); other jurisdictions differ (no single global figure)
• Sunrise issue — uneven global adoption: a compliant VASP sending to a counterpart in a not-yet-implemented jurisdiction cannot complete the originator/beneficiary data exchange (structural friction)
• Self-hosted-wallet treatment is complex and jurisdiction-specific (no universal rule); Travel Rule implemented per-jurisdiction with differing thresholds/scope/data/timelines, adoption still uneven — strictly jurisdiction-specific, evolving; not legal/compliance advice