3DS mobile money payment failure debug : recover your 12% lost basket
Almadies fashion e-commerce merchant, Tuesday morning, panic : "Mohamed, we lose 8% of our average basket on 3DS. On 1,200 orders per month, that is 96 baskets that never close. I do not know why and I do not know where to start." We spent 4 hours digging logs, his PayDunya webhooks and Hotjar sessions. The main culprit : an Orange Money OTP timeout at 90 seconds while his operator network pushes them at 180. Fix in 1 line of config. Revenue recovered : ~2.8M FCFA/month.
This article documents the systematic debug method for 3DS and mobile money payment failures we use on Senegalese e-commerce. Read it before hiring a 500k consultant.
The real 2026 failure rate in Senegal
From our aggregated data on 12 monitored SN e-commerces (cumulated volume 480M FCFA/month) :
| Method | Average failure rate | Range |
|---|---|---|
| Wave | 4.2% | 2.8% - 6.5% |
| Orange Money | 8.7% | 5.1% - 14.3% |
| Free Money | 11.2% | 7.8% - 18.0% |
| 3DS Visa/MC card | 14.5% | 9.2% - 22.1% |
| Weighted average | 9.8% | 7.1% - 13.4% |
A 12% average is credible if you have a lot of intl cards. Above 15%, you clearly have a technical or UX problem to fix.
Top 7 mobile money failure causes
1. OTP timeout too short (cause #1, ~28% of failures)
User receives OTP by SMS but submits it 60-120 seconds late on degraded networks. If your integration timeouts at 90s, you lose them. Configure your API calls with 180-240 seconds minimum timeout.
2. OTP not received (cause #2, ~22%)
OTP arrives late or not at all. Causes : recent SIM swap, Free Mobile operator saturated on Dakar Plateau, badly formatted number (+221 vs 221 vs 00221). Fix : strict E.164 validation client-side and USSD OTP fallback if SMS expires.
3. Insufficient balance detected late (~15%)
Client launches payment, validates OTP, and only then the operator says "insufficient balance". Frustrating. Fix : add an upstream message reminding to check balance, and a partial payment flow if your business allows.
4. SIM swap / number change (~12%)
Very common in Senegal, client changes number and forgets to update Wave/OM account. OTP goes to old number. Fix : suggest number re-verification every 6 months in your flow.
5. Transient operator error 503/504 (~10%)
Especially end of month (payday) and Friday evenings, mobile money APIs saturate. 503/504 responses. Fix : implement exponential retry (3 attempts at 5s/15s/45s) and a background reprocessing queue.
6. Merchant number temporarily blocked (~8%)
Your merchant account can be suspended 1-4h for "anti-fraud verification" if you have an unusual spike. Nobody warns you. Fix : active webhook monitoring + SMS alert to your team if 5 consecutive failures.
7. Amount formatting error (~5%)
Amount in cents vs units, comma vs dot, currency XOF vs FCFA. PayDunya accepts XOF, CinetPay too, but some legacy APIs expect a plain integer without currency. Fix : systematic backend normalization with unit tests.
Top 5 3DS card failure causes
1. Card not 3DS Secure enrolled (cause #1 ~35%)
Many Ecobank, CBAO, SGBS cards are issued without 3DS enabled by default. Client must call their bank to activate. Fix : explicit help message on "3DS not enrolled" error + redirect to issuing bank support number.
2. Card limit exceeded (~20%)
Monthly internet limit reached (often 500,000 to 2M FCFA/month on local cards). Fix : clear message "your internet limit is exceeded, contact your bank", not just "payment error".
3. 3DS authentication expired (~15%)
Visa/MC 3DS page displays, client types OTP late, session expires. Fix : pre-load 3DS page on "Pay" click without waiting backend validation, increase session timeout.
4. Country banned / geo blocking (~12%)
Acquirer blocks transactions from certain IPs/countries. Fix : if your clients are diaspora, communicate upfront they should disable VPN.
5. Expired card not detected client-side (~8%)
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Form accepts an expired date, error only appears at debit time. Fix : front-side validation with date picker locked to future dates.
The Kolonell debug method in 5 steps
Step 1 — Log instrumentation (day 1)
Before any fix, you need clarity. Log server-side for each attempt :
- Transaction start timestamp
- Method (Wave/OM/Free/Card)
- Amount
- Intermediate status (init / OTP sent / OTP validated / settlement)
- Operator error code (exact, not mapped)
- User-Agent and IP
- Elapsed time between each step
Store 90 days minimum. Without this data, debug = guessing.
Step 2 — Aggregate by cause (day 2-3)
Build a simple dashboard : top 10 error codes by method and by day. 80% of failures come from only 3-5 causes. Focus there.
Step 3 — Reproducibility test (day 4)
For each top cause, reproduce in PayDunya/CinetPay sandbox then in real prod with your own number. If you cannot reproduce, you cannot fix.
Step 4 — Fix prioritized by impact (week 2)
Calculate financial impact of each cause = (failures / month) x average basket. Fix by decreasing ROI. OTP timeout above, for example, is often 1 config line for 1-3M FCFA recovered/month.
Step 5 — Continuous monitoring (post-fix)
Set up Slack/WhatsApp alert if a method failure rate exceeds 2x its 7-day average. Failures always come back, be alerted in 15 minutes not 15 days.
Full field case : Almadies merchant, 2.8M FCFA/month savings
Audit done March 2026. Initial volume 1,200 orders/month, 78,000 FCFA average basket, 93.6M FCFA revenue. Failure rate : 16% (~15M/month lost revenue).
Top fixes applied :
- OTP timeout from 90s to 240s (Orange Money) : -3.5 points
- Exponential retry on 503 (Wave + OM) : -1.8 point
- Front-side 3DS pre-validation : -2.1 points
- Explicit balance message : -0.9 point
- Active monitoring + alerting : -0.7 point
Post-fix failure rate : 6.9%. Recovered revenue : +2.8M FCFA/month. Audit + dev cost : 1.2M FCFA one-shot. Payback : 13 days.
FAQ — Senegal e-commerce payment failures
What is an acceptable failure rate on a Senegalese e-commerce ?
Target less than 8% weighted average. Above 12%, you have a technical or UX problem to fix. The best SN e-commerces run at 5-7% with a Wave + Orange Money + 3DS card mix. Below 5%, either your volume is too small for reliable stats or you exclude some risky methods.
How to know if the failure is from my site or the operator ?
Log the exact error code returned by the API. 4xx codes (400, 401, 403) are almost always your side (formatting, auth, security). 5xx codes (500, 502, 503, 504) are operator. If 90% of your errors are 4xx, fix your code. If 90% are 5xx, set up retry + operator alerting.
Should you show a generic or detailed error message to the client ?
Detailed, always. "Insufficient balance", "Incorrect OTP", "Limit exceeded" let the client act. "Payment error, try again" generates immediate churn. Legally, you can detail without risk. UX-wise, it makes the difference between 88% and 95% retry conversion.
How much does a full payment stack audit cost for an e-commerce ?
For an SN site with 3 payment methods and 500-2000 orders/month : 800,000 to 1.8M FCFA. The audit includes log instrumentation, top cause identification, prioritized fix plan and implementation of the 3-5 top ROI fixes. Payback is usually under 30 days on sites above 30M FCFA monthly revenue.
Conclusion : 12% failure = 12% revenue to grab for free
Before scaling Ads, fix your payment failures. It is the fastest ROI lever for a Senegalese e-commerce. Each point gained = 1% additional revenue without spending an FCFA on acquisition.
For a free audit of your failure rates with numbers, WhatsApp +221 77 596 93 33 or request a quote at /en/free-quote. We review your logs within 48h.
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.
