The verdict in three sentences
On mobile, 3D Secure 2 (3DS2) breaks a significant share of card payments through the redirect to the bank, the OTP not received, and drop-off in a secondary tab. The observed failure rate sits around 12–18 %, but a good part is recoverable with a wallet fallback, a clean retry and clear messaging. Every payment lost at 3DS is an already-won sale evaporating at the last second — the point in the funnel where optimization pays back the most.
Frequent causes of mobile 3DS failures
Most failures are not real bank declines but experience breaks. Identifying them lets you target remediation.
| Cause | Symptom | Estimated share of failures |
|---|---|---|
| OTP SMS not received / late | Customer waits, expires | 30–40 % |
| Failed bank-app redirect | Broken return to merchant | 15–25 % |
| Drop-off in secondary tab | Session lost | 10–20 % |
| Insufficient balance | Real decline | 10–15 % |
| Card not 3DS-eligible | Issuer rejection | 5–10 % |
| Network timeout (3G) | Page stuck | 5–10 % |
These proportions are a 2026 order of magnitude: instrument your checkout to measure your own, since the mix varies by issuing bank and network quality.
Remediation and business impact
Each remediation lever has a measurable effect on the final conversion rate. Here is the estimated impact on a basket of failed payments.
| Lever | Expected effect | Effort |
|---|---|---|
| Wallet fallback (Wave/OM) | +30 % of failures recovered | Medium |
| Guided immediate retry | +10–15 % recovered | Low |
| Clear error message + prompt | +5–10 % recovered | Low |
| Open 3DS in the same tab | Fewer drop-offs | Medium |
| Cart recovery (email/SMS) | +5 % deferred | Medium |
| Longer timeout + network retry | Fewer 3G failures | Low |
The cost of a lost payment is not only the sale's margin: it is also the acquisition budget already spent to bring that customer to the pay button.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Aïda runs an online shop in Dakar with 400 card payment attempts per month and an average basket of 25,000 FCFA. At a 15 % 3DS failure rate, she loses 60 payments, i.e. 1,500,000 FCFA in potential sales evaporating each month. By adding a "pay with Wave" backup button (+30 % of failures recovered) and a clear error message with retry (+10 %), she recovers about 24 payments, i.e. 600,000 FCFA/month regained for a modest development effort.
FAQ
Does a 3DS failure mean the card is declined?
Rarely: most failures are experience breaks (OTP not received, broken redirect), not bank declines. That is why so many payments are recoverable with a simple fallback.
Does a wallet fallback complicate checkout?
Little, if the aggregator already exposes Wave and Orange Money. You show the wallet as backup as soon as a card payment fails, without forcing the customer to re-enter everything.
Should you auto-retry on a 3G timeout?
Yes, with a controlled retry and a longer timeout suited to slow connections. In the African market, a share of failures comes purely from network latency at the moment of redirect.
How do I measure my real 3DS failure rate?
Instrument every step of the card funnel: initiation, redirect, return, confirmation. Without those events, you conflate voluntary drop-offs with technical failures, and you optimize blind.
Let's talk about your project. We instrument your card funnel and wire a Wave fallback to recover much of your 3DS failures. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
