Getting started

Google Pay not working in India: payment failed, stuck or not received

Google Pay not working in India? Use this decision guide for failed, pending and debited-but-not-received UPI payments, and keep proof for your bank.

Editorial illustration for Google Pay not working in India: payment failed, stuck or not received

When a UPI payment from Google Pay seems to fail, do not pay again straight away. Check your bank account for a debit first. No debit means nothing left your account and you can retry later; a debit with no confirmation means the payment is in transit or needs a reversal, and your proof matters. we will not quote timelines, because your bank and the payment app set those.

Which of these three is happening?

SituationWhat to checkNext step
App will not open or payPhone, network, app updateRestart, switch networks, update the app, retry
Payment shows failedBank statement for a debitIf no debit, retry once; if debit, note the reference and wait for a reversal
Payment shows pendingStatement and the app's historyWait, do not repeat it, and check again later
Debited, receiver says not receivedStatement line and the receiver's own recordShare the transaction reference with your bank through its official route

What should you write down at once?

  • Date and exact time.
  • Amount.
  • The receiver's name or UPI ID, as shown on the screen.
  • The transaction reference number or ID.
  • The bank account the money was debited from.
  • A screenshot of the status screen.

A worked example with made-up numbers

Say you pay a vegetable seller ₹640 and the app says failed. You try again, and it works. Later your statement shows two debits of ₹640, one from each attempt, with one marked as reversed or pending. Total if both stayed: 640 plus 640 is ₹1,280, which is ₹640 more than you meant to pay.

What you do next is calm: record both lines and the times, wait for the pending one to resolve on its own, and ask your bank about it only if it has not. How long to wait is for your bank to tell you.

Why do these show up in my expense records twice?

Because the statement shows what the bank did, not what you meant. A failed payment, a retry and a reversal can appear as three lines. If you track from statements, mark the reversed one so you do not count it as spending. SpendixAI can flag possible duplicate imports and has a Possible duplicate charges report listing the same amount to the same merchant within two days, a useful prompt for exactly this case. You confirm what is real.

A short checklist for the next failure

  1. Pause; do not retry yet.
  2. Check the bank account for a debit.
  3. Write down time, amount, receiver and reference.
  4. Screenshot the screen.
  5. Wait, then check again.
  6. Contact the bank through its own app or branch if money is stuck.

Finally, take a minute to review your limits and habits. If you often pay small amounts to the same few people or shops, note the usual amounts, so an odd figure stands out. Look at your statement weekly rather than monthly, so a missing credit or an unexpected debit is caught while the memory of the day is still fresh and the receiver can easily confirm what happened.

If failures happen often, look at the pattern. Do they cluster at a certain time of day, on one network, with one bank account or with one kind of receiver? Writing down five failures with their details can show a cause that a single incident hides, and it gives your bank something concrete to investigate when you raise the matter through its official channel.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports