Note: We recommend that you automate this manual proccess using the API.
You can send a transaction manually to a counterparty VASP using the Send Transaction Notification button.
This will prompt a three-stage form modal consisting of:
The Beneficiary Information step of the form will show two options depending on the protocol the counterparty VASP uses.
If a valid Travel Address is provided by your counterparty VASP this means you can use the TRP protocol. This currently comes in the form of an LNURL.
If a Travel Address is used, the first name must be the one associated with the LNURL Travel Address.
If a Travel Address is used, the last name must be the one associated with the LNURL Travel Address.
The Counterparty VASP must provide the Travel Address. This LNURL contains information about the customer of the Counterparty VASP that wishes to do the transaction. If this is introduced correctly, our software will infer what counterparty VASP data the LNURL is associated with.
If a VASP does not have TRP as a fallback, email can be used. To use this protocol, you can simply add a Wallet Address instead of a Travel Address.
The first name of the customer who owns the Wallet Address.
The last name of the customer who owns the Wallet Address.
A Wallet Address with the correct format for any of our supported virtual assets.
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:
Here you can find a list of all the assets we support. If you can't find an asset, you can always contact 21 Analytics and request to add an asset. You should choose the virtual asset used in the transaction.
The amount of the virtual asset selected for the transaction.
If you are using the TRP protocol, you will now see the second step of the form:
If you are using the Email protocol, you will now see the second step of the form:
A list of VASPs added on Counterparty VASPs. You should choose the VASP the beneficiary is a customer of.
A virtual asset transaction will create a Transaction ID for this particular transaction in the blockchain. You can usually find these either on your wallet or on a blockchain explorer.
The third and last step of the form is the Originator Information.
Here you will find the following steps:
The first name of the originator customer of your VASP.
The last name of the originator customer of your VASP.
A number used to identify your customer within your system. This can be mapped to an external custodial system. Each customer should have a unique Account Number.
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.
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 Steet Name or Address Line fields.
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.
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 where the originator customer resides.
Country where the originator customer resides.