E
IMPORTANT
The Travel Rule currently requires that every BUY order must be sent to your customer via
a paper wallet, https://generalbytes.atlassian.net/wiki/spaces/ESD/pages/963281004/Terminal+Settings#Printing-Settings-(for-BATMs-with-attached-printers)
a PDF wallet (see: PDF Wallet Generation),
SMS,
or Email.
There is currently no way (using the TR) to send coin to any other type of wallet!
It is impossible to technically identify the owner of the customer-presented wallet, so
therefore those wallets do not comply with Travel Rule requirements.
What is this?
This feature enables you to comply with your regional Travel Rule legal requirements, and enables compliant transactions for your customers.
Components
Outgoing TransfersView the transfer logs. | |
Travel Rule SettingsConfigure your Travel Rules. | |
Travel Rule ProvidersAdd or adjust a Travel Rule Provider.
| |
VASPsAdd or adjust a VASP:
|
Example
This example enables immediate self-hosted compliance for your Organization.
Create a Travel Rule Provider: “Internal”, see: Travel Rule Providers
Create a new VASP, see: Travel Rule VASPs
Add a new Setting, see: Travel Rule Settings
Configure your AML/KYC setting to use the new Travel Rule, see: https://generalbytes.atlassian.net/l/cp/U57zcH33
Configure your Terminal(s) to use the proper AML/KYC setting, see: https://generalbytes.atlassian.net/wiki/spaces/ESD/pages/963281004/Terminal+Settings#General-Settings
Any transaction that has been packaged via a Travel Rule can be viewed from the Transaction Log:
An example Transfer/Envelope: