Statuses and lifecycle

Track and interpret the state of the Travel Rule data exchange transaction.

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 sender decided to cancel the transaction, either in accordance with the rules or manually, and not to proceed with it. The counterparty was identified, and the data was not sent. Because some the rule rejected the transaction.
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.
No VASP - assumed unhosted wallet	`counterpartyVaspNotFound`	The transaction targets an unhosted wallet, or the counterparty VASP could not be identified.
Counterparty VASP not reachable	`counterpartyVaspNotReachable`	The counterparty is not reachable due to missing protocol support. To simulate this scenario, use the "Sumsub test not reachable VASP" (ID: 683584cd36898664230ee173) in your transaction.
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`	The counterparty VASP has specified that the wallet address is not controlled by their organisation.
Counterparty declines the transaction	`counterpartyVaspGeneralDecline`	For inbound and outbound messages, the counterparty declines the transaction. Mostly applicable when dealing with counterparties on connected protocols.
Not enough counterparty data	`notEnoughCounterpartyData`	Not enough information was found about the second side of the transaction.
Not applicable	`notApplicable`	A transaction receives the notApplicable Travel Rule status when Travel Rule exchange is intentionally skipped based on your configuration, including: The transaction amount being below the minimum threshold, and/or The counterparty being classified as a non-VASP entity (when the corresponding setting is enabled). This status indicates that Travel Rule requirements do not apply to the transaction under your current settings, and therefore no Travel Rule data exchange is performed.
Unknown	N/A	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 about 7 hours ago