Skip to main content

EMV 3-D Secure v2.1.0+ Notice

Updated

Table of Contents

 

Overview

With the advent of 3-D Secure v2, some changes have been made to the Hosted Payment Page (eKashu) solution so that integrators can better meet the requirements necessary to perform EMV 3DS 2.1.0+ authentications.

 

First and Last Name Requirement

In order to be able to perform EMV 3DS 2.1.0+ authentications, eKashu requires a first name and last name to be provided during the initial POST to eKashu or the card number entry form set up to allow collection of cardholder information and for this data to be collected.

Without this data, EMV 3DS 2.1.0+ isn’t possible, and 3DS 1.0.2 will be used instead, provided eKashu is configured to do this. Therefore, the following options can be utilized to achieve this in eKashu:

  • To avoid the need to collect the rest of the cardholder properties such as email address and the cardholder address, you can use the below fields to provide the first name / last name to eKashu as part of your initial POST:
    • ekashu_card_first_name
    • ekashu_card_last_name
  • Alternatively, you may enable the capture of “Cardholder Properties” during the first step of eKashu by providing a true value for the below eKashu property:
    • ekashu_card_address_editable

 

New Variables for eKashu

A new eKashu variable has been added to allow for the easier collection of cardholder names: ekashu_card_name_required, which accepts a Boolean (true or false) value. This variable is most useful for integrations that are providing the below variables / value combination:

  • ekashu_card_address_required = false
  • ekashu_card_address_verify = false
  • ekashu_card_zip_code_verify = false

Normally, this combination of eKashu variables would cause eKashu not to collect any cardholder data and not show the cardholder form.

When the cardholder form is editable, passing a true value for ekashu_card_name_required to eKashu will allow the cardholder to enter their name only. When the cardholder form is non-editable, it will allow your integration to provide the cardholder name as a part of the initial POST and ensure that the cardholder name is included when attempting 3DS2.

Another new eKashu variable has been added to allow integrations to enforce collection of cardholder names as mandatory: ekashu_card_name_mandatory, which accepts a Boolean value. This variable is most useful for integrations that are providing the below variables / value combination:

  • ekashu_card_address_required = false
  • ekashu_card_address_verify = false
  • ekashu_card_zip_code_verify = false
  • ekashu_card_name_required = true

Normally, this combination of eKashu variables would cause eKashu to not validate the cardholder’s name before moving on to the 3DS stage (and subsequent authorization stage).

When the cardholder form is editable, passing a true value for ekashu_card_name_mandatory to eKashu will make the entry of the cardholder’s name mandatory and eKashu won’t allow the cardholder to proceed.