Search

Are you looking for test card numbers?

Would you like to contact support?

Risk-management icon

Velocity rules

Velocity checks trigger based on the number of transactions a shopper has attempted in a given time. The average number of transactions from a good shopper varies depending on your business, so configure these checks to the behavior of your shoppers.

If a shopper abandons the transaction after redirecting to a payment method or 3D Secure, this counts as an attempt. These abandoned attempts are not listed in your payments.

Velocity Rules trigger on your merchant-level account, and the number of times the rule is triggered is not aggregated across the company-level account.

Contact the Adyen Support Team to enable this risk rule for recurring payments.

Card/bank account holder name used more than x times within a time period

Triggers when the number of transactions associated with the same cardholder name exceeds a given number of transactions in a given time period.

Fraudsters often use the same cardholder name when testing cards, so as to more easily automated their process. This check is aimed at detecting when the same name is being used across a set number of transactions. 

Card/Bank account number already used by another shopper

Triggers when a the payment method for the transaction has already been used with a different Shopper Reference.

Fraudsters create multiple accounts, and attempt to use the same compromised account with different techniques and attack vectors. This check is aimed at identifying when a payment method is being used across multiple accounts.

Enable this setting across all your merchant-level accounts to provide the most reliable results.

Card/Bank account number used more than x times within a time period

Triggers when the number of transactions associated with the same card or bank account number exceeds a given number of transactions in a given time period.

 

Card number chunk used more than x times within a time period

Triggers when the number of transactions associated with the first 12 digits of a card (a chunk) exceeds a given number of transactions in a given time period.

This allows you to run a velocity check across a range of BINs.

Different cards/bank accounts used by the same shopper

Triggers when the same payment details have been used by the same shopper in the last 48 hours. Provide a shopperReference (a unique user ID) with a payment. You can then use this check to determine if that shopperReference has used different cards or bank accounts.

This can help detect account takeovers, which tend to come from registered accounts with otherwise good history.

Shopper email used more than x times within a time period

Triggers when the number of transactions associated with an email address exceeds a given number of transactions in a given time period.

Fraudsters use the same email for clusters of transactions because creating new emails is time intensive. This check allows you to set velocity limits on any email address.

Shopper IP used more than x times within a time period

Triggers when the number of transactions associated with an IP address exceeds a given number of transactions in a given time period.

Fraudsters often use the same IP address for consecutive fraudulent transactions. This could be while they are attempting different card details, or techniques. This check allows you to set velocity limits on any particular IP address.

Shopper initiated a transaction more than X times within a time period

Triggers when the number of transactions initiated by a shopper exceeds a given number of transactions in a given time period. The default setting 5 times over 90 minutes. Unlike other velocity checks, which are based on a single matching attribute, you can base this check on:

  1. Device Fingerprint: A technique used to identify shoppers by making a fingerprint of their device/browser. In most cases, the fingerprint is unique for each device or browser. Contact Support Team to ask about using device fingerprinting with your account.
  2. Persistent Cookie: A unique identifier stored in different places on the shopper's device and across browsers. To turn on persistent cookie tracking for your account contact Support Team.
  3. Shopper IP
  4. Shopper Email Address

Shopper delivery address used more than x times within a time period

Triggers when the number of transactions associated with a shopper delivery address exceeds a given number of transactions in a given time period.

Fraudsters often use the same shipping address to receive stolen goods. You can set velocity limits on any shipping address to prevent fraudsters from using it.