The Travel Rule for Crypto Payments, Explained (2026)

The Travel Rule is FATF Recommendation 16 applied to crypto: when a regulated virtual-asset service provider (a VASP, or CASP in the EU) sends a virtual-asset transfer, it must collect, hold, and transmit specified information about both the originator (sender) and beneficiary (recipient) to the receiving provider, and make it available to authorities. FATF's baseline de minimis threshold is USD/EUR 1,000, but jurisdictions diverge sharply — the EU applies the rule to every transfer with no minimum, while the US uses USD 3,000.

We build Settlematic, a non-custodial crypto payment platform, and Travel Rule scope turns entirely on custody — so it matters for how these obligations land. Everything below is sourced to FATF, EU, and US primary frameworks and last verified on 7 September 2026.

What is the Travel Rule?

FATF Recommendation 16 originally required banks to attach originator information to wire transfers. In June 2019 FATF extended it to virtual assets and VASPs. The originating VASP must obtain and hold required originator and beneficiary data, transmit it securely to the beneficiary VASP alongside the transfer, and provide it to authorities on request. The beneficiary VASP must be able to detect when incoming information is missing or incomplete. The goal is a traceable record of who is sending and receiving value through the regulated system.

What information must be shared?

At or above the applicable threshold, the full data set applies. Below it, a reduced set (typically names plus a wallet address or reference) applies, without mandatory verification unless suspicion arises.

• Originator: name; account number or wallet (DLT) address (or a unique transaction reference); and physical address, OR national identity number, OR customer ID number, OR date and place of birth.
• Beneficiary: name; and account number or wallet address (or unique reference).
• For legal entities: a Business Identifier Code (BIC), Legal Entity Identifier (LEI), or other unique official identifier where one exists.

What are the thresholds by jurisdiction?

The EU's Transfer of Funds Regulation is the strictest: one euro of USDC triggers the same data obligation as a large BTC transfer. If any CASP in the chain — originator, beneficiary, or intermediary — is established in the EU, the rule applies.

How does the Travel Rule apply to payment flows?

The Travel Rule binds VASPs/CASPs, not the underlying blockchain and not self-hosted wallets. In a payment context, that means it attaches to the regulated intermediaries in the flow — for example an exchange or custodial processor that sends or receives on a customer's behalf. Two patterns matter for merchants:

• VASP-to-VASP: a transfer between two regulated providers is squarely in scope; each must exchange originator/beneficiary data.
• VASP-to-unhosted-wallet: when one side is a self-hosted (non-custodial) wallet, the VASP still has obligations — it must collect and, in some regimes, verify the counterparty information from its own customer, even though there is no counterparty VASP to transmit to.

Where does non-custodial change the picture?

This is the nuance most guides skip. The Travel Rule is an obligation on intermediaries that control funds. In a true non-custodial model like Settlematic, each invoice or checkout deposit address is cryptographically bound at issuance to a wallet the merchant controls; Settlematic never holds keys and cannot redirect, freeze, or hold funds. Payments settle wallet-to-wallet, and Settlematic watches the chain for detection and reconciliation. Because it never takes custody or moves value on a customer's behalf, the classic originating-VASP transmission duty does not arise in the same way it does for a custodial processor.

That is not a claim that non-custodial means no compliance. AML, sanctions screening, and KYB/KYC obligations attach to payment services regardless of custody, and the regulatory classification of any specific business depends on its facts and jurisdiction. Settlematic supports KYB/KYC onboarding and Travel Rule workflows precisely because merchants and their banking partners still need them. The point is narrower: removing custody removes the intermediary-holding-funds trigger that makes the Travel Rule's transmission burden heaviest.

What should a merchant do?

• Know your counterparties: if you route through an exchange or custodial processor, they carry Travel Rule duties that flow down to your onboarding and data.
• Match your jurisdiction's threshold: EU merchants should assume every transfer is in scope; US merchants focus on USD 3,000 and above.
• Keep records: originator/beneficiary data and reconciliation are audit essentials — see are crypto payment gateways safe.
• For EU-specific licensing context, read accepting crypto payments under MiCA.

Get started

If you want settlement that lands directly in wallets you control, with reconciliation and Travel Rule-ready onboarding built in, explore the Gateway or book a demo.

This article is general information, not legal or tax advice. Travel Rule implementation varies by jurisdiction and your specific role in a payment flow — consult qualified counsel. Verified 7 September 2026 — rules change.