Skip to content
Free guide: How to use AI in compliance
← Back

FATF Travel Rule Compliance for Crypto in 2026: A Practical Guide for VASPs

Michelangelo Frigo Michelangelo Frigo (Co-Founder at Zyphe) Published June 2, 2026Updated October 18, 2026
World map with VASP transfer route between two compliance jurisdictions

What the FATF Travel Rule requires of VASPs in 2026: EU, UK and US thresholds, the data to transmit, the protocols that carry it, and the KYC layer under it.

Table of contents

Key highlights

  • The Travel Rule is now the floor, not the frontier: every VASP that sends or receives a transfer to or from another VASP sits inside scope. Thresholds differ by jurisdiction: none in the EU, £800 for the full data set on UK cross-border transfers, USD 3,000 in the US. Many VASPs entering 2026 are still not technically ready.
  • Originator VASPs must transmit the customer's verified name, account or wallet identifier and, depending on the jurisdiction, an address, ID document number, customer identification number or date and place of birth, together with the beneficiary's name and account or wallet identifier.
  • The rule does not stand alone. In the EU it lives in the Transfer of Funds Regulation, which the MiCA licence depends on; in the US it is FinCEN's recordkeeping rule alongside OFAC sanctions screening; in the UK it is Part 7A of the MLR 2017, supervised by the FCA.
  • Messages travel over open protocols (TRISA, and TRP from the OpenVASP Association) and commercial networks (VerifyVASP, Notabene, Sumsub and others). None of them reaches every counterparty, so serious VASPs support more than one, and none of them works without a KYC layer underneath that has already captured the data the protocol transmits.
  • The most common 2026 failure is buying a protocol before fixing the KYC layer feeding it. A message you cannot fill in because collection never captured the address is a violation, not a success.
  • Zyphe's KYC stack collects, verifies, and structures customer data in the shape Travel Rule protocols transmit. The output of verification becomes the input of the Travel Rule message with no manual transformation step.
  • Get the sequence right (KYC first, Travel Rule second, audit trail under every decision) and procurement teams ship in 4 to 8 weeks. Get it wrong and they spend 6 to 12 months in remediation.

The FATF Travel Rule requires originator and beneficiary VASPs to exchange specific verified customer information with the virtual asset transfers they make to each other. In 2026 the rule is enforced in the EU under the Transfer of Funds Regulation (for every transfer, regardless of amount), in the UK under Part 7A of the Money Laundering Regulations 2017, and in the US under FinCEN's recordkeeping and travel rule (from USD 3,000). The technical question is no longer whether to implement, but which protocol, on what KYC foundation, with what audit trail.

TL;DR

The FATF Travel Rule has applied to crypto since FATF extended Recommendation 16 to Virtual Asset Service Providers in 2019. What changed by 2026 is that the national rules are in force. In the EU the Transfer of Funds Regulation has applied since 30 December 2024, to every crypto-asset transfer between providers regardless of amount. In the UK, Part 7A of the Money Laundering Regulations 2017 has applied since 1 September 2023. In the US, FinCEN's recordkeeping and travel rule covers transmittals of USD 3,000 or more, and FinCEN's 2019 guidance confirmed that it covers convertible virtual currency. The technical question is no longer whether to implement; it is which protocol, on what KYC foundation, with what audit trail. This piece walks through the 2026 state of the rule, the protocols that carry it, and the foundational mistake of buying transmission before fixing collection.

Reading time: ~17 minutes

What exactly does the FATF Travel Rule require in 2026?

The Travel Rule, formally FATF Recommendation 16 as extended to virtual assets, requires the originator VASP and the beneficiary VASP in any transfer between them to exchange a defined set of customer information. FATF lets countries set a de minimis threshold of USD/EUR 1,000, below which a reduced data set applies (the names of both parties and their wallet addresses or a transaction reference). National rules then set their own thresholds: the EU has none for transfers between crypto-asset service providers, the UK requires the full data set from £800 on cross-border transfers, and the US applies its rule from USD 3,000.

