Travel Rule related rules

Rules are necessary in order to set up the conditions for checking the Travel Rule data exchange transactions. After you activate the rules, they are automatically applied to check each transaction for compliance with the specified parameters.

The pre-configured rules cover various scenarios to ensure thorough risk evaluation for each transaction. Find the full list of Travel Rule-related rules in the following table.

Rule title	Rule action	Description
Travel Rule: New TR data exchange request	Pre-scoring	Collects the counterparty data and launches a chain of protocols to find the most suitable one for a data exchange transaction. Based on the result, scoring rules are applied.
Travel Rule: Unhosted wallet verification	Pre-scoring	Provides an option to process transactions with unhosted wallets. Gets triggered only if the system did not find any reachable VASP.
Travel Rule: Counterparty AML Screening	Pre-scoring	Initiates AML screening of the counterparty and creates an AML case.
Travel Rule: Counterparty AML Screening - Hits to review	Scoring	Changes the transaction status to Required action if any matches are found during AML check.
Travel Rule: Counterparty AML Screening - True Positive Hit	Scoring	Changes the transaction status to Rejected if any AML matches have True positive status.
Travel Rule: On hold	Scoring	If data transfer status is OnHold, the transaction gets the Requires action status. This applies only to inbound transactions. You need to review the user details and confirm or decline the data match.
Travel Rule: Pending counterparty VASP action	Scoring	If data transfer status is awaitingCounterparty, the transaction gets the Awaiting User status. Counterparty VASP needs to perform actions with the transaction.
Travel Rule: Counterparty VASP not found	Scoring	If the found counterparty VASP does not participate in any of the supported protocols or was identified as an unhosted wallet, the data exchange transaction will get the Counterparty VASP not found status.
Travel Rule: Sunrise VASP (Jurisdiction)	Scoring	Puts on hold transactions owned by VASPs located in non-Travel Rule jurisdictions.
Travel Rule: VASP Screening (Due Diligence Status)	Scoring	If the counterparty VASP Due Diligence status differs from completed, the data exchange transaction will get the OnHold status.
Travel Rule: FCA watchlist	Scoring	FCA has issued a warning against this entity (VASP).
Travel Rule: Counterparty VASP did not respond	Scoring	The counterparty VASP appears to be in our network, but it did not respond to our request. The transaction will be assigned the Unreachable VASP tag.
Travel Rule: Counterparty VASP confirmed data mismatch	Scoring	If the counterparty VASP found via the GTR protocol has confirmed that the provided data does not match their user information, the transaction will be rejected.
Travel Rule: Wallet does not belong to the counterparty VASP	Scoring	The counterparty VASP confirmed that the provided wallet address does not belong to them. The transaction will be rejected. This applies only for outbound transactions.
Travel Rule: Wallet does not belong to your organisation	Scoring	You confirmed that the provided wallet address does not belong to your organisation. The transaction will be rejected. This applies only for inbound transactions.
Travel Rule: Request expired	Scoring	You can specify the time period during which you want to receive the Travel Rule data exchange transaction details from the beneficiary VASP. If the response from the counterparty VASP was not received in the specified time, the transaction will be assigned the Expired tag.
Travel Rule: Customer name mismatch	Scoring	For inbound transactions, this rule checks if the full name of the transaction beneficiary from the originating VASP matches the recipient full name on the beneficiary VASP side. If the names do not match, the transaction will be rejected on the beneficiary VASP side.
Travel Rule: Counterparty customer name mismatch	Scoring	For outbound transactions, this rule checks if the full name of the transaction beneficiary from the originating VASP matches the recipient full name on the beneficiary VASP side. If the names do not match, the transaction will be rejected on the originating VASP side.
Not enough counterparty data	Scoring	The transaction will be rejected due to insufficient data from the counterparty VASP.
Not enough beneficiary information	Scoring	This rule checks whether all fields in the beneficiary information are present in the transaction. If any of these fields are missing, the transaction will be rejected.
Not enough originator information	Scoring	This rule checks whether all fields in the originator information are present in the transaction. If any of these fields are missing, the transaction will be rejected. It is used only for individual applicants.
Verify undiscovered wallets as unhosted	Scoring	This rule puts on hold the transaction if the system could not find any reachable VASP, and then tries to verify the wallet as unhosted. If verified, it will let you proceed with the transaction.