The verdict in three sentences
In Nairobi as everywhere, approving a sale on a payment screenshot is an open door to fraud: a screenshot is edited in thirty seconds. Fake-receipt fraud hits 2 to 5 % of transactions approved by eye, an invisible but real cost. The only reliable defense is to verify status server-side (webhook + API call), which brings fraud to near zero, for a module of 300,000 to 700,000 FCFA.
Why a screenshot proves nothing
A receipt shown on screen is just an image: amount, name, reference and timestamp are all editable. A seller trusting the eye sometimes approves a payment that never happened, or an old recycled receipt. Only the provider's source of truth counts.
| Fake-receipt signal | What the seller sees | Server truth |
|---|---|---|
| Edited amount | Right amount on image | No transaction |
| Recycled receipt | Yesterday's payment | Reference already used |
| Wrong beneficiary name | Your name shown | Funds never received |
| Modified timestamp | Today's date | No trace at provider |
| Pending shown as success | Success on image | Actually pending |
The verification that cuts fraud
The rule is simple: never release goods without server confirmation. The webhook notifies the payment, an API call verifies the status, and a unique reference per order blocks the reuse of an old receipt.
| Control | What it blocks | Effect on fraud |
|---|---|---|
| Provider webhook | The nonexistent payment | Fraud / 10 |
| API status check | The edited receipt | Certain confirmation |
| Unique reference / order | The recycled receipt | Automatic rejection |
| Exact amount matching | The wrong amount | Gap flagged |
| Delay before release | Haste | Control window |
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.
Wanjiru runs a shop in Nairobi and collects 3,000,000 FCFA/month, often approving on a screenshot during rush hours. With 3 % fake receipts, she loses 90,000 FCFA/month of goods handed over with no real payment. Moving to systematic server verification, that loss drops to under 5,000 FCFA/month. A 500,000 FCFA module pays back in under six months on avoided fraud alone, not counting time saved.
FAQ
Can an M-Pesa or MoMo screenshot really be fake? Yes, trivially: any editing app changes amount, name and date. An image receipt has no evidentiary value without server confirmation.
How do I verify without slowing the sale? The webhook confirms in seconds; the API status call is instant. The check is faster than manually reading a receipt, and far safer.
How much does an anti-fake-receipt module cost? Budget 300,000 to 700,000 FCFA depending on providers and integration with your existing till or store.
How do I stop reuse of an old receipt? Through a unique reference per order, server-side: an already-used receipt is rejected automatically, even if the image looks perfect.
Does this work in physical retail? Yes: at the point of sale, we show the confirmed status on the till screen before releasing goods. No more eye validation on the customer's phone.
Let's talk about your project. We wire server-side verification of your M-Pesa and MoMo payments to kill fake-receipt fraud. 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.
