Travel Rule Settings

Create a new Travel Rule Setting.

The arbitrary name you assign to describe the Travel Rule.

The Organization that you selected when creating the Travel Rule.

The Provider that you selected when creating the Travel Rule.

Open

View the selected Travel Rule details.

Delete the selected Travel Rule.

An arbitrary description of the new Setting.

The Organization that implements the Setting.

The Provider that is implemented by the Setting.

The VASP that is implemented by the Setting.

The sender wallet type(s) permitted by the Setting.

The recipient wallet type(s) permitted by the Setting.

Mandatory originator/beneficiary personal data required by the Travel Rule Regulation.

The BATM will abort the transaction after X seconds if no response has been received from the VASP counterparty and the user has a custodial wallet.

Enable to permit the user to declare the wallet type in cases where CAS cannot determine it. This decision will be stored with the Travel Rule transfer for future reference.

The maximum amount permitted for your customer to declare self-ownership.

• Check your local regulations!

The currency type specified by the Maximum Limit Amount.

This configuration only applies to outgoing transfers (BUY transactions).

Unhosted Wallets
When a user self declares an unhosted wallet type, this wallet will be linked to their current identity. By default, only newly generated or unhosted wallets recognized by an extension are associated with an identity.

Custodial Wallets
If a transfer using a custodial wallet is manually approved by the user (when beneficiary VASP hasn't responded in time) , this wallet will be linked to their current identity. The default behavior is that only wallets recognized by an extension, or wallets for which a transfer was approved by a beneficiary VASP, are associated with an identity.

All such associations will be stored with the identity's "Owned Wallets" for future reference.

Important:
Enabling this configuration allows users to reuse wallets for transactions even if the declared wallet type might be incorrect.

This situation can occur if a user incorrectly declares a custodial wallet as unhosted and proceeds with the transaction while remaining within set limits. For custodial wallets, an issue may also arise if the selected beneficiary VASP hosting the custodial wallet is incorrect or has not yet approved the transfer.

In both scenarios, this may result in funds being received by the incorrect beneficiary VASP, who may hold or return the customer's funds until the transfer complies with the Travel Rule.

If allowed, incoming transfers from Travel Rule providers are evaluated based on an internal mechanism on the server (currently based only on first and last name). The server will attempt to automatically evaluate these transfers. If evaluation fails, manual intervention will be required.

If not allowed, incoming transfers are not evaluated automatically, and manual intervention will be required.

Important:
This setting does not affect automatic evaluation by extensions! This always occurs before the internal server evaluation. If the transfer is resolved by an extension, this setting is ignored.