Optimize payment request data
Last updated: August 20, 2025
For optimal performance, the Fraud Detection solution relies on quality payment request data for risk rules and Checkout.com's machine learning models. The more data you provide, the greater the confidence in the data quality and the effectiveness and efficiency at preventing fraud.
We recommend the following:
- Always provide as much data for your payment requests as possible.
- Integrate the Risk.js package, and the Risk Android SDK or Risk iOS SDK for every customer-initiated payment flow.
The data confidence for each type of integration is as follows:
| Integration | Data confidence |
|---|---|
High | |
High | |
High | |
API with:
| High |
API with:
| High |
API with:
| Medium |
API with full card details in the | Low |
We recommend providing the following data points for optimal performance:
| Data point | Contribution to performance | How to provide data |
|---|---|---|
Billing address country | Required | Gateway |
Billing address street | Optional | Gateway |
Billing address ZIP code or post code | Optional but highly recommended | Gateway |
Customer email | Required | Gateway |
Customer IP address | Required | Gateway and Risk.js package |
Customer name | Optional but highly recommended | Gateway |
Customer phone | Optional but highly recommended | Gateway |
Device and browser data | Required | Risk.js package |
Shipping address country, ZIP code or post code | Optional but highly recommended | Gateway |
Shipping address street | Optional | Gateway |
If you collect device data through a third-party provider, you can share this data with Checkout.com using the API. Device data strengthens the risk assessment and enriches your analytics in the Dashboard.
When you call the Request a payment endpoint, provide the device data in the risk.device object.
You can use the following device-signal properties in your custom rules. Provide the required data using the API as follows:
| Property | Description | Required data |
|---|---|---|
| The unique device fingerprint. | Provide the device fingerprint in the |
| The device's IP address. If | Provide the device IP address in one of the following fields:
|
| The city associated with the geolocation IP address.
Example – | |
| The ISO-2 country code associated with the device's IP address.
Example – | |
| For web flows, the browser used on the device.
| Provide the device user agent in the |
| For web flows, indicates whether the device browser is in incognito mode. | |
| The device model.
| |
| The device’s operating system (OS).
| |
| The version of the device’s operating system. | |
| The timezone of device's IP address.
|
In your payment request, you can provide custom string, number, or boolean fields in the metadata object. For example:
You can reference metadata to create advanced rules for your risk strategies. For example, if you want to use your own fraud score or account age rule.