TRP supports both custodial and non-custodial VASPs. The main differences relate to data responsibility and wallet control.
For custodial providers:
- the platform stores and manages user accounts;
- originator and beneficiary data are formed on the VASP side;
- TRP is used as an infrastructure for Travel Rule message exchange;
- stricter business validation and KYC controls may apply.
- Exchange / Custodian
- Centralized wallet management
- Full Travel Rule compliance flow
For non-custodial providers:
- wallet control remains with the end user;
- the VASP acts as the transmitting party for Travel Rule data;
- some data may be limited depending on the business model;
- enhanced checks are applied for incoming and outgoing transfers.
- Wallet provider
- Self-custody wallets
- Selective data sharing according to regulation
After completing the basic integration, it is recommended to:
- test all scenarios in the Test environment;
- verify error handling and edge cases;
- complete production onboarding;
- enable monitoring and alerts.