Adding 3D Secure 2 can help ensure a secure checkout for your customer, protect your business against fraudulent transactions, and keep your transactions compliant with strong customer authentication (SCA) requirements.
3D Secure 2 (3DS2) is the new industry standard for customer authentication and is a recognized solution for meeting PSD2’s Strong Customer Authentication (SCA) requirements. ReThink Pay 3DS2 solution is easy to integrate and provides a simple way to authenticate eligible card transactions with a low-friction checkout experience for cardholders.
Provides a more seamless mobile experience with native SDKs for both Android and iOS
Offers better, more secure methods to replace static passwords in the rare event of a challenge
Uses device and browser data for more accurate risk assessments that typically happen behind the scenes rather than requiring cardholder involvement
Helps meet SCA requirements for biometrics and two-factor authentication (2FA)
For eligible cards, 3DS2 can move liability for chargebacks due to fraud from the merchant to the card issuer.
ReThink Pay solution supports exemptions that will be available under SCA requirements, so your customers can experience the least possible amount of friction on applicable transactions
Data shows that issuers may approve more transactions when using 3DS2 (vs. 3DS1).
With built in support for both 3D Secure 1 and 2 authentication protocols, ReThink Pay Paycan help ensure your transactions meet SCA requirements.
decrease in cart abandonment1
reduction in transaction time2
3D Secure 2 is an additional fraud protection layer for online credit and debit card transactions that adds an authentication step for customers making online purchases.
Merchant tokenizes the customer card or uses the previously tokenized cardd
Optional: Merchant requests authentication insight, Braintree's guidance on SCA applicability
ReThink Pay Payadvises if SCA is required or recommended
Optional: Merchant decides to request exemptions; three possible outcomes:
1) exemption applied,
2) exemption not applied and no challenge, or
3) exemption not applied and challenge
Merchant does not request exemptions; two possible outcomes:
1) issuer issues challenge or
2) issuer does not issue challenge
Merchant initiates the verification or authorization
SCA requirements have been the source of a lot of questions -- and a lot of uncertainty -- for merchants who do business in affected countries/regions. We’ve put together some resources to help you understand these requirements and prepare your business.
PSD2: Strong Customer Authentication Explained
What is 3D Secure 2?
How SCA Applies to Common Payment Scenarios
Ready to integrate? Our newest front-end SDK is built to support all 3DS2 authentication paths.