3D Secure 2 | Braintree Payments

3D Secure 2

Adding 3D Secure 2 to your checkout can help ensure security for your customers and help protect your business against fraudulent transactions.

The next-generation authentication solution

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. Braintree’s 3DS2 solution is easy to integrate and provides a simple way to authenticate eligible card transactions with a low-friction checkout experience for cardholders.

Questions about SCA or how to prepare for the September 14, 2019 deadline?

Check out our merchant resources

KEY ENHANCEMENTS TO 3DS2

Provides a more seamless mobile experience with native SDKs for both Android and iOS

Uses device and browser data for more accurate risk assessments that typically happen behind the scenes rather than requiring cardholder involvement

Offers better, more secure methods to replace static passwords in the rare event of a challenge

Helps meet SCA requirements for biometrics and two-factor authentication (2FA)

Shift chargeback liability

For eligible cards, 3DS2 can move liability for chargebacks due to fraud from the merchant to the card issuer.

Lift authorization rates

Data shows that issuers may approve more transactions when using 3DS2 (vs. 3DS1).

70%

decrease in cart abandonment¹

85%

reduction in transaction time²

1-2. Frictionless Experience with Verified by Visa, Visa, 2018.

How Braintree’s 3DS2 solution works

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 card

Merchant tokenizes the customer card or uses the previously tokenized card

Merchant requests authentication insight

Optional: Merchant requests authentication insight, Braintree's guidance on SCA applicability
Braintree advises if SCA is required or recommended

Merchant initiates 3DS

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 creates transaction

Merchant initiates the verification or authorization

Merchant resources

SCA requirements have been the source of a lot of questions -- and a lot of uncertainty -- for merchants who do business in affected countries. We’ve put together some resources to help you understand these requirements and prepare your business.