Configure risk settings

Risk settings define how you want to handle risk for your company. By default, you configure risk settings on your company account, and the risk settings apply to all merchant accounts in your company.

To view or manage your risk settings:

1. Log in to your Customer Area with your company account.
2. Go to Revenue & risk > Settings.

On the Risk settings page, you can configure risk settings in different categories:

• General settings
• Case management settings
• Account data property settings
• Region configuration (for your live environment only)

General

Select which general RevenueProtect features you want to use. Settings include:

• Select additional payment methods that you have added to your account to be included in the risk evaluation. This only applies to the risk evaluation of transactions that trigger manual risk rules.
  If you are using the latest version of the risk profile, selecting additional payment methods does not apply to the risk evaluation by the machine learning rules.
• Turn on RevenueProtect premium features.
• Turn on RevenueProtect for in-person payments. This could apply if you expect to process Mail Order/Telephone Order (MOTO) or Manual Key Entry (MKE) (MKE) transactions.

Case management

Configure case management settings. Settings include:

• Set up what you want to do after a case is accepted, rejected or expires.
• Set up a capture delay for payments that have gone into case management.

Account

Configure risk settings for your account that influence risk checks such as block and trust lists. Settings include:

• Settings for recurring transactions, for example:
  • Exclude recurring transactions from the risk evaluation.
• Settings for block and trust lists, for example:
  • Stop using the Adyen global referral list.
  • Maintain referrals per merchant account.

Region configuration

This setting only applies to your live environment.

By default, payments and risk checks are processed through our EU data center.
To reduce latency while running ShopperDNA risk checks, we recommend that you configure risk to run in the same data region as where you process payments. If this has not been done while you onboarded, you can specify the region in this risk setting, and prepare the migration.

The default configuration can introduce latency for transactions outside of the EU. You can choose to use location-based endpoints to process payments through any other data centers.

Migration steps

If you want to use a location-based endpoint for your payments, we recommend that you prepare ShopperDNA data in the same region before migrating your payment requests:

1. In the Region Configuration section, select a region and set the configuration to Storing data. The Storing data setting means you want to replicate data from the EU region and store the replicated data in the region you selected. We recommend that you keep the Storing data setting for 60 days. You can configure this on your company or merchant account based on your setup. For example, if your merchant accounts are separated by region, configure the data replication on the relevant merchant accounts.
2. After data is replicated and stored for at least 60 days in the region you selected, change the configuration from Storing data to Active. EU (default setting) and the region you selected will both be in Active status.
3. Start submitting payment requests using the location-based endpoint for your selected region.