Back
UPI Error Code List and Their Meanings
A failed UPI payment rarely fails silently. It almost always throws up a short error code, and that code is more useful than most people realize, since it usually tells you immediately whether the problem is on your end, the recipient's, or somewhere in the banking infrastructure between you. Knowing what the common codes mean turns a confusing failure into a two-minute fix most of the time.
Why UPI Transactions Fail in the First Place
A single UPI payment passes through several systems in sequence: your app, your bank, the NPCI network, and the recipient's bank. A failure at any one of those points produces a different code. Common root causes include incorrect payment details, a bank server that is temporarily down, patchy network connectivity, insufficient balance, authentication mistakes such as a wrong PIN, transaction limits being exceeded, or a straightforward technical glitch somewhere in the chain. The error code is the system's way of telling you which of these it hit.
Common UPI Error Codes and What They Actually Mean
Code 00, Success. The transaction completed. No action needed.
Code 91, Bank Server Down. The receiving or sending bank's server is temporarily unreachable. Wait a few minutes and retry.
Code 92, Unable to Process. A general technical decline upi message, usually a temporary glitch somewhere in the payment chain. Retrying after some time typically resolves it.
Code 94, Duplicate Request. A near-identical transaction has already been submitted or processed. Check your history before retrying to avoid a double payment.
Code U16, Risk Threshold Exceeded. The transaction was flagged by fraud or risk-monitoring parameters. Retry later, or contact your bank if it keeps recurring.
Code U17, Transaction Declined. The bank declined the payment outright, often due to insufficient balance or an account restriction.
Code U19, Invalid Credentials. Usually an incorrect UPI PIN was entered. Re-enter carefully rather than repeatedly guessing.
Code U28, Transaction Limit Exceeded. The amount exceeds a limit set by your bank or the UPI system itself. Split the payment or retry within the allowed limit.
Code U30, Format Error. Payment details, such as the UPI ID or account information, were entered in an invalid format. Verify recipient details carefully.
Code U31, Invalid UPI ID. The UPI ID entered does not exist or was typed incorrectly. Double-check the recipient's ID before retrying.
Why it matters: Codes starting with U generally point to something checkable on your side, wrong PIN, wrong ID, exceeded limit, while codes like 91 and 92 usually point to infrastructure issues you cannot fix directly and just need to wait out.
| Error Pattern | Likely Cause | What to Do |
|---|---|---|
| 91 / 92 (numeric, infra-related) | Bank server or network issue | Wait and retry after a few minutes |
| U16 / U17 (risk or decline) | Risk flag or bank-side decline | Retry later, or contact your bank if repeated |
| U19 / U30 / U31 (input-related) | Wrong PIN, format, or UPI ID | Recheck and correct the entered details |
| U28 (limit-related) | Transaction exceeds allowed limit | Reduce the amount or split the payment |
If Money Was Debited but the Transaction Still Failed
This specific scenario understandably causes the most anxiety, but it is also the most predictable outcome to resolve. When a debit happens alongside a failure, the transaction is usually marked pending in the background, and the amount is reversed automatically once reconciliation completes between the banks involved. The exact reversal window varies by bank, typically a few hours to a couple of banking days, so checking your transaction history rather than immediately retrying the payment is the safer first step.
Reducing How Often You Hit These Errors
Double-check the recipient's UPI ID and the amount before confirming, since format and ID errors are among the most common and most avoidable failures.
Keep your payment app updated, since older versions occasionally throw errors that a current build has already fixed.
Avoid retrying a payment immediately after a failure without checking your history first, to prevent an accidental duplicate transaction.
Know your bank's per-transaction and daily UPI limits in advance so a limit-related decline does not catch you off guard.
When to Actually Contact Support
Escalate to your bank or payment provider directly if an error persists across several retry attempts spread over a reasonable window, if a debited amount is not reversed within the expected timeline, or if you notice a transaction you never authorized. Having the transaction reference number ready before you call or chat noticeably speeds up resolution.
Stashfin's UPI Money Transfer is built to keep this friction to a minimum in the first place, letting you Scan & Pay to a mobile number or UPI ID, or move funds to your own bank account, on rails designed to fail cleanly and clearly rather than leave you guessing at a cryptic code.
Key Takeaways
UPI error codes are diagnostic, not just an inconvenience. Codes in the 90s range usually point to infrastructure issues like a bank server outage, while U-prefixed codes typically point to something checkable on your end, a wrong PIN, an invalid UPI ID, or an exceeded limit. If money is debited during a failed transaction, it is almost always reversed automatically within a bank-defined window, so checking history before retrying is the safer move. Persistent errors or unreversed debits are the clear signal to contact support directly.
