3D Secure authentication is supposed to reduce fraud. For Indian merchants accepting international cards, it often reduces revenue instead. This guide explains exactly what happens at 3DS for international transactions on Indian payment gateways, why abandonment is so high, and what can actually be done about it.
What Is 3DS and Why Indian Merchants Get It Wrong
3D Secure (3DS) is a fraud-prevention protocol where cardholders authenticate a card transaction via a second step — typically a one-time password (OTP), biometric, or bank app confirmation.
For domestic Indian transactions: 3DS works well. Indian cardholder gets OTP on Indian phone number, enters it, transaction completes.
For international cardholders paying Indian merchants: the same flow creates a broken experience.
Why 3DS Fails for International Cards on Indian Gateways
Problem 1: The OTP Goes to the Wrong Place
When a US Visa cardholder attempts to pay an Indian merchant via a gateway that mandates 3DS, the 3DS authentication request goes to the US cardholder's bank (the card issuer). The US bank sends an OTP to the phone number on file — often a US phone number.
If the cardholder:
- Is traveling and doesn't have US mobile roaming active
- Has an outdated phone number on file with their bank
- Doesn't recognize the 3DS popup (looks unfamiliar vs US merchant checkouts) …they abandon the checkout.
Abandonment rate from 3DS friction on international cards: 20-40% depending on geography and card issuer.
Problem 2: The 3DS Page Looks Unfamiliar
US and UK cardholders are accustomed to their bank's 3DS interface in English, branded with their bank's logo. 3DS flows from Indian gateway integrations sometimes show unfamiliar interfaces, triggering "this looks like a phishing page" responses. Cardholder abandons.
Problem 3: Some International Issuers Decline 3DS Requests from Indian Merchants
Certain card issuers have settings that decline 3DS authentication requests from merchants in specific geographies or MCC categories. The cardholder never even sees the authentication page — the transaction is declined before it gets there.
Problem 4: 3DS 1.0 vs 3DS 2.0 Mismatch
3DS 2.0 introduced frictionless authentication — the card issuer can approve low-risk transactions without showing the cardholder any OTP page at all. But if your Indian gateway is still running 3DS 1.0 for international transactions, every transaction triggers a visible authentication step regardless of risk level.
Result: High-friction, high-abandonment checkout for international customers.
The Real-World Conversion Impact
Typical international checkout without 3DS friction: 65-75% conversion rate
With mandatory 3DS friction: 35-50% conversion rate
A business doing $10,000/month in international cards is potentially losing $2,500-$3,000/month in revenue from 3DS abandonment alone.
What Indian Merchants Can Actually Do
Option 1: Switch to a Gateway with International-Optimised 3DS
Gateways built specifically for international acceptance (like Playto Pay) handle 3DS differently:
- Apply risk-based 3DS: low-risk international transactions skip the friction step
- Support 3DS 2.0 frictionless flows
- Route through international card processing infrastructure that handles cross-border authentication better
Option 2: Negotiate 3DS Exemptions
In some geographies (EU primarily, under PSD2), merchants can apply for 3DS exemptions for low-risk transactions under certain thresholds. For Indian merchants processing EU cards: consult your gateway on whether exemption requests are supported.
Option 3: Accept the Friction, Optimise Messaging
If your gateway doesn't support better 3DS handling: add clear checkout messaging. "You'll receive a one-time verification code from your bank. This is a normal security step." Reduces abandonment from confusion (doesn't solve the OTP delivery problem).
FAQ
Why do my US customers abandon checkout at the verification step? 3DS authentication friction. The OTP or bank verification step is unfamiliar or difficult for international cardholders, causing abandonment rates of 20-40%.
Can I disable 3DS for international cards? Not unilaterally — 3DS requirements depend on your gateway, card network rules, and cardholder's issuer. Switch to a gateway with risk-based 3DS or frictionless 3DS 2.0 for international transactions.
Does Playto Pay have lower 3DS friction for international cards? Playto Pay's international card processing is built for cross-border acceptance with optimised authentication flows for international cardholders. Significantly lower abandonment vs domestic-first Indian gateways with mandatory 3DS.