• Hey there! Welcome to TFC! View fewer ads on the website just by signing up on TF Community.

Card networks in India will sunset 3DS 1.0.2 and will support only EMV® 3DS 2.1 or higher

Abhishek012

TF Pioneer
Card networks in India will sunset 3DS 1.0.2 and will support only EMV® 3DS 2.1 or higher:

In order to remain competitive in the nowadays challenging environment and if you still have not upgraded to the EMV 3DS 2.1, now is the time to do so.

This October marks a significant milestone for 3-D Secure. Card networks will sunset 3DS 1.0.2 in India. How can we ensure a seamless and secure shopping experience for online shoppers in India ?

The sunset of 3DS 1.0.2, for most countries, went into effect mid-October. Some countries received network extensions until 2023. If you do business in India, there are important implications for you to consider.

It not only benefits your customer’s online transactions, supported by security and a better experience. It also benefits your business by protecting it from fraud and chargebacks, while abandonment rates are decreased. It promises better conversion with the needed trust on all digital payment sides.

New-3D-secure-specification.jpg

Visa Secure (formerly Verified by Visa):

Visa extended 3DS 1.0 support for India through October 12, 2023. It’s important to note that Visa is continuing to support 3DS 1.0 transaction processing solely for domestic transactions. Cross-border transactions initiated by merchants from those countries to the rest of the world must be made using EMV® 3-D Secure for authentication beyond October 15, 2022.

Mastercard SecureCode:

Mastercard extended the sunset of 3DS 1.0 for India and Bangladesh through October 3, 2023. Any transactions sent to the 3DS 1.0 Directory Server after this date will result in an error.

October 3, 2023: 3DS 1.0 Directory Server will stop routing verify enrollment requests (VEReqs). The 3DS 1.0 Directory Server will result in an unauthenticated status. (transaction status “N”)

November 1, 2023: The Mastercard firewall will respond to VEReqs with a site not found error, as the 3DS 1.0 Directory Server URL will no longer be available

American Express SafeKey:

American Express will sunset of 3DS 1.0 for India from October 13, 2023.

What to do now:

With the sunset that took place in October, most of the 3DS 1.0 world has migrated to EMV® 3-D Secure – but if you are in the one of countries that received an extension, don’t delay - upgrade now to maximize the benefits of EMV 3DS and avoid possible added costs.

Reminder of important dates:
  • 03 October 2023: Mastercard will stop supporting 3-D Secure 1 in India and Bangladesh.
  • 13 October 2023 American Express is terminating SafeKey 1.0 in India. All secure payments will be processed through the EMV 3DS 2.x flow.
What will happen if you stay with 3DS 1.0.2 ?

Customers everywhere are willing to authenticate and identify themselves for the sake of their security shopping online. Staying with 3DS 1 will create unsuccessful transactions (Errors in transactions). This will cause-
  • Unsatisfied customers
  • Cart abandonments
  • A higher risk of fraud
  • Money loss
  • Business shrinkage
EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC.

EMVCo’s work is overseen by six member organisations—American Express, Discover, JCB, Mastercard, UnionPay, and Visa— which recognise a shared responsibility for the reliability and security of payment transactions and the technology infrastructure that makes them possible.



I know you guys will ask, what about RuPay card ? right ?

Simple answer - I don't know.

Well, RuPay is not a member of EMVCo, LLC.

RuPay develop its own 3Ds gateway called - Bharat Ecommerce Payment Gateway (BEPG)

You may heard about this famous bengali song - Jodi tor dak shune keu na ase ekla chalo re, ekla chalo, ekla chalo, ekla chalo re (English translation - If no one answers your call then walk on your own, Walk alone, walk alone, walk alone)

Last time i read somewhere RuPay launch BEPG 2.0 (BEPG Phase 2)

Recently, you guys have already seen many banks are added merchants name and transaction amount on RuPay OTP page. This is the part of a RuPay BEPG migration.

I don't know when RuPay will discontinued old RuPay Paysecure gateway and fully migrate to new BEPG 2.0 gateway.

Benefits of Bharat eCommerce Payment Gateway (BEPG) -

