Configure your risk profile<\/div>
Configure a risk profile to fit your business needs. <\/p><\/p><\/a><\/div>\n","url":"https:\/\/docs.adyen.com\/risk-management\/configure-risk-settings","articleFields":{"description":"Use your Customer Area to turn on and configure risk management features.","last_edit_on":"23-12-2019 15:23"},"algolia":{"url":"https:\/\/docs.adyen.com\/risk-management\/configure-risk-settings","title":"Configure risk settings","content":"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.\nRequirements\nBefore you begin, take into account the following requirements and limitations.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an online payments integration.\n\n\nCustomer Area roles\nMake sure that you have one of the following role(s): Merchant change risk settingsRisk admin\n\n\nLimitations\nCase management and risk-based authentication risk settings are only relevant if you enable premium features.\n\n\n\nManage risk settings\nTo view or manage risk settings in your Customer Area:\n\nLog in with your company account.\nGo to Revenue & risk > Settings > Go to risk settings.\n\n\nTo change risk settings for a specific merchant account, switch to that merchant account and select the Override company settings checkbox.\n\nOn the Risk settings page, you can configure risk settings in different categories:\n\nGeneral settings\nCase management settings (premium only)\nAccount data property settings\nRegion configuration (for your live environment only)\n\nGeneral\nSelect which general risk features you want to use. Settings include:\n\nEnable premium features.\nSelect additional payment methods that you have added to your account to be included in the risk evaluation. Only applies to the risk evaluation for risk lists and custom rules. Custom rules require that you enable premium features.\n\nSelecting additional payment methods does not apply to the risk evaluation by the machine learning rules.\n\nConfigure settings for risk-based authentication. Risk-based authentication is enabled by default when you enable premium features.\nEnable risk for in-person payments. This could apply if you expect to process Mail Order\/Telephone Order (MOTO) or Manual Key Entry (MKE) transactions.\nDisable risk management. This turns off Protect for your company. By default, risk management is turned on.\n\nCase management\nConfigure case management settings. With case management, you can add an extra layer of fraud protection by manually reviewing transactions before they are captured. Settings include:\n\nSet up what you want to do after a case is accepted, rejected or expires.\nSet up a capture delay for payments that have gone into case management.\n\nAccount\nConfigure risk settings for your account that influence risk checks such as block and trust lists. Settings include:\n\nSettings for recurring transactions, for example:\n\nExclude recurring transactions from the risk evaluation.\n\nSettings for risk lists, for example:\n\nStop using the Adyen global referral block list.\nMaintain risk lists per merchant account.\n\n\nRegion configuration\nThis setting only applies to your live environment.\nBy default, payments and risk checks are processed through our EU data center.\nTo 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.\nThe 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 center.\n\nStoring data in other regions can have legal, privacy, or regulatory implications. Configuring the endpoints and risk region serves as a specific instruction to Adyen to change your existing setup. Discuss with your legal team before changing your settings.\n\nMigration steps\nIf 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:\n\nIn 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.\nAfter data is replicated and stored for at least 60 days in the region you selected, change the configuration from Storing data to Active. EU (the default setting) and the region you selected now both have the Active status.\nStart submitting payment requests using the location-based endpoint for your selected region.\n\n\nChanges to region settings will not be applied immediately. Our Support Team will review the setting. You will receive email notifications about the support ticket.\n\nNext steps\n\nCreate a risk profileSet up at least one risk profile, and assign it to one, several, or all merchant accounts. Configure your risk profileConfigure a risk profile to fit your business needs. \n","type":"page","locale":"en","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Risk management","lvl2":"Configure risk settings"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/risk-management","lvl2":"\/risk-management\/configure-risk-settings"},"levels":3,"category":"Risk Management","category_color":"green","tags":["Configure","settings"]}}