This manual describes the GUI of 21 Travel Rule.
Once 21 Travel Rule is installed and used for the first time, the user is prompted to set a password and, optionally, configure counterparty VASPs.
When the database doesn't contain a user, 21 Travel Rule prompts the compliance officer to create one.
You can un-hide the password fields. There are no password restrictions defined. Only one user is currently supported in the GUI (the API supports more). After entering the required user name and password, you are logged in immediately. The user name shows in the upper right corner of 21 Travel Rule.
Once logged in, you need to configure your own VASP. You can configure four different sets of attributes:
Fill out those you feel are relevant for your VASP.
Once you have saved a configuration, you are encouraged to configure counterparty VASPs.
TRP is our preferred protocol. First, fill out the name of your VASP and the associated LEI. Upon saving, a signing public key shows. If you wish to use message signing, you can give this to a counterparty VASP.
If a VASP does not support any Travel Rule protocol, 21 Travel Rule can instead send an email with the relevant information. This makes you compliant with the Travel Rule nonetheless.
If you want to configure email, and we recommend you do that, you can do that on the 'Email' tab. The field values probably come from the IT department.
On the tab 'AOPP', you can configure the callback URL. The end user's wallet uses this URL to submit a signature and new VA address. This URL must be publicly accessible.
Each incoming transaction needs to be associated with a counterparty VASP. If the incoming transaction's counterparty VASP is not configured, you will not see that transaction in the inbox.
Each counterparty VASP supports exactly one protocol. That protocol can be:
Three fields are required when configuring a VASP that supports TRP. Two are optional.
The name field is used to identify the VASP. For example, 'SDX'.
The API URL field tells 21 Travel Rule where the counterparty VASP runs its TRP protocol. You get this information from the counterparty VASP.
The LEI field is a unique identifier for the counterparty VASP, and they should provide it for you. The LEI registry is also public.
The Signing Public Key is optional. When filled out, the Message Signing TRP extension is going to be used when sending Travel Rule transactions. Both the originator and the beneficiary VASP need to configure this to work.
The last checkbox controls how 21 Travel Rule handles incoming Travel Rule transactions from this particular VASP. It will move transactions from this VASP immediately to the archive when checked.
Add the name of the VASP and the email address. 21 Travel Rule will then send an email when you select this VASP when sending a Travel Rule transaction. It is required to have your email configured. See Email configuration.
Regardless of protocol, inbound and sent/approved Travel Rule transactions end up in the inbox and archive, respectively.
The inbox contains inbound transactions of known VASP (and known VASPs only). A compliance officer can inspect the transactions and move them to the archive once he has dealt with them.
The transaction details can be viewed by clicking anywhere on the transaction line. Besides the previously shown data, this shows all other relevant data concerning the transaction. For example, the amount is shown as the VA amount and the approximate dollar equivalent when the transaction was received. In addition, several items link to block explorers, Google Maps, and the public LEI registry for your convenience.
Transaction Status describes the status of the Travel Rule transaction, not the on-chain transaction. Transactions in the inbox have the status 'Pending'. In the archive, they are 'Executed'.
The Transaction Type tells you whether this transaction was sent or received.
Sending Travel Rule transactions is the bread and butter of 21 Travel Rule.
The Travel Rule stipulates that beneficiary and originator data must be sent to the beneficiary VASP. Therefore, when clicking 'Send Transaction Notification' on the 'Transaction' tab, you are shown a pop up asking for the beneficiary data.
The first and last names should come as no surprise. The originating user supplies these; he gets them from the beneficiary user. The wallet address is the beneficiary user's deposit address from his VASP.
Instead of a wallet address, a beneficiary VASP can give his user a Travel Address. This Travel Address is an encoded URL. When you give 21 Travel Rule a Travel Address, it decodes it. We then know the beneficiary VASP. Then we can ask the beneficiary VASP for a VA address. Using a Travel Address prevents asking the user to which VASP (if any) they will send their coins.
If the user does not supply a Travel Address, he should tell you to which VASP he is sending the coins. Fill that out under 'Select Beneficiary VASP'. Only to previously added VASPs can coins be sent (and received)!
The fields should be self-explanatory. You need to fill out the on-chain transaction ID. That means that the on-chain transaction should already have taken place. You only got the VA address in the previous step with the Travel Address. Do the on-chain transaction while leaving the web page with the second step open.
The final step is including the originator information. This information comes from your internal systems. As specified in IVMS101, you must supply either street name + building number or address line.
Once you click send, 21 Travel Rule sends the information to the beneficiary VASP via the applicable protocol. The Travel Rule transaction ends up in the 'Archived' tab.
You might receive a Travel Rule message out of band. For example, you got an email or took a phone call that relayed Travel Rule information.
To keep all Travel Rule information in the same place, you can retroactively add this information to the system.
Go to the 'Archive' tab on the 'Transactions' screen. You will see an 'Archive New Transaction' button in the top right corner. Enter the data in the shown pop and save.
When your AML auditor or a government official requests data from the system, you can export either a single transaction or the entire database.
Go to the inbox or archived tab to export a single transaction and expand a transaction. On the bottom left corner of the expansion, you will see an 'export' button. Clicking that button will export the transaction as an Excel/CSV file.
Similarly, you can export the entire database of archived transactions. First, go to the archived tab. Then, a button in the top right corner reads 'Export transactions'. This will export all transactions as an Excel/CSV file.
The tab 'Private Wallets' shows all the address ownership proofs your VASP has received throught the Address Ownership Proof Protocol.
The only column worth mentioning is the 'Signed Proof' column. This column shows the message the user saw on his wallet that he signed. Your VASP generates it.
You can export all the proofs with the 'Export Proofs' button.
Additionally you can add an Address Proof by hand. Click on the 'Add Address Proof' button and fill out the fields in the pop up shown.
This feature allows you to keep all relevant information in one place, just like adding an out of band received Travel Rule transaction.