Solutions overview
Harness the power of your data
Support and investigations
Support services for Ravelin
Online payment fraud
Account security
Policyabuse
Marketplace fraud
3DSecure
Resource Zone
Deep dives on fraud & payments topics
API & developer docs
APIs, glossary, guides, libraries and SDKs
Global Payment Regulation Map
Track PSD2 & more with a full report
Blog
The latest fraud & payments updates
Insights
In-depth guides to fraud, payments & security
About Ravelin
Discover the story about Ravelin
Careers
Join our dynamic team
Customers
Read more about our happy customers
Press
Get the latest Ravelin news
Support & investigations
Accept more payments securely
Protect your customer accounts
Policy abuse
Stop policy abuse to protect your bottom line
Ravelin for marketplace fraud
3D Secure
Ravelin 3DS & SDKs
Resource zone
Global Payment regulation map
Read more about our happy custmomers
Blog / News
From 14 March 2020, Visa expects all European issuers to have adopted 3D Secure v2.1 - what does this mean for merchants?
Share this article:
There’s a lot going on in the economic news right now so in case you missed it, Visa’s mandate for issuers to be ready for 3DS 2.1 was last Saturday 14 March 2020.
Although there are no Visa requirements for merchants to be 3DS ready, the expectation would be that they must also be v2.1 ready to support any transactions which are stepped up by the issuer.
3DS 2.1 is a huge improvement on version 1, so if issuers are prepared and want to use 3DS, it’s likely that they will use v2.1. For merchants. this could mean:
Alternatively, merchants may not see any changes, as it’s not yet mandatory for issuers to use 3DS, just to be ready for it. However, issuers do have the right to reject transactions without 3DS as they choose.
This will benefit merchants who are ready for 3DS 2.1, even if issuers are not. For example, if a merchant requests authentication through 3DS2, and the issuer is not enrolled in v2, the issuer will still take liability even though no authentication takes place.
It’s unclear what action will be taken if a Visa issuer is not ready for 3DS 2.1. Visa launched a new performance program for merchants and issuers that process transactions. Although the rules don't strictly relate to this new deadline of v2.1 adoption, they could use these to monitor overall performance by issuers.
As another example, we can look at the Mastercard 3DS 2.1 mandate for issuers (18th of October 2019). In the UK, as of 28 January 2020, there has been no enforcement action taken for Mastercard issuers not supporting 3DS 2.1.
2.1+ is a Mastercard version of 3DS in between 2.1 and 2.2. It adds some of the functionality available in 2.2 - most importantly exemptions.
By September 2020, merchants should be prepared to support the highest 3DS version supported by the issuers - v2.2. This will allow merchants to benefit from exemptions to 3DS.
31st December 2020 is the current Strong Customer Authentication (SCA) deadline, from 1st January 2021, merchants should expect to see SCA on all payments unless the issuer grants an exemption.
Jessica Allen, Head of Content
Blog / Fraud Analytics
Fraud prevention is a delicate balance between stopping fraud and maintaining good customer experiences. But what is the most effective way to measure this outcome?
Ravelin Technology, Writer
Blog / Machine Learning
Online payment fraud is one of the biggest threats facing grocery merchants. And it’s only gotten worse. How are fraudsters using the cost of living crisis to take advantage of your business?
There’s a new fraud threat on the rise – and it’s your customers. First-party fraud is infamously tricky to catch and a huge revenue risk. How can you detect and deter criminal behavior in your customer base?