1) Enhanced consumer experience
2) Additional payment options on RuPay cards
3) No compromise on security and risk
4) Simplified architecture
5) Improvement in success rate
6) Self-healing system

Highlights of Bharat eCommerce Payment Gateway (BEPG) -

What’s New -


1) BEPG provides currently available functionalities of eCommerce system

2) Server to server API for ‘OTP Generation and OTP Validation’ during ‘Authentication’ of transactions.

3) Tokenization for In-App merchants and ‘Card on File’ to simplify consumer experience.

4) Quick checkout functionality where registered RuPay consumers can do transactions without Additional Factor of
Authentication (AFA).

5) Connected checkout functionality where Trusted Merchants can participate to register RuPay consumers to facilitate
transactions without Additional Factor of Authentication (AFA).

6) Amount and merchant name has been added to Issuer Authentication System (IAS) API call for consumer friendly
OTP delivery.

7) Online reversal message for payment gateways have been introduced to facilitate CNP reversals.

8) Subscription based transaction lifecycle has been added.

9) Equated Monthly Instalments (EMI) solutions introduced for both Credit and Debit products.

10) Refund based on Original Credit Transfers (OCT) for quicker refund process to consumers.

11) Card to card payments for Credit card payments and balance transfer transactions for Credit cards.
 
What about diners club?

Discover Protectbuy already sunset 3DS 1.0.2 on OCTOBER 14, 2022.​

Discover Global Network (DGN) announced sunset dates for ProtectBuy 2.1​

EMVCo and the other payment networks are collectively deprecating the 3DS v2.1 protocol to make 3DS 2.2 the default protocol and eventually phase in 3DS 2.3.1.​

The following dates are announced for phasing out 3DS 2.1 and mandating 3DS 2.2.

DateCertification StatusAction Required
July 31, 2023DGN will stop certification for ProtectBuy v2.1 Any partners that wish to be certified for ProtectBuy must be certified for v2.2 or higher.
September 25, 2024 The client is certified for both v2.1 and v2.2 Shut off v2.1, and direct all traffic to v2.2 or higher.
The client is only on v2.1 Certify for v2.2 or higher using BAU certification process.
Clients not certified for any ProtectBuy version Follow the BAU ProtectBuy certification process for new certification requests.
 
Card networks in India will sunset 3DS 1.0.2 and will support only EMV® 3DS 2.1 or higher:

In order to remain competitive in the nowadays challenging environment and if you still have not upgraded to the EMV 3DS 2.1, now is the time to do so.

This October marks a significant milestone for 3-D Secure. Card networks will sunset 3DS 1.0.2 in India. How can we ensure a seamless and secure shopping experience for online shoppers in India ?

The sunset of 3DS 1.0.2, for most countries, went into effect mid-October. Some countries received network extensions until 2023. If you do business in India, there are important implications for you to consider.

It not only benefits your customer’s online transactions, supported by security and a better experience. It also benefits your business by protecting it from fraud and chargebacks, while abandonment rates are decreased. It promises better conversion with the needed trust on all digital payment sides.

View attachment 20611

Visa Secure (formerly Verified by Visa):

Visa extended 3DS 1.0 support for India through October 12, 2023. It’s important to note that Visa is continuing to support 3DS 1.0 transaction processing solely for domestic transactions. Cross-border transactions initiated by merchants from those countries to the rest of the world must be made using EMV® 3-D Secure for authentication beyond October 15, 2022.

Mastercard SecureCode:

Mastercard extended the sunset of 3DS 1.0 for India and Bangladesh through October 3, 2023. Any transactions sent to the 3DS 1.0 Directory Server after this date will result in an error.

October 3, 2023: 3DS 1.0 Directory Server will stop routing verify enrollment requests (VEReqs). The 3DS 1.0 Directory Server will result in an unauthenticated status. (transaction status “N”)

November 1, 2023: The Mastercard firewall will respond to VEReqs with a site not found error, as the 3DS 1.0 Directory Server URL will no longer be available

American Express SafeKey:

American Express will sunset of 3DS 1.0 for India from October 13, 2023.

What to do now:

With the sunset that took place in October, most of the 3DS 1.0 world has migrated to EMV® 3-D Secure – but if you are in the one of countries that received an extension, don’t delay - upgrade now to maximize the benefits of EMV 3DS and avoid possible added costs.

