Risk fields

Adyen's API for payment requests contains several optional fields that can be provided by the merchants. Some of these fields are quite important when the merchant uses several risk checks in the Risk System. We recommend the use of the following fields in order to use to its fullest the capabilities of Adyen's Risk system.

Field
Required
Description
billingAddress (error)

The address where the shopper is going to receive the bill. Providing the following detailed information street, houseNumberOrName, city, postalCode, stateOrProvince, country.

Used in the following risk checks:

browserInfo (error) With the browser info data, we can determine if the device is mobile or not, which is used for device fingerprinting and other device logic.
deliveryAddress (error)

The address where the shopper is going to receive goods/services. Providing the following detailed information street, houseNumberOrName, city, postalCode, stateOrProvince, country.

Used in the following risk checks:

deliveryAddressType (tick)

Specifies whether the shopper is allowed to view and/or modify delivery address fields.

It can have the following values:

  • 1: the delivery address fields are visible but unmodifiable.
  • 2: the delivery address fields are not visible, thus fields will be unmodifiable.
  • Not supplied: the delivery address fields are visible and modifiable.

If the field is supplied, the deliveryAddressType field is is part of the merchant signature.

deliveryDate (error)

The expected date of delivery or fulfillment of the goods/services to the shopper.

Used in the following risk checks:

dfValue (error)

Information from the shopper's device and uses the combined value to identify the device of the shopper.

Used in the following risk checks:

merchantOrderReference (error) A reference that merchants can use to link multiple transactions to each other.
merchantReference (tick)

A reference to uniquely identify the payment. This reference is used in all communication with you about the payment status. We recommend using a unique value per payment; however, it is not a requirement.

If you need to provide multiple references for a transaction, you can enter them in this field. Separate each reference value with a hyphen character ("-").

This field has a length restriction: you can enter max. 80 characters.

offset (error)

An integer value that adds up to the normal fraud score.

The value can be either a positive or negative integer.

riskdata.deliveryMethod (error)

The method to deliver the goods to the shopper.

Used in Delivery Method Check.

riskdata.externalRiskScore (error)

Used only before authorisation and when external risk provider is used by merchant.

Used in External Risk Score Check.

riskdata.shopperAccountCreationDate (error)

This specifies the date when the shopper's account was created.

Format: yyyy-MM-dd HH:mm:ss.sssZ

Used in Shopper Account Age check.

shopper (error)

Shopper personal information that includes shopper name, date of birth, and so on (only in countries where it is legal to collect). For more information, refer to Shopper information fields.

Used in the following risk checks:

shopperEmail

(error)

The shopper's email address.

We recommend providing this information, as it is used in velocity fraud checks.

Depending on your integration this field may be mandatory for you, check with the Support Team.

It is not advisable to use a hard-coded email address.

Used in the following risk checks:

shopperReference (error)

A unique identifier for the shopper, for example, a customer ID.

We recommend providing this information, as it is used in velocity fraud checks. It is also the key in recurring payments.

This field is mandatory in recurring payments.

Used in the following risk checks: