Use case — Crypto
Travel Rule transfers
Determine scope, find the counterparty, exchange the required data.
The problem
Transfers above a threshold require originator and beneficiary information to travel with the value, including for unhosted wallets.
Modules used
Travel Rule scope
Counterparty VASP discovery
Travel Rule
Unhosted wallet proof
The flow
What runs, in order
Each step is an independently configurable module with its own result on the decision object.
- 1
Step 1
Scope test on the transfer against the applicable threshold
- 2
Step 2
Counterparty VASP discovery and protocol negotiation
- 3
Step 3
Data exchange and message record retained against the transaction
- 4
Step 4
Ownership proof collected for unhosted wallet counterparties
Outcome
What the team is left holding
A per-transfer message record that shows what was sent, to whom, and when.
See VerifiX on your own onboarding flow
A 30-minute walkthrough with a compliance engineer, or a sandbox key in your inbox today.