Contact us

To help us direct you question to the best team to provide an answer please select which option best descibes you.

  • I would like to speak to someone about setting up a new account
    Next
  • I'm an existing customer and need help with my account
    Next
  • I’m looking to integrate payments to my software platform or application
    Next
  • I’m a member of the media
    Next

All you need for 3D Secure version 2

Secure Customer Authentication delivered at the highest standard

3DS-2 SCA

3D Secure v2

In September 2019, new requirements for authenticating online payments were rolled out in Europe as part of Payment Services Directive 2 (PSD2). A new set of technical standards required for payment authentication known as Strong Customer Authentication (SCA), designed to help reduce fraud and increase security for end users.

The PSD2 mandate is now fully in place across the EEA and the UK will be enforced starting 14th March 2022.

What You Need To Know

One of the most important changes to come with the introduction of PSD2 is the implementation of 3D Secure v2, a mandatory update to the 3D Secure payment processing system from EMVCo.

The goal of 3D Secure v2 is to enable “frictionless authentication” with mobile support, biometric validation, and streamlined checkout experiences for the customer, resulting in fewer abandoned carts and a better conversion rate for eCommerce businesses.

To help you with the process we’ve updated our Development Centre with an Introduction to 3D Secure v2.

Visit the Development Centre

PDS2 3D Secure

Strong Customer Authentication (SCA)

In order to accept payments under the new European SCA requirements,
you need to ensure your customer can authenticate for a payment using two of the following:

3DS-2 Password & Pin

Something They Know

A password, a PIN code, a security question.

Mobile & Hardware Token

Something They Have

A mobile phone or a hardware token.

Fingerprint & Facial Recognition

Something They Are

A fingerprint or facial recognition.

3DS2 will allow you to process transactions using the above,handle exemptions from
SCA transactions in different business models, and work with more complex payment use cases.

Find Out More

What You Need To Do

The PSD2 mandate started in September 2019, since when we have been working with merchants to implement 3DS v2 as soon as possible.

The standard is now required in Europe for all merchants, so ensure you are up to date with your integration as required by each financial authorities of the EU regions in which you operate. The risk is that transactions authorisations will be declined where 3DS v2 is not used to authenticate the transaction.

Active monitoring and suspension of merchants who have not yet updated to 3DS v2 began in December 2020 for EEA regional merchants and will start from 14th March 2022 for UK based merchants.

Soft declines are increasing across all markets, with issuers ramping up their stand-up processes for Strong Customer Authentication. From August 2021, soft decline transactions must be resubmitted using 3DS v2.

If you need more information or if you have any concerns, please get in touch with your Partner Manager, and read our post 2 below.

Do merchants have anything to fear from 3DS 2?

3DS-2 Deadline

Timeline

From 1st February 2020, we expect issuers will begin to enforce transactions using risk-based authentication and one-time passwords (OTP)

14th March 2020 - “Visa are Mandating for all EEA Card issuers to support 3DS2 by March 14, 2020 so we highly recommend that you have your 3DS2 Technology in place to start Strong Customer Authentication”

31st December 2020 -  “European Banking Authority announced SCA enforcement date as of the 31st December 2020. Countries across the EEA are generally expected to follow this new timeline”

3DS 2.2 mandate needs to be implemented by 31st December 2020

Active supervision and monitoring will begin on 31st December 2020

14 March 2022 – FCA expected enforcement date for the UK for SCA

Should you have any other enquiries, check our FAQs or please contact us.

Paysafe – London
UK: 0800 294 1404INT: +44 (0) 118 928 5075
e: uk.customerservice@paysafe.com

Integration

Plug and Play
Easy set up and connection to a range of tailor made and customisable payment solutions

24hr Support
Dedicated technical and customer support, whenever you need it.

A Single API
One API giving you access everything, from payment acceptance to wallets and APMs.

Our latest thinking

Silent suffering: the case for better supporting men in the workplace

Nov 25, 2021 - Keep an eye on the men in your life: they could be suffering more than you know.

  • Giacomo Austin, VP Compliance Strategy & Advisory
Read more

Keep an eye on the men in your life: they could be suffering more than you know.

Read more
Why next-generation payments are the key to taking open banking to the next leve…

Nov 23, 2021 - Both consumers and merchants have proved they’re eager for change in financial services, but what we’ve seen since PSD2 is just the beginning. We look beyond the opening up of APIs to see what sort of next-generation payments will satisfy demand as innovation in open banking gains pace.

  • Udo Mueller, CEO paysafecard
Read more

Both consumers and merchants have proved they’re eager for change in financial services, but what we’ve seen since PSD2 is just the beginning. We look beyond the opening up of APIs to see what sort of next-generation payments will satisfy demand as innovation in open banking gains pace.

Read more
A day for reflection: Trans Day of Remembrance

Nov 18, 2021 - As the fight for trans equality and acceptance rages on, it’s important we spend time reflecting on how far we’ve come, and those we’ve lost along the way.

  • Samuel Riggs, Global Corporate Social Responsibility Manager
Read more

As the fight for trans equality and acceptance rages on, it’s important we spend time reflecting on how far we’ve come, and those we’ve lost along the way.

Read more

Let's Get Started

This field is mandatory.
This field is mandatory.
This field is mandatory.
This field is mandatory.
This field is mandatory.
This field is mandatory.
This field is mandatory.
This field is mandatory.
loading...