Mobile Recharge Failed: What a Retailer Can Do

You’ve typed the number, pressed the button, and the screen shows “pending”. Or “failed”. The customer is watching you, and their phone is nearly out of balance. Everything in you wants to press the button again.

Don’t. A second attempt made in a hurry, or a promise at the counter that you can’t keep, makes a small delay into a bigger problem. This guide gives you the checks to make, what to write down, and what to say to the customer while you wait.

What does each status mean, and why not retry?

Open your transaction history and find the recharge. Your panel may use different words from the three below. If it does, ask support what they mean before you act.

SiOnline’s support page, as of 17 October 2026, describes a transaction where money left and nothing arrived as usually a settlement delay that reverses on its own. That page talks about transactions in general, not recharges only. It adds that most settlement delays clear on their own, and that you should call with the transaction reference if the record still shows pending.

So why not just retry? Because you don’t know yet that the first attempt failed. If it did go through, a second attempt could take money from your wallet again and send the customer a second recharge. SiOnline’s deposit-request guide gives the same advice for a missing wallet deposit: don’t transfer a second time, call first.

Start with checks that don’t change anything on the account. Look at the history. Look at the balance. Compare the number on the record with the number the customer gave you. None of those can make things worse.

Case 1: the record says pending

Check. Open the history entry and look at the status and any reference shown.

You see. Pending, with no final result.

Fix. Wait, then refresh and look again after you’ve served your next customer. If it still says pending, contact support with the reference. Support is open 24 hours, 7 days, so you don’t have to wait for tomorrow.

If your internet dropped during the attempt, say so when you call. And don’t start a new recharge for the same number in the meantime, even if the customer asks you to “just try once more”.

Case 2: the record says failed

Check. Compare your wallet balance now with the balance before the attempt. If you didn’t note it down, look at your history for entries around the time of the recharge.

You see. Either the balance is unchanged, or it has dropped and the recharge shows failed.

Fix, if the balance is unchanged. Nothing has left your wallet. Check the number again and tell the customer. Ask them to look at their own balance first, so you don’t send a second recharge to a number that already got the first. Make one fresh attempt only if their balance hasn’t changed and the number is confirmed.

Fix, if the balance has dropped. If the balance went down and the record shows failed, the money may still be on its way back. Don’t attempt again.

SiOnline’s wallet guide, as of 17 October 2026, is written for wallet balances and deposits. It says a failed transaction that is reversing can make the balance look wrong for a while, and it tells you to check your transaction history, check for pending settlements and find the reference before you call. That same order works for a recharge: history first, then the reference.

There’s one more thing to look at. If the attempt failed straight away and your balance was low, the balance may not have covered the amount. The support page says that when you can sign in but can’t complete the job, it’s almost always a balance too low to cover the transaction. Top up first.

If it did not work. Failed transactions are reconciled. If a reversal has not reached your wallet, contact support.

Case 3: the record says success, but nothing arrived

Check. Compare the number on the record, digit by digit, with the number the customer gave you. Check the operator and the amount as well.

You see. Either they match, or one digit or the operator is different.

Fix. If they match, ask the customer to check their own number again. Sometimes the recharge is there and they’re looking at the wrong screen. If it did reach their number, don’t send another. If something differs, you have a wrong-number or wrong-operator case. The next section covers that.

If it did not work. Contact support with the reference and the exact details.

What if the recharge went to the wrong number or operator?

This is the hardest case. Don’t assume a wrong-number recharge can be reversed, and don’t tell the customer it can’t be either. Ask support what, if anything, can be done for your account, and ask for the answer in writing.

Here’s what you can do straight away:

1. Stop. Don’t recharge the right number until you’ve noted the wrong one, so the two records don’t get mixed up.
2. Write down the details. The wrong number, the number the customer wanted, the operator, the amount, the time and the reference on the record.
3. Contact support at once.
4. Tell the customer the truth. The recharge went to a different number, you’ve reported it, and you’ll tell them what you’re told.

