NO-3DS Transaction

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.

Transaction Flow:

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.

Integration Enablement:

New Card Transaction Flow

1. Call “Card Info” API -Get Card details using card bin. You can also use this API to check if a card is eligible for Mandate/Subscription payments.

2. Call “Card transaction” API - Call this API using Card details and cvv provided by the customer to initiate a card transaction

Saved Card Transaction Flow

1. Call “List Card” API - List all the cards stored for a customer. This API gives back only card tokens and other metadata relevant to the cards stored against the customer.

2. Call “Card transaction” API -Call this API using card token and cvv provided by the customer to initiate a card transaction