
The FATF published its seventh Targeted Update on virtual assets on 16 July 2026, recording the Travel Rule in force in 83 percent of surveyed jurisdictions, 91 of 109, against 73 percent a year earlier, with 11 more in progress for 93 percent in total. In the same document, 55 of those 91 jurisdictions had not yet issued findings or directives or taken any enforcement or supervisory action against VASPs on Travel Rule compliance. The law arrived. Enforcement did not, and that gap is the live operational problem.
For six years the industry had one answer to why Travel Rule compliance was hard, and FATF's own Best Practices names it: the sunrise problem, defined as the uneven adoption of the Travel Rule across jurisdictions arising from delays or inconsistent standards, and identified as the single largest obstacle.
That diagnosis implied a scaling path: more jurisdictions pass the law, the pool of counterparties able to exchange data grows, and compliance gets easier. The legislative variable has largely delivered, with 39 of the 63 non-prohibition jurisdictions reporting completion of every tracked implementation step.
Compliance did not get easier, and FATF frames the reason as a second phase of the same problem. The original issue was a counterparty in a jurisdiction with no rule; the new one is a counterparty with a rule and no oversight, which is worse from the sending firm's seat, because the first was legible and the second looks identical to compliance until tested.
Trace an outbound institutional transfer. The firm must determine whether the destination belongs to a VASP or an unhosted wallet, identify which VASP, establish a channel to it, transmit originator and beneficiary data, and form a view on whether that counterparty will handle the data adequately. All of it sits in front of a settlement that completes in minutes.
When the counterparty will not or cannot receive the data, the obligation does not lift. The sending firm's duty exists from the day its own jurisdiction's law takes effect, regardless of the receiving side, and the accepted answer is documented best efforts: attempt transmission, record the attempt and the counterparty's non-response, risk-assess, and decide whether to proceed.
That is the failure mode and it is a quiet one. The firm holds a file of its own attempts as the evidence of compliance, with no counter-record from anyone. Nothing breaks and no transfer fails until a supervisor reads the file and asks what the firm concluded from a counterparty that never answered. The blast radius is every transfer to that counterparty since onboarding, because the answer is the same for all of them.
Here is the trap in the scaling question. The variable everyone measured has saturated, and the outcome did not follow, which means legislative coverage was a proxy rather than the cause.
What binds instead is counterparty verifiability, and FATF's most fundamental finding in the same update is that jurisdictions continue to struggle to identify the natural and legal persons conducting VASP activities. If a supervisor cannot establish who operates a VASP in its own jurisdiction, a sending firm abroad cannot do better from outside, and no messaging protocol repairs that: the missing input is the entity's identity rather than a channel to it.
The second constraint is that compliance cost attaches to the counterparty relationship rather than the transaction. Each new counterparty is an onboarding event, so the cost curve follows the count of relationships and volume growth across existing ones amortizes nothing. Correspondent banking solved this with pre-established bilateral authorizations before any payment moved; this market has no equivalent, which is why throughput growth has never made the problem smaller.
Three indicators are computable from a firm's own records and worth reporting monthly. The share of outbound value sent to counterparties that returned no Travel Rule data. The share sent to destinations the firm could not classify as VASP or unhosted at all. And the age of the oldest unresolved best-efforts file, because that number is the length of the exposure a supervisor will eventually read.
Two defenses do not work. Treating a counterparty's jurisdiction as a proxy for its practice fails on FATF's own numbers, since roughly 60 percent of jurisdictions with the rule in force have never supervised it, so a counterparty's address tells you about its legislature rather than its controls. And treating prohibition jurisdictions as an empty set is an error worth naming: six jurisdictions fully prohibit VASP activity and eight prohibition jurisdictions already have the Travel Rule in force, so prohibition is a distinct counterparty class rather than an absence of counterparties.
Three work. Ask the counterparty directly whether it has ever been examined on Travel Rule compliance and record the answer, since jurisdiction data cannot answer it. Set a volume ceiling per unverified counterparty rather than a binary allow or block, converting an unbounded exposure into a sized one. And re-paper counterparties on a fixed cycle, because the enforcement picture is what moves.
The playbook is short. Classify every counterparty by what has been verified rather than by where it sits, cap exposure per class, keep the best-efforts file in a form that answers the supervisor's actual question (what the firm concluded and did, not merely that it tried), and escalate any counterparty whose non-response persists past the cycle, since a permanent non-responder is a decision made by default.
The residual risk cannot be drafted away. A sending firm is accountable for data handling it cannot observe at a counterparty it cannot audit, and under the unhosted-wallet case there is no counterparty to exchange data with at all, which FATF lists among emerging and increasing risks. Those exposures can be sized and documented; they cannot be removed while the firm transacts across borders.
What is improving is measurement, which sounds thin and is not. A published annual series separating law from supervision, counting jurisdictions at each stage and naming enforcement as the lagging variable gives a compliance function a defensible basis for treating two counterparties in differently supervised jurisdictions differently. The honest statement for 2026 is that the legislative phase is finished and the supervisory phase has barely started, so the firms that handle this well will be the ones that stopped tracking whether a counterparty's country has a rule and started tracking whether anyone has ever checked.
For informational purposes only. Not an offer to buy or sell any security. Available only to accredited investors who meet regulatory requirements.