The Travel Rule, derived from FATF Recommendation 16, requires VASPs and other financial institutions to collect, transmit and make available originator and beneficiary information when conducting virtual asset transfers.

The Travel Rule - derived from FATF Recommendation 16 - requires VASPs and other financial institutions to collect, transmit, and make available originator and beneficiary information when conducting virtual asset transfers. The objective is to bring virtual asset transactions into line with the information-sharing requirements that have applied to traditional wire transfers for decades.
Implementation, however, has been uneven across jurisdictions, creating both compliance challenges and competitive implications for VASPs operating across borders.
In the Isle of Man, Travel Rule-related obligations are incorporated into the AML/CFT Code guidance. VASPs registered under the DBA are expected to collect and transmit the required originator and beneficiary information and to implement processes for verifying this information where appropriate. The precise technical implementation depends on the business model and the Travel Rule solution adopted.
In the EU, MiCA and the associated Transfer of Funds Regulation implement the Travel Rule for crypto-asset transfers, requiring CASPs to transmit specified information with every transfer, regardless of value. This is one of the more stringent implementations globally.
Other jurisdictions, including the UK, Singapore, Japan, Canada, and various FATF members, have implemented or are in the process of implementing Travel Rule requirements, each with variations in scope, thresholds, and technical expectations.
For VASPs, the practical challenges are significant. Travel Rule compliance requires technical infrastructure to transmit originator and beneficiary data with transactions. Several technology providers have developed Travel Rule protocols and messaging solutions, and VASPs need to assess and select appropriate solutions based on their transaction volumes, counterparty networks, and jurisdictional requirements.
Counterparty identification presents a particular challenge. When a VASP receives a transfer from an unhosted wallet or from a VASP in a jurisdiction that has not yet implemented the Travel Rule, the receiving VASP must still assess the transfer and determine appropriate due diligence measures. This requires clear internal policies and trained staff.
The compliance trajectory is clear: Travel Rule implementation will continue to expand globally, thresholds will likely decrease, and supervisory expectations will increase. VASPs that invest in Travel Rule compliance now are positioning themselves ahead of the curve, while those that defer will face increasing pressure from regulators, counterparties, and banking partners.
At Kybri, we advise VASPs on Travel Rule compliance, including policy development, technology vendor assessment, and implementation planning.
A thirty-minute call, no obligation. If the answer is that you do not need us yet, you will hear that too.