Reminder of important dates:
  • 03 October 2023: Mastercard will stop supporting 3-D Secure 1 in India and Bangladesh.
  • 13 October 2023 American Express is terminating SafeKey 1.0 in India. All secure payments will be processed through the EMV 3DS 2.x flow.
What will happen if you stay with 3DS 1.0.2 ?

Customers everywhere are willing to authenticate and identify themselves for the sake of their security shopping online. Staying with 3DS 1 will create unsuccessful transactions (Errors in transactions). This will cause-
  • Unsatisfied customers
  • Cart abandonments
  • A higher risk of fraud
  • Money loss
  • Business shrinkage
EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC.

EMVCo’s work is overseen by six member organisations—American Express, Discover, JCB, Mastercard, UnionPay, and Visa— which recognise a shared responsibility for the reliability and security of payment transactions and the technology infrastructure that makes them possible.



I know you guys will ask, what about RuPay card ? right ?

Simple answer - I don't know.

Well, RuPay is not a member of EMVCo, LLC.

RuPay develop its own 3Ds gateway called - Bharat Ecommerce Payment Gateway (BEPG)

You may heard about this famous bengali song - Jodi tor dak shune keu na ase ekla chalo re, ekla chalo, ekla chalo, ekla chalo re (English translation - If no one answers your call then walk on your own, Walk alone, walk alone, walk alone)

Last time i read somewhere RuPay launch BEPG 2.0 (BEPG Phase 2)

Recently, you guys have already seen many banks are added merchants name and transaction amount on RuPay OTP page. This is the part of a RuPay BEPG migration.

I don't know when RuPay will discontinued old RuPay Paysecure gateway and fully migrate to new BEPG 2.0 gateway.

Benefits of Bharat eCommerce Payment Gateway (BEPG) -

1) Enhanced consumer experience
2) Additional payment options on RuPay cards
3) No compromise on security and risk
4) Simplified architecture
5) Improvement in success rate
6) Self-healing system

Highlights of Bharat eCommerce Payment Gateway (BEPG) -

What’s New -


1) BEPG provides currently available functionalities of eCommerce system

2) Server to server API for ‘OTP Generation and OTP Validation’ during ‘Authentication’ of transactions.

3) Tokenization for In-App merchants and ‘Card on File’ to simplify consumer experience.

4) Quick checkout functionality where registered RuPay consumers can do transactions without Additional Factor of
Authentication (AFA).

5) Connected checkout functionality where Trusted Merchants can participate to register RuPay consumers to facilitate
transactions without Additional Factor of Authentication (AFA).

6) Amount and merchant name has been added to Issuer Authentication System (IAS) API call for consumer friendly
OTP delivery.

7) Online reversal message for payment gateways have been introduced to facilitate CNP reversals.

8) Subscription based transaction lifecycle has been added.

9) Equated Monthly Instalments (EMI) solutions introduced for both Credit and Debit products.

10) Refund based on Original Credit Transfers (OCT) for quicker refund process to consumers.

11) Card to card payments for Credit card payments and balance transfer transactions for Credit cards.
Now I am seeing two different UI for OTP Authentication Page whenever I did txns via Visa and MasterCard.

One UI reflects 3DS 1.0.2
And
Second UI reflects EMV® 3DS 2.1 or higher ?
 
Dear Abhishek

Thanks for sharing such updates which is worth knowledge.

So , layman's question as .....We need to approach Bank for card placement at this juncture and if so, what will be the request tagline with Bank
 
which bank ? SS bhejo.
This UI is the New UI and common across all Banks.

Earlier each bank OTP PAGE has its own Unique UI but this new UI is common in all banks.

Some gateways like Paytm is using Both UI. Sometimes txns were routed via old UI and Sometimes via new UI.



Payzapp shifted to new UI. Even after multiple attempts only New UI OTP page is opening.
 

Attachments

  • Screenshot_20230623_101239_Zomato.jpg
    Screenshot_20230623_101239_Zomato.jpg
    136.1 KB · Views: 49
This UI is the New UI and common across all Banks.