The best fix is to avoid it. Read the number back to the customer, digit by digit, along with the operator and the amount, before you confirm. It takes a few seconds, and it catches a wrong digit before any money moves.

What can you do before every recharge to prevent trouble?

A few habits take almost no time:

• Note your wallet balance before you start, so you can compare it afterwards.
• Read the number, operator and amount back to the customer and wait for a “yes”.
• Don’t leave the screen half-finished to serve someone else. Finish the attempt or cancel it.
• Look at the final status before you tell the customer it’s done.

None of this stops every failure. But it means that when one happens, you already have the facts you need.

A quick example

Here’s a made-up example, just to show the order of thinking. Say a customer asks for a recharge, you confirm it, and the screen shows “pending”. You note your wallet balance, write the number, operator and amount on a slip, and tell the customer, “It hasn’t confirmed yet. I’m checking, and I won’t send it again until I know.” You serve two other people. Then you refresh. If it now says success, you ask the customer to check their phone. If it still says pending, you ring support with the reference and the slip in your hand. At no point did you press the button twice.

What should you note before you call?

SiOnline’s support page lists three things that make a call short: your ID, the exact message on the screen, and a transaction reference if money is involved. For a recharge, add a few more so support can find the entry quickly:

• Your ID (agent ID, PSA ID or CSP ID, whichever account it concerns)
• The exact message the screen showed, not your summary of it
• The transaction reference
• The mobile number, the operator and the amount
• The date and time of the attempt
• Your wallet balance before and after

Keep these in a simple log, even a notebook. Over hundreds of recharges, something will go wrong sooner or later, and a log turns a long phone call into a quick lookup. It also helps if a different person is at the counter the next day.

What should you tell the customer?

Say only what you know. The customer mostly wants to know if their money is safe, so be plain.

• Pending: “The recharge has not been confirmed yet. I am checking, and I will not send it again until I know.”
• Failed, balance unchanged: “That attempt did not go through and no money has left my account. I will check your number and your balance before I try again.”
• Wrong number: “The recharge went to a different number. I have noted everything and reported it. I will tell you what I am told.”

Don’t promise a refund, a time or a result. You don’t control how a failure gets resolved, and a promise you can’t keep costs you the customer’s trust.

What are the common mistakes?

A few things make recharge problems worse. Pressing the button a second time “to be sure” is the biggest. The next is guessing, for example telling the customer “it’ll come back in ten minutes” when you don’t know. A third is changing the number to “fix” it without noting what the first one was. And a fourth is forgetting to write down the time and the reference, which are the first things support will ask for.

If you do one thing differently after reading this, make it this: when something looks wrong, stop and write down what you see before you do anything else.

How do you contact support?

As of 17 October 2026, SiOnline’s phone support runs 24 hours, 7 days. Ring +91 91091 35959 for anything happening at your counter right now. Use WhatsApp if you need to send a screenshot, and use email (support@sionline.co.in) when you want a written record. The support page says SiOnline never asks for a password, an OTP or remote access to your computer. If anyone does, end the contact and ring the number published on SiOnline’s support page.

More help: SiOnline support, contact and customer care and the help centre. For how recharge works on SiOnline, see the Mobile and DTH recharge page. You may also find the mobile recharge retailer app checklist useful.

Questions retailers ask

Why did my recharge fail but my wallet balance dropped?

SiOnline’s wallet guide, as of 17 October 2026, says a failed transaction that is reversing can make the balance look wrong for a while. Check your history and the reference, and don’t recharge again. If the money hasn’t come back, contact support.

Can a wrong-number recharge be reversed?

Don’t assume it can, and don’t tell the customer it can’t. Follow the wrong-number steps above and ask support for an answer in writing.

The customer is in a hurry. Can I just try once more?

Not yet. You don’t know the first attempt failed. Check the history, the balance and the number first. Retry only when you’ve confirmed the balance hasn’t changed and the customer’s own balance hasn’t changed either.