> ## Content Index
> Fetch the complete content index at: https://blog.amlbot.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Global Crypto Travel Rule 2026: Which Jurisdictions Have Implemented It?
- URL: https://blog.amlbot.com/global-crypto-travel-rule-implementation/
- Published: 2026-09-17T12:41:06.000Z
- Updated: 2026-09-17T12:41:06.000Z
- Author: AMLBot Team
- Tags: AMLBot Academy

Ninety-one out of 109\. That is how many surveyed jurisdictions had passed legislation implementing the Crypto Travel Rule when FATF [published](https://www.fatf-gafi.org/en/publications/Fatfrecommendations/targeted-updated-virtualassets-vasps-2026.html?ref=blog.amlbot.com) its Seventh Targeted Update on 16 July 2026 — 83%, up from 73% a year earlier, with another 11 jurisdictions reporting that implementation is under way. Read on its own, that number looks like the finish line.

Then there is the second number in the same report. Of those 91 jurisdictions with Travel Rule legislation on the books, around 60% had not yet issued findings or directives, or taken any supervisory or enforcement action against VASPs on Travel Rule compliance.

> (Source: FATF, "Seventh Targeted Update on Implementation of the FATF Standards on Virtual Assets and VASPs," 16 July 2026 — [https://www.fatf-gafi.org/en/publications/Fatfrecommendations/targeted-updated-virtualassets-vasps-2026.html](https://www.fatf-gafi.org/en/publications/Fatfrecommendations/targeted-updated-virtualassets-vasps-2026.html?ref=blog.amlbot.com))

Those two figures together describe the actual state of play for any crypto business moving value across borders. Legislation has spread quickly. Operational reality has not caught up evenly, and more importantly for compliance teams, the laws that have passed are not the same law. FATF sets a standard. Ninety-one legislatures wrote their own versions of it.

If you need the underlying mechanics first — originator and beneficiary data, why the obligation exists, what Recommendation 16 asks of virtual asset transfers — that ground is covered in detail in [what the FATF Crypto Travel Rule requires](https://blog.amlbot.com/fatf-crypto-travel-rule-what-is-it/). This article assumes that baseline and asks the next question instead: which domestic rule actually applies, jurisdiction by jurisdiction, and where do those rules diverge enough to break a single global workflow.

The short version of the argument: the Travel Rule is global as a standard but local as a legal obligation**.** A business cannot build cross-border compliance from Recommendation 16\. It has to know which domestic rule attaches to each side of each transfer.

## A Global Standard Does Not Mean a Single Global Travel Rule

FATF establishes a set of common principles that most implementations share. Identify the originator. Identify the beneficiary. Collect the required information. Transmit the relevant information between obliged institutions. Retain it. Detect transfers arriving with incomplete data. Apply risk-based controls to what you find.

What FATF does not do is create domestic law. It is a standard-setting body, and every one of those principles has to be enacted by a legislature or a regulator before it binds anyone. That enactment step is where the divergence enters, because each jurisdiction independently decides which entities are obliged, when the obligation attaches, what monetary figure changes the requirement, how unhosted wallets are treated, what happens when the counterparty sits in a jurisdiction that has not implemented the rule, and how any of it is supervised.

The single most common analytical error in this area involves thresholds, so it is worth slowing down on it.

A Travel Rule threshold does not automatically mean "below this amount, the Travel Rule disappears." Depending on the regime, a threshold figure can determine whether additional information is required on top of a reduced core dataset, whether identity has to be verified rather than merely collected, whether enhanced checks apply to a self-hosted wallet transfer, or whether a particular recordkeeping obligation is triggered at all. Four different regulatory functions, all expressed as a currency figure in a table.

Two examples make the contrast concrete. The EU generally requires originator and beneficiary information to accompany CASP-mediated crypto transfers with no general minimum-transfer exemption, and its €1,000 figure does something quite specific and narrow — it governs when additional ownership and control assessment applies to certain transfers involving a customer's self-hosted address. The United States, by contrast, applies its longstanding Funds Travel Rule to covered transmittals of $3,000 or more, a genuine value trigger inherited from a pre-crypto wire transfer framework.

Those two numbers, €1,000 and $3,000, are not comparable quantities. They answer different questions. Which leads to the practical rule for reading everything that follows: do not compare jurisdictions by copying one threshold number into a spreadsheet column without recording what that number actually triggers.

## Crypto Travel Rule Implementation Map for Major Jurisdictions in 2026

The table below covers nine regimes that between them account for most regulated cross-border crypto flow. Each row states the status, the framework and supervisor, what the headline threshold actually does, how self-hosted wallets are handled, and the one feature that most distinguishes that regime from its peers.

**European Union**

- Status in 2026: In force.
- Framework and Regulator: Regulation (EU) 2023/1113, the Transfer of Funds Regulation, directly applicable across member states and supervised nationally.
- Threshold or Key Trigger: no general de minimis exemption for CASP-mediated crypto transfers; €1,000 is relevant to additional ownership and control assessment.
- Self-Hosted Wallets: the CASP must obtain the relevant information, and above €1,000 involving a customer's own self-hosted address it must take adequate measures to assess ownership or control.
- Key Difference: the broadest harmonised scope of the nine, applying uniformly across all member states.

**United Kingdom**

- Status in 2026: In force since 1 September 2023, with FCA guidance still current.
- Framework and Regulator: Money Laundering Regulations 2017, Part 7A, supervised by the FCA.
- Threshold or Key Trigger: the €1,000 figure was replaced by £800, effective 30 June 2026 under SI 2026/621.
- Self-Hosted Wallets: information-request requirements apply depending on the transfer amount and the risk presented.
- Key Difference: the FCA expects firms to adapt their handling to whether the counterparty's jurisdiction has implemented the rule.

**United States**

- Status in 2026: In force under the existing Bank Secrecy Act framework.
- Framework and Regulator: the FinCEN Funds Travel Rule and money transmitter rules.
- Threshold or Key Trigger: $3,000 for covered transmittals of funds.
- Self-Hosted Wallets: no separate EU-style self-hosted regime; obligations follow from MSB status and the applicable BSA requirements.
- Key Difference: a substantially higher value trigger than the FATF baseline.

**Canada**

- Status in 2026: In force since 1 June 2021.
- Framework and Regulator: the PCMLTFA and its regulations, supervised by FINTRAC.
- Threshold or Key Trigger: virtual currency transfer record obligations attach at CAD 1,000 or more.
- Self-Hosted Wallets: not addressed through a distinct ownership-verification rule; handled inside the broader recordkeeping model.
- Key Difference: tightly integrated with FINTRAC's recordkeeping and reporting architecture rather than standing as a separate transfer rule.

**Australia**

- Status in 2026: expanded VASP framework in force, with obligations for newly regulated virtual asset services applying from 1 July 2026 under the transitional rules.
- Framework and regulator: the AML/CTF Act and AML/CTF Rules 2025, supervised by AUSTRAC.
- Threshold or key trigger: no small-transfer carve-out; obligations follow the VASP's role in the transfer.
- Self-hosted wallets: no transmission to another institution, because none exists, but payer information collection, the payee's full name and wallet-type due diligence still apply, and incoming transfers from self-hosted wallets carry their own information requirements.
- Key difference: explicit domestic and international scope, combined with detailed wallet-type due diligence.

**Singapore**

- Status in 2026: In force.
- Framework and Regulator: MAS Notice PSN02 under the Payment Services framework, applying to DPT service providers, supervised by MAS.
- Threshold or Key Trigger: applies to all transfer sizes, with S$1,500 separating a reduced core dataset from expanded originator information and verification.
- Self-Hosted Wallets: the Notice is built around institution-to-institution value transfers, with wallet risk handled through wider AML/CFT controls.
- Key Difference: a clear two-tier structure of reduced data below the line and expanded data above it.

**Hong Kong**

- Status in 2026: In force, with immediate secure transmission of required information mandatory from 1 January 2024.
- Framework and Regulator: the AMLO and the SFC AML/CFT Guideline for licensed VASPs, supervised by the SFC.
- Threshold or Key Trigger: HK$8,000 determines the fuller originator and recipient dataset; smaller transfers carry a narrower set.
- Self-Hosted Wallets: the SFC expects platforms to ascertain ownership or control of the unhosted wallet, and treats customer self-declaration alone as insufficient.
- Key Difference: explicit ownership and control expectations attached to unhosted wallets.

**Switzerland**

- Status in 2026: In force through Swiss payment-transfer requirements applied to blockchain transactions.
- Framework and Regulator: the AMLA and AMLO-FINMA, with FINMA Guidance 02/2019, supervised by FINMA or a recognised self-regulatory organisation.
- Threshold or Key Trigger: the CHF 1,000 figure in Art. 51a AMLO-FINMA is a crypto identification threshold, not a simple Travel Rule cut-off.
- Self-Hosted Wallets: supervised institutions must prove the customer controls the external wallet using suitable technical means.
- Key Difference: wallet-control verification built directly into the transfer requirement.

**United Arab Emirates**

- Status in 2026: In force.
- Framework and Regulator: the federal AML/CFT framework and virtual asset Travel Rule, supervised by the relevant authorities including VARA within Dubai.
- Threshold or Key Trigger: AED 3,500 triggers specified information and verification requirements, while collection duties can apply below it.
- Self-Hosted Wallets: enhanced due diligence for transfers to and from unhosted wallets, alongside explicit sunrise-issue policy expectations.
- Key Difference: particularly explicit counterparty-VASP and unhosted-wallet requirements.

Several of these entries repay a closer look, because the summary form compresses distinctions that matter operationally.

The **EU** runs the broadest harmonised regime of the nine. Because the TFR is a regulation rather than a directive, it applies directly across member states without national transposition, which removes one layer of fragmentation that plagues other EU AML rules. The detailed obligations that follow from that — required data fields, the treatment of intermediary CASPs, missing-information procedures — are set out fully in the [EU Crypto Travel Rule requirements for CASPs](https://blog.amlbot.com/eu-crypto-travel-rule-casp-requirements/).

The **UK** change is the most recent moving part in that list. The Money Laundering and Terrorist Financing (Amendment) Regulations 2026 were made on 9 June 2026 and came into force on 30 June 2026, converting euro-denominated thresholds in the MLRs to sterling. The cryptoasset transfer figure moved from €1,000 to £800, which is a deliberate tightening rather than a currency conversion. It does not mean every transfer under £800 sits outside the framework; it changes the point at which particular Part 7A information and verification requirements bite.

The **US** entry is the one most often misread in global comparisons, because $3,000 looks like a permissive threshold next to the FATF baseline. It is a different kind of rule, applied to covered transmittals under a framework that predates crypto by decades, and it interacts with a broader set of BSA obligations that do not switch off below the threshold. The full picture of [US Crypto Travel Rule requirements under FinCEN](https://blog.amlbot.com/us-crypto-travel-rule-fincen-requirements/) is worth reading before treating that figure as a global outlier in either direction.

**Canada** structures the obligation around records rather than around a standalone transfer rule. Financial entities, MSBs and foreign MSBs must include the originator's and beneficiary's name, address and account or reference number when sending virtual currency transfers, and take reasonable measures to obtain that information on transfers they receive. Where information is missing, the entity must take reasonable measures to obtain it and then apply documented risk-based policies on whether to allow, suspend or reject the transfer. That recordkeeping-first design shapes how the requirement sits inside [Canada's wider AML requirements for crypto MSBs](https://blog.amlbot.com/crypto-regulations-in-canada/).

> (Source: FINTRAC, "Travel rule for electronic funds and virtual currency transfers" — [https://fintrac-canafe.canada.ca/guidance-directives/transaction-operation/travel-acheminement/1-eng](https://fintrac-canafe.canada.ca/guidance-directives/transaction-operation/travel-acheminement/1-eng?ref=blog.amlbot.com))

**Australia** is the newest entrant and the most explicit about domestic scope. Under the reformed framework, non-incidental virtual asset transfers can attract Travel Rule obligations based on the VASP's role rather than on whether the transfer crosses a border, and the obligations for newly regulated virtual asset services applied from 1 July 2026 under the transitional rules. The wallet-type determination requirement — deciding, before providing the service, what kind of wallet is receiving the value — is unusually prescriptive. The detail sits in [Australia's 2026 Crypto Travel Rule requirements](https://blog.amlbot.com/australia-crypto-aml-regulations/).

**Singapore and Hong Kong** both use a two-tier data model, but they draw the line differently and for different reasons. Under PSN02, which applies to digital payment token (DPT) service providers, transfers up to S$1,500 carry names and account or reference numbers for both sides, while transfers above that require additional originator detail such as address, identification number or date and place of birth, with verification before transmission. Hong Kong frames the same obligation through the ordering institution's duties: its AML Guideline requires the fuller originator and recipient dataset before a virtual asset transfer of not less than HK$8,000 is carried out, with a narrower set below that figure. Neither creates an exemption zone.

**Switzerland** deserves care because two Swiss numbers get conflated constantly. The CHF 1,000 figure in Article 51a AMLO-FINMA is a crypto identification threshold, not a Travel Rule transmission cut-off. The distinctive Swiss requirement comes from FINMA Guidance 02/2019, which applies Swiss payment-transfer information rules to blockchain transactions and expects supervised institutions to prove a customer's control over an external wallet using suitable technical means before transacting with it.

> (Source: FINMA, money laundering supervision materials referencing Guidance 02/2019 on payments on the blockchain — [https://www.finma.ch/en/documentation/dossier/dossier-geldwaeschereibekaempfung/geldwaeschereiaufsicht-2022/](https://www.finma.ch/en/documentation/dossier/dossier-geldwaeschereibekaempfung/geldwaeschereiaufsicht-2022/?ref=blog.amlbot.com))

The **UAE** operates a federal virtual asset Travel Rule with supervision distributed across authorities, including VARA within Dubai. VARA's rulebook sets an AED 3,500 trigger for specified information and verification requirements while firms remain subject to the wider federal AML/CFT regime, and it is notably explicit about two things other rulebooks leave implicit: counterparty-VASP due diligence before executing a transfer, and a documented plan for handling counterparties in jurisdictions without equivalent requirements. The supervisory expectations that surround this are covered in [VARA AML requirements for crypto businesses in Dubai](https://blog.amlbot.com/vara-licensing-dubai-aml-requirements/).

All nine regimes have implemented Travel Rule-style requirements. None of them has implemented the same operational rule.

## The Biggest Differences Are Thresholds, Scope, and Self-Hosted Wallets

Three differences do most of the damage to a single global workflow. They are worth isolating from the jurisdiction summaries above, because each one requires a different design decision rather than a different configuration value.

1. **First, thresholds mean structurally different things.** Line them up and the point makes itself. The US $3,000 figure is a covered-transmittal trigger. Singapore's S$1,500 separates reduced information from expanded information, with the rule applying either way. Hong Kong's HK$8,000 determines which dataset accompanies the transfer. The EU has no general crypto de minimis at all, and its €1,000 governs self-hosted ownership assessment. The UK's £800, effective from June 2026, sets where particular Part 7A requirements attach. VARA's AED 3,500 triggers specified information and verification duties inside a broader federal framework that imposes collection obligations below it. Six figures, six different regulatory functions. A comparison that lists currency and number without recording what the trigger does is not merely incomplete — it is actively misleading, because it invites a business to configure a global minimum and assume everything below it is out of scope.
2. **Second, domestic scope differs.** Australia states plainly that non-incidental VASP virtual asset transfers can be subject to the requirement whether domestic or international. Other regimes reach the same territory through different legal concepts — payment-services law in Singapore, funds-transfer law in the US, an AML ordinance in Hong Kong, a directly applicable regulation in the EU. The consequence is that "is this a cross-border transfer?" is the wrong first question in several of these jurisdictions. The right first question is what role the regulated institution plays in the transfer.
3. **Third, self-hosted wallet rules diverge more sharply than anything else in this comparison.** Compressed to a single view:
- **EU** — additional ownership and control measures for transfers above €1,000 involving a customer's self-hosted address;
- **Australia** — no institution-to-institution transmission where there is no beneficiary institution, but payer information, payee name and wallet-type due diligence still apply, and incoming self-hosted transfers carry their own information requirements;
- **Hong Kong** — explicit ownership or control assessment, with customer self-declaration alone treated as inadequate;
- **Switzerland** — verification that the client controls the external wallet by suitable technical means, the most prescriptive of the six on this specific point;
- **UAE** — enhanced due diligence on transfers to and from unhosted wallets;
- **US and Canada** — treatment follows the broader AML and recordkeeping model rather than an EU-style ownership rule.

The unifying principle across all six approaches is easy to state and easy to get wrong in system design: **the absence of another VASP does not mean the absence of AML obligations.** What disappears when a transfer goes to a self-hosted wallet is the counterparty to send data to. Nothing else disappears — not collection, not verification where required, not risk assessment, not recordkeeping.

It is also worth separating two questions that get merged in product discussions, since proving that a customer controls a wallet and satisfying a Travel Rule obligation are related but not identical problems, as [why self-hosted wallet ownership and Travel Rule compliance are different questions](https://blog.amlbot.com/self-hosted-wallet-ownership-verification/) works through in detail. Note also what none of these regimes do: none prohibits self-hosted wallets, none uses an identical definition of "unhosted," and no single technical verification method satisfies all of them.

## Cross-Border Transfers Must Be Mapped From Both Sides

Turn the map into a transaction and the practical problem appears immediately. An EU CASP sends crypto to a US MSB. "Does the Travel Rule apply?" is not a question that can be answered, because there are two rules in play and they do not match. The sending side operates under a regime with no general de minimis; the receiving side operates under a $3,000 covered-transmittal framework and a different required dataset. A transfer of $500 sits inside the sender's obligation and outside the receiver's threshold. Neither institution is wrong. They are complying with different laws.

Answering it properly means holding eight variables at once: originator jurisdiction, beneficiary jurisdiction, the sender's legal obligations, the receiver's obligations, the threshold difference and what each threshold triggers, the required dataset on each side, whether the counterparty can technically receive the data, the missing-information policy, and the custodial or self-hosted status of the wallets involved.

The second scenario is the harder one. A UK cryptoasset business sends to a VASP in a jurisdiction with no operational Travel Rule infrastructure — one of the 11 still implementing, or one of the 91 with legislation but no supervisory activity behind it. The FCA's expectation here is instructive precisely because it does not let the firm off: determine the counterparty jurisdiction's implementation status, take reasonable steps to establish whether the counterparty can receive the data, collect and verify the required information regardless, store it even when it cannot be transmitted, and make risk-based decisions about incoming transfers where information is absent.

That is the sunrise issue in its 2026 form. It has not been solved by 83% adoption; it has migrated from "most countries have no rule" to "many countries have a rule with no operational capacity behind it," which is a subtler problem and in some ways a harder one to detect from the outside. The operational mechanics of why this keeps breaking are examined in [why Travel Rule implementation becomes difficult across jurisdictions](https://blog.amlbot.com/crypto-travel-rule-implementation-key-challenges-for-crypto-businesses/).

Because the counterparty's regulatory status is a live input into several of these regimes — the UAE requires confirming that the beneficiary VASP is appropriately regulated before executing a transfer, and Hong Kong and Australia both build counterparty assessment into their frameworks — this is not something to determine at the moment a transfer is instructed. It belongs in an onboarding process, which is the argument for a documented method covering [how to review a counterparty VASP before exchanging transfer data](https://blog.amlbot.com/counterparty-vasp-due-diligence-guide/). One caution attaches to that: confirming a counterparty complies with its Travel Rule tells you it is regulated and capable of data exchange. It does not tell you the counterparty is low AML risk.

Practically, cross-border compliance needs a maintained jurisdiction matrix rather than institutional memory. At minimum it should carry, for each relevant jurisdiction: the regulator, the covered entity type, transfer scope, the threshold and what it triggers, required data fields, verification rules, self-hosted wallet treatment, counterparty requirements, the missing-data response, the effective date, and the source and version date of the entry. That last field is the one teams skip and the one that decays fastest — the UK entry in this article would have been wrong three months before publication.

One approach deserves explicit rejection. "Apply the strictest rule globally" sounds prudent and is often the wrong answer. Collecting Swiss-level wallet-control proofs on every transfer worldwide creates data you have no legal basis to hold in some jurisdictions, adds privacy exposure, and introduces product friction that pushes customers toward less regulated venues. The better principle is to map the obligations that actually attach to each transfer path, then define a defensible cross-border operating standard on top of that map — one you can explain to a supervisor in terms of the rules that apply, not in terms of maximalism.

## 83% Adoption Does Not Mean the Travel Rule Is Finished

Come back to where this started. Ninety-one of 109 jurisdictions have Travel Rule legislation, up ten percentage points in a year. Add the 11 with implementation in progress and 93% of surveyed jurisdictions have the rule in force or on the way. That progress is real and it changes the baseline assumption a crypto business should hold about any given market.

But implementation has moved into a different phase, and the question a compliance team asks about a jurisdiction has to move with it. "Has this country passed a Travel Rule?" was the right question in 2021\. In 2026 it is only the first field. What follows it is what determines whether a transfer can actually be processed:

- *Is the legislation in force, or passed with a future commencement date?*
- *Which entities does it cover, and does that include the counterparty's business model?*
- *What does the threshold actually trigger — transmission, additional data, verification, or a recordkeeping duty?*
- *How are self-hosted wallets treated on each side?*
- *What is required when information is missing or unreliable?*
- *Is the rule actively supervised, or is it one of the roughly 60% with no enforcement history?*
- *Can the counterparty operationally exchange the required data at all?*

FATF's own 2026 findings make the same distinction from the supervisory side, flagging the gap between legislation and effective implementation as the central weakness in the current picture rather than a residual detail. The global Travel Rule is converging at the level of principle and remains fragmented at the level where crypto businesses actually have to process transactions. Both halves of that sentence are true simultaneously, and a compliance programme that only believes the first half will be surprised regularly. For cross-border VASPs, knowing that a jurisdiction has "implemented the Travel Rule" is only the first field in the compliance matrix, not the final answer.

## FAQ

#### Which Countries Have Implemented the Crypto Travel Rule in 2026?

Most major crypto markets have implemented Travel Rule requirements, including the European Union, United Kingdom, United States, Canada, Singapore, Hong Kong, Switzerland, Australia, and the UAE. FATF reported in July 2026 that 83% of surveyed jurisdictions — 91 of 109 — had passed Travel Rule legislation, with a further 11 reporting implementation in progress.

#### Is the Crypto Travel Rule the Same in Every Country?

No. FATF provides the global standard, but jurisdictions implement it through domestic law. Differences can include regulated entity types, transfer scope, thresholds, required information, identity-verification rules, self-hosted-wallet treatment, and handling of incomplete transfers. Two regimes can both be fully FATF-aligned and still impose materially different obligations on the same transfer.

#### What Is the FATF Travel Rule Threshold?

FATF provides a USD/EUR 1,000 de minimis framework, but countries can and do implement different thresholds. The threshold should not automatically be read as meaning that all Travel Rule obligations disappear below that amount, since in several regimes the figure determines the size of the required dataset or whether verification applies rather than whether the rule applies at all.

#### Does the EU Crypto Travel Rule Have a Minimum Threshold?

The EU's Transfer of Funds Regulation generally requires originator and beneficiary information for CASP-mediated crypto transfers without a general minimum exemption. A €1,000 threshold is specifically relevant to additional ownership or control assessment for certain transfers involving self-hosted addresses, which is a narrower function than a general exemption.

#### What Is the US Crypto Travel Rule Threshold?

The United States applies its Funds Travel Rule to covered transmittals of funds of $3,000 or more. Crypto businesses treated as money transmitters under FinCEN's framework may therefore fall within these information-transmission requirements, while remaining subject to other Bank Secrecy Act obligations that do not depend on that figure.

#### What Is the UK Crypto Travel Rule Threshold in 2026?

The UK's 2026 amendments to the Money Laundering Regulations changed the relevant cryptoasset transfer threshold from €1,000 to £800, in force from 30 June 2026\. The sterling figure is set lower than a direct currency conversion would produce, and it affects particular information and verification requirements rather than placing every transfer below £800 outside the wider AML framework.

#### Does the Travel Rule Apply to Self-Hosted Crypto Wallets?

There is no single global answer. A self-hosted wallet has no VASP to receive Travel Rule data, but jurisdictions can impose additional information, ownership-control, due diligence or risk-assessment requirements on the regulated business interacting with that wallet. The transmission obligation may fall away while collection, verification and recordkeeping duties remain.

#### Which Jurisdictions Have Strict Self-Hosted Wallet Rules?

The EU, Switzerland, Hong Kong, Australia and the UAE all have notable requirements concerning transfers involving self-hosted or unhosted wallets, although the obligations differ significantly in structure and scope. Switzerland's expectation that institutions prove customer control of an external wallet by technical means is the most prescriptive on that particular point, though none of these jurisdictions prohibits self-hosted wallets.

#### What Happens if a VASP Sends Crypto to a Country Without the Travel Rule?

The originating VASP must follow its own domestic obligations regardless of what the receiving side can do. Depending on the jurisdiction, this may require collecting and storing the relevant information, taking reasonable steps to determine whether the counterparty can receive it, and applying a documented risk-based policy when the other side cannot comply.

#### Why Is Global Travel Rule Compliance Still Difficult if 83% of Jurisdictions Have Legislation?

Passing legislation does not create one interoperable global system. National regimes still differ in thresholds, definitions, required data, self-hosted-wallet treatment, technical implementation, counterparty obligations and enforcement maturity. FATF's 2026 findings also note that a majority of jurisdictions with Travel Rule legislation have not yet taken supervisory or enforcement action, which means legal adoption and operational capacity are not the same thing.