VASP-to-VASP Transactions
Select this screen to send Travel Rule data, review messages from counterparty VASPs, and import incoming transfers. Your customer's role determines the transaction type: Sent when your customer is the originator, or Received when your customer is the beneficiary.
21 Travel Rule exchanges and stores compliance data. Your wallet or custody system executes the blockchain transfer and credits the beneficiary. Approving a Travel Rule request does not move funds; confirming a TRP transaction reports a transfer that you have already executed.
Start with Your Task
Exchange Data with Counterparty VASPs
- Send funds to another VASP's customer: use Outgoing Transaction to send the Travel Rule data. Follow the TRP or TRUST or email walkthrough for your counterparty.
- Review a received message: TRP requests appear automatically in Inbox; received TRUST data appears in Archived. Open the existing record to review it.
- Import an incoming transfer: use Incoming Transaction when you need to enter the details yourself, for example when your customer supplies the originator information. You can request confirmation from the originator VASP by email, or save the record without sending a message. This form is not needed for transactions already received through TRP or TRUST.
Obtain Self-Hosted Wallet Ownership Proofs
For a transfer involving a self-hosted wallet, follow the wallet ownership proof workflow.
Follow a TRP Transaction
The tabs tell you who acts next:
- Inbox: your VASP needs to act.
- Waiting: the counterparty VASP needs to act.
- Archived: the TRP exchange has ended.
Inbox and Waiting contain only TRP transactions. Archived also contains TRUST, email, and imported transactions.
If a TRP transaction is blocked because the counterparty is unknown or untrusted, complete counterparty due diligence before proceeding.
Outgoing Transactions
Your customer is the originator, and the transaction type is Sent. After you send the request, it follows these steps in your dashboard:
| Tab | Status | What happens next |
|---|---|---|
| Waiting | Pending | The beneficiary VASP reviews your request. Approval moves it to Inbox. |
| Inbox | Approved | Your VASP executes the blockchain transfer, then uses Confirm to submit its transaction ID. This moves it to Archived. |
| Archived | Executed | The TRP exchange is complete. |
An approved outgoing transaction appears in Inbox because your VASP must
confirm or cancel it. If you will not execute the transfer, use
Cancel Transaction; it moves to Archived as Cancelled. If the beneficiary
VASP declines the request, it moves directly from Waiting to Archived as
Declined.
Incoming Transactions
Your customer is the beneficiary, and the transaction type is Received. A request from the originator VASP appears automatically in your dashboard:
| Tab | Status | What happens next |
|---|---|---|
| Inbox | Pending | Your VASP reviews the data, then uses Approve to move the request to Waiting. |
| Waiting | Approved | The originator VASP executes the blockchain transfer and confirms its transaction ID. This moves it to Archived. |
| Archived | Executed | The TRP exchange is complete. Check receipt of funds in your wallet or custody system. |
To reject an incoming request, use Decline; it moves from Inbox to Archived as
Declined. If the originator VASP cancels after your approval, it moves from
Waiting to Archived as Cancelled.
See the Inbox actions guide for the action forms, or the TRP flow for the exchange between both VASPs.
Protocols and the Blockchain Transfer
- TRP: send the request before executing the blockchain transfer. Once the beneficiary VASP approves it, the originator VASP transfers the funds and confirms the blockchain transaction ID. The confirmation completes the TRP exchange.
- TRUST: the outgoing form requires the transaction ID of an executed blockchain transfer. Successfully sent and received TRUST messages appear directly in Archived, without the TRP approval and confirmation steps. See the TRUST flow.
- Email: send data for an executed transfer, or request confirmation of the beneficiary details before executing it. For an incoming transfer, you can request confirmation of the originator details before crediting your customer. Email records appear directly in Archived; follow up on replies in email. See the email flow.
An archived record does not by itself establish that funds arrived or that your compliance checks are complete. Email records are labelled Executed even when you requested confirmation before transferring funds. Incoming transfers saved without email are labelled Registered. Check your custody records and the counterparty's response before proceeding with your customer.
Available Actions on Tabs
Each transaction tab provides the following controls:
- Search finds transactions matching text
across multiple transaction properties. Enter a term in
Search for any transaction propertyand clickSearch. Click the cross in the search field to clear it. - Outgoing Transaction starts a transaction for which your customer is the originator.
- Incoming Transaction records a transaction for which your customer is the beneficiary.
- Export Transactions downloads the rows matching the current filters.
- Pagination moves between pages when a table contains more than 15 rows.
Use filtering and sorting to find records. Open a transaction's details to review its data or event history.