Frictionless Payments

How can frictionless payments help you and your clients?


As more and more of us use the internet to make regular transactions, the rate of financial fraud has also increased. To tackle issues more and more of fraud, the European Union has implemented a number of measures, mostly around security. With the event of 3D Secure v2, all payments must now go through risk assessments by banks and schemes.

Risk-based assessments are based on the following elements:

  • Client information

  • Transaction value (usually large amounts are subject to challenge)

  • Transaction history

  • Device information

  • Behavioral history

In essence, frictionless payments aim to reduce the complexity and stress of the entire transaction process for you and your client. We encourage you to optimize frictionless payments with your clients by populating as much information.

You will find these additional input fields in the following methods:

SOAP API v1

REST API v2

Input Reference Help:

These fields are considered to have high importance for scoring, they recommend that they be populated in the information is available. The most important fields are ranked from R1 (being the most important) to R4.

ObjectFieldDescriptionsPriority
billingAddressbillingAddress.cityBilling addressR2
billingAddress.country
billingAddress.addressAdditional1
billingAddress.addressAdditional2
billingAddress.addressAdditional3
billingAddress.zipcode
billingAddress.state
holderContactholderContact.lastNameHolder contact informationR1
holderContact.emailR1
holderContact.phoneR3
holderContact.mobileR3
holderContact.workPhoneR3
deliveryAddressdeliveryAddress.cityDelivery address informationR1
deliveryAddress.country
delivery
Address.addressAdditional1
deliveryAddress.addressAdditional2
deliveryAddress.addressAdditional3
deliveryAddress.zipcode
(postal code)
deliveryAddress.state
deliveryAdditionalInfodeliveryAdditionalInfo.Contact.emailDelivery contact emailR2
deliveryAdditionalInfo.DeliveryBillingMatchDescribes delivery and billing addresses are the same.R4
Values: booleanIndicator
deliveryAdditionalInfo.deliveryAddressCreationDateCreation date of delievery addressR4
deliveryAdditionalInfo.estimatedDeliveryDelayEstimated delivery dateR4
deliveryAdditionalInfo.deliveryModeDelivery Method for example: Postal Office or Amazon boxR4
authenticationAuthentication.merchantCustomerAuthentMethodAuthentication method used to authenticate the buyer before making the payment.R4
Values: merchantCustomerAuthentMethod
Authentication.merchantCustomerAuthentDateTimeDate and time of the cardholder authenticationR4
Date/Time in UTC
customerAccountInfocustomerAccountInfo.customerAccountIdAdditional information about the account optionally provided by the 3-D Secure Requestor.R4
customerAccountInfo.numberOfPurchase180DaysThe amount of customer transactions made over the last six months (last 180 days)R4
customerAccountInfo.numberOfTransactionYearNumber of accepted or abandoned transactions in the last year on the merchant's customer account.R4
customerAccountInfo.customerAccountCreationDateWhen the customer account was originally created.R4
customerAccountInfo.numberOfAttemptsAddCard24HoursNumber of distinct cards used by the merchant's account in the last 24 hours.R4
customerAccountInfo.suspiciousActivityIndicatorNotes if a suspicious activity is detected on customer account in the merchant's website.R4
customerAccountInfo.numberOfTransaction24HoursHow many transactions did the customer make in the last 24hoursR4
customerAccountInfo.customerAccountChangeDateLast date the customer account was changedR4
customerAccountInfo.passwordChangeDateDate of last change of password of the customer accountR4
customerAccountInfo.addPaymentMeanDateDate of last added form of payment made to account. For example a new card registered to the accountR4

Did this page help you?