Overview

As part of Cardinal’s commitment to support the industry’s transition to newer EMV 3DS protocols and to align with EMVCo’s management of protocol versions to ensure global coherence of the EMV 3DS ecosystem, Cardinal will align network discontinue dates for 3DS 2.1.0.

Merchants must be aware that specific card networks will begin to fail 3DS 2.1.0 transactions based on their sunset date.

What to expect

Listed below are the two error scenarios specific to the 2.1.0 sunset.

Scenario 1: Card Range Not Present in the PRes.

Outcome: Cardinal returns an error for the transaction when a card range is not found in the PRes.

cmpi_Lookup Response will include: 

• ErrorNo= 2274 

• ErrorDesc = Card Not Enrolled in EMV 3DS

Scenario 2: The legacy override field ThreeDSVersion with the value 2.1.0 is included on the cmpi_lookup request.

Outcome: Cardinal will send the AReq with message version as 2.1.0; however - the networks would error the transaction as 2.1.0 will be decommissioned.

cmpi_Lookup Response will include:

• ReasonCode = 102

• ReasonDesc = {{Depends on the card brand}}

Card Brand Specific Reason Descriptions for ReasonCode 102

Visa: Message Version Number received is not valid for the receiving component, 2.1.0,2.2.0

Mastercard: Message Version Number Not Supported Message Version Number received is not valid for the receiving component

American Express: Message Version Number Not Supported component, Supported Versions are [2.2.0, 2.3.1]

Discover: Message version not supported, messageVersion invalid value '2.1.0' supported versions:

ELO: Message version not supported, messageVersion invalid value '2.1.0' supported versions:

JCB: Message Version Number not supported

Network Sunset Date

Below are the dates by network on when they are sunsetting EMV 3DS 2.1.0

• Visa Secure – Sept. 25th, 2024

• Mastercard Identity Check – Sept. 24th, 2024

• JCB J/Secure – Sept. 26th, 2024

• Amex Safekey – Sept. 30th, 2024

• Discover Protect Buy – Oct. 18th, 2024