Under Transaction Monitoring→ Settings, you can configure the following:

General — lets you adjust basic Transaction Monitoring settings, as described in this section.
Tags — lets you create and manage tags that can be used for dynamic risk scoring and other purposes, as described in this section.
AML Screening — lets you select the provider for AML watchlist checks and customize the search configuration for screening, as described in this section.

If your organization has the Travel Rule service enabled, you will also see two additional menu items:

Travel Rule — lets you configure your Travel Rule workflows to meet global and local regulatory requirements. For example, you can set confirmation timeouts for outgoing Travel Rule messages or specify which data will be shared with counterparty VASPs. For incoming transactions, you can configure wallet ownership verification and define how data comparison should be performed. The detailed guidance on configuring Travel Rule is provided in this article.
Integration Wizard — lets you streamline your onboarding to Sumsub’s Travel Rule solution. You can complete a guided questionnaire to share your organization’s needs, and we will generate a tailored step-by-step integration guide with relevant documentation links. The Integration Wizard is described in this article.

General transactions and Travel Rule settings

In the General settings you can configure the following:

Setting	Configuration
Default currency	Select the default currency for transaction monitoring from the drop-down list. Any transaction amount will be converted to this currency if the `amountInDefaultCurrency` field is not filled during transaction creation.
Activate mirrored transactions for finance transactions	This functionality is only available if your transaction counterparties are Sumsub applicants. Tick this checkbox if you want to automatically create transactions for both the remitter and the beneficiary with just one API call.
Send a notification via email when a level/action is triggered by Transaction Monitoring rules	In addition to the webhook notification, we can send the applicant an email with a link to the SDK each time the level change is triggered by matched rules.

Transactions and Travel Rule Tags settings

In the Tags settings, you can manage predefined tags and create new ones.

To edit a predefined tag:

In the Transactions and Travel Rule Settings, navigate to Tags.
Click on the pencil icon next to the tag.
Change the tag bar color or weight. Enable (or disable) the Score applicant checkbox. To learn more about setting up tags, refer to this article.
Save your changes.

To create a new tag:

In the Transactions and Travel Rule Settings, navigate to Tags.
Enter the tag name, choose the bar color, select the Score applicant checkbox if you want to use the tag for scoring applicants as part of ongoing risk assessment, and set its weight in %.
Save your changes.

To configure transaction counterparty AML screening:

In the Transactions and Travel Rule Settings, navigate to AML Screening.
Select a provider that you want to use for AML screening. If the provider is locked, enter your credentials, as described in Comply Advantage and World-Check One.
Select a search configuration. You can search by the warning types or by providing a search profile identifier:
- When searching by the warning types, specify the categories of PEPs for which you want to screen your applicants and add the associated types of adverse media.
- When searching by custom search profiles, enter a profile identifier. To search for profiles from your Comply Advantage key, make sure to provide the key, as described in this article.
Configure name-matching criteria and desired fuzzy-matching levels:
- Strict matching — to flag applicants only upon an exact match.
- Default matching — to allow for variations in spelling.
- Fuzzy matching — to allow for variations in the range of names.
Set the expiration period for AML cases in days. A new case will be created automatically if, at the time of transaction creation, the latest case is older than the selected number of days.
Save your changes.