Screenshot payment fraud drains African merchants daily. Learn how to verify every mobile money payment against the operator SMS and lock each code forever.
— reads
Every day, merchants across Africa lose real money to edited payment screenshots. A customer sends a doctored image of an M-Pesa, Orange Money or Airtel Money confirmation, the merchant releases the goods or the service, and the payment turns out never to have happened. The root problem is deceptively simple: the merchant is trusting a customer-side artifact. A screenshot is a picture, and pictures can be edited in seconds with a free phone app. Screenshot payment fraud is not a sophisticated hack — it is a Photoshop job, and it works precisely because busy sellers have no fast way to check the truth.
KODA flips the trust model completely. Every mobile money operator already sends the merchant a confirmation SMS or notification the moment a payment lands. That message — not the customer's screenshot — is the ground truth, because it comes from the operator's own system to your own phone. When you learn how KODA works on How KODA verifies mobile money payments, you see the core move: the platform matches the customer's reference code against the confirmation that arrived on the merchant's device, and returns a verdict in about three seconds. There is no telco API to license, no contract to sign, and no integration to build before you can start.
Here is the step-by-step flow in practice. The customer pays you the normal way and reads you their transaction reference code. You submit that code to KODA — by typing it into the Manual Console, dropping it into a WhatsApp thread, sending a USSD string, or letting the checkout collect it. The KODA Sentinel Android app, running quietly on the merchant phone, reads the incoming operator SMS and forwards it to the engine automatically. The engine cross-checks the code, the amount and the sender against that real confirmation. If everything lines up, you get a green verdict. If the code does not exist, or the amount is wrong, you get a rejection before any goods leave your hands.
The single biggest win is permanent replay protection. Once a reference code is verified, it is locked forever, across every channel at once. Nobody can pay you a single time and then reuse that same code for a second order, a third order, or at a different till. For high-volume sellers in the sectors covered on KODA for restaurants, retail, schools & marketplaces, this one feature eliminates the most common street-level fraud: the recycled receipt. A code that has already been spent is dead on arrival, whether the fraudster tries the Manual Console, the API, or WhatsApp.
Merchants defeating screenshot fraud usually stop making three mistakes. The first is accepting a screenshot as proof at all — a screenshot proves only that someone can operate an image editor. The second is confirming payment by eye instead of by reference code, which lets a scammer flash a real-looking amount that never actually moved. The third is relying on the customer's word about timing; a payment that is still pending, reversed, or sent to the wrong number can look identical to a good one in a screenshot. Verifying the code against the operator's own confirmation removes all three blind spots at once.
What makes KODA genuinely different is that it never touches your money. It is not a bank, a wallet, or an escrow service. It does not move, hold, or handle a single franc or shilling — it only tells you, truthfully and instantly, whether a payment that the customer claims to have made actually happened. On top of the core match, the engine adds anti-forgery checks on the device SMS stream, fraud scoring with velocity rules, and screenshot forensics for the cases where a customer insists on sending an image. You keep your existing mobile money numbers and your existing workflow; you simply gain a truth check.
If you sell to the public, the maths is unforgiving: even one faked payment a week can erase the margin on dozens of honest sales. Fixing it does not require new hardware or a developer. To see the full verification flow, read How to Verify an M-Pesa Payment Without a Telco API, and to understand how spoofed confirmations are caught, read How KODA Catches Fake Payment SMS. When you are ready, head to Get started with KODA free and verify your first mobile money payment free — the next screenshot a customer sends you should be met with a code check, not a leap of faith.
Yes — screenshots are trivial to edit. That is exactly why KODA never trusts a screenshot alone and verifies the code against the merchant’s own operator confirmation SMS.
KODA locks every verified reference code permanently. A second attempt with the same code is rejected instantly — see How KODA verifies mobile money payments.