3DS Performance | Country Metrics
India 3DS metrics
India has a pretty heavily mandated card authentication regime. Visa, Mastercard, and American Express all deprecated the original 3DS1 protocol for Indian transactions between October and November 2023, forcing a migration to 3DS2, and the card networks have since pushed the minimum further to EMV 3DS 2.2.0. On the domestic scheme side, the National Payments Corporation of India launched SecureNxt for RuPay cards in June 2024, bringing the same EMV 3DS-based authentication to India's homegrown card network.
Authentication requirements are tightening in India more broadly too, though not through a 3DS-specific rule. The RBI's Authentication Mechanisms for Digital Payment Transactions Directions, issued in September 2025, made two-factor authentication mandatory for all digital payments (cards, UPI, mobile wallets) from April 1, 2026, with at least one factor generated dynamically per transaction. The rule doesn't name a specific protocol, but for card-not-present transactions it's generally satisfied through the 3DS2 infrastructure already in place.
The data below reflects 3DS sessions for customer initiated transactions (CIT) through Evervault's own platform in India, between January 1st, 2026 and June 30th, 2026. Some results were excluded where data was incomplete or insufficient, or where sessions were configured to fail the challenge outright to reduce customer friction.
Metric descriptions
Metric | Description |
|---|---|
Success rate | The percentage of 3DS sessions that successfully authenticated the cardholder through a frictionless or challenge flow (successful authentications divided by the total number of frictionless and challenge sessions). |
Challenge / frictionless / attempt split | Of all sessions, the percentage that went through a challenge flow, the percentage that went through a frictionless flow, and the percentage resolved through an attempt flow. Attempt flows are a network-level fallback (e.g., Visa's Attempts Server) used when the issuer couldn't perform full authentication. It's not a genuine authentication decision by the issuer, so we report it separately. |
Challenge flow success rate | Of the sessions that went through a challenge flow, the percentage that successfully authenticated the cardholder. |
P50 time to completion | The median: 50% of challenge flows resolved faster than this, and 50% took longer. |
P75 time to completion | 75% of challenge flows resolved faster than this, and 25% took longer. Useful alongside P50 for seeing how quickly things start to slow down beyond the typical case. |
P95 time to completion | 95% of challenge flows resolved faster than this value. It captures how long the slowest (but still common) sessions take, without being distorted by the most extreme handful of outliers. |
Percentiles are used instead of a single average for time to completion. Completion times vary a lot depending on the authentication method, the cardholder, and the ACS. A single average would hide the gap between typical "fast" sessions and "slower" but still valid sessions. We also excluded sessions that took longer than 5 minutes to resolve. Most challenge flows are completed faster than that, and the extreme outliers (10-30+ minutes) heavily skewed the results.
Country metrics
In India, the 3DS success rate has been around 81.5%. Across all sessions, 0.26% followed a frictionless flow, 94.25% followed a challenge flow, and 5.48% were resolved through an attempt flow. When challenges did occur, they typically resolved in 23 seconds, with 95% resolving within 75 seconds.
Metric | Value |
|---|---|
Success rate | 81.5% |
Challenge / frictionless / attempt split | 94.25% / 0.26% / 5.48% |
Challenge flow success rate | 81.5% |
Time to completion for challenge flows (P50 / P75 / P95) | 23s / 32s / 75s |
Top five 3DS failure reasons
These are the top five failure reasons that we see. These are our own human readable error codes, which are easier to parse than the raw 3DS protocol statuses.
Rank | Failure reason | Description |
|---|---|---|
1 |
| The cardholder cancelled the transaction. |
2 |
| The current session configuration is not permitted for this card. For example, defining a merchant initiated transaction reason of |
3 |
| The authentication timed out. This is likely because the cardholder abandoned the transaction. |
4 |
| Typically this is due to the cardholder failing to provide the correct 3DS authentication details. This transaction should be considered as potentially fraudulent. |
5 |
| The card is not enrolled in 3DS and therefore cannot be authenticated. |
We excluded challenge-required from this list because it's not a genuine failure. It reflects sessions where a challenge was required but the session was set to fail-on-challenge to avoid forcing the cardholder through the challenge flow.
Issuer metrics
Issuer enrollment has been at 90.0% with 1.667% of transactions failing because the cards themselves aren't enrolled.
Issuer | Success rate | Challenge / frictionless / attempt split | Time to completion for challenge flows (P50 / P75 / P95) |
|---|---|---|---|
State Bank Of India | 96.6% | 50.57% / 0.0% / 49.43% | 20s / 28s / 58s |
Kotak Mahindra Bank Ltd | 93.3% | 100.0% / 0.0% / 0.0% | 20s / 28s / 67s |
Union Bank Of India | 91.7% | 47.06% / 0.0% / 52.94% | 25s / 54s / 111s |
Bobcard Limited | 90.0% | 100.0% / 0.0% / 0.0% | 25s / 31s / 49s |
The South Indian Bank Ltd | 90.0% | 100.0% / 0.0% / 0.0% | 25s / 27s / 31s |
Canara Bank | 89.7% | 100.0% / 0.0% / 0.0% | 24s / 35s / 48s |
The Federal Bank Ltd | 88.9% | 93.06% / 0.0% / 6.94% | 23s / 29s / 76s |
Icici Bank Ltd | 87.0% | 100.0% / 0.0% / 0.0% | 23s / 35s / 100s |
Idfc First Bank Limited | 86.7% | 99.19% / 0.0% / 0.81% | 19s / 28s / 58s |
Standard Chartered Bank | 83.3% | 100.0% / 0.0% / 0.0% | 23s / 32s / 55s |
Hdfc Bank Limited | 81.1% | 98.65% / 0.0% / 1.35% | 23s / 30s / 64s |
Axis Bank Limited | 76.7% | 100.0% / 0.0% / 0.0% | 20s / 28s / 62s |
Sbi Cards And Payment Services Limited | 72.2% | 98.98% / 0.0% / 1.02% | 24s / 36s / 101s |
Bank Of Baroda | 66.7% | 46.15% / 0.0% / 53.85% | 13s / 23s / 26s |
Dcb Bank Limited | 61.6% | 100.0% / 0.0% / 0.0% | 23s / 31s / 148s |
The Hongkong And Shanghai Banking Corporation Limited | 61.5% | 100.0% / 0.0% / 0.0% | 32s / 50s / 78s |
Indusind Bank Limited | 59.5% | 100.0% / 0.0% / 0.0% | 30s / 48s / 125s |
Punjab National Bank | 23.1% | 100.0% / 0.0% / 0.0% | 9s / 16s / 39s |
Card brand metrics
Visa accounts for the majority of 3DS volume in India at 83.36%. Other card brands are present, but we excluded them because their share of the volume wasn't meaningful.
Card brand | % of volume | Success rate | Challenge / frictionless / attempt split | Time to completion for challenge flows (P50 / P75 / P95) |
|---|---|---|---|---|
Visa | 83.36% | 88.6% | 95.42% / 0.32% / 4.26% | 22s / 30s / 76s |
India vs. the global average
India's success rate trails the global average significantly, at 81.5% versus 95.7%. India is far more challenge-leaning than the global average, with 94.25% of sessions going through a challenge flow compared to 22.67% globally, and frictionless authentication almost entirely absent (0.26% versus 68.36% globally). Despite the heavy reliance on challenges, India's challenge flow success rate (81.5%) is roughly in line with the global figure (81.8%). Completion times run somewhat faster than the global average across all three percentiles.
Metric | India | Global average |
|---|---|---|
Success rate | 81.5% | 95.7% |
Challenge / frictionless / attempt split | 94.25% / 0.26% / 5.48% | 22.67% / 68.36% / 8.97% |
Challenge flow success rate | 81.5% | 81.8% |
Time to completion for challenge flows (P50 / P75 / P95) | 23s / 32s / 75s | 25s / 40s / 106s |
Evervault's universal 3DS solution
If you're looking to add 3D Secure, or are having issues with your current provider, check out Evervault's 3DS solution. It's a single integration that lets you trigger 3DS on any transaction across all your payment processors.
This data reflects 3DS sessions processed through Evervault's platform only, and may not represent the broader market. It's shared for general information purposes only.
© 2026 Evervault Inc. All rights reserved.