When the network drops, KODA Sentinel captures the operator's payment SMS, queues it, and forwards it for verification the moment signal returns — nothing is missed.
— reads
Connectivity in the places KODA serves is not a given. The network drops in a basement shop, a rural market, a power cut, a congested evening — and a verification tool that only works online would simply go blind for the duration, leaving the merchant back to trusting screenshots. KODA Sentinel is built for that: when the phone has no connection, it captures the operator's payment SMS, stores it safely on the device, and forwards it for verification the instant signal returns. Nothing is missed. Sentinel is introduced in Auto-Verify Every Payment with the KODA Sentinel App.
The key idea is that the proof arrives on the phone regardless of the internet. The operator's confirmation SMS is delivered over the mobile network, not the data connection, so it reaches the merchant even when there is no browsing. Sentinel reads it on the device the moment it lands, queues it locally if there is nothing to send it over, and holds it until a connection is back. The merchant's record of being paid is captured at the instant of payment, not whenever the internet happens to return.
When connectivity comes back, the queue drains on its own. Each stored confirmation is forwarded to the engine, matched, fraud-scored and replay-locked exactly as a live one would be, and the verdicts flow into the merchant's feed and books. There is no manual catch-up, no re-entering anything, and no worrying that a sale made during the outage slipped through — store-and-forward closes the loop automatically once the phone can talk to the engine again.
This is the difference between a tool that works in a demo and one that works in a Congolese market. Outages are not rare events to be excused; they are routine. A verification system that fails during them fails exactly when a merchant is busiest and most exposed, and a fraudster who notices the tool is offline has an open window. Store-and-forward shuts that window: being offline delays the verdict by minutes, but it never cancels it.
It pairs naturally with late-payment handling. Where When a Payment Arrives Late: KODA Still Confirms It holds an order open while a slow operator confirmation catches up, store-and-forward holds the captured confirmation while the merchant's own connection catches up. Between them, neither a slow network at the telco nor a dead connection on the counter can cause a genuine payment to be lost or a verdict to be skipped. The payment's truth is preserved and delivered as soon as it possibly can be.
Nothing about the safety relaxes because a confirmation waited offline. A queued SMS is checked against the How KODA Catches Fake Payment SMS anti-forgery model and locked for single use just like an instant one, so the delay buys a forger nothing. And because the capture happened on the device at the moment of payment, the record is harder to tamper with, not easier. Offline is a timing condition, not a trust discount — the model is on How KODA verifies mobile money payments, and operator delivery health is on KODA platform status & operator parse health.
If your shop loses signal and you still take payments, you should still be verifying them. Install Sentinel and it will keep capturing every operator confirmation through the dead zones and settle them the moment you are back online — automatically, with nothing lost. See how Sentinel automates capture in Auto-Verify Every Payment with the KODA Sentinel App, how it fits the five doors in Five Ways to Accept & Verify Mobile Money (One Engine), and Get started with KODA free to put offline-proof verification on your counter.
The verdict needs a connection, but KODA Sentinel keeps working through outages: it captures the operator's payment SMS offline, stores it on the phone, and forwards it for verification the moment signal returns. Nothing is lost. See Auto-Verify Every Payment with the KODA Sentinel App.
The operator's confirmation SMS arrives over the mobile network, not the data connection, so it reaches the phone even with no internet. Sentinel reads and queues it on the device, then sends it when a connection is back.
No. The queue drains automatically — each stored confirmation is forwarded, matched, scored and locked on its own, with no manual catch-up or re-entry.
No. A queued confirmation passes the same How KODA Catches Fake Payment SMS anti-forgery checks and single-use lock as a live one. Capturing it on the device at the moment of payment makes it harder to tamper with, not easier.
When a Payment Arrives Late: KODA Still Confirms It waits for a slow operator confirmation to arrive; store-and-forward waits for the merchant's own connection to return. Together they ensure no genuine payment is lost to either kind of delay.