Compliance · By the Paypled team ·
The travel rule, explained for finance teams.
The travel rule requires identifying information about the sender and recipient to accompany crypto transfers between service providers. What it is, what data travels, how thresholds differ by jurisdiction, and what it means for a business paying in USDT.
If your business pays suppliers or contractors in USDT, the travel rule is the compliance requirement most likely to delay a payment you thought was simple. It is not new, it is not specific to crypto in origin, and it is not something Paypled can waive. This explainer covers what it is and what it changes in practice. It is general information, not legal advice; the thresholds and formats below move, so confirm them with counsel for the jurisdictions you operate in.
What the travel rule is
The travel rule comes from the Financial Action Task Force’s Recommendation 16, which has long required banks to send originator and beneficiary information along with wire transfers. In 2019 the FATF extended it to virtual-asset service providers (VASPs): exchanges, custodians and payment platforms. When one VASP sends a crypto transfer to another, identifying information about the sender and the recipient must travel with the transfer, and the receiving VASP must be able to screen it.
Jurisdictions implement the rule in their own law. The United Kingdom brought it into force for cryptoasset businesses on 1 September 2023. The European Union applied it to crypto-asset service providers through the recast Transfer of Funds Regulation from 30 December 2024. Many other countries have equivalent rules at different stages.
What data travels
Typically: the originator’s name, the account or wallet identifier used for the transfer, and one of an address, a date and place of birth, or a customer identification number; and the beneficiary’s name and wallet identifier. The data is transmitted VASP to VASP over a messaging protocol, not written on the blockchain. The transfer itself looks the same on-chain as any other.
Thresholds differ
The FATF suggests a threshold of USD or EUR 1,000, below which reduced information may apply. The EU regime applies to crypto transfers with no minimum threshold. The UK regime requires full information for transfers at or above £1,000 and reduced information below that. Other jurisdictions set their own numbers. A business paying across several regions should assume the strictest applicable rule and collect full beneficiary details for every payout; the marginal cost of asking is far lower than the cost of a held payment.
Unhosted wallets
A transfer to a wallet that no service provider controls (a self-custody or ‘unhosted’ wallet) does not have a receiving VASP to exchange data with. Regimes handle this differently: some require the sending VASP to collect and verify information about the wallet’s owner above a threshold, some require a risk-based assessment, and some restrict such transfers for business customers. Expect to be asked who controls a self-custody address before a large payout goes to it.
What it means operationally
Collect beneficiary details before you need them. A contractor’s legal name and the identity of the exchange or wallet they use are easy to gather at onboarding and painful to chase on payday. Expect holds when the receiving VASP cannot accept travel-rule data or when a name does not match. Keep the sanctions screening separate in your mind from the travel rule: the first blocks a counterparty, the second attaches information, and a payout can fail either test.
How Paypled handles it
Originator and beneficiary data travels with the transfer to the receiving VASP, screening runs before anything is broadcast, and a withdrawal that cannot satisfy the rule is held for review rather than sent and reversed. In the console that is the ‘pending review’ state after you confirm a USDT withdrawal. Beneficiary details you provide once are reused for later payouts to the same destination.
A short checklist
Collect legal names and wallet or exchange identifiers at onboarding. Know which of your counterparties use self-custody. Assume the strictest threshold that applies to you. Keep records for the retention period your regime requires, which is at least five years in the UK and EU. Review the rules annually; this is an area that changes.
Takeaways
- The travel rule attaches sender and recipient information to VASP-to-VASP transfers; it is not visible on-chain.
- Thresholds and unhosted-wallet treatment differ by jurisdiction; assume the strictest.
- Collect beneficiary details at onboarding, not on payday.