What is the travel rule
The FATF Travel Rule (Recommendation 16) requires Virtual Asset Service Providers (VASPs) to collect, exchange, and verify originator and beneficiary information for virtual asset transfers above certain thresholds. Didit provides the infrastructure to track this data and enforce compliance through automated rules.Submitting travel rule data
Include thetravel_rule_details object when creating a transaction:
| Field | Type | Description |
|---|---|---|
status | string | Current compliance status (see statuses below) |
protocol | string | Travel rule protocol used (e.g., TRISA, TRP, OpenVASP) |
required | boolean | Whether the travel rule applies to this transaction |
obligations_count | number | Number of outstanding compliance obligations |
originator_data | object | Information about the originator (sender) |
beneficiary_data | object | Information about the beneficiary (receiver) |
metadata | object | Additional protocol-specific metadata |
Travel rule statuses
| Status | Description |
|---|---|
UNKNOWN | Travel rule applicability has not been determined |
COMPLIANT | All required data has been exchanged and verified |
PENDING_ACTION | Your VASP needs to take action (e.g., provide originator data) |
PENDING_COUNTERPARTY | Waiting for the counterparty VASP to provide or confirm data |
FAILED | Data exchange failed or compliance requirements were not met |
EXEMPT | Transaction is exempt from travel rule requirements (e.g., below threshold) |
Originator and beneficiary data
Theoriginator_data and beneficiary_data fields are free-form objects for VASP-to-VASP information exchange. Typical fields include:
| Field | Description |
|---|---|
name | Full name of the originator or beneficiary |
account_number | Wallet address or account identifier |
address | Physical address |
institution_name | Name of the originating or beneficiary VASP |
institution_country | Country of the VASP |
Preset rules
Didit includes built-in rules that automatically flag transactions based on their travel rule status:| Rule | Trigger | Action |
|---|---|---|
| Pending counterparty | Status is PENDING_COUNTERPARTY | Hold transaction for review |
| Pending action | Status is PENDING_ACTION | Flag for analyst action |
| Missing required data | required is true but originator or beneficiary data is incomplete | Flag for review |
Console view
The transaction detail view in the Business Console includes a dedicated Travel Rule tab showing:- Current compliance status with a visual badge
- Originator and beneficiary data side by side
- Protocol and obligation details
- Timeline of status changes
Next steps
Submitting transactions
How to include travel rule data in the Create Transaction payload.
Rules & scoring
Built-in travel rule rules and how to customise them.
Console guide
Viewing travel rule status in the transaction detail view.