The information set covers the originator first. Under the FATF baseline the required fields are: the originator's name; the originator's account or wallet identifier; and the originator's physical address, OR a national identity number, customer identification number, or date and place of birth. The EU sets a longer list: Article 14(1) of the Transfer of Funds Regulation asks for the originator's address including the country, the official personal document number and the customer identification number, or alternatively the originator's date and place of birth, plus the originator's LEI where it has provided one and the message format has the field. The UK accepts one of customer identification number, address, ID document number, or date and place of birth.

On the beneficiary side, the originator VASP must transmit the beneficiary's name and the beneficiary's account or wallet identifier. The beneficiary VASP must check that the required information arrived, and needs risk-based procedures to decide whether to execute, reject, return or suspend a transfer that arrives with missing or incomplete information.

Operators routinely under-appreciate three properties of the rule. First, thresholds are measured per transfer, but transfers that appear to be linked count together (the UK rule says so explicitly), and deliberately splitting a transfer to stay under a threshold is structuring: an offence in the US and a suspicious-activity red flag everywhere. Second, the information must travel with the transfer, not after the fact: the EU requires it in advance of, or simultaneously or concurrently with, the transfer. Reconciliation processes that batch Travel Rule messages overnight or weekly do not meet that standard. Third, the originator information must be verified at the source, not self-attested by the customer: the EU and UK rules both require the originator's provider to verify it against documents or information from a reliable, independent source before the transfer. A KYC layer that has not actually verified the originator's address cannot legitimately transmit it.

How does the Travel Rule interact with MiCA and the EU Transfer of Funds Regulation?

In the European Union, the Travel Rule is operationalised through the Transfer of Funds Regulation (Regulation (EU) 2023/1113), not directly through MiCA. The relationship between the two regulations is one of the most-misunderstood elements of the 2026 EU crypto compliance landscape.

For a deeper read on the licensing side, see VASP KYC compliance under MiCA.

The Transfer of Funds Regulation imposes the Travel Rule mechanics. It entered into force in June 2023 and has applied since 30 December 2024. It defines the originator and beneficiary information that crypto-asset service providers must transmit and receive, brings crypto transfers under the same framework as wire transfers in traditional finance, and applies to every crypto-asset transfer regardless of amount, with no de minimis threshold. The EUR 1,000 figure matters in one place: for a transfer of more than EUR 1,000 to or from a self-hosted address, the provider must assess whether that address is owned or controlled by its own customer.

MiCA (Regulation (EU) 2023/1114) imposes the licensing, prudential, conduct, and market-integrity framework on Crypto-Asset Service Providers (CASPs). MiCA does not itself contain Travel Rule clauses. Instead, it requires CASPs to have effective systems to detect and prevent money laundering and terrorist financing, and Article 64 obliges the national authority to withdraw the authorisation of a CASP that does not. A systemic Travel Rule failure therefore also puts the MiCA licence at risk.

We break down the wider obligations in our MiCA KYC requirements guide for 2026.

In practice, the EU compliance stack for a CASP processing crypto transfers in 2026 looks like: MiCA authorisation (the licence to operate), Transfer of Funds Regulation compliance (the Travel Rule mechanics), and Customer Due Diligence under the national laws that transpose the current AML directives, supervised by the national authority. Two dates change that stack: from 10 July 2027 the CDD rules move into the directly applicable AML Regulation (EU) 2024/1624, and from 2028, six months after it publishes the list of entities it selected in 2027, the new EU authority, AMLA, directly supervises about 40 high-risk cross-border firms, which may include CASPs. The Travel Rule sits at the technical heart of all of this; if the messaging layer is non-compliant, every other layer above it is exposed.

For US-facing VASPs, the parallel framework is FinCEN's Bank Secrecy Act recordkeeping and travel rule (31 CFR 1010.410), which applies to transmittals of USD 3,000 or more and, as FinCEN's 2019 guidance confirmed, to convertible virtual currency. A 2020 proposal to lower the threshold to USD 250 for cross-border transfers was never finalised, so USD 3,000 is still the figure in the rule. OFAC sanctions screening applies on top, on every counterparty and at any amount (a transfer that touches a sanctioned wallet exposes the originator VASP regardless of whether the beneficiary VASP catches it).

