When an operator reverses a mobile money payment, KODA parses the reversal SMS and fires a payment.reversed event — so you're the first to know, not the last.
— reads
Occasionally an operator reverses a mobile money payment after it has been confirmed — a correction, a dispute, a fraud claw-back on the network's side. It is rare, but when it happens a merchant who does not find out quickly can ship goods or release a service against money that is no longer there. KODA's reversal detection exists to make sure you are the first to know, not the last: when the operator sends a reversal message, KODA reads it and fires a payment.reversed event straight away.
The mechanism is the same one that powers everything else — the operator's own SMS. Just as a confirmation message proves a payment happened, a reversal message proves it has been undone, and KODA parses that reversal the instant it reaches the merchant's phone. The order is flagged, the previously verified payment is marked reversed, and any system listening on a webhook is notified immediately, so automated fulfilment can be paused or pulled back before value walks out the door. The webhook event model is detailed in Get a Webhook the Moment a Payment Is Verified.
It is important to be completely honest about the limit here, because overstating it would be worse than useless. KODA cannot prevent a reversal. It never holds or moves the money, so it has no power to block the operator from clawing a payment back — no verification tool that sits outside the network does. What KODA can do, and does, is collapse the time between the reversal happening and you knowing about it from possibly never to a few seconds. Being first to know is the entire value, and it is a large one.
That speed changes what you can do about it. A merchant who learns of a reversal immediately can hold an order that has not yet shipped, stop a service before it is consumed, or reach the customer while the transaction is fresh. A merchant who learns weeks later, from a bank statement or a shortfall at reconciliation, has usually already lost the goods. The reversal event turns a silent loss into an actionable alert, and it feeds straight into the records that let you act on it.
Reversals also belong in your paperwork, and KODA keeps them there. A reversed payment is stamped as such and carried into your Mobile Money Reconciliation: Find the Money You Forgot so month-end reflects reality rather than an optimistic total, and it attaches to the evidence trail used in Win Mobile Money Disputes with an Automatic Evidence File — the confirmation, the reversal, the locked reference and the timeline all in one file. If a customer later claims the payment stood, you have the operator's own messages showing it was confirmed and then undone.
Reversal detection sits naturally alongside late-payment handling, because both are about respecting what the network actually says over time rather than at a single instant. When a Payment Arrives Late: KODA Still Confirms It holds an order open until a slow confirmation arrives; reversal detection reopens the question if a confirmed payment is later undone. Between them, KODA tracks a payment's real state as the operator reports it, instead of freezing a verdict the network might still change.
You cannot stop a telco from reversing a payment, but you can refuse to be the last to find out. Get started with KODA free and subscribe to the payment.reversed event so your systems hear about a clawed-back payment the moment the operator says so — see how the events work in Get a Webhook the Moment a Payment Is Verified and watch operator message health on KODA platform status & operator parse health. The goods you save are the ones you would otherwise have shipped against money that was already gone.
No. KODA never holds or moves the money, so it cannot block an operator-side reversal. What it does is detect the reversal from the operator's own message and alert you within seconds — making you the first to know rather than the last.
It reads the reversal message the operator sends to the merchant's phone, just as it reads a confirmation, and fires a payment.reversed event immediately. The order is flagged and any listening webhook is notified — see Get a Webhook the Moment a Payment Is Verified.
You can hold an unshipped order, stop a service before it is used, or contact the customer while it is fresh. The event turns a silent, late-discovered loss into an immediate, actionable alert.
Yes. A reversed payment is stamped and carried into your reconciliation, in Mobile Money Reconciliation: Find the Money You Forgot, and into the evidence file used to Win Mobile Money Disputes with an Automatic Evidence File — with the confirmation, the reversal and the timeline together.
Late handling, in When a Payment Arrives Late: KODA Still Confirms It, holds an order open until a slow confirmation arrives. Reversal detection reopens a confirmed payment if the operator later undoes it. Both track the payment's real state over time.