--- title: "Data quality and risk field reference" description: "Learn which fields to include in your payment request to improve the risk evaluation, and trigger risk rules." url: "https://docs.adyen.com/risk-management/configure-your-risk-profile/risk-field-reference" source_url: "https://docs.adyen.com/risk-management/configure-your-risk-profile/risk-field-reference.md" canonical: "https://docs.adyen.com/risk-management/configure-your-risk-profile/risk-field-reference" last_modified: "2019-09-06T14:25:00+02:00" language: "en" --- # Data quality and risk field reference Learn which fields to include in your payment request to improve the risk evaluation, and trigger risk rules. [View source](/risk-management/configure-your-risk-profile/risk-field-reference.md) 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 such as `shopperIP`, `shopperReference` and `shopperEmail` are not always required, but strongly recommended to include. 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. ## Data quality 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. For both the rules **Machine learning: fraud risk** and **Machine learning: bot attack risk**, 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. 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. If you use a Web Drop-in/Components integration, we [collect additional risk data](/risk-management/fraud-data-collection) that you send when the shopper pays, with the option for more data collection [outside of the checkout page](/risk-management/fraud-data-collection/#collect-additional-data). If you have built a Web API-only integration, you can also [collect this data](/risk-management/fraud-data-collection/#data-collection-add-sdk) and then send it in your payment request. The following table shows some example fields that are highly relevant for the risk evaluation. | Data point | Used by | Required field in payment request | | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | | Billing address | * Default **Shopper address** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) * [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules | `billingAddress` | | Delivery address | - Default **Shopper address** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) - [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules - [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) and custom lists | `deliveryAddress` | | Email address | * Default **Shopper email** and **Email domain** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) * [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules * [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) and custom lists | `shopperEmail` | | IP address | - Default **Shopper IP address** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) - [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules - [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) and custom lists | `shopperIP` | | The shopper’s first and last name | * Default **Shopper name** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) * [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) and custom lists * [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules | `shopperName` | | Your reference to uniquely identify the shopper | - Default **Shopper reference** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) - Custom lists | `shopperReference` | | The shopper’s phone number | * Default **Phone number** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) * [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) and custom lists * [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules | `telephoneNumber` | | Card number | - Default **Bank identification number (BIN)** [risk lists](/risk-management/configure-your-risk-profile/risk-lists) - Default **Fraudulent card number or bank account number (IBAN)** [block risk list](/risk-management/configure-your-risk-profile/risk-lists) - Default **Non-fraudulent card number or bank account number (IBAN)** [block risk list](/risk-management/configure-your-risk-profile/risk-lists) - Default **Card number or bank account number (IBAN)** [trust risk list](/risk-management/configure-your-risk-profile/risk-lists) - [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules | `paymentMethod.number` `paymentMethod.encryptedCardNumber` | | The account creation date | * [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) | `accountInfo.accountCreationDate` | | Browser information | - [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) and custom lists - [Data collection](/risk-management/fraud-data-collection/): device information - [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules | `browserInfo` | | The date and time that the item will be delivered | * [Custom rules](/risk-management/configure-your-risk-profile/custom-rules): include if you want to use the `hoursToDelivery` field. | Checkout API v69 or earlier:* `deliveryDate`Checkout API v70 or later:* `deliverAt` | | [Risk data](/risk-management/fraud-data-collection/) for Web API-only and additional risk data for Web Drop-in/Components | - [Machine learning](/risk-management/configure-your-risk-profile/machine-learning-rules) rules | `riskData` | ## See also * [Risk lists](/risk-management/configure-your-risk-profile/risk-lists) * [Custom rules](/risk-management/configure-your-risk-profile/custom-rules) * [Machine learning rules](/risk-management/configure-your-risk-profile/machine-learning-rules) * [Post-authorization rules](/risk-management/configure-your-risk-profile/post-auth-rules) * [Data collection to detect fraud](/risk-management/fraud-data-collection/) * [Adyen Uplift requirements and recommendations](/uplift/uplift-requirements)