If a UPI payment shows pending or failed but your account was debited, do not pay again straight away. Note the amount, time and reference number, check your bank statement for the debit, and then watch for a matching credit, which is the reversal. Only when both the debit and the credit are in your statement is the loop closed.
What should you write down first?
- Date and time of the attempt.
- Amount, to the rupee.
- Payee name or handle.
- The reference number from the app's payment detail screen, if it shows one.
- The status shown: pending, failed or processing.
- A screenshot of that screen, saved before you leave it.
These six items are what the bank's support team will ask for, so collecting them early saves several calls.
How do you track it until the credit arrives?
Keep a small log, in a sheet or a notes page, with one row per stuck payment.
| Date | Amount | Payee | Reference | Debit seen | Reversal credit seen |
|---|---|---|---|---|---|
| 14 Oct | ₹1,850 | Electronics shop | ref from app | Yes, 14 Oct | Pending, check 17 Oct |
| 22 Oct | ₹320 | Auto fare | ref from app | No debit | Not needed |
The second row shows the happy case: failed, and no debit in the statement, so there is nothing to wait for. In the first row you were debited, so you wait for the matching credit. Banks and apps usually state their own timeframe for reversals, so look it up in your app's help page rather than relying on a number from the internet.
Should you pay again while it is pending?
Check three things before you do. First, whether the merchant or the person received the money, which you can ask them to confirm from their side. Second, whether your statement actually shows a debit. Third, whether the app now says success. If the merchant has the money, a second payment becomes a duplicate. If the payment is urgent, say so to the merchant and agree on how the first amount will be adjusted or refunded.
What does the reversal look like in your records?
It is a credit for the same amount, usually within a short time of the debit, with a narration that mentions reversal or return. Add it to your tracking as a refund against the original expense, not as income. For example, if you were debited ₹1,850 and later credited ₹1,850, your net spending on that attempt is ₹0, and both rows should stay in your records so the totals reconcile.
How can SpendixAI help here?
If you paid again out of worry, the Possible duplicate charges report lists payments of the same amount to the same merchant within two days, which is exactly the pattern a repeat payment leaves. When you upload your statement, review the rows before saving, and tag the refund as a refund and not as income. It works on what is in your statement, so it will not show a pending item that your bank has not posted yet.
How long is too long to wait?
Your bank and the app each publish how long a reversal should take, and the figures differ by case, so find them on the official help pages and put the end date of that period in your log. On that date, if the credit has not arrived, escalate in writing. Until then, resist the urge to repeat the payment or to chase through several channels at once, because duplicate complaints slow things down.
A short checklist
- Screenshot and note the reference.
- Check the statement for a debit.
- Confirm with the payee whether they received it.
- Log it, and tick it off when the credit lands.
- Escalate in writing only when the bank's own stated period has passed.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

