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.

Billing Address Object

ObjectFieldDescriptionPriority
billingAddressbillingAddress.cityBilling addressR2
billingAddress.countryR2
billingAddress.addressAdditional1R2
billingAddress.addressAdditional2R2
billingAddress.addressAdditional3R2
billingAddress.zipcodeR2
billingAddress.stateR2

Holder Information

ObjectFieldDescriptionPriority
holderfirstNameHolder contact informationR1
lastNameR1
emailR1
phoneR3
mobileR3
workPhoneR3

Delivery Address Information

ObjectFieldDescriptionPriority
deliveryAddressdeliveryAddress.cityDelivery address informationR1
deliveryAddress.countryR1
Address.addressAdditional1R1
deliveryAddress.addressAdditional2R1
deliveryAddress.addressAdditional3R1
deliveryAddress.zipcodeR1
deliveryAddress.stateR1

Delivery Address Additional Information

ObjectFieldDescriptionPriority
deliveryAdditionalInfonumberOfItemsBasketTotal quantity of all products in the basketR2
addressDeliveryBillingMatchIndicatorSpecifies whether the delivery and the billing addresses are the sameR2
deliveryAddressCreationDateThe date on which the last delivery address used by the merchant's account was reported in the transactionR2
estimatedDeliveryDelayEstimated Delivery Delay (in days) by the MerchantR2
deliveryModeDelivery Method (Postal Office or Amazon box and so on)R2

Holder Account Information

ObjectFieldDescriptionPriority
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

Authentication

ObjectFieldDescriptionPriority
authenticationmerchantCustomerAuthentMethodNOAUTHENT = 1 - No authentication of the customer by the merchantR2
OWNCREDENTIAL = 2 - Customer authentication by the merchant using his own system
FEDERATEDID = 3 - Customer authentication by the merchant using an identifier federated(facebook, ...) (e.g.Facebook)
ISSUERID = 4 - Customer authentication by the merchant using information of the issuer's payment mean
THIRDPARTY = 5 - Customer authentication by the merchant using a third system
FIDO = 6 - Customer authentication by the merchant with FIDO(Fast IDentity Online) system
merchantCustomerAuthentDateTimeISO8601 date time formatR2

Did this page help you?