3DS Transaction

Introduction

A 3DS (3D Secure) transaction is an online payment authentication protocol designed to enhance security and reduce fraud during card-not-present transactions. 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.

Transaction Flow:

Advantages:

• Enhanced Security: Adds an extra layer of authentication to verify the cardholder's identity, reducing fraud risks.

• Liability Shift: Shifts liability for chargebacks from merchants to the issuing bank, offering merchants protection against fraudulent transactions.

• Regulatory Compliance: Meets regulatory requirements, such as PSD2 SCA (Strong Customer Authentication), ensuring adherence to global payment standards.

• Increased Customer Trust: Provides customers with confidence in the security of their transactions.

• Support for High-Risk Transactions: Ensures secure processing even for high-value or high-risk payments.

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