Skip to main content
u
glossaryGlossary

/

Travel Rule Compliance

Travel Rule Compliance

The Travel Rule is a requirement that a business sending crypto on behalf of a customer passes identifying information about the sender and the recipient to the business receiving it. It copies a rule banks already follow for wire transfers: information about the parties "travels" with the payment.

Where it comes from

The Financial Action Task Force (FATF) is an intergovernmental body, set up in 1989, that issues standards against money laundering and terrorist financing. Its recommendations are not binding on their own. Countries adopt them into national law, and the details differ. In 2019 FATF extended its standards to virtual assets and to virtual asset service providers (VASPs), such as exchanges and custodians. The Travel Rule is the best-known part of that extension. In the EU, a similar requirement applies to crypto-asset transfers alongside MiCA.

What it generally requires

In general terms, for a transfer above the local threshold, the sending VASP collects and sends:

  • the sender's name and account or wallet identifier;
  • the recipient's name and account or wallet identifier;
  • in some countries, more details such as an address or date of birth.

The receiving VASP checks that the data arrived and screens it. Thresholds, data fields and the treatment of transfers to or from a wallet the customer controls differ between countries. A VASP also needs KYC data about its own customers to have anything to send. Ask your compliance adviser which rules apply to you.

The Lightning angle

A Lightning payment passes through routing nodes that see only the previous and next hop. Payment data is encrypted per hop, so routing nodes cannot read or attach sender details. Where the Travel Rule applies, the identifying information is exchanged between the businesses involved, outside the payment route. Whether and how the rule applies to a given Lightning flow depends on the jurisdiction and on the activities each business performs, so it needs a jurisdiction-specific assessment.

How Amboss handles Travel Rule compliance

Travel Rule messaging between VASPs happens in dedicated Travel Rule tools. Reflex covers the screening and policy layer around it: it screens channel peers by IP address and funding source against sanctions lists, checks funding addresses against the OFAC SDN list, and produces exportable audit reports. Amboss describes this as extending your existing AML program into the Lightning payment layer. Amboss's payment-provider guidance also says your business remains responsible for its own compliance obligations. See also compliance automation.

PAYMENTS FOR YOUR BUSINESS

Give your customers another way to pay.

Accept Bitcoin and stablecoin payments on your website or app with Amboss.

Talk to sales