{"title":"Data quality and risk field reference","category":"default","creationDate":1779620071,"content":"

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<\/code> and reference<\/code>. Other fields such as shopperIP<\/code>, shopperReference<\/code> and shopperEmail<\/code> are not always required, but strongly recommended to include.<\/p>\n

To get the most benefit out of Protect, we recommend that you collect and then send in as many fields as possible in your payment request.<\/p>\n

Data quality<\/h2>\n

Machine learning predicts the likelihood of a transaction being fraudulent based on the data in the payment request, historical shopper data, and interaction patterns with the payment form.<\/p>\n

For both the rules Machine learning: fraud risk<\/strong> and Machine learning: bot attack risk<\/strong>, it is important to provide high quality data to reach the most correct risk classification. Similarly, when you use risk lists or custom rules, the payment request has to contain the data to trigger the correct action.<\/p>\n

You can influence the quality of the data. We recommend that you always send in as many fields as possible, and avoid sending in dummy or placeholder data.<\/p>\n

If you use a Web Drop-in\/Components integration, we collect additional risk data<\/a> that you send when the shopper pays, with the option for more data collection outside of the checkout page<\/a>. If you have built a Web API-only integration, you can also collect this data<\/a> and then send it in your payment request.<\/p>\n

The following table shows some example fields that are highly relevant for the risk evaluation.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Data point<\/th>\nUsed by<\/th>\nRequired field in payment request<\/th>\n<\/tr>\n<\/thead>\n
Billing address<\/td>\nbillingAddress<\/code><\/td>\n<\/tr>\n
Delivery address<\/td>\ndeliveryAddress<\/code><\/td>\n<\/tr>\n
Email address<\/td>\nshopperEmail<\/code><\/td>\n<\/tr>\n
IP address<\/td>\nshopperIP<\/code><\/td>\n<\/tr>\n
The shopper\u2019s first and last name<\/td>\nshopperName<\/code><\/td>\n<\/tr>\n
Your reference to uniquely identify the shopper<\/td>\nshopperReference<\/code><\/td>\n<\/tr>\n
The shopper\u2019s phone number<\/td>\ntelephoneNumber<\/code><\/td>\n<\/tr>\n
Card number<\/td>\npaymentMethod.number<\/code>
paymentMethod.encryptedCardNumber<\/code><\/td>\n<\/tr>\n
The account creation date<\/td>\naccountInfo.accountCreationDate<\/code><\/td>\n<\/tr>\n
Browser information<\/td>\nbrowserInfo<\/code><\/td>\n<\/tr>\n
The date and time that the item will be delivered<\/td>\nCheckout API v69 or earlier:
  • deliveryDate<\/code><\/li><\/ul> Checkout API v70 or later:
    • deliverAt<\/code><\/li><\/ul><\/td>\n<\/tr>\n
Risk data<\/a> for Web API-only and additional risk data for Web Drop-in\/Components<\/td>\nriskData<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

See also<\/h2>\n