For UK cryptoasset businesses, Part 7A of the Money Laundering Regulations 2017, made by HM Treasury and supervised by the FCA, carries the obligation. The names of both parties and their account numbers travel with every transfer. Cross-border transfers of £800 or more also carry the originator's customer identification number, address, ID document number, or date and place of birth. When every business involved is in the UK, those extra identifiers can be supplied on request, within three working days.

Australia applies its own version through AUSTRAC, and the AML/CTF obligations for digital currency exchanges in Australia cover the enrolment, registration and transfer information duties a virtual asset service provider carries there.

Building the broader programme is covered in our AML strategy for crypto exchanges.

Which technical protocols actually carry Travel Rule messages?

Two open protocols and several commercial networks carry most Travel Rule messages in 2026. They are technically distinct but increasingly interoperable (TRISA and TRP, for example, are bridged), and most of them carry the data in IVMS101, the shared data model for Travel Rule fields. Serious VASPs are now expected to support more than one, because counterparty VASPs do not all use the same network.

TRISA (Travel Rule Information Sharing Architecture). An open-source protocol built around a directory of verified VASPs, cryptographically signed messages between VASPs, and a peer-to-peer model where each VASP runs its own node. TRISA emphasises that the messaging layer should not centralise customer data in any single operator's infrastructure. Adoption is strongest among VASPs prioritising open standards.

TRP (Travel Rule Protocol), from the OpenVASP Association. OpenVASP began as an open protocol developed initially by Bitcoin Suisse and several European VASPs. The OpenVASP Association later merged with the TRP working group, and TRP version 3, which combines the two protocols, is now the association's protocol. It is an open, permissionless standard: VASPs exchange Travel Rule data with each other directly, without joining a commercial network.

VerifyVASP. A commercial Travel Rule network operated as a managed service, launched in Singapore by Dunamu, the operator of the Korean exchange Upbit, with strong adoption among Asian VASPs. In Korea it is linked with CODE, the rival network backed by the exchanges Bithumb, Coinone and Korbit. Compared with the open protocols, VerifyVASP trades openness for a more managed onboarding experience.

