Travel Rule

Travel Rule refers to FATF Recommendation 16, extended to crypto, which obliges virtual asset service providers (VASPs) to collect and pass on identifying information about the sender and receiver when value moves above a set threshold. That threshold is commonly USD or EUR 1,000, though the exact figure and the data required depend on local implementation. The originating provider must transmit originator details (and beneficiary details) to the receiving provider, so that identity information effectively travels with the transfer. The rule exists to stop pseudonymous crypto rails from becoming a blind spot for aml controls.

For gambling operators the key question is scope: whether a crypto casino cashier that holds and moves customer funds is acting as a VASP for a given transfer. The answer varies by jurisdiction and by how the cashier is structured, but operators that custody crypto and process withdrawals to external wallets can find themselves in scope. Where the rule applies, the compliance burden includes capturing the required counterparty data, transmitting it securely to the receiving provider, and handling inbound transfers that arrive without complete information. This sits on top of, and depends on, the operator KYC programme captured as kyc, since the originator information has to come from verified identity records.

In practice the Travel Rule does not stand alone; it is one input into a wider control set. The data it produces feeds transaction-monitoring, giving analysts counterparty context that improves alerting on structuring and high-risk flows. Whether and how the rule bites also depends on the operator location, framed as its gambling-jurisdiction, and any VASP registration regime it imposes, so two operators with similar products can face different obligations. Because cross-border interoperability between providers is still maturing, operators often treat Travel Rule readiness as an ongoing programme rather than a one-time configuration.