How will I transition to Adyen’s new risk engine?

We have started rolling out upgrades to Adyen’s risk engine. These changes will make RevenueProtect easier to use, reducing the load on operational teams and enabling them to optimize authorization rates while maintaining healthy fraud and chargeback rates. 

We are progressively rolling out the new version to all Adyen merchants throughout 2024. We'll contact you directly or through your account manager when your profile is ready for transition. If you need to know whether you already have the new version, see below for instructions on recognizing it in the Customer Area.

Know when will your risk profile be upgraded to the new version

The transition will occur automatically, and an exact date will be communicated to you beforehand. 

Know whether your risk profile has been transitioned to the new version

We'll have reached out to you before the transition. You can also check if you have the new version in your Customer Area.

Go to Risk > Risk Profiles. Select a risk profile and then select Risk rules. If you see the tabs Allow, Block, and Review (RevenueProtect premium) or Allow and Block (RevenueProtect basic), you have the new version of the risk engine.

What are the main differences between the new version of the risk profile?

Risk rules are now based on outcomes (Allow, Block or Review).

Until now, RevenueProtect has relied on static risk rules to assess the risk of shopper transactions. The new profile is powered by machine learning models that assess the properties of each incoming payment request and give the transactions a risk classification. If the risk is too high based on this classification and your settings, RevenueProtect will block the transaction. For more details, visit our documentation.

Action required during the transition

If you're a RevenueProtect basic user, no actions are required during the transition. If you're a RevenueProtect premium user, you may need to take some actions. 

Custom risk rules

Custom Risk Rules from your previous risk profile have not been automatically copied to your new risk profile. If you used custom risk rules that were important to your risk management strategy and business logic, please ensure that you manually recreate these rules after the transition. We strongly recommend using the new backtest feature to test the rule and see if you still need it.

Manual review rules

Risk rules that were configured to send a transaction to case management will also need to be reconfigured in your new risk profile. In the new version, risk rules use actions and not risk scores. For more details, visit our documentation.

What Backtesting is and how to use it

Backtesting is a new feature available to RevenueProtect premium users. You can use it to test the impact of a risk rule before activating it.

A backtest runs the risk rule against your historical transaction data to identify which payments would have triggered the rule. Since results based on historical data indicate what future performance will look like, this can give you more confidence in the effect that the rule will have before you turn it on. The backtest will help you spot:

• Risk rules that would not perform well and that do not need to be re-created
• Risk rules that are important in catching fraud or that are specific to your business 

Ultimately, backtesting can give you helpful insights into your risk profile performance and reduce the time you spend manually monitoring risk rule performance. For more details, visit our documentation.

Further action required

Aside from the above, there are no additional actions that you need to take. However, if you're a RevenueProtect premium user, feel free to explore all of the new product features, such as adjusting the risk threshold of our machine learning models or fine-tuning your risk profile. You can contact the Adyen Support Team if you still have questions or doubts.