NO-THREE DS PROTOCOL

Introduction

3DS authentication is typically recommended for transactions as it provides an extra security layer, enabling issuing banks to verify the cardholder’s identity. This process also shifts liability from the merchant to the issuer. However, 3DS can introduce friction points, such as OTP entry failures or bank page errors, which may lower transaction success rates.

To mitigate these issues, merchants may choose No-3DS transactions(skip 3DS authentication) for specific cases, using risk-based assessments such as customer purchase history, order value, or other criteria.

Risk management is critical in No 3DS transactions, as bypassing 3DS can increase the likelihood of chargebacks, placing greater responsibility on the merchant.

Advantages:

• Improved Conversion Rates: Reduces friction during checkout, leading to higher transaction success rates.

• Faster Payment Processing: Eliminates the need for additional authentication steps, providing a smoother and quicker payment experience.

• Enhanced User Experience: Simplifies the checkout process, especially for repeat customers, reducing abandonment rates.

• Increased Flexibility: Allows merchants to apply risk-based rules to selectively bypass 3DS for trusted users or low-risk transactions.

• Better Retention of Repeat Customers: Encourages repeat purchases by offering a hassle-free payment experience for known, trusted users.

• Liability Shift Control: Empowers merchants to balance risk and user experience by selectively choosing when to bypass liability transfer to issuers.

Gateway Supported list

Pre-Requisites

• Enable No-3DS support on the gateway/PSP side.

Dashboard Configuration

Enable the No-3DS flow for supported gateway under PG Control Center section on the Juspay dashboard.

• Login to Juspay dashboard → Navigate to Payments tab → Select PG Control Center → Select the No-3DS supported gateway → Go to Payment method configurations -> select Advanced Features and enable No-3ds toggle

Integration Changes and Workflow

Integration Changes:

Merchant must pass No-3DS parameters in the order creation and in the process SDK payload to intimate Juspay to initaite No-3DS transaction

Work Flow:

• Enable No-3DS support under required gateway on Juspay dashboard

• While creating the Order at Juspay using Juspay Order Create API, pass the parameter metadata.txns.allow_card_no_3ds=true and is mandatory

• During the transaction initiation using Juspay Process SDK payload, pass the parameter authType=NO_THREE_DSand is mandatory

• Once the transaction is completed, Juspay will send the transaction status in order status response and webhooks