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 also increases. To tackle the issue of an increasing amount 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
Behavioural 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 as possible.

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. It is recommended to populate them whenever possible. The most important fields are ranked from R1 (most important) to R4.

Billing Address Object

Object	Field	Description	Priority
`billingAddress`	billingAddress.city	Billing address	R2
	billingAddress.country		R2
	billingAddress.addressAdditional1		R2
	billingAddress.addressAdditional2		R2
	billingAddress.addressAdditional3		R2
	billingAddress.zipcode		R2
	billingAddress.state		R2

Holder Information

Object	Field	Description	Priority
`holder`	firstName	Holder contact information	R1
	lastName		R1
	email		R1
	phone		R3
	mobile		R3
	workPhone		R3

Delivery Address Information

Object	Field	Description	Priority
`deliveryAddress`	deliveryAddress.city	Delivery address information	R1
	deliveryAddress.country		R1
	Address.addressAdditional1		R1
	deliveryAddress.addressAdditional2		R1
	deliveryAddress.addressAdditional3		R1
	deliveryAddress.zipcode		R1
	deliveryAddress.state		R1

Delivery Address Additional Information

Object	Field	Description	Priority
`deliveryAdditionalInfo`	numberOfItemsBasket	The total quantity of all products in the basket	R2
	addressDeliveryBillingMatchIndicator	Specifies whether the delivery and the billing addresses are the same	R2
	deliveryAddressCreationDate	The date on which the last delivery address used by the merchant's account was reported in the transaction	R2
	estimatedDeliveryDelay	Estimated Delivery Delay (in days) by the Merchant	R2
	deliveryMode	Delivery Method (e.g., Postal Office, Amazon box)	R2

Holder Account Information

Object	Field	Description	Priority
`customerAccountInfo`	customerAccountInfo.customerAccountId	Additional information about the account is optionally provided by the 3-D Secure Requestor.	R4
	customerAccountInfo.numberOfPurchase180Days	The amount of customer transactions made over the last six months (last 180 days)	R4
	customerAccountInfo.numberOfTransactionYear	Number of accepted or abandoned transactions in the last year on the merchant's customer account.	R4
	customerAccountInfo.customerAccountCreationDate	When the customer account was originally created.	R4
	customerAccountInfo.numberOfAttemptsAddCard24Hours	Number of distinct cards used by the merchant's account in the last 24 hours.	R4
	customerAccountInfo.suspiciousActivityIndicator	Notes if a suspicious activity is detected on the customer account in the merchant's website.	R4
	customerAccountInfo.numberOfTransaction24Hours	How many transactions did the customer make in the last 24 hours	R4
	customerAccountInfo.customerAccountChangeDate	Last date the customer account was changed	R4
	customerAccountInfo.passwordChangeDate	Date of last change of password of the customer account	R4
	customerAccountInfo.addPaymentMeanDate	Date of last added form of payment made to account. For example, a new card registered to the account	R4

Authentication

Object	Field	Description	Priority
`authentication`	merchantCustomerAuthentMethod	NOAUTHENT = 1 - No authentication of the customer by the merchant OWNCREDENTIAL = 2 - Authentication by merchant’s own system FEDERATEDID = 3 - Customer authentication by a federated identifier (e.g., Facebook) ISSUERID = 4 - Customer authentication using the issuer’s payment method info THIRDPARTY = 5 - Customer authentication by a third-party system FIDO = 6 - Customer authentication with a FIDO (Fast IDentity Online) system	R2
	merchantCustomerAuthentDateTime	ISO8601 date time format	R2