Home>
Merchant Communications
>
How to optimise your authentication service
Checkout.com understands the importance of increasing approval rates and reducing abandoned transactions for your business. By fully utilising our Authentication integrated flow and passing us the most impactful data, we can help you maximise your performance and provide a better experience for your customers.
We now support all optional fields on our Authentication integrated flow, as well as the required and conditional fields. Working with Visa we’ve been able to identify that merchants who utilise priority fields see an uplift in authentication and approval rates and more frictionless user experiences.
What should you do?
To make sure you are taking full advantage of the benefits our Authentication integrated flow offers:
- Review the data you are passing us in your authentication requests
- Review the priority data fields that have been identified
- If you aren’t passing us those priority data fields yet, fill the gaps. You have an opportunity to see a significant improvement in your authentication and approval rates by passing us this extra data.
What are priority data fields?
The introduction of EMV 3D Secure 2 supplied over ten times more data than 3DS1. 3DS2 is not just about being compliant with regulations, but about reducing your fraud level, maximising your performance, and enabling the best possible user experience for your cardholders when they’re shopping with you.
Merchants that supplied more than 50% of the priority data fields saw:
- Increased transaction approval rates of 6%*
- An increase of 57% in frictionless user experiences*
- Reduced false declines
- Reduced costs of chargebacks and lost business
This demonstrates how more data enables better decisions and in turn increased approval rates, and a recent Visa publication showed that certain fields drive better performance than others. These are called priority fields.
At Checkout.com our Authentication integrated flow supports all mandatory, conditional and optional data fields. We highly recommend providing the priority fields so you can utilise the product fully, helping you to achieve the best possible performance for each transaction and maximise your approval rate.
The priority fields are as follows:
|
Conditional priority field
|
Example input
|
|
payment_ip
|
"1.12.123.255"
|
|
billing_address
|
|
|
source.billing_address.addressline1
|
"Checkout.com"
|
|
source.billing_address.city
|
"London"
|
|
source.billing_address.state
|
"LON"
|
|
source.billing_address.zip
|
"W1T 4TJ"
|
|
source.billing_address.country
|
"GB"
|
|
customer.email
|
"[email protected]"
|
|
customer.name
|
bruce_wayne
|
|
source.phone.number
|
“0204567895”
|
|
shipping_address
|
|
|
shipping.address.address_line1
|
"Checkout.com"
|
|
shipping.address.city
|
"London"
|
|
shipping.address.state
|
"LON"
|
|
shipping.address.zip
|
"W1T 4TJ"
|
|
shipping.address.country
|
"GB"
|
|
Optional priority field
|
Example input
|
|
3ds.account_change_indicator
|
"less_than_thirty_days"
|
|
3ds.account_change
|
"2019-08-24T14:15:22Z"
|
|
3ds.account_date
|
"2019-08-24T14:15:22Z"
|
|
3ds.account_password_change
|
"2019-08-24T14:15:22Z"
|
|
3ds.account_password_change_indicator
|
"no_change"
|
|
3ds.purchase_count
|
“1”
|
|
3ds.add_card_attempts
|
“less_than_thirty_days”
|
|
3ds.transactions_today
|
“10”
|
|
3ds.transactions_per_year
|
“2”
|
|
3ds.account_age
|
"no_account"
|
|
3ds.shipping_address_usage
|
“less_than_thirty_days”
|
|
3ds.shipping_address_age
|
“less_than_thirty_days”
|
|
3ds.account_name_matches_shipping_name
|
“true”
|
