--- page_title: No-3DS support for Card Payments product: Resources - Global page_source: https://juspay.io/sea/docs/resources-global/docs/no-3ds-protocol/no3ds-support-for-card-payments llms_txt: https://juspay.io/sea/docs/llms.txt product_llms_txt: https://juspay.io/sea/docs/resources-global/llms.txt --- # 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 | Gateway | Type of Transactions | |---|---| | 2C2P | New card transactions, saved card transactions, mandate | | Midtrans | | | Dlocal | | | Stripe | | | Payfort | | | Checkout | | | Worldpay | | | HyperPG (Juspay) | | | Adyen | | ## 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** ![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/resources-global/Screenshot%202024-12-03%20at%204.26.31%E2%80%AFPM.png) ## Integration Changes and Workflow --- ## Integration type : Juspay HyperCheckout (Payment Page) ### Substep **Integration Changes:** No changes required wrt Integration. **Work Flow:** * Enable No-3DS support for the eligible gateway via Juspay dashboard. * Juspay routes the transaction to the underlying No-3DS supported gateway for processing. * Upon completion, Juspay updates the merchant with the transaction status through the Order Status API and webhooks. > **Note** > * During UAT testing, test the Cred Offer on CUG using your app/website pointed to Juspay Sandbox. > > * CUG testing guide: [Link](https://juspay.io/in/docs/offer-engine/docs/issuer-offers/cug-testing) --- ## Integration type : Juspay Express Checkout SDK ### Step 1.1. Substep **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](https://juspay.io/sea/docs/resources-global/docs/no-3ds-protocol/create-order-apiorders), pass the parameter `metadata.txns.allow_card_no_3ds=true` and is mandatory * During the transaction initiation using [Juspay Process SDK payload](https://juspay.io/sea/docs/resources-global/docs/no-3ds-protocol/process-sdk-payloadcards), pass the parameter `authType=NO_THREE_DS`and is mandatory * Once the transaction is completed, Juspay will send the transaction status in order status response and webhooks --- ## Integration type : Juspay Express Checkout API ### Step 1.1. Substep **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](https://juspay.io/sea/docs/resources-global/docs/no-3ds-protocol/create-order-apiorders), pass the parameter `metadata.txns.allow_card_no_3ds=true` and is mandatory * During the transaction initiation using [Juspay Transaction API(/txns)](https://juspay.io/sea/docs/resources-global/docs/no-3ds-protocol/card-transactiontxns), pass the parameter `auth_type=NO_THREE_DS`and is mandatory * Once the transaction is completed, Juspay will send the transaction status in order status response and webhooks > **Note** > If you are using single API to create a order and initiates the transaction consecutively, then No-3DS parameters are required to be passed in [order create with payments API](https://juspay.io/sea/docs/resources-global/docs/no-3ds-protocol/create-order-with-payments) --- ## See Also - [Steps for QA (Integrating Merchants)](https://juspay.io/sea/docs/resources-global/docs/merchant-testing/steps-for-qa-integrating-merchants)