The verdict in three sentences
Orphan payments — money in with no matching order — silently distort your revenue and stock levels. In 2026, they average 2 to 5 % of a merchant's mobile-money transactions. Ignoring them widens a cumulative gap; a weekly exception queue resolves them in 24 to 72 hours.
Orphan causes
A payment ends up unmatched for very concrete reasons. Identifying the cause dictates the fix: refund, allocate, or chase the customer.
| Cause | Estimated 2026 frequency | Typical fix |
|---|---|---|
| Double-tap (paid twice) | 1 to 2 % of tx | Refund the duplicate |
| Wrong reference entered | 1 to 1.5 % of tx | Allocate manually |
| Partial payment | 0.5 to 1 % of tx | Chase the balance |
| Order cancelled after payment | 0.3 to 0.8 % of tx | Refund |
| Divergent Moov/MoMo reference format | Variable | Normalize the key |
| Test / wrong amount | Rare | Refund |
The resolution workflow
An exception queue only helps if each orphan follows a clear path with a deadline. Here is the target workflow, from spotting to closing the exception.
| Step | Action | Target delay | Decision |
|---|---|---|---|
| 1 | Spot the orphan | Weekly | — |
| 2 | Identify the cause | 24 h | Refund / allocate |
| 3 | Contact customer if needed | 48 h | Per response |
| 4 | Apply the fix | 72 h | Close |
| 5 | Log the resolution | Immediate | Traceability |
The key decision is refund vs allocate: if the customer has a pending order at the right amount, allocate; if there is no counterpart, refund within the 72-hour window to avoid disputes.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Fatou sells fabric online in Johannesburg, with 1,500 transactions a month across two wallets. She noticed an unexplained monthly gap of around 90,000 FCFA. Setting up a weekly exception queue, she found 3.5 % of her transactions were orphans: mostly duplicates (to refund) and wrong references (to allocate). Within six weeks, her monthly gap fell below 8,000 FCFA, and two customer disputes were avoided thanks to refunds within 72 hours.
FAQ
What share of transactions is normally orphaned? In 2026, a mobile-money merchant commonly sees 2 to 5 % unmatched transactions. Above 5 %, look for a structural problem: a misconfigured reference format or a faulty payment funnel.
Should I refund or allocate an orphan? If the customer has a pending order at the exact amount, allocate the payment. Otherwise, refund within 72 hours to stop an unhappy customer from opening a dispute with the operator.
Why do duplicates happen? The "double-tap" occurs when a customer, thinking the payment failed, retries. It accounts for 1 to 2 % of transactions and is fixed by refunding the duplicated amount.
Is a weekly queue enough or do I need real time? For most SMEs, a weekly review within a 72-hour resolution window is enough. Real time is only justified beyond several thousand daily transactions.
Let's talk about your project. We set up your exception queue to eliminate orphan payments. 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.
