Improve payment request data quality
Last updated: December 11, 2024
When you create a payment request, you must include all required API fields for the request to be valid.
However, including certain optional payment and authentication fields can help better identify fraudulent transactions and reduce false declines.
Providing additional authentication data helps identify recent account or password changes, which may indicate increased fraud risk.
If your payment request has 3ds.enabled
set to true
, we recommend that you always also include the following fields:
3ds.account_info.account_age
3ds.account_info.account_change
3ds.account_info.account_password_change
Providing additional customer data for cardholder-initiated transactions (CITs) may improve your acceptance rate. It also helps issuer and Checkout.com fraud prevention systems verify the transaction's legitimacy, and reduces the likelihood of false declines.
Information
We recommend integrating with our Risk SDK for CITs. The SDK captures device data that helps identify potentially fraudulent transactions.
If your payment request has source.type
set to one of the following:
ach
card
customer
id
network_token
token
Then we recommend also including the following fields:
source.billing_address
source.account_holder.first_name
source.account_holder.last_name
customer.name
customer.email
payment_ip
– ifpayment_type
is not set toMOTO
shipping.address
– if you're shipping goods
Providing additional customer data for Mail Order/Telephone Order (MOTO) transactions helps issuer and Checkout.com fraud prevention systems verify the transaction's legitimacy. This can reduce the likelihood of false declines.
If your MOTO payment request has source.type
set to one of the following:
ach
card
customer
id
network_token
token
Then we recommend also including the following fields:
customer.phone
shipping.address