Travel Rule: SELL

Implementing the Travel Rule for SELL transactions requires 2 timelines to simultaneously transition the legacy transaction record and the travel rule transfer (together).

The flow requires you (the Operator) to determine the wallet type (custodial vs unhosted) in advance with your customer.

Wallets of type “UNKNOWN"are automatically rejected when using the Travel Rule.

NOTE: Every time you modify a TR transfer, the change is recorded internally.

This embedded PDF flowchart illustrates the various use cases for SELL transactions:

The legend explains the different arrow styles used in the timelines.
Download the PDF to view all 7 use cases:

How to Implement the Travel Rule for SELL transactions

1. Setup a Travel Rule Provider

See: Travel Rule Providers
For SELL transactions, the transfer direction is Incoming.

2. Setup a VASP

Create a VASP if you haven’t already done so.

See: Travel Rule VASPs

3. Configure the Travel Rule Settings

Enable or disable automatic evaluation of incoming Travel Rule transfers.
See: Travel Rule Settings

4. (Optional) Input Queues

Implement Input Queues to hold approved transactions before cash-out.

See: Input Queues

5. AML/KYC Settings

Configure the tier used by compliant Terminals to include the TR requirement.

Ensure your Terminal uses this the AML/KYC setting.
See: AML / KYC Settings