Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Outgoing Transaction

Note: We recommend that you automate this manual process using the API.

On any transaction tab, click Outgoing Transaction when your customer is the originator of the transaction. 21 Travel Rule then notifies your counterparty VASP about the transaction, including all required Travel Rule data.

Enter a Travel Address or wallet address in the same form. 21 Travel Rule uses TRP for a Travel Address or a wallet address found in the TRP directory. For other wallet addresses, it looks for an owner on TRUST. If neither protocol finds a counterparty VASP, you can send the notification by encrypted email.

For email notifications, the presence of the transaction ID determines whether the email includes a request for the counterparty to confirm the beneficiary details. Upon which you will proceed in executing the transaction on the blockchain.

This is typically used when your customer provides the beneficiary details. See below for more details.

The form contains three stages:

1. Beneficiary Information

The Beneficiary Information step accepts either a Travel Address or a wallet address. Use Auto-detect VASP for TRP or TRUST, or select a specific counterparty VASP to use encrypted email.

TRP or TRUST Protocol

Use a Travel Address for TRP, or a wallet address for automatic TRP directory and TRUST lookup.

Beneficiary Natural Person

Beneficiary Legal Person

You can send to both natural or legal beneficiaries. If a Travel Address is used, the first and last name (in the case of a natural person beneficiary) or the legal name (in the case of a legal person beneficiary) must match the one associated with the Travel Address as found in the corresponding Address Book entry.

Travel Address

The Counterparty VASP must provide the Travel Address. This Travel Address contains information about the customer of the Counterparty VASP that wishes to conduct the transaction. If this is introduced correctly, 21 Travel Rule will infer which counterparty VASP data the Travel Address is associated with.

Counterparty VASP Selection

Auto-detect VASP is selected by default and marked as recommended. Leave it selected to discover the counterparty VASP through TRP or TRUST when you submit the transaction.

If no counterparty VASP is found, the form returns to Beneficiary Information. If email is configured, the selection is cleared and the Auto-detect VASP option is removed. Select a counterparty VASP to continue using encrypted email.

Email Protocol

Select the beneficiary's counterparty VASP to use encrypted email. You can do this directly or after automatic detection fails.

Beneficiary Natural Person

Beneficiary Legal Person

First Name

The first name of the customer who owns the Wallet Address.

Last Name

The last name of the customer who owns the Wallet Address.

Wallet Address

A Wallet Address with the correct format for any of our supported digital assets.

Counterparty VASP

A choice of trusted counterparty VASPs maintained at Counterparty VASPs. You should choose the VASP the beneficiary has an account with.

2. Digital Asset

This step will show different fields depending on your chosen protocol in the Beneficiary Information step. You will see the following fields on both flows:

Fields Overview (Digital Asset)

Digital Asset

Here you can find a list of all the assets we support. 21 Travel Rule supports the complete list of ISO24165 DTIs (Digital Token Identifiers). If you can't find an asset, you can always contact 21 Analytics and request to add an asset. You should choose the digital asset used in the transaction.

Amount

The amount of the digital asset selected for the transaction.

TRP or TRUST

For TRP or TRUST, the second step of the form also has a Transaction ID (TxID) field. It is optional for TRP inquiries, but required for TRUST notifications.

Email

If you are using the Email protocol, you will now see the second step of the form:

This has some additional fields apart from Digital Asset and Amount; these are:

Transaction Status and the Transaction ID (TxID) field

The encrypted Email protocol for outgoing transactions supports two different workflows with two different email contents:

  1. If the transaction has been executed, the email will simply share Travel Rule data with the beneficiary VASP.
  2. Alternatively, you can ask the beneficiary VASP for confirmation of the Travel Rule data before executing the transaction.

Thus, the form will ask you to choose between those two variants, and if you chose number 1, it will ask you for a transaction ID as well:

Comment (optional)

A optional comment for the transaction.

3. Originator Information

The third and last step of the form is the Originator Information.

Originator TRP

Originator Email Natural Person

Originator Email Legal Person

Fields Overview (Originator Information)

Here you will find the following steps:

Originator Name

The name of your customer. The options in the drop down are fetched from the address book.

Customer Identification

This is a data point that allows to uniquely identify your customer. Typically a Passport Number, Phone Number, Date of Birth or Bank Account Number.

If the selected originator is a legal person, enter its legal ID. This field is required for TRP and TRUST transactions with a legal originator.

You can receive from both natural or legal originators when choosing encrypted email.

Street Name (optional)

The name of the street the originator customer of your VASP resides at on their ID. This is optional unless you are using TRP. If TRP is used, either this field or Address Line is required, as well as the Building Number.

Building Number (optional)

The building number on either the street or address in which the originator customer of your VASP resides at on their ID. This is optional unless using the TRP flow. This would be required alongside either the Street Name or Address Line fields.

Address Line (optional)

The Address Line where the originator customer of your VASP resides, as shown on their passport or ID. This is optional unless using the TRP flow. If TRP is used, either this field or Street Name is required, as well as the Building Number.

Postal Code

The postal code of the originator customer of your VASP. This postal code is tied to the address on the customer's passport or national ID.

City

City where the originator customer resides.

Country

Country where the originator customer resides.