News and insights

After 24 September 2024, no transactions authenticated using EMV 3DS 2.1 can be processed.

In addition, Mastercard has also announced a requirement to support extra EMV 3DS features:

• All ecommerce businesses must support and perform authentication app re-direction through the merchant app, the 3DS SDK and EMV 3DS v2.2 transactions if the cardholder authentication method is out of band (OOB).
• 3RI payments are optional, however they offer you the ability to system-generate a payment transaction when the cardholder is not in session. These transactions are used when there is an initial purchase while the cardholder is in session, called consumer-initiated transaction (CIT), followed by subsequent transactions that are 3RI merchant-initiated transaction (MIT). With 3RI payments, you can keep your fraud liability protection for the full amount authenticated by using the DS Transaction ID field. This proves that strong customer authentication (SCA) was used when the customer was involved

In addition to the sunset of EMV 3DS 2.1, a number of card schemes have indicated they intend to support EMV 3DS 2.3.1 during this year and have urged participants to prepare to start authentication using EMV 3DS 2.3.1.

What you need to do:

Be aware that after 24 September 2024, no transactions authenticated using EMV 3DS 2.1 can be processed.

Contact your gateway support team to:

• Avoid declined transactions and potential fines
• Make sure they are correctly supporting EMV 3DS 2.2 in line with the card scheme rules.
• Make sure they are aware of the approaching sunset date for EMV 3DS 2.1

Visa announced several changes to the Visa Secure Program including 12 extra required data fields, to be effective earlier this year. Following feedback from the industry, Visa has changed the requirements, reducing the number of required data fields from 12 to five for browser transactions or three for in-app purchases.
 

From 12 August 2024, Visa will need the following data fields to be included in authentication:

These new data fields apply only to standard 3DS payment transactions. Non-payment transactions and 3DS requestor-initiated (3RI) transactions are exempt from these requirements.

What you need to do:

Make sure your 3DS provider is aware of this rule and is making any changes needed to meet the demand by 12 August.

Visa has requested all acquirers in Europe to provide guidance and clarity to car rental merchants around card acceptance.
 

If you accept Visa, you can accept all types of Visa cards, including Visa Debit, without requiring any updates or modifications to your existing merchant service agreement or payment terminal. According to the Visa Rules, all Visa cards have to be treated on equal terms, including Visa Debit. Please make sure your Terms & Conditions reflect this policy.
 

Visa Debit and Visa Credit cards work similarly. Visa Debit also supports pre-authorisations for both rental services and potential damages.
 

All you need to do is:

• Inform the cardholder about potential additional transactions and obtain their consent before pre-authorisation, mirroring the process used with a Visa Credit card.
• Clarify to the cardholder that the pre-authorisation will temporarily restrict the account balance of Visa Debit card or the credit line of Visa Credit card. Ensure there are sufficient funds available in their account – otherwise the pre-authorisation will not be successful.

By following these guidelines, you can minimise potential issues and provide a seamless payment experience for your customers.

What you need to do: 

Visa provided several guides to help car rental merchants, please see below links:

Short Version – this can be shown at the merchant’s front desk or customer-facing areas

Medium Version – Provides additional details and guidance to merchants