Checkout here often ends with the customer entering a PIN on their handset. Your site is not part of that step, and it has to survive not being part of it.
A mobile money transaction happens between the customer and their operator. Your order is waiting for a message afterwards.
Confirmation arrives as a request from the payment operator, not from the customer's browser. If that endpoint is cached, throttled or behind a challenge, the payment succeeded and the order did not.
A customer may take a minute to find their phone and enter a PIN. Pending orders are held for a realistic human interval rather than a network timeout.
Traffic is overwhelmingly mobile and often on variable networks, so reducing round trips matters more than shaving kilobytes.
Operators occasionally deliver a callback late or twice. Records are kept so a payment can be matched to an order rather than guessed at.
Kenya is far from most infrastructure, so where the origin sits is a decision we make with you rather than a default.
Every mobile money failure looks the same from the outside: money left the customer's account and the shop has no order. Almost always the callback never arrived.
A fast storefront that loses payment confirmations has failed at the only step that mattered. Callback reliability is the number here.
Payment happening off-site drives most of this, and network conditions drive the rest.
| Setting | What we do | Why |
|---|---|---|
| Callback endpoint | Exempt from caching, throttling and bot challenges | Confirmation arrives as a machine request from the payment operator, and anything that blocks or caches it produces a paid customer with no order. |
| Pending order window | Sized for somebody finding their phone and entering a PIN | The wait includes a human action on a separate device, which is far longer than any timeout written for a network response. |
| Callback reconciliation | Late and duplicate messages matched to orders | Operators sometimes deliver confirmations twice or minutes late, and without records those become either double orders or lost ones. |
| Round trips | Reduced ahead of payload size | Traffic is mobile and network quality varies, so an extra sequential request costs more than the bytes it would have carried. |
| Origin placement | Decided explicitly rather than inherited | Kenya is distant from most infrastructure, so accepting a default origin means accepting a latency nobody measured. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the store across — migration is free, payment callbacks tested.