This article is for Adyen's legacy risk engine. Are you using Adyen's latest risk engine? Refer to this page.

How do I manage Velocity rules?

Q: How do I manage Velocity rules?

<html><head></head><body>Velocity checks trigger based on the number of transactions a shopper has attempted in a given time. There are Velocity rules for card numbers, email address, IP address and shipping address. In general, it is not recommended to assign a very high scoring to Velocity rules as the risk of blocking genuine shoppers is higher. The counter of Velocity rules included payments despite their transaction outcome. For example, for the number of card number usage all transaction attempts are included. The only expectation is the ‘Mastercard or Visa card number usage’ rule, to avoid limiting the impact on card testing activity, it is recommended to assign a score of 100 to this rule.</body></html>

Green warning sign with exclamation mark.

Do you have the right user role?

Please check whether you have one of the following user roles:

Merchant Change Risk Settings
Risk Admin

If you don't have the required user role, please reach out to your admin.

Velocity checks trigger based on the number of transactions a shopper has attempted in a given time. There are Velocity rules for card numbers, email address, IP address and shipping address.

In general, it is not recommended to assign a very high scoring to Velocity rules as the risk of blocking genuine shoppers is higher. The counter of Velocity rules included payments despite their transaction outcome. For example, for the number of card number usage all transaction attempts are included.

The only expectation is the ‘Mastercard or Visa card number usage’ rule, to avoid limiting the impact on card testing activity, it is recommended to assign a score of 100 to this rule.