Understanding M-Pesa STK Push Payment Status

WayaDesk / M-Pesa payments

A sent payment prompt is not the same as a completed payment. The customer may not see it, may dismiss it or may decide not to continue. An operator should describe the state they can actually verify instead of telling a customer that any displayed prompt has already paid for access.

Separate request and outcome

The payment request begins the journey. Provider-confirmed results establish the outcome used by the billing workflow. Customer access is another stage. These stages may be observed at different times, particularly when the customer’s browser or the operator’s network is interrupted.

Help the customer without creating another charge

Ask whether a provider confirmation was received and locate the existing purchase record. Keep the customer on the appropriate recovery path rather than immediately issuing another request. If the first attempt is unresolved, a second attempt can make later reconciliation more confusing.

• Find the existing reference and its latest recorded state.
• Check provider evidence when the result is uncertain.
• Start another purchase only after the earlier attempt has been resolved appropriately.

A useful pilot case

Close the customer’s browser after a controlled payment attempt and inspect whether the operator can still locate the transaction. The important result is a traceable record and correct entitlement, not whether a single browser tab remained open throughout the demonstration.

Explain what staff can promise

Avoid guaranteeing that every phone displays a prompt immediately. Staff can explain the recorded state, the next verification action and the access recovery process. This keeps communication useful while respecting the difference between the billing application and the mobile payment service.