The message comes in on WhatsApp, often with a screenshot and some frustration: “Your site said payment failed but money deducted from my account. Where is my order?” You look in your store and there is no paid order. You look in the gateway dashboard and find either nothing, a failed attempt, or, confusingly, a successful payment.
When a customer reports a payment failed but money deducted, there are only a few things that can have happened, and each needs a different reply. This post is a seller’s playbook: what to ask the customer, how to find out which case you are in, what to tell them and when to involve the gateway or the bank. It is general information, not legal or financial advice; banks and gateways each have their own complaint processes, and their rules apply.
Payment failed but money deducted: the three usual causes
1. The bank blocked the money, but the payment never completed
The customer’s bank reserved or debited the amount, but the payment did not reach success at the gateway. A network timeout, a slow bank server, or the customer closing the app at the wrong moment can all cause this. To the customer it looks like they paid. To you, nothing arrived.
In this case the money normally goes back to the customer automatically, through their bank. You do not need to refund anything, because you never received it.
2. The payment succeeded, but your store did not hear about it
The gateway shows the payment as captured or successful. Your store still shows the order as pending, failed or missing. The message from the gateway to your website did not arrive, often because the customer left the page before the redirect and the background notification failed. You do have the money, and the order needs fixing on your side.
3. The customer paid twice
The first attempt seemed to fail, so the customer tried again and the second one worked. Later the first one also completed, or was debited and reversed. They may now have one order and two debits, or two orders. One payment needs to be refunded or will reverse by itself, depending on what the gateway shows.
What to ask the customer first
Before you search anything, collect the facts. Ask politely for:
- The exact amount and the date and time of the attempt.
- How they paid: UPI app, card, net banking or wallet.
- The transaction reference. For UPI this is usually the UTR or reference number in their app’s history. For cards, the bank statement line may show a reference.
- A screenshot of the bank statement or bank app transaction, not just the “payment successful” screen in a UPI app or on your site. The bank entry is what shows whether the money actually left.
- The email or phone number they used at checkout.
Reassure them while you check. “Thanks, I am looking into it now, I will reply shortly with what I find” is better than silence, and keeps a worried customer from going straight to their bank with a dispute.
Finding out which case you are in
- Search the gateway dashboard by the customer’s email, phone number, amount and time. Also search by the reference number they gave you, if your gateway supports it.
- Check the payment status. Gateways use labels such as created, attempted, failed, authorised, captured, or refunded. The exact words vary, but you are looking for whether any attempt reached success.
- Compare with your store. Look for orders from that customer around that time, including ones marked pending payment, failed or cancelled. They may be hidden by a filter; our post on orders that seem to vanish in WooCommerce covers where they go.
- Look for a second attempt a few minutes later with the same amount.
Now match what you find to the three cases:
| Gateway shows | Store shows | Likely case | What to do |
|---|---|---|---|
| No payment, or failed only | Pending or failed order | Money blocked at the bank | Explain it reverses through their bank; offer to hold the order while they pay again if they want to |
| Captured or successful | Pending, failed or no order | Store did not get the update | Mark the order paid after confirming, then fix the cause |
| Two successful payments | One or two orders | Double payment | Keep one, refund the other through the gateway |
| Authorised but not captured | Pending | Payment held, not completed | Check your gateway’s capture settings; it may capture automatically or release the hold |
What to tell the customer in each case
If the money never reached you
Be specific and calm. Tell them you can see the attempt did not complete on your gateway, so you have not received the money, and that a failed transaction amount debited from their account is returned by their own bank. The bank sets how long this takes. The Reserve Bank of India has rules on turnaround times for reversing failed transactions, which are published on the RBI website; the customer can raise a complaint with their bank if the reversal does not appear.
Offer a way forward: they can wait for the reversal and pay again, or pay again now by another method if they need the order quickly. Never promise a reversal date yourself. You do not control it.
If you did receive it
Apologise for the confusion, confirm the order and send the usual confirmation. Then fix the underlying cause, because it will happen again. A payment that succeeds at the gateway but not in the store is usually a webhook or plugin setting; our page on fixing gateway errors in WooCommerce walks through the technical checks.
If they paid twice
Tell them you have found two payments, that you are keeping one for the order and refunding the other. Give them the refund reference from the gateway. Refunds go back through the payment method’s own system, so explain that the time to see it depends on their bank.
Mistakes that make it worse
- Refunding money you never received. If the gateway shows no successful payment, sending the customer money yourself, by bank transfer for example, means they are paid twice once their bank reverses the original debit.
- Trusting a screenshot alone. A screen from the customer’s app tells you what their app showed, not what your gateway recorded, and screenshots are easy to edit. Check your own dashboard before you ship.
- Telling the customer to “contact the bank” with nothing else. Give them what you found, so their bank conversation is short.
- Leaving the order in limbo. Mark it clearly, add a note with what you found and when, so anyone else on your team sees the history.
- Ignoring the pattern. One case is bad luck. Several in a week means something on your site or in your gateway setup needs attention.
When to involve the gateway or the bank
Raise a ticket with your gateway if its dashboard is unclear: a payment stuck in an in-between state, a reference the customer has that you cannot find, or a capture that never happened. Give them the payment ID, amount, time and the customer’s reference.
The customer’s bank is the right place for a debit that never reached your gateway. You cannot see inside their bank, and the gateway cannot either. If a customer has already raised a dispute, respond through the gateway’s dispute process instead of refunding directly; our guide on how chargebacks work explains why.
Once things are sorted, check that the payment appears where you expect in your next settlement. Our post on when gateway money reaches your bank explains how to trace it.
Card payments: holds that look like debits
With cards, there is an extra twist. Some payments are first authorised, which reserves the amount on the card, and then captured, which actually takes it. If the capture never happens, the reservation is released by the card issuer. Until then, the customer sees the amount as gone from their available balance, and may describe it as “deducted”. Check whether your gateway captures payments automatically or needs a manual step; if it needs one, uncaptured payments will produce exactly these messages.
A note template worth saving
Keep a short internal note on every case, in the order notes or a shared sheet:
- Customer name, contact and order number.
- Amount, method, date and time of each attempt.
- Customer’s reference number and gateway payment IDs.
- What the gateway showed, what the store showed, and which case it was.
- What you told the customer, and when.
- Refund reference, if any.
After a few months these notes show whether failures bunch around one payment method, one time of day or one device, which points you to the cause.
Fewer of these messages next time
No setup removes failed payments entirely, because many start at the customer’s bank. What you can control is whether your store hears about successful payments reliably, and how clearly your checkout tells customers what happened. A gateway with good reporting and a properly configured plugin makes these cases faster to resolve. Our main guide to picking a payment gateway for small businesses covers what to look for.
The customer who wrote to you is mostly worried about their money. Find which of the three cases it is, tell them plainly, and write it down. That is usually all it takes.
