Search

Are you looking for test card numbers?

Would you like to contact support?

Risk-management icon

Configure custom risk rules

Build your own custom rules around the unique fraud risks faced by your business.

In addition to using our standard risk rules, we allow you to create your own custom risk rules. You can use these to refuse a transaction, or to send it for a Manual Review.

To build your own custom risk rules:

  1. Create custom risk fields.
  2. Create custom risk rules.
  3. Assign actions to your rules.

You can also have a look at our example of a custom risk rule.

This functionality requires additional configuration on Adyen's end. To enable it, contact the Support Team.

Step 1: Create custom risk fields

  1. Log in to your Customer Area.
  2. From your company-level account, go to Risk > Custom risk fields.
  3. Select New variable > Custom Field and provide:
    • The name of the field (one word name).
    • The data type of the field: String, Number, Date, or Boolean.
    • A field description.

You can then submit data to the additionaldata.riskdata.<customfieldname> field and create a custom rule around it.

Step 2: Enable risk fields provided by Adyen

In your custom risk rules, you can use the custom risk fields you created, as well as risk fields that we provide for you:

To use such an Adyen-provided risk field, you need to enable it.

  1. Log in to your Customer Area.
  2. From your company-level account, go to Risk > Custom risk fields.
  3. Find the Adyen-provided field you want to use, and enable it by turning on the toggle in the Status column.

Step 3: Create a rule

  1. Log in to your Customer Area, and select a merchant-level account.
  2. Go to RiskRisk profiles.
  3. Under Custom Rules, select + New Rule.
  4. Enter a Rule Name.
  5. For each condition select:
    • Field Name. This is one of the fields you are submitting with the payment (for example, the amount of the transaction).
    • An Operator. This compares the Field Name to the Field Value (for example, GREATER THAN (>)).
    • Field Value. This is the criteria you'll use to trigger your rule (for example, 40000).

      You can enter multiple Field Values in a condition by separating them with a comma.

  6. Add any additional conditions to the rule by selecting AND or OR.
  7. Select Save.

Example

Below is an example of a custom risk rule. It will be triggered when someone attempts to purchase flight tickets that are either:

  • one-way (numberOfLegs | == | 1) 
  • AND to a destination that is Lagos or Abuja (destination_code | IS IN | LOS,ABV).
  • AND business class (class_of_travel | == | Business)

OR

  • one-way (numberOfLegs | == | 1) 
  • AND to a destination that is Lagos, Abuja, or Port Harcourt (destination_code | IS IN | LOS,ABV,PHC).
  • AND with a price above 1,000.00 (amount | > | 100000)
  • AND is in Euros, Pounds, or US Dollars (currency | IS IN | EUR,GBP,USD)

Step 4: Assign an action

Finally, choose what action is taken when your rule is triggered. You can either:

Step 5: Test the custom risk rule

  1. Make a payment request including the fields you turned on in step 2:
{
   "amount":{
      "currency":"USD",
      "value":1000
   },
   "reference":"98739872454D",
   "paymentMethod":{
      "type":"scheme",
      "number":"4111111111111111",
      "expiryMonth":"10",
      "expiryYear":"2020",
      "holderName":"John Smith",
      "cvc":"737"
   },
   "returnUrl":"https://your-company.com/...",
   "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
   "additionalData":{
      "riskdata.deliveryMethod":"express",
      "riskdata.basket.item.productTitle":"Blue Shirt",
      "riskdata.promotions.promotion.promotionName":"Big Sale promotion"
   }
}
  1. Take note of the pspReference in the payment response.
  2. Log in to your Customer Area, and select the merchant-level account you used to make the payment.
  3. In the Search payments, search for the pspReference and select the payment.
  4. Select the number listed under Fraud scoring.
    A page will open with a breakdown of which fraud checks triggered.