Error code U13 in Google Pay: what it means and how to fix it
Error code U13 in Google Pay is a UPI response code that means "external error". It is defined by the National Payments Corporation of India (NPCI), which runs UPI, and it signals that a system outside the Google Pay app, usually your bank's server or the UPI switch, did not respond correctly. Your PIN and your account are normally fine. Wait 15 to 30 minutes, check your bank statement for a debit, and retry only if no money left your account.
This guide explains what U13 means (in plain words, including for Hindi searches like "U13 ka matlab"), why it appears during payments and balance checks, what to do if money was debited, and the fixes that actually help.
What does error code U13 mean?
U13 means "EXTERNAL ERROR" in NPCI's official list of UPI error and response codes. The UPI Error and Response Codes document (version 2.3.1) lists U13 in the section for errors from the UPI service layer, next to codes such as U14 (encryption error) and U28 (PSP not available).
In practice, "external" means the failure happened outside the app you are using. Google Pay is a UPI app that passes your request to its partner bank, then to the NPCI switch, then to your own bank. If one of those links times out or returns an unexpected reply, the request is rejected with U13.
That is why the same code appears in Google Pay, PhonePe, Paytm and BHIM, and why searches like "U13 error in bank" are accurate: the problem usually sits with a bank system, not the phone. In Hindi, U13 ka matlab is simply "bahari truti" (external error): the bank or UPI network did not complete the request.
Why does the U13 error appear in Google Pay?
The U13 error appears when one of the systems behind a UPI request is slow, unavailable or rejects the message format. The most common triggers are:
- Bank server downtime or maintenance: banks run scheduled maintenance, often late at night, and their UPI service can stop responding for a while.
- Peak-hour load: on salary days, festival sales and month-end, bank UPI servers can time out.
- Weak or switching connection: if your phone drops between Wi-Fi and mobile data during the request, the reply may never arrive.
- Outdated app or bank link data: an old app version or stale bank account registration can send requests the bank does not accept.
- Account-side restrictions: a frozen account, a mobile number no longer linked to the bank account, or a KYC hold can make the bank reject UPI requests.
The first three causes are temporary and clear on their own. The last two need action from you or your bank.
How to fix error code U13 in Google Pay
The fix for U13 is to rule out the temporary causes first, then check your bank link. Work through these steps in order:
- Check whether money was debited. Open your bank app or SMS alerts before retrying. If money left your account, skip to the next section instead of paying again.
- Wait and retry. Give it 15 to 30 minutes. Bank downtime and peak-hour timeouts usually clear without any action.
- Change your connection. Google Pay's own help suggests switching to mobile data or another connection. Avoid moving between networks while the payment is processing.
- Try a smaller amount or enter the UPI ID manually. Google also recommends this for failed payments, instead of picking the recipient from recent contacts.
- Update Google Pay. Install the latest version from the Google Play Store or the App Store. Only install it from official stores; see our look at whether third-party APK sites are safe.
- Clear the app cache. On Android, open Settings, go to Apps, select Google Pay, open Storage and tap Clear cache. Clearing storage as well signs you out, so you will have to verify your number again.
- Use another linked bank account. If a second account works, the problem sits with the first bank, which confirms an external cause.
- Contact your bank. If U13 keeps appearing for one account over several hours, ask the bank whether UPI is blocked, the number is unlinked or KYC needs updating.
If Google Play itself throws errors while you update, our guide to the Play Store error DF-DFERH-01 covers the usual fixes.
Money debited after a U13 error: what to do
If money was debited but the payment failed with U13, do not pay again: the amount is normally reversed to your account automatically. Google states in its Google Pay India help page on failed payments that money deducted for a failed payment is refunded within 5 business days, and its issues and fraud help page notes that banks usually take up to 3 business days to add money back.
Follow this order:
- Look for a reversal entry marked "UPI-REV" or "UPI-RET" with the same UPI transaction ID on your bank statement.
- If the status shows "Payment processing", do not repeat the payment. Google advises waiting while the bank completes it.
- If no refund arrives after 5 business days, open Google Pay, go to See transaction history, tap the transaction, tap Having issues? and create a ticket. You may need to upload a bank statement; screenshots and ATM mini statements are not accepted.
- If the transaction is more than 21 days old, contact your bank directly, as Google's partner banks cannot raise a complaint after that period.
- If your bank does not resolve it, file a UPI complaint through NPCI's dispute redressal mechanism on npci.org.in.
Google also lists a Nodal Officer contact ([email protected]) for issues that stay unresolved after 30 days.
U13 error when checking your bank balance
U13 also appears when Google Pay cannot check your balance, and the cause is the same: the bank did not answer the balance enquiry in time. A balance check is a live request to your bank through UPI, so it fails whenever the bank's UPI service is down or overloaded, even if payments worked minutes earlier.
Because a balance check moves no money, it is safe to retry. Wait a few minutes, make sure your connection is steady, and try again. If it still fails, use your bank's own app, net banking or SMS banking to see the balance, which tells you whether the bank's core systems are up.
If balance checks fail with U13 for days on one account while other accounts work, the bank link itself may be broken. Removing the bank account from Google Pay and adding it again forces a fresh registration with your bank. You will need the mobile number registered with that bank in the phone, and you may have to verify it again by SMS.
U13 compared with other common UPI error codes
U13 is one of several NPCI codes that look alike but need different responses. This table uses the definitions from NPCI's UPI error code list:
| Code | NPCI meaning | What to do |
|---|---|---|
| U13 | External error | Wait, retry, check the bank link |
| U16 | Risk threshold exceeded | Usually a limit or risk check: wait or ask your bank |
| U28 | PSP not available | The app's partner bank is down: retry later |
| U30 | Debit has been failed | Check the balance and account status with your bank |
| Z9 | Insufficient funds in remitter account | Add funds or pay a smaller amount |
| ZM | Invalid MPIN | Re-enter or reset your UPI PIN |
The key difference: U13 and U28 point at systems outside your control, while Z9 and ZM point at something you can fix on your side.
FAQ
Is the U13 error my fault?
Usually not. U13 is an external error, which means a bank or UPI system failed to respond, not that you entered something wrong.
Does U13 mean my UPI account is blocked?
Not by itself. If U13 keeps appearing on one bank account for several hours while other accounts work, ask that bank whether UPI is restricted on the account.
Can I reinstall Google Pay to fix U13?
Reinstalling rarely helps because the error comes from outside the app. Update the app and clear its cache first; reinstall only if the app itself misbehaves, as covered in our app not installed error guide.
Related: How to split expenses in Google Pay, Fix Google Play error DF-DFERH-01, Fix "App not installed" on Android
Leave a Reply