Data transfer statuses
Track and interpret the state of the Travel Rule messages.
The following is a list of possible statuses you can get during the VASP data exchange.
Tip
To test VASP data exchange, refer to this article.
| UI status | API status | Description |
|---|---|---|
| Awaiting counterparty | awaitingCounterparty | The counterparty was successfully identified and the data has been sent. Awaiting a response from the counterparty. |
| Cancelled | cancelled | The counterparty was identified, and the data was sent. However, the counterparty decided to decline the message, be it by the rules or manually, and not to proceed with it. |
| Completed | completed | Data exchange completed. |
| Counterparty mismatched personal data | counterpartyMismatchedData | The counterparty cross-checked the data we provided against their records and reported a mismatch. |
| Counterparty unconfirmed ownership | counterpartyUnconfirmedOwnership | For outbound messages, the counterparty was identified, and the data was successfully sent. However, the counterparty returned a negative response regarding wallet ownership verification. |
| Counterparty VASP not found | counterpartyVaspNotFound | The counterparty VASP could not be identified. |
| Counterparty VASP not reachable | counterpartyVaspNotReachable | The counterparty is not reachable: although the counterparty has been identified, no response has been received. |
| Expired | expired | The counterparty was identified, and the data was sent. However, no response was received from the counterparty within the expected timeframe. The confirmation timeout settings can be adjusted in the Transactions and Travel Rule -> Settings -> General tab. |
| Finished | finished | The blockchain transaction ID has been updated in the Completed transaction record. This status always follows the Completed status. |
| OnHold | onHold | For inbound messages, wallet ownership has been confirmed. Review the customer details and confirm or decline the data match. |
| Unconfirmed ownership | unconfirmedOwnership | For inbound messages, you confirmed that the wallet does not belong to you. |
| Counterparty declines the transaction | counterpartyVaspGeneralDecline | For inbound and outbound messages, the counterparty declines the transaction. Mostly applicable when dealing with counterparties on connected protocols. |
| Unknown | unknown | For inbound and outbound messages, the status shows because the Travel Rule: New TR data exchange request rule is not installed or is in Test Mode. To resolve this, simply install the rule and set it to active. |
Updated 6 days ago