The Travel Rule requires originator and beneficiary information to travel with a virtual-asset transfer. Submit a transfer here and we handle the classification and the counterparty data exchange: whether the rule applies at all, whether the counterparty is a VASP or a self-hosted wallet, and the VASP-to-VASP exchange itself.
decision is the authoritative outcome for your integration:
decision | What it means |
|---|---|
APPROVED | Cleared. The transfer can proceed. |
IN_REVIEW | Held for review. Do not treat as cleared. |
DECLINED | Not cleared. |
AWAITING_OWNERSHIP | Waiting on the originator to prove they control a self-hosted wallet. |
Self-hosted counterparties
When the counterparty is a self-hosted wallet rather than a VASP, there is no institution to exchange data with, so ownership has to be proven by the person. We email the originator - supplied as subject_email, which must be an existing end user of your account - a hosted link where they sign a one-time message with their wallet. On success we clear ownership ourselves and the decision moves on; you do not need to call anything else. The same mechanism is exposed standalone under Wallet Screening.
Submitting the same client_reference again returns the existing record rather than creating a second transfer, so a retry after a timeout is safe.
In this section
| Endpoint | What it does |
|---|---|
POST /travel-rule/transfers | Submit a transfer for Travel Rule handling |
GET /travel-rule/transfers | List submitted transfers, filterable by decision |
GET /travel-rule/transfers/{transfer_id} | Fetch one submitted transfer |