What the travel rule is
The travel rule is the requirement that identifying information about the sender and the recipient accompanies a funds transfer from one financial institution to the next, all the way along the payment chain. The name comes from the idea that the information travels with the money.
The principle comes from the Financial Action Task Force, the international standard setter for anti-money laundering, and has been part of its recommendations on wire transfers for many years. FATF later extended the same principle to virtual asset transfers. Countries implement the standard in their own laws, and the details differ between jurisdictions.
In Canada, the travel rule is part of the framework under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act. It applies to electronic funds transfers and to virtual currency transfers carried out by reporting entities, including money services businesses. It is a standing requirement on every relevant transfer, separate from the reporting thresholds that apply to some of them.
Why it exists
Before the travel rule, a payment could pass through several banks with only an account number attached. Each institution in the chain knew its own client but not the person at the other end. That gap made it easier to move criminal proceeds or terrorist funds without anyone seeing the full picture.
The travel rule closes the gap in three ways:
- Screening. Every institution in the chain can screen the sender and recipient names against sanctions lists, not just its own client.
- Monitoring. Each institution can see patterns, such as many unrelated senders paying one beneficiary, that would be invisible with account numbers alone.
- Tracing. If law enforcement later needs to follow the money, the records at each step identify the parties.
For virtual currency the logic is the same. A blockchain shows that value moved from one address to another, but not who controls those addresses. Requiring regulated providers to exchange identifying information alongside the transfer brings virtual currency closer to the standard long applied to bank wires.
What travels with an electronic funds transfer
For an electronic funds transfer, the information that must be included and passed on covers both ends of the payment. In general terms:
- Originator: the name and address of the person or entity requesting the transfer, and their account number or, where there is no account, a reference number that allows the transfer to be traced.
- Beneficiary: the name and address of the person or entity receiving the funds, and their account number or a reference number.
When an MSB sends a wire, it includes this information in the payment message. When it receives or passes on a wire, it must take reasonable measures to make sure the information is there, and it must have risk-based procedures to decide what to do if it is missing or incomplete. That might mean asking the sending institution for the missing details, holding the payment, or in some cases returning it.
In Canada the requirement applies regardless of the amount of the transfer. A EUR 500 payment carries the same originator and beneficiary information as a EUR 500,000 one.
What travels with a virtual currency transfer
For virtual currency transfers, the equivalent information is required: the originator's name, address and account or reference number, and the beneficiary's name, address and account or reference number. The account number might be the wallet address or an internal account identifier.
The difficulty is that blockchains were not designed to carry this data. The information usually travels through a separate channel between the sending and receiving providers, using one of several messaging protocols that have developed for the purpose. Interoperability between protocols is improving but is not complete.
A further complication is the unhosted wallet: a wallet controlled directly by an individual or business, rather than held at a regulated provider. A transfer to an unhosted wallet has no receiving institution to pass information to. Providers deal with this through their own risk-based procedures, which commonly include collecting beneficiary information from the client, verifying that the client controls the wallet where the wallet is said to be the client's own, and screening the address on-chain. These steps sit alongside the travel rule rather than replacing it.
What clients need to provide
Most of the originator information comes from the client's onboarding file, so a business client rarely has to supply it again for each payment. The beneficiary information is a different matter, because the provider only knows what the client tells it.
For a bank wire, a complete beneficiary instruction normally includes:
- The beneficiary's full legal name, exactly as held by its bank.
- The beneficiary's full address, including country.
- The account number or IBAN.
- The beneficiary bank's name and BIC or other routing code.
- A payment reference or purpose, such as an invoice number.
For a virtual currency transfer, expect to provide the beneficiary's name and address, the wallet address and network, and whether the wallet is held at a provider or is unhosted. If the wallet is your own, expect to be asked to prove control of it.
Shortened names, missing addresses and vague references are the most common causes of delay. They are easy to fix before the payment is sent and much harder to fix once it is held at an intermediary bank.
A worked example
The following example is illustrative. A Vancouver-based holding company is a client of an MSB. It instructs a payment of EUR 80,000 to a component supplier in Germany.
The MSB already holds the holding company's legal name, registered address and client account number from onboarding, so the originator data is complete. The client's instruction supplies the supplier's legal name, its street address in Germany, its IBAN, its bank's BIC and a reference quoting the invoice number. The MSB screens both names, builds the payment message with all of these details and sends it to its correspondent bank.
At each step along the chain, the institution handling the payment can see who sent it and who is due to receive it, and can run its own checks. The German bank credits the supplier and keeps a record of the originator. If anyone later needs to trace the payment, every institution has the same picture.
Now change one detail: the instruction gives the supplier's name as a three-letter abbreviation and leaves out the address. The MSB will ask for the full details before sending. If the payment had gone out incomplete, it might have been held by the correspondent or the receiving bank, which costs far more time than fixing the instruction at the start.
What happens when information is missing
Incoming payments sometimes arrive with incomplete information. The originator's address may be missing, or the name may be truncated by an older payment system.
A receiving provider is expected to have a procedure for this. It will look at the risk: the amount, the countries involved, whether the client expected the payment, and whether the sending institution has a history of incomplete messages. Low-risk gaps may be resolved by asking the client or the sending bank. Higher-risk gaps may lead to the funds being held until the information is supplied, or returned.
Repeated failures by a particular sending institution can lead a provider to restrict or end its dealings with that institution.
For a client expecting funds, the practical step is to give your payer complete instructions and ask them to include their own full name and address in the payment. If you know a payment will come from a third party, such as a parent company paying on behalf of a subsidiary, tell your provider in advance. That avoids a mismatch between the expected and actual originator.
Payments on behalf of others
The travel rule identifies the actual originator and beneficiary. That matters where a payment is made for someone else.
Take an illustrative case. A trading company asks its provider to pay a supplier, but the funds really belong to an affiliated company that has no account of its own. The originator in the payment message will be the trading company, because it is the client giving the instruction. The provider will separately want to know that the funds belong to the affiliate, because it must make a third party determination and record that information.
Clients sometimes try to simplify a payment by putting a different name in the originator or beneficiary field, for example the name of a parent company because it is better known. Do not do this. The names in the payment message must be accurate, and false information in a payment can create problems for everyone in the chain, from screening alerts to regulatory breaches.
Differences between countries
The travel rule is an international standard, but its implementation varies. Some jurisdictions set a monetary threshold below which less information is required for virtual asset transfers. Others, including Canada, apply the requirement to all transfers. Some countries have implemented the rule for virtual assets in detail, while others are still working on it.
These differences cause friction. A Canadian provider sending virtual currency to a provider in a jurisdiction that has not implemented the rule may be unable to exchange information in the usual way, and will apply its own risk-based measures instead. A bank in one country may reject a wire because a field that is optional in the sending country is mandatory in its own.
For business clients making regular cross-border payments, the answer is to provide full information every time, whatever the destination. Complete data satisfies the strictest standard in the chain, and it is the simplest way to avoid payments getting held along the way.
Before you act
This article is general information about the travel rule. It is not legal advice, and the precise requirements depend on the jurisdictions and institutions involved in each transfer.
Travel rule requirements continue to develop, particularly for virtual assets, so check the current position in each jurisdiction involved. For CCYFX services, see the International payments and Digital asset conversion pages.
