The verdict in three sentences
An unprocessed payment webhook is a ghost order: the customer paid but your system ignores it, or worse, they pay twice. Without recovery, 2 to 5 % of webhooks are lost and double-charging generates 3 to 6 % of disputes. Idempotency, fallback polling and daily reconciliation bring that figure under 1 %.
The three pillars of a reliable webhook
A webhook is not reliable by nature: the network drops, the operator retries, your server restarts. Three mechanisms make the system robust.
| Pillar | Role | 2026 rule |
|---|---|---|
| Idempotency key | An event processed once only | Mandatory, per transaction |
| Signature verification | Reject fake calls | Window < 5 min, shared secret |
| Fallback polling | Catch missed webhooks | Every 60 s for 30 min |
| Queue | Absorb spikes and retries | Exponential retry |
| Event log | Audit and replay | 90-day retention |
The idempotency key is the central pillar: it guarantees that the same event, received twice, creates only one order and one charge. Without it, operator retries become double charges.
What reliability keeps you from losing
Every missed webhook has a direct cost and a reputation cost. Here is the quantified impact (2026 order of magnitude).
| Problem | Without mechanism | With mechanism |
|---|---|---|
| Lost webhooks | 2 to 5 % | < 0.5 % |
| Unconfirmed orders | 2 to 5 % | near zero |
| Double-charge disputes | 3 to 6 % | < 1 % |
| Confirmation delay | variable | < 60 s (polling) |
| Reconciliation time | manual, hours | automatic, minutes |
Fallback polling queries the operator every 60 seconds when the webhook fails to arrive, and daily reconciliation compares your orders against operator statements to catch the last gaps.
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
David runs a booking platform in Nairobi handling 1 500 payments/month at 15 000 FCFA (about 25 USD) average, or 22 500 000 FCFA. With 4 % lost webhooks, 60 orders/month go unconfirmed and 4 % double-charge disputes cost him roughly 540 000 FCFA/month in refunds and support. He adds an idempotency key, 60 s fallback polling and daily reconciliation. Unconfirmed orders fall to near zero and disputes under 1 %. He recovers about 480 000 FCFA/month and removes hours of manual support.
FAQ
What is an idempotency key? It is a unique identifier attached to each payment attempt. If your server receives the same event twice, the key guarantees only one order and one charge are recorded.
Why fallback polling if webhooks exist? Because 2 to 5 % of webhooks are lost (network, restart). Querying the operator every 60 seconds for 30 minutes catches those cases without leaving the customer in limbo.
How long should I keep event logs? Keep them at least 90 days. It lets you replay an event after a bug and justify a transaction during a dispute with an operator or customer.
How do I verify a webhook signature? Compare the sent signature with one computed from your shared secret, and reject any call whose timestamp is older than 5 minutes. That blocks malicious replays.
Can reconciliation be automated? Yes. A daily job compares your orders against operator statements and flags gaps. It turns hours of manual matching into a report of a few minutes.
Let's talk about your project. We make your payment webhooks idempotent and reconciled to eliminate ghost orders and double charges. 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.
