The FATF Travel Rule requires VASPs to share sender and recipient information for crypto transfers above a threshold; Plastron does not handle Travel Rule data but screens the underlying wallet for AML risk free.

The Financial Action Task Force introduced the Travel Rule for crypto in its 2019 updated Recommendation 16, requiring VASPs to obtain, hold, and transmit originator and beneficiary information on virtual asset transfers above certain thresholds — $1,000 in the US, €1,000 in the EU, and equivalent amounts in most other jurisdictions. The rule extends the wire transfer Travel Rule from traditional finance into crypto, with significant compliance implications for exchanges, custodians, and any business processing crypto transfers on behalf of customers. Unlike traditional wire transfers, crypto transactions are pseudonymous by design: the blockchain shows wallet addresses but not the identities behind them. This creates a technical gap between what the Travel Rule requires — verified counterparty identification — and what the blockchain natively provides. VASP-to-VASP transfers can be handled through dedicated Travel Rule protocols (TRISA, OpenVASP, Notabene), but transfers involving self-hosted wallets remain a regulatory grey area in many jurisdictions. The other half of Travel Rule compliance — which is often overlooked — is the sanctions screening requirement: you must not only collect beneficiary information but also screen both parties against OFAC and other sanctions lists before processing the transfer. A Travel Rule-compliant transfer to a sanctions-listed beneficiary is still a regulatory violation. Plastron covers the wallet screening component: before you initiate or accept a crypto transfer, screen both wallets to confirm neither carries sanctions or high-risk exposure.