Earlier each bank OTP PAGE has its own Unique UI but this new UI is common in all banks.

Some gateways like Paytm is using Both UI. Sometimes txns were routed via old UI and Sometimes via new UI.



Payzapp shifted to new UI. Even after multiple attempts only New UI OTP page is opening.
Arey hai yeh new wala dekha hu, bahot ganda sa lagta hai mujhe but UI ka 3DS 2.1 gateway se direct koi connection nahi hai.

UI toh kaise bhi design kar sakte ho but hai yeh sab Card network and TSP companies decide karti hai. Big private banks me TSP companies woh khud he hote hai.
 
Arey hai yeh new wala dekha hu, bahot ganda sa lagta hai mujhe but UI ka 3DS 2.1 gateway se direct koi connection nahi hai.

UI toh kaise bhi design kar sakte ho but hai yeh sab Card network and TSP companies decide karti hai. Big private banks me TSP companies woh khud he hote hai.
Not only difference in UI Design


My one visa card is not working on new UI on any merchant but when same merchant's gateway open old UI otp page txn goes through.

Something is different other than UI design

Also, Terminal ID is different for both UI.
Payment Gateways using different terminals. one terminal - old UI OTP page and second Terminal - New UI OTP page
 
Now I am seeing two different UI for OTP Authentication Page whenever I did txns via Visa and MasterCard.

One UI reflects 3DS 1.0.2
And
Second UI reflects EMV® 3DS 2.1 or higher ?
Recently mujhe pata chala now RuPay is developing 'NPCI BEPG SecureNxt' with EMV 3DS v2.3

Visa card ecom gateway name - Visa Secure (formerly verified by Visa),
Mastercard ecom gateway name - Mastercard ID Check (formerly Mastercard SecureCode)
JCB card ecom gateway name - JCB J/secure
UnionPay card ecom gateway name - UnionPay SecurePay (currency supported - AUD, CAD, CHF, CNY, EUR, GBP, HKD, JPY, NZD, SGD, USD)
Now RuPay's upcoming ecom gateway name - BEPG SecureNxt. 😀😀
 
Last edited:
This UI is the New UI and common across all Banks.

Earlier each bank OTP PAGE has its own Unique UI but this new UI is common in all banks.

Some gateways like Paytm is using Both UI. Sometimes txns were routed via old UI and Sometimes via new UI.



Payzapp shifted to new UI. Even after multiple attempts only New UI OTP page is opening.
This new UI is made by Payu. If any merchant is using Payu as a payment gateway, then this new interface shows for Mastercard and Visa cards issued by banks that are using Wibmo for the OTP page. Wibmo is owned by Payu; I think that's why Payu is showing their own UI for Wibmo pages.

Whereas Razorpay payment gateway shows a completely different UI.

@Abhishek012 what do you think?
 
This new UI is made by Payu. If any merchant is using Payu as a payment gateway, then this new interface shows for Mastercard and Visa cards issued by banks that are using Wibmo for the OTP page. Wibmo is owned by Payu; I think that's why Payu is showing their own UI for Wibmo pages.

Whereas Razorpay payment gateway shows a completely different UI.

@Abhishek012 what do you think?
Razorpay also redirecting to this new UI Page, when you select complete Txn on Payment Page.

Not only Razorpay other Gatways too.
Like Worldline-Ingenico and Paytm

SBI also use Wibmo for OTP Page but SBI OTP Page is same as earlier even when other Cards redirected to this New UI.
 
Koi mujh jaise noob ko simple language me smjha skta hai ki ye sunset ka kya scene hai aur mere pass Jo existing cards hai uspe mujhe kuch karna padega?
 
This new UI is made by Payu. If any merchant is using Payu as a payment gateway, then this new interface shows for Mastercard and Visa cards issued by banks that are using Wibmo for the OTP page. Wibmo is owned by Payu; I think that's why Payu is showing their own UI for Wibmo pages.

Whereas Razorpay payment gateway shows a completely different UI.

@Abhishek012 what do you think?
UI is made by technology service providers.

Wibmo is TSP
Payu is a payment gateway.

Ofcourse Wibmo is owned by Payu but the work of both is different.
 
Back
Top