Discuss how Travel Rule exchange could fit your operating
model once the platform is authorised. This starts a
conversation — it does not enable or install anything.
What this component does
Exchange originator and beneficiary information
Validate counterparties where required
Handle self-hosted wallet cases
Retain Travel Rule evidence
Do not submit identity documents, private keys, passwords or
confidential customer data. See our
Privacy Policy.
Planned — subject to authorisation and implementation
Travel Rule exchange
Planned exchange of originator and beneficiary information for qualifying crypto-asset transfers.
Category
RiskOS
Availability
Planned
Delivery
Fintech Meta and/or partner
Required controls
Originator/beneficiary information exchange
Counterparty validation
Self-hosted wallet handling
Dependencies
Address risk scoring
KYB and KYC
Purpose
The Travel Rule requires certain information to accompany qualifying
crypto-asset transfers. This component exchanges and records that information.
Planned capability
Exchange of originator and beneficiary information, counterparty validation and
handling of self-hosted wallet cases.
Primary users
Compliance operations.
Required controls
Information exchange, counterparty validation and self-hosted wallet handling.
Dependencies
Depends on address risk scoring and identity verification.
Delivery model
Expected delivery: Fintech Meta infrastructure and/or an approved specialist
partner, with Fintech Meta retaining the oversight required by the final
operating model.
Audit evidence
Travel Rule messages and validation records.
Regulatory considerations
Applies to qualifying transfers under the relevant regime.
Availability
Planned — subject to authorisation and implementation.