Beyond these, other commercial networks (notably Notabene and Sumsub's Travel Rule offering) operate as intermediaries, and blockchain analytics firms such as Chainalysis plug into them for transaction risk scoring rather than running a messaging network of their own. Commercial networks can speed up adoption with smaller counterparties but introduce a vendor-network lock-in tradeoff that procurement teams should evaluate carefully.

The 2026 reality is that no single protocol or network covers all counterparties, so the right answer for a serious VASP is to support an open protocol (TRISA or TRP) as a primary, with VerifyVASP or another commercial network as a secondary for counterparty coverage. Before accepting a single-protocol implementation, check it against your own counterparty list.

Why does KYC have to be the foundation, not the afterthought?

The most expensive lesson VASPs have learned since the national Travel Rules took effect is that buying a Travel Rule protocol does nothing if the KYC layer feeding it has not already captured and verified the data the protocol transmits.

This is why we treat compliant onboarding for crypto exchanges as the foundation.

The Travel Rule message is structured. The fields are defined. The originator VASP must populate name, account or wallet identifier, address (or alternative identifier), and beneficiary information. If the originator VASP's KYC flow only captured a passport scan and a selfie, the address field is empty. If the KYC flow allowed a self-attested address without verification, the address field is unverified. Because the EU and UK rules require the originator data to be verified before the transfer, sending an unverified value is a breach in its own right: a missing field is a gap the beneficiary VASP will flag, while an unverified one passes on data nobody checked.

The architectural sequence that works is: verified KYC layer first, then Travel Rule transmission layer on top. The KYC layer captures the data once, structures it in the canonical shape the Travel Rule protocols expect, and exposes it to the transmission layer as structured customer-record output. The Travel Rule layer becomes a transmission and counterparty-verification problem rather than a data-collection problem.

Manuel Tumiati, Zyphe's CTO and co-founder, has framed the architectural pattern in customer conversations: the platform underneath has to do the actual collection work, and the structured-record output is what makes downstream compliance routing possible. The same point applies to Travel Rule. The protocol on top is only as good as the verified collection underneath.

In practice, this means the procurement order should be: KYC platform first (with Travel-Rule-compatible data capture), then Travel Rule protocol. VASPs that bought a Travel Rule protocol before fixing their KYC layer are in 2026 doing manual data re-entry into Travel Rule messages, which is itself a control failure auditors flag.

How does Zyphe structure collected data for Travel Rule compatibility?

Zyphe's KYC platform is built around the assumption that the verified customer record will be consumed by downstream compliance systems, including Travel Rule protocols, sanctions screening engines, transaction monitoring tools, and regulator-export pipelines. Concretely, the collection layer produces:

A verified, structured originator record per customer, with name as verified against an NFC chip read from the passport or government ID where available, address verified against a primary document (utility bill, bank statement, government letter) or against electronic ID source data (eIDAS-recognised electronic IDs, SPID for Italy, BankID for Nordic countries), and account or wallet identifier captured at the VASP layer linked to the verified customer record.

The eIDAS angle is covered in our eIDAS 2.0 and the EU Digital Identity Wallet.

A regulator-defensible audit trail for every field in the record, including the verification method, the document reference, the timestamp, the verifying agent (human or automated), the confidence score, and the policy version at the time of verification. This audit trail is what allows a VASP to demonstrate to its supervisor (a national authority in the EU, the FCA in the UK, FinCEN in the US) that the data transmitted in a Travel Rule message was verified to the standard the regulator requires.

A decentralised storage architecture: after verification, the source documents and biometrics are encrypted and split across thousands of storage nodes into the user's own vault, using a 29-of-100 threshold scheme, and only a key the user holds can unlock them. The VASP receives verification results and proofs, not copies, and the Travel Rule message transmits the verified fields, not the source documents, so there is no central store of customer documents to leak.

The full mechanics live in our decentralised KYC primer.

A structured output API that the VASP's Travel Rule layer (TRISA node, TRP endpoint, VerifyVASP integration) can consume directly, so the transmitted message contains exactly the data the protocol specifies and exactly the data that was verified, with no manual transcription step.

You can wire this up via our KYC API integration guide.

What are the most common Travel Rule implementation mistakes?

Six failure modes show up repeatedly in Travel Rule implementations.

Buying the protocol before fixing the collection. Already covered above. A TRISA node connected to a KYC stack that did not capture address fields produces empty Travel Rule messages.

Treating the threshold as a customer-level threshold. Where a threshold exists, it is per transfer, with linked transfers counted together, and in the EU there is no threshold at all. Structuring transfers below a threshold to avoid the rule is a separate AML violation.

Assuming the beneficiary VASP will verify the counterparty. The originator VASP carries its own obligation to identify the counterparty and check whether it is a VASP it can safely send customer data to (not a self-hosted wallet or an unregulated exchange) before transmitting. FATF's 2021 guidance on virtual assets expects this counterparty due diligence from every VASP.

Skipping sanctions screening at the Travel Rule layer. The Travel Rule message gives the originator VASP first-look visibility on the beneficiary identity. Failing to screen that beneficiary against OFAC, EU consolidated, UK OFSI, and UN lists at the moment of transmission is a sanctions failure regardless of whether the wallet itself was flagged.

We cover the regulatory baseline in AML transaction monitoring in 2026.

Single-protocol-only implementation. No single protocol or network reaches every counterparty VASP in 2026. A single-protocol implementation leaves the VASP unable to transmit to a share of its legitimate counterparties.

No audit trail for Travel Rule decisions. Supervisors in all three markets (national authorities in the EU, the FCA in the UK, and FinCEN's "reasonably designed" AML programme standard in the US) expect a VASP to show why it transmitted, held, escalated or rejected a transfer, with the underlying reasoning and the policy version. The EU rule makes it explicit on the receiving side: the beneficiary's provider must have risk-based procedures for deciding whether to execute, reject, return or suspend a transfer with missing information. Travel Rule platforms that do not produce this audit trail leave the VASP exposed at the next supervisory examination.

What does a VASP Travel Rule readiness checklist look like?

Use this as the procurement and engineering checklist for a 2026 Travel Rule implementation.

Foundation layer (the KYC stack):

  1. Verified originator name from NFC chip read or eIDAS-recognised electronic ID
  2. Verified originator address from primary document or eIDAS source
  3. Account or wallet identifier captured at VASP layer, linked to verified customer record
  4. ID document number, customer identification number, and date and place of birth captured as each jurisdiction requires (the EU asks for more than the FATF baseline)
  5. Source documents stored with regulator-defensible audit trail and decentralised architecture
  6. Structured customer-record output API exposed to downstream systems

Travel Rule protocol layer:

  1. Primary protocol selected (TRISA or TRP recommended for open-standard alignment)
  2. Secondary protocol or commercial network for counterparty coverage above 95%
  3. Per-message audit trail capturing transmission, counterparty verification, sanctions screening outcome
  4. Threshold logic set per transfer (linked transfers aggregated) and per jurisdiction (none in the EU, £800 for UK cross-border transfers, USD 3,000 in the US), with anti-structuring detection
  5. Counterparty VASP verification: directory check, regulated-status confirmation, CDD-evidence exchange

Compliance overlay:

  1. Sanctions screening (OFAC, EU consolidated, UK OFSI, UN, government-direct) on every Travel Rule transmission
  2. Transaction monitoring layer integrated with Travel Rule messages for post-transfer surveillance
  3. Documented reasoning and policy version for every Travel Rule decision, to the standard your supervisor applies
  4. SAR/STR routing logic for Travel Rule transmissions that surface suspicious patterns
  5. Regular Travel Rule audit-readiness exports for supervisory examinations

Treat any unchecked item in the foundation layer as a blocker: the protocol layer cannot work around it. Gaps in the other two layers are what a supervisor is most likely to find at the next examination.

When is Travel Rule readiness work the wrong investment to make right now?

In the spirit of honest evaluation, three scenarios where a VASP should pause on Travel Rule investment until upstream gaps are closed.

The KYC layer is broken and the firm tries to fix Travel Rule first. Already covered above, worth restating as an explicit anti-pattern. The Travel Rule message transmits verified KYC fields. A firm with unverified address, missing UBO, or weak source-of-funds documentation cannot transmit compliant Travel Rule messages regardless of which protocol is in place. The correct sequence is KYC remediation first, Travel Rule second. Firms that try to reverse the order spend 6-12 months in remediation that the KYC-first sequence would have avoided.

The firm operates only below the local threshold, outside the EU. A VASP whose transfers all sit below the threshold where it operates (USD 3,000 in the US; in the UK, transfers below £800 still carry names and account numbers) carries a lighter Travel Rule load. This scenario does not exist in the EU, where every transfer between providers is in scope regardless of amount. The compliance posture should still document the threshold-monitoring control to demonstrate to supervisors that the firm tracks the threshold. Beyond that, full multi-protocol deployment is over-investment until the volume profile changes.

The firm has no named MLRO or compliance governance layer. Travel Rule protocols transmit data and produce alerts. Without a named accountable individual reviewing the decisions, the protocol surface produces an audit trail that the supervisor will examine and find the firm has no human governance underneath. The fix here is to appoint the named officer before completing the protocol deployment.

Outside these three scenarios, Travel Rule readiness is required infrastructure for any VASP operating in a regulated jurisdiction. The remaining question is which protocol mix and which KYC foundation.

What is the bottom line on Travel Rule readiness for VASPs?

The FATF Travel Rule is no longer the frontier; it is the floor. Every VASP that sends or receives transfers to or from other VASPs in a regulated market needs a Travel Rule-compatible KYC layer and a transmission protocol that covers their actual counterparty distribution. The implementation sequence that works is KYC first, Travel Rule second, audit trail underneath every decision. The implementation that fails is protocol-first, KYC-after, audit-trail-never. Procurement teams that get the sequence right ship in 4-8 weeks; teams that get it wrong spend 6-12 months in remediation.

Book a VASP compliance consultation, 30 minutes, no obligation, and our compliance team will walk through your Travel Rule readiness against the 16-point checklist above.

For the onboarding layer the Travel Rule depends on, see KYC for crypto: the verified counterparty record, the screening, and how the data is structured for Travel Rule messaging tools.

  1. KYC for crypto exchanges: building a compliant onboarding flow in 2026
  2. AML transaction monitoring in 2026: what the regulations actually require
  3. KYC API integration: add identity verification to your app in 15 minutes
  4. Decentralised KYC: what it is, how it works
  5. eIDAS 2.0: how the EU Digital Identity Wallet changes KYC
  6. Zyphe MCP vs Anthropic's KYC screener: why they are complementary

Cited sources

Michelangelo Frigo Michelangelo Frigo (Co-Founder at Zyphe) Michelangelo Frigo is a privacy and identity infrastructure expert and co-founder of Zyphe.

Frequently Asked Questions

The FATF Travel Rule, formally Recommendation 16 as extended to virtual assets in 2019, requires originator and beneficiary VASPs to exchange customer information with every virtual-asset transfer between them. FATF lets countries set a USD/EUR 1,000 threshold below which a reduced data set applies, and national rules differ: the EU applies the full rule to every crypto-asset transfer regardless of amount, the UK requires the full data set from £800 on cross-border transfers, and the US applies its rule from USD 3,000. It applies to your VASP in every jurisdiction that has implemented the standard, which in 2026 includes the EU, the UK and the US.

Under the FATF baseline, the originator's name, account or wallet identifier, and one of physical address, national identity number, customer identification number, or date and place of birth, plus the beneficiary's name and account or wallet identifier. The EU asks for more: Article 14 of the Transfer of Funds Regulation lists the originator's address including the country, the official personal document number and the customer identification number, or alternatively the date and place of birth. The originator data must be verified before the transfer.

In the EU, the Transfer of Funds Regulation (EU) 2023/1113 has applied since 30 December 2024 and covers every crypto-asset transfer between providers regardless of amount; EUR 1,000 matters only for transfers to self-hosted addresses. In the UK, Part 7A of the Money Laundering Regulations 2017, supervised by the FCA, has applied since 1 September 2023, with the full data set required on cross-border transfers from £800. In the US, FinCEN's recordkeeping and travel rule (31 CFR 1010.410) applies to transmittals of USD 3,000 or more, including convertible virtual currency.

In 2026, no single protocol or network reaches every counterparty. A serious implementation uses an open protocol (TRISA, or TRP from the OpenVASP Association) as the primary, with VerifyVASP or another commercial network as the secondary, aiming for counterparty coverage above 95%. The protocol choice should follow your counterparty distribution, not your vendor's preference.

No. The Travel Rule transmits verified customer data, and a transmission protocol cannot transmit data the KYC layer never collected. VASPs that bought protocols before fixing collection end up running manual re-entry workflows that create more compliance exposure, not less. Fix KYC first, then layer the Travel Rule transmission on top.

MiCA does not itself contain Travel Rule clauses. It requires CASPs to have effective systems to prevent money laundering and terrorist financing, and Article 64 obliges the national authority to withdraw the authorisation of a CASP that does not. In the EU the Travel Rule lives in the Transfer of Funds Regulation, so a systemic Travel Rule failure also puts the MiCA licence at risk.

Buying a Travel Rule protocol before the KYC layer has captured the data the protocol transmits. The result is empty or unverified field values in Travel Rule messages. The EU and UK rules both require the originator's CASP to verify the originator data against a reliable, independent source before the transfer, so an unverified value is a breach in its own right. Always sequence: verified KYC first, then Travel Rule transmission.

If the KYC layer is already capturing verified originator data in a structured format, layering a Travel Rule protocol on top takes 4-8 weeks. If the KYC layer is not Travel-Rule-ready, the realistic timeline including KYC layer remediation is 3-6 months. Most 2026 timelines fail because the KYC remediation gets underestimated.

Zyphe's KYC platform produces structured, verified customer records in the shape Travel Rule protocols and networks (TRISA, TRP, VerifyVASP) transmit. The output of verification becomes the input of the Travel Rule message through a structured API, with no manual transcription. We pair with several Travel Rule protocol providers and can recommend the right protocol mix for your counterparty profile.

AML compliance without the PII liability

Screening, monitoring and reporting built on a privacy-first identity layer.

See Zyphe AML