1. Introduction

With the introduction of the PSD2 guideline, it is more important than ever to keep track of your 3-D Secure transactions.

Regardless of the our integration mode(s) you use, we make this really easy for you. Use this guide to learn where to look and how to read the available information.

Become a 3-D Secure expert in no time!

2. Understand 3-D Secure statuses

Apart from clearly defined exclusions and excemptions, any of your customers will have to pass a 3-D Secure authentication check. The transaction reaches both a 3-D Secure status (which is the outcome of the authentication check) and a global transaction status (which indicates the outcome of the authorisation request).

Hence, both are the result of two different steps:

• 3-D Secure status: First, your customer has to prove that s/he is the rightful owner of the credit card used for the transaction. This authentication check takes place on your customer’s issuer online portal
• Global transaction status: Second, your acquirer checks by consulting your customer’s issuer whether enough funds are available for the transaction, resulting in an (un)successful authorisation. Learn more about the global transaction status and all possible outcomes

You can look up the results via a GetPayment/GetPaymentDetails request to our platform. Properties paymentOutput.cardPaymentMethodSpecificOutput.threeDSecureResults.eci and statusOutput.statusCode contain the 3-D Secure status and the global transaction status respectively. 

The table below gives you a full overview of possible scenarios and how our platform displays them to you in either way:

3. Partial end of liability shift

All the major schemes listed below are aligned and determined to ensure that the official 3DS v1 switch off happens in October 2022:

• VISA
• Mastercard
• American Express
• JCB
• Diners Discover

VISA and Mastercard already announced a transition period towards EMV 3DS. 

Essentially, only fully authenticated transactions will be supported by both VISA and Mastercard, resulting in a decrease of fraud liability protection for merchants using 3DS v1.

You will be able to see this in in our response to CreatePayment/CreateHostedCheckout requests in properties payment.paymentOutput.CardPaymentSpecificOutput.threeDSecureResults.version=v1 and payment.paymentOutput.CardPaymentSpecificOutput.threeDSecureResults.eci=12.

For version=v1 and eci=6, the liability shift still applies.

Visa

Mastercard