Last update 29/01/2019

2. 3-D Secure v2.1 (Available in TEST)

2.1 Introduction

In 2013, the European Commission published a proposal for the revised version of the Payment Services Directive, known as PSD2 to simplify payment processing and create the rules and regulations for payment services in the EU and there began the need for new version of 3-D Secure, v2.1.

The biggest change is that you, as a merchant, are asked to share more data: issuers are hungry for data points to improve the accuracy of their decision ultimately leading to a frictionless scenario, but you are the ones on the front line capturing the data.

The 3DS v2 approach to risk evaluation is more effective, but requires the entire ecosystem to change, allowing you to push the data through to the issuer.

With the introduction of this new guidline, the major card schemes have updated their 3DS logos. As you are creating your own payment page, make sure to implement these new logos (Visa / Mastercard / JCB /… ).

The transaction flow involves the following steps:

1. You send us a DirectLink request for the transaction, containing a number of additional parameters.

These parameter can be devised to three sets:

a. Mandatory parameters that need to be captured in the payment page where the cardholder is entering the card details.

Field Description Format   Mandatory
browserAcceptHeader Exact content of the HTTP accept headers as sent to the merchant from the Cardholder’s browser. *
Length: Variable, maximum 2048 characters
Type: String
If the total length of the accept header sent by the browser exceeds 2048 characters, the 3DS Server truncates the excess portion.
Yes
browserColorDepth Value representing the bit depth of the color palette for displaying images, in bits per pixel. Obtained from Cardholder browser using the screen color Depth property. Data Type: String
Values accepted:
1 = 1 bit
4 = 4 bits
8 = 8 bits
15 = 15 bits
16 = 16 bits
24 = 24 bits
32 = 32 bits
48 = 48 bits
Yes
browserJavaEnabled Boolean that represents the ability of the cardholder browser to execute Java. Value is returned from the navigator java Enabled property. Data Type: Boolean
Values accepted:
true
false
Yes
browserLanguage Value representing the browser language as defined in IETF BCP47. Returned from navigator language property. Length: Variable, 1–8 characters
Data Type: String
Yes
browserScreenHeight Total height of the Cardholder’s screen in pixels. Value is returned from the screen height property. Data Type: Int
Between 0 and 999999
Yes
browserScreenWidth Total width of the cardholder’s screen in pixels. Value is returned from the screen width property. Data Type: Int
Between 0 and 999999
Yes
browserTimeZone Time difference between UTC time and the Cardholder browser local time, in minutes. Data Type: Int
Between -720 and 840
 Yes
browserUserAgent Exact content of the HTTP user-agent header. * Length: Variable, maximum 2048 characters Data Type: String
Note: If the total length of the UserAgent sent by the browser exceeds 2048 characters, the 3DS Server truncates the excess portion.
 Yes

*HTTP_ACCEPT and HTTP_USER_AGENT don't have to be sent with browserAcceptHeader and browserUserAgent, otherwise we will fill it with the browser parameters.

Note: Please don't forget to calculate the parameters in your SHA signature.

Please find below a Javascript code example to capture these parameters.

<script type="text/javascript" language="javascript">

function createHiddenInput(form, name, value)
{
var input = document.createElement("input");
input.setAttribute("type", "hidden");
input.setAttribute("name", name); 
input.setAttribute("value", value);
form.appendChild(input);
}

var myCCForms = document.getElementsByName("MyForm");
if (myCCForms != null && myCCForms.length > 0)
{
var myCCForm = myCCForms[0];
createHiddenInput(myCCForm, "browserColorDepth", screen.colorDepth);
createHiddenInput(myCCForm, "browserJavaEnabled", navigator.javaEnabled());
createHiddenInput(myCCForm, "browserLanguage", navigator.language);
createHiddenInput(myCCForm, "browserScreenHeight", screen.height);
createHiddenInput(myCCForm, "browserScreenWidth", screen.width);
createHiddenInput(myCCForm, "browserTimeZone", new Date().getTimezoneOffset());
}
</script>

b. Required additional parameters (cf. Extra request parameters)

c. Recommended parameters (list of parameters) that if sent will have a positive impact on transaction conversion rates. Based on the information contained in these parameters, a potential frictionless authentication flow may take place, where the cardholder won’t need anymore to authenticate himself and therefore a quicker transaction completing is expected.

