Required risk field reference

Learn which fields to include in your payments request to trigger risk checks

You include a variety of fields when you send in a payment request. Some of these fields are mandatory to make a payment, for example amount and reference. Other fields are not always required, think of shopperIP and shopperEmail.

To get the most benefit out of your risk configuration, we recommend that you collect and then send in as many fields as possible in your payment request. Doing this ensures that you trigger the risk checks, as these checks depend on specific fields being present in the request.

Extra fields for standard risk checks

The following is a list of API fields that are required for some of our standard risk checks:

Field	Required for	Checkout API /payments	Classic integration /authorise
`billingAddress`	Billing address differs from delivery address Billing address does not match cardholder address (AVS) Shopper address referral list German SCHUFA check Brazil CPF check	`billingAddress`	`billingAddress`
`deliveryAddress`	Billing address differs from delivery address Shopper address referral list Multiple distinct delivery addresses used by shopper Shopper initiated a transaction more than X times within a time period Custom rules Custom lists	`deliveryAddress`	`deliveryAddress`
`shopperEmail`	PayPal auth-result email Multiple distinct email addresses used by Shopper Email address and shopper name comparison Email is likely to be fake or automatically generated Shopper initiated a transaction more than X times within a time period Email domain referral check Shopper email referral check Multiple distinct email addresses used by shopper Shopper email used more than x times within a time period Custom rules Custom lists	`shopperEmail`	`shopperEmail`
`shopperIP`	Shopper IP originates from high-risk country Shopper country differs from issuing country Shopper IP referral check Shopper initiated a transaction more than x times within a time period Multiple distinct IP addresses used by shopper Shopper IP used more than x times within a time period Shopper used shared IP address Custom rules Custom lists	`shopperIP`	`shopperIP`
`shopperName`	Email address and shopper name comparison Shopper name referral check German SCHUFA check Custom rules Custom lists	`shopperName`	`shopperName`
`shopperReference`	Card/Bank account number already used by another shopper Different cards/bank accounts used by the same shopper Shopper reference referral check Multiple distinct references used by shopper Custom lists	`shopperReference`	`shopperReference`
`telephoneNumber`	Brazil CPF check Telephone number referral list Custom rules Custom lists	`telephoneNumber`	`telephoneNumber`

Extra fields for specific cases

The following table shows a number of API fields that you can use for specific risk checks or your own, custom risk setup.

Field	Required for	Checkout API /payments	Classic integration /authorise
`accountInfo.accountCreationDate`	Required if you want to use the creation date option for the shopper account age check. Although the `accountInfo` object is used for 3D Secure transactions, you can also use this object to include the `accountCreationDate` in your payment request. Shopper account age Custom rules	`accountCreationDate`	`accountCreationDate`
`browserInfo`	Required for 3D Secure transactions, but you can also use this field in your custom risk rules or custom lists. Custom rules Custom lists	`browserInfo`	`browserInfo`
`deliveryDate`	Required if you want to use the time to delivery check, or if you want to use the field `hoursToDelivery` in a custom risk rule. Time to delivery Custom rules	`deliveryDate`	`deliveryDate`

Are you looking for test card numbers?

Would you like to contact support?

Required risk field reference

Extra fields for standard risk checks

Extra fields for specific cases