Hey, just a heads up! EMV 3DS 2.1.0 won't be supported anymore.

Early this April, Mastercard sent an announcement to all stakeholders which reminded them to update EMV 3DS version from 2.1.0 to 2.2.0 on time. So, make sure you're up to date with the latest versions to avoid any issues!

Here are several things you need to know which can help you catch up with the new requirements and deadlines of secure payment.

Deadline

For the update, Mastercard set a clear timeline:

"September 23, 2024 - Version 2.1.0 sunset. The final date for EMV 3DS v2.1.0 transactions on the Identity Check network

September 24, 2024 - EMV 3DS v2.1.0 transactions will begin to generate errors on the Identity Check network."

If you cannot fully migrate to version 2.2.0 by the decommission deadline, your transaction will be crashed cause transaction of version 2.1.0 will not be supported by the identity check network.

For SDK Operators

DS public Certificate (Certificate Id: 134243) for SDK Device encryption will be expired on 15 June 2024. SDK operators are advised to plan and execute the necessary updates to their products well before the expiry date to ensure a smooth transition.

Failure to update SDK products to support the new certificate may result in transaction failures and disrupted services for your customers. It is, therefore, imperative that you take the necessary steps to update your SDK products in a timely manner.

For 3DS Server Operators

Mastercard will initiate an automated cleanup of merchant enrollment records in the ISSM app. Records of merchants without EMV® 3DS activity for a period exceeding 13 months will be removed. Monthly deletions will commence from June 1st, 2024. And, acquirers can review pending deletions in the ISSM application. It is advised to review and prepare for these deletions accordingly.

For All Operators

Mastercard is in the process of renewing the Subordinate Certificate Authorities (Sub CAs) that are utilized for signing certificate requests. This renewal is a crucial step to maintain the security and integrity of the certificate signing process. As a result, operators must promptly update their trust stores to incorporate the newly renewed Sub CA. Failure to do so may result in connectivity issues or certificate validation failures.

The updated Sub CA will be used exclusively for signing new or renewal certificate requests through Mastercard Connect. This means that 3DS operators and service providers must ensure that they load the new Sub CAs into their trust stores to maintain smooth connectivity and uninterrupted service.

By following these instructions, operators can ensure that their systems are prepared for the new Sub CA and maintain a secure and reliable connection with Mastercard Connect.

Moreover, Mastercard also mentioned 3DS connectivity update which can be checked in detail on AN 7396 Clarification of Identity Check 2.0 Directory Server Connectivity (mastercard.com).

In Conclusion

The clock is ticking, We are going to bid a farewell to 3DS 2.1.0 literally. Let's work together to make everything prepared for 3DS 2.2.0 this year. If you want do know more about version 2.1.0 and 2.2.0 and their difference, you can read our past blogs. Follow our website to help you keep informed of any changes or updates that may affect your business operations.

One more thing: Don't forget, if you need any help, HiTRUST team is always here for you!