Travel Rule

The Travel Rule is the plainest idea in payments compliance: the identity of who is paying and who is being paid should travel with the money. It takes its name from the requirement that originator and beneficiary information accompany a transfer through every institution in the chain, rather than staying behind at the bank where the payment began.

The rule lives in Recommendation 16 of the FATF standards, the intergovernmental framework most countries have committed to write into national law. For bank wires it has been settled practice for decades; correspondent chains carry structured originator and beneficiary fields precisely because of it. The FATF updated the standard in June 2025 as part of its payment transparency work, tightening expectations about the quality and completeness of the data that travels.

The consequential extension came in 2019, when the FATF applied Recommendation 16 to virtual asset transfers. Above a recommended threshold of USD/EUR 1,000, the institution sending a stablecoin or other virtual asset transfer must collect and transmit the originator’s name, account or wallet identifier, and a further identifier such as an address or date of birth, along with the beneficiary’s name and wallet identifier. The receiving institution must collect that data and screen it. Each jurisdiction sets its own threshold and timing when implementing the standard, which is why the details differ between, say, the EU’s Transfer of Funds Regulation and the US approach.

That uneven adoption created the sunrise problem. An institution in a jurisdiction where the rule is live must exchange data with counterparties in jurisdictions where it is not, and where no local law compels, or in some cases even permits, the counterparty to reciprocate. In practice institutions resolve this with counterparty due diligence and contractual commitments, or by declining transfers where the required information cannot move.

The 2025 revision matters for the bank side too. The updated Recommendation 16 pushes toward structured, complete party data in payment messages, aligned with the richer formats of ISO 20022, so that screening systems stop guessing at names in free-text fields. The FATF’s stated aim is payment transparency: every institution in a chain should be able to see, and check, exactly who stands at each end of the transfer it is processing.

The operational weight of the rule sits in the transmission itself. Payment messages built for banks carry the data natively; virtual asset transfers need a parallel channel, since the ledger entry alone carries no identity. That is why Travel Rule compliance for stablecoin settlement is a data-exchange discipline between institutions, layered on top of the transfer, and why it belongs in any evaluation of a settlement rail. A fuller treatment, including what the rule means operationally for institutions using stablecoin rails, is in the Travel Rule guide.