Introduction

What is 3D Secure?

3D Secure (3DS) is a security protocol that was developed to provide an additional layer of security for online credit/debit card transactions. It allows an issuing bank to authenticate their cardholders during a card-not-present (CNP) transaction. If the authentication is successful, then liability for fraudulent transactions shifts away from the merchant to the card issuer, which reduces chargebacks to the merchant.

Nuvei supports 3DS v2 (3DS2), which supports all major card networks and is accessible through more devices and platforms including integration with a mobile number that uses a secure passcode for transaction verification.

For more details, see the 3DS Explained topic.

What’s the easiest way to implement 3DS into my payment flows?

The best practice is to use one of the Nuvei out-of-the-box, end-to-end solutions for 3DS, for example Nuvei Web SDKs or the Nuvei Payment Page.

These solutions take all the hard work out of implementing 3DS and manage all the 3DS requirements along the entire payment flow, both on the client side and server side.

What if I want to handle some or all of the 3DS steps myself?

No Problem!

Refer to the 3DS Implementations topic for Nuvei’s range of 3DS enabled implementations.

Taking the “Hard Work” Out of 3DS

Nuvei solutions take the “hard work” out of implementing 3DS:

• Our streamlined implementations accelerate 3DS implementation.
• Helps you comply with PSD2 mandates in EEA countries whilst utilizing maximum exemptions flow and balancing conversion with security.
• Dynamic decision-algorithms optimize real-time transaction processing by:
  • Classifying “out of scope” transactions to smoothly route them through a non-3DS flow and avoid redundant churn.
  • Leveraging strong customer authentication exemptions to maximize conversion rates.
  • Using authentication challenges, in the face of moderate risk to push for higher conversion rates.
  • Allowing automated re-submission for Soft Declines with a challenge request to keep you compliant and save loss.
  • Rejecting risky transactions or Challenge them to ensure payment account ownership.

Next Steps

• For more detailed 3DS definitions, refer to 3DS Explained.
• To implement 3DS, refer to 3DS Implementations.
• For some additional 3DS function, refer to 3DS Functions.