Our system receives the card number in your request and checks online whether the card is registered in the VISA/MasterCard/JCB/AmEx directory (registered means that identification is possible for the card number, i.e. the card is a 3-D Secure card).

2. Based on the schemes directory response and whether additional parameters in 1.c (Recommended parameters - list of parameters) above were provided (given if the cardholder is registered for 3-D Secure), two potential flows are expected if the cardholder is registered:

2.1. A frictionless flow: The cardholder doesn't physically need to authenticate themselves because the authentication took place in the background without their input. In this case, the liability shift is on the issuing bank.

2.2. A challenge flow: The cardholder needs to identify himself.

i. The answer to the DirectLink request contains a specific payment status and an html code that has to be returned to the customer to start the identification process (cf. Additional return fields). The block of html code will automatically start the identification process between the cardholder (customer) and his issuing bank.

ii. The cardholder identifies himself on the issuing bank’s page.

iii. Our system receives the identification response from the issuer.

iv. If the identification was successful, our system will submit the actual financial transaction to the acquirer.
3. You receive the result of the global identification and online authorisation process via e-Commerce mode feedback channels.

Apart from the standard DirectLink parameters, you also need to send the following information:

Field Description
FLAG3D

Fixed value: ‘Y’

Instructs our system to perform 3-D Secure identification if necessary.

HTTP_ACCEPT The Accept request header field in the cardholder browser, used to specify certain media types which are acceptable for the response. This value is used by the issuer to check if the cardholder browser is compatible with the issuer identification system. *
For example:
Accept: */*
HTTP_USER_AGENT The User-Agent request-header field in the cardholder browser, containing information about the user agent originating the request. This value is used by the issuer to check if the cardholder browser is compatible with the issuer identification system. *
For example: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
WIN3DS Way to show the identification page to the customer. Possible values:
  • MAINW: display the identification page in the main window (default value).
  • POPUP: display the identification page in a pop-up window and return to the main window at the end.
  • POPIX: display the identification page in a pop-up window and remain in the pop-up window.
ACCEPTURL URL of the webpage to show the customer when the payment is authorised. (or waiting to be authorised).
DECLINEURL URL to which the customer is redirected if the maximum number of failed authorisation attempts has been reached (10 by default, but which can be changed in the Technical Information page, "Global transaction parameters" tab, "Payment retry" section).
EXCEPTIONURL URL of the webpage to show the customer when the payment result is uncertain.
PARAMPLUS Field to submit the miscellaneous parameters and their values that you wish to be returned in the post-sale request or final redirection.
COMPLUS Field to submit a value you wish to be returned in the post-sale request or output.
LANGUAGE Customer’s language, for example: “en_US”
Optional
TP To change the layout of the "order_A3DS" page, you can send a template name/url with this parameter. (go to e-Commerce: Dynamic template).

*HTTP_ACCEPT and HTTP_USER_AGENT will not need to be sent if send browserAcceptHeader and browserUserAgent.

For more information, go to Transaction Feedback.

If the cardholder is not registered, the normal DirectLink response is returned. If the cardholder is registered, the following (additional) fields will be returned:

Field Description
STATUS
New value: “46” (waiting for identification)
HTML_ANSWER

BASE64 encoded html code to be added in the html page returned to the customer.

This tag is added as a child of the <ncresponse> global XML tag. The field HTML_Answer field contains HTML code that has to be added in the html page returned to the customer's browser.

This code will automatically load the issuer bank identification page in a pop-up in the main window, depending on the WIN3DS parameter value.

To avoid any interference between the html tags included in the content of the HTML_ANSWER XML tag, with the rest of the XML returned as a response to the DirectLink request, the HTML_ANSWER content is BASE64 encoded by our system before returning the response. Consequently, this must be BASE64 DEcoded before it is included in the html page sent to the cardholder.

Test Cards

You can use the following test card to simulate a 3-D Secure registered card in our test environment:

Frictionless Flow

Brand Card number Expiry date
VISA 4186455175836497 Any date in the future
Mastercard
5137009801943438 Any date in the future
American Express
375418081197346 Any date in the future

Challenge Flow

Brand Card number Expiry date
VISA 4874970686672022 Any date in the future
Mastercard
5130257474533310 Any date in the future
American Express
379764422997381 Any date in the future

Note: More test cards numbers can be downloaded here.

Incorrect identification

If a transaction is blocked due to incorrect identification, the transaction result will be:

STATUS = 0

NCSTATUS = 5

NCERROR = 40001134

2.3 Exclusions and exemptions for 3DsV2

2.3.1 3DSv2 and exclusions

With the introduction of 3DSv2, card holder authentication will generally become mandatory as defined by the EU’s Second Payment Services Directive (2015/2366 PSD2). Nevertheless, some transactions are excluded from this rule if one of the following scenarios applies:

  • Mail order/telephone order
  • One leg journey - Payee's PSP (aka Merchant's acquirer) or Payer's PSP (aka Buyer's payment method issuer) is outside of EEA zone
  • Anonymous prepaid cards up to 150€ (article 63)
  • MIT - merchant initiated transactionsMail order/telephone order

2.3.2 SCA and 3DS frictionless / challenge flow

Part of this new regulation is the Strong Customer Authentication (SCA). This involves the possibility that the issuer (the card holder’s bank) will ask additional information from the card holder. In such a scenario the authentication process will result in a challenge flow (requiring the card holder to actively authenticate) instead of a frictionless flow (requiring no authentication by the card holder).

However, we offer our merchants the possibility to indicate the preferred flow. This can be achieved by sending additional parameters which will be used by the issuer for risk assessment. Depending on the issuer’s decision, a frictionless flow might take place. In some scenarios 3DS might even be skipped altogether if specific exemptions apply.

2.3.3 Indication of the preferred flow

To indicate the preference for a frictionless flow during the authentication request, the merchant may send the additional parameter Mpi.threeDSRequestorChallengeIndicator. Depending on the merchant’s assessment of the risk of fraud, specific values may be sent (i.e. for low risk assessment: 02, for an increased risk of fraud: 03

Parameter   Values Mandatory / Optional
 Mpi.threeDSRequestorChallengeIndicator  01 = No preference
02 = No challenge requested
03 = Challenge requested: merchant Preference
04 = Challenge requested: Mandate
Mandatory (in case for a preference for a specific flow)

The merchant can further raise the chance of a frictionless flow / conversion rate by sending more optional fields.

2.3.4 Exemptions of 3DS

For some transactions, the merchant might be able to skip 3DS (resulting in a frictionless flow) and go for the authorization directly. This process is limited to transactions which are either excluded from SCA (as described above) or which can benefit from specific exemptions. These exemptions need to be part of an agreement between the merchant and his / her acquirer. In a scenario like this, the merchant will indicate to skip the authentication process by sending these additional parameters:


Parameter Values   Mandatory / Optional
 FLAG3DS  N = Skip the 3DS authentication process  Mandatory (in case 3DS should be skipped)
 3DS_EXEMPTION_INDICATOR  03 = Issuer TRA*
04 = Low amount exemption
05 = Merchant/Acquirer TRA*
06 = White Listing
07 = Corporate
08 = Delayed Shipment
09 = Delegated authentication (certified wallet)
 Mandatory (in case 3DS should be skipped)

* Transaction risk analysis

However, it is still up to the issuer whether an authentication process has to take place. In case the issuer insists on 3DS, the transaction will be declined.

As a leading global digital payment service provider, Ingenico Payment Services provides a seamless response to the complexity of payments, whatever the channel: online, mobile and point-of-sale. Offering innovative e-commerce, multi-channel, financial, and marketing solutions, it helps merchants to manage, collect and secure their payments, prevent fraud and increase their revenues through higher conversions. Ingenico Payment Services is part of the Ingenico Group, the global leader in seamless payment.

This website uses cookies to be able to give you the best user experience. If you don't want to accept these cookies, we allow you to change the cookie settings. Click 'Accept' to allow all cookies from this website.

Cookie settings

Introduction

Functional

Functional cookies are required for the website to operate correctly. These cookies cannot be disabled.

Optimized

Optimization cookies allow us to analyze site usage so we can measure and improve our website.
This is the default level.

Personalized

Personalization cookies are used for social media and advanced personalization. They allow us to show you information related to your company.


Example functionality allowed

  • Store country preference
  • Store language preference

Example functionality not allowed

  • Saving personal data
  • Anonymous tracking via Google Analytics
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics

Example functionality not allowed

  • Saving personal data
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics
  • Serve content relevant to your interests
  • Serve ads relevant to your interests
  • Tracking for remarketing purposes

Example functionality not allowed

  • Saving personal data