# Why Mobile Money Payments Fail on WooCommerce, and How to Recover Them

URL: https://fosiarw.com/mobile-money-payment-failed-woocommerce/
Updated: 2026-11-16
Site: FOSIA AGENCY

**In short:** when a Mobile Money payment failed on WooCommerce, the cause is usually one of a few: the customer did not approve with the PIN in time, the balance was too low, the number belongs to another network, the operator was down, or your site never received the confirmation. Each has a different fix. Show the customer the real status and reason, never “Thank you” for an unpaid order, and give them a one-tap way to pay again.

A failed Mobile Money payment costs twice. The customer who wanted to buy leaves confused, and your WooCommerce orders list fills with orders you cannot ship. The good news: most failures are predictable, and most can be recovered within minutes if you know what happened. This guide uses PawaPay’s own failure codes and WooCommerce’s documentation to sort them out.

## The reasons the network gives

When a payment fails, PawaPay returns a failure code. Its [failure codes page](https://docs.pawapay.io/v2/docs/failure_codes.md) lists the ones you meet during live operation. Here they are in plain words, with what to tell the customer:

| PawaPay code | What happened | What to tell the customer |
| --- | --- | --- |
| PAYMENT_NOT_APPROVED | The customer did not authorise, for example did not enter the PIN in time | Keep your phone unlocked and approve the prompt |
| INSUFFICIENT_BALANCE | Not enough money in the wallet | Top up, or pay from another number |
| PAYER_NOT_FOUND | The number does not belong to that operator | Check the number and the network chosen |
| PAYMENT_IN_PROGRESS | Another payment is still pending on the wallet | Wait a few minutes, then try again |
| WALLET_LIMIT_REACHED | The customer reached a limit on the wallet | Pay with another number, or another day |
| UNSPECIFIED_FAILURE | The operator gave no reason | Try again; if it repeats, try later |

Two notes from PawaPay’s documentation. On PAYMENT_IN_PROGRESS, some providers process only one transaction at a time, and after a PIN that was not entered in time it can take up to 10 minutes before the customer can start a new one. And limits are real: PawaPay says transaction limits vary by market and are set by the central banks, typically as daily, weekly or monthly caps.

## Failures that are not the customer’s fault

### The operator is down

Operators have outages. PawaPay’s team monitors them and stops accepting payments to an operator whose success rate is too low; a payment attempted then is refused with PROVIDER_TEMPORARILY_UNAVAILABLE. PawaPay publishes operator status on its dashboard and its status page, and offers an availability endpoint so a checkout can warn customers before they try.

### The confirmation never reached your site

The customer paid, but the order still says Pending payment. PawaPay’s API is asynchronous: it sends the final status to your callback URL, and if your site does not answer, it retries up to 8 times over about 25 minutes, then stops. The usual causes, from the Fosia Pay docs: the callback URL is not saved in the PawaPay dashboard, the site is not on HTTPS, or a security plugin or firewall blocks PawaPay’s requests. Fosia Pay Lite also re-checks payments with PawaPay in the background for a few hours, so a customer who paid and closed the page is confirmed even when no callback arrives.

### The amount does not fit the operator

Some operators refuse decimals (INVALID_AMOUNT) and every operator has minimum and maximum amounts (AMOUNT_OUT_OF_BOUNDS). Fosia Pay Lite reads your account’s amount rules from PawaPay, so amounts follow the decimals and limits set on your account.

## What your customer sees decides whether they retry

The worst failure is the silent one: the customer returns to a page that says “Thank you, your order has been received” when no money moved. They wait for a delivery that never comes, and you get an angry call.

Fosia Pay Lite reads the payment status from PawaPay before it shows the return page. A paid order gets a thank-you. Otherwise the customer sees “Payment not received yet” with “Pay now” and “Check again”, “Payment failed” with the reason in plain words and “Try again”, or “Confirming your payment” while the page checks again by itself. The same reason is written on the order as an order note.

[Image: Mobile Money payment failed screen with the reason and Try again, next to Payment not received yet with Pay now] Left: the customer came back without paying and sees “Pay now” and “Check again”. Right: the payment failed for a low balance, with “Try again”. Never “Thank you” for an unpaid order (sample data).

## Recovering the sale, step by step

[Image: Steps to recover an order after a Mobile Money payment failed on WooCommerce] Four steps to turn a failed or pending Mobile Money order into a paid one.

1. **Read the reason.** Open the order and read the note. A low balance needs a different message from a wrong number.
2. **Fix the cause with the customer.** A short WhatsApp message works: “Your payment for order 1042 did not go through because the balance was too low. Here is the link to pay when you are ready.”
3. **Send a payment link.** WooCommerce’s [paying for orders](https://woocommerce.com/document/managing-orders/paying-for-orders/) guide lists three ways to pay a Pending payment order later: the “Pay for this order” link in the order invoice e-mail (Order actions, Send order details to customer), the Pay button in the customer’s account, and the “Customer payment page” link on the order screen, which you can copy and share.
4. **Check the result.** The order should turn to Processing on its own once the payment is confirmed.

Mind your stock settings. WooCommerce’s [order statuses](https://woocommerce.com/document/managing-orders/order-statuses/) page explains that with Hold stock enabled, unpaid Pending payment orders are cancelled after the time limit you set, and stock from a Failed order goes back to inventory. A very short hold time can cancel an order while a customer is still topping up.

## Preventing failures before they happen

Fosia Pay Lite already avoids one class of failure: it hides Mobile Money at checkout when it cannot work, such as without a valid token or for a billing country your PawaPay account does not cover. Its dashboard shows failed payments by reason and unfinished checkouts, so you can see whether low balances or abandoned PINs cost you most.

[Fosia Pay Pro](https://pay.fosiarw.com/fosia-pay/) ($19.99 a year or $59 once for life) goes further: the number is checked as the customer types, operator outage alerts show at checkout before paying, a failed payment gets a one-tap retry with the reason, and an operator status and “Why payments fail” dashboard sits in WordPress.

Before you go live, test the bad cases too. PawaPay’s sandbox has numbers that fail on purpose with insufficient balance or payment not approved: our [PawaPay setup guide](https://fosiarw.com/pawapay-woocommerce-setup-guide/) shows where to find them, and the [Tanzania guide](https://fosiarw.com/tanzania-mobile-money-woocommerce/) gives a ready test plan.

## Frequently asked questions

### The customer says they paid, but the order is still pending. Who is right?

Check the payment in your PawaPay dashboard first. If it is completed there, the confirmation did not reach your site: check the callback URL, HTTPS and your firewall. The customer can tap “Check again”, and Fosia Pay Lite’s background checks also confirm it.

### Should I cancel failed Mobile Money orders?

Not straight away. Contact the customer with the reason and a payment link first; many failures are a timeout or a low balance that is fixed in minutes.

### Can the customer pay from a different number after a failure?

Yes. With Fosia Pay Lite, “Try again” sends the customer back to pay, with the same number or another one.

### Does a failed payment cost me fees?

FOSIA takes no commission on any payment. For PawaPay’s fees, check your agreement with PawaPay.

### Does this work with the block checkout?

Yes. Fosia Pay Lite supports the classic and the block checkout; see our guide to [Mobile Money on the block checkout](https://fosiarw.com/woocommerce-block-checkout-mobile-money/).

Want fewer “payment failed” messages? Install [Fosia Pay Lite](https://pay.fosiarw.com/) for free and test every failure in sandbox, see what Pro adds on the [pricing page](https://pay.fosiarw.com/pricing/), or read the [Fosia Pay guide](https://fosiarw.com/accept-mobile-money-woocommerce-fosia-pay/).
