Most recharges and bill payments succeed or fail within seconds. A small share end up "pending": the request reached the provider and was sent on to the operator, but the operator has not yet confirmed the result. Pending transactions are a normal part of payments, but handling them badly causes double recharges, wrong refunds and angry customers.
Why transactions go pending
- The operator's or biller's systems are slow or temporarily unavailable.
- Network timeouts occur between systems in the chain.
- High load at peak times, such as month-end or festival periods.
- The operator accepted the request but delays the confirmation.
What not to do
- Do not retry with a new reference. If the first request eventually succeeds, the customer gets recharged twice.
- Do not mark it failed and refund immediately. If it later succeeds, you have given away the money.
- Do not leave the customer without information.
What to do
- Show the transaction as "processing" with its reference.
- Wait for the provider's webhook, or check status at sensible intervals.
- When the final status arrives, update the transaction and, if failed, refund the wallet automatically.
- Notify the customer or retailer of the final result.
Most pending transactions resolve on their own within minutes; some take longer.
Communicating with customers
A clear message prevents anxiety: "Your recharge is being processed. You will receive confirmation shortly. If it fails, the amount will be refunded automatically." Retailers should have this message ready.
When a pending transaction stays pending
Escalate it to the provider with the reference. Good providers resolve these through reconciliation with the operator.
Measuring
Track the share of pending transactions by operator and time of day. Unusual increases can signal problems with an operator or provider.
Our platform resolves pending transactions automatically through status checks and notifies your server by webhook. See the mobile recharge API.
0 comments