Search docs

Are you looking for test card numbers?

Would you like to contact support?

Start searching Adyen's documentation...


Custom risk rules

In addition to our pre-configured checks, you can build your own custom rules around the unique fraud risks faced by your business.

These allow you to define which attributes and behaviours will result in a payment being either refused, or set aside for a Manual Review.

Here we describe the steps required for building your own custom risk rules:

  1. Enabling custom risk fields.
  2. Creating custom risk rules.
  3. Assigning actions to your rules.

You can also check out an example of a custom risk rule.

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

Step 1: Enable custom risk fields

First, you'll need to enable the fields you'll use in your custom risk rules. 

  1. Log in to your Customer Area.
  2. From your company-level account, navigate to Risk > Custom risk fields.
  3. Turn on Show inactive to view all the risk fields you can use.
  4. Toggle on the fields that you'll use in your custom risk rules. You can include paymentsrisk databasketpromotional, or airlinefields that you're sending with each payment.

Step 2: Create a rule

Next you'll want to create a custom risk rule. Each rule needs at least one condition, containing:

  • 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 also build more customized rules by joining multiple conditions together, using AND and OR.

To create a custom risk rule:

  1. Go to your Customer Area, and select a merchant-level account.
  2. Navigate to Risk > Risk profiles.
  3. Under Custom Rules, click + New Custom Risk Rule.
  4. Enter a Rule Name.
  5. For each condition select a Field Name and Operator, and enter a Field Value.

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

  6. Add any additional conditions to the rule by clicking AND or OR.
  7. Click Save.

Step 3: Assign an action

Finally, you'll want to choose what action is taken when your rule is triggered. You can either refuse the transaction, or send it to Case Management for a manual review.

Refuse the transaction

To refuse the transaction, you'll need to assign a fraud score to your rule. Enter a value under Score. When your rule is triggered, this is how much the fraud score will increase for the transaction. The transaction will be refused if the overall fraud score is 100 or higher. For more information on fraud scores, see How does the fraud score work?

Send transaction to manual review

To forward the transaction for manual review, turn on Override. For more information on how to manually review transactions, see Case Management - Manual Review.


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)


  • 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)