Improve payment request data quality

Last updated: August 14, 2024

When you create a payment request, there is a minimum amount of data that you must include for the request to be valid. In the API reference, these are marked as required fields.

However, including certain optional payment and authentication data in your payment requests can help issuers to identify fraudulent transactions and reduce false declines.

If you've integrated with Flow, Hosted Payments Page, or Payment Links, we automatically collect the optimal transaction data to improve the quality of the payment request.

Alternatively, if you've integrated with our API we recommend you always include the following API fields in your payment requests:

customer.email
customer.name
customer.phone
payment_ip, to allow the risk engine to check the customer's IPv4 or IPv6 address
shipping.address, if you're shipping physical goods to the customer
source.account_holder.first_name
source.account_holder.last_name
source.billing_address
source.phone

We also recommend that you integrate our Risk SDK to capture advanced fraud signals that are leveraged in our fraud scoring machine learning model.

Providing additional authentication data can help issuers to identify recent account or password changes, which can be indicators of an increased fraud risk.

If you request authentication for a payment by setting 3ds.enabled to true we recommend you always include the following API fields in your payment requests:

3ds.account_info.account_age
3ds.account_info.account_change
3ds.account_info.password_change

Improve payment request data quality

Payment data

Authentication data