"Payment failed" is one of the least helpful messages on the internet. It covers everything from a mistyped OTP to a bank's servers being down for maintenance, and it rarely says which. Most people's response is to try again, sometimes three or four times, which occasionally works and occasionally leaves them with several debits to chase.
This guide is about why payments fail and how to tell the causes apart. If your account was debited and the payment still shows failed, the main question is when the money comes back, which our guide to money debited but transaction failed answers with RBI's deadlines for each payment type. If the payment shows pending, read UPI payment pending first: pending isn't failed. For UPI-specific causes, see UPI transaction failed.
Declined, failed, pending, reversed: four different outcomes
These words get used loosely, but they describe different things, and they lead to different next steps.
| Outcome | What happened | Your money | Retry? |
|---|---|---|---|
| Declined | Your bank said no: not enough money, a limit, a security check, a blocked card | Not debited (or a hold released quickly) | Only after fixing the reason, or with another method |
| Failed (technical) | Something in the chain didn't respond or broke mid-way | Usually not debited; sometimes debited and reversed later | Yes, after checking you weren't debited |
| Pending | The result hasn't reached your app yet | Unknown, may be debited | No. Wait for it to resolve |
| Reversed | You were debited, the payment didn't complete, and the money came back | Back in your account | Yes, if you still want to pay |
Where a payment can break
An online payment passes through several hands in a few seconds. A failure anywhere ends the payment, and the error you see depends on where it happened.
- 1You and your deviceWrong PIN or OTP, lost connection, app or browser closed
- 2Merchant's checkoutMethod not offered, session expired, page error
- 3Payment providerGateway or aggregator unavailable, risk rules, configuration
- 4NetworkCard network or UPI timeouts between banks
- 5Your bankFunds, limits, card settings, fraud checks, downtime
1. You and your device
The most common causes are also the easiest to fix:
- A wrong UPI PIN, card PIN or OTP. Repeated wrong entries can also lock you out for a while.
- An OTP that never arrived: the SIM with your bank-registered number isn't in the phone, the signal is weak, or the OTP expired while you were switching apps.
- The connection dropped after you authorised. The payment may still have gone through; check before retrying.
- You switched away from the bank's page or closed the UPI app mid-payment, or the browser blocked the bank's authentication page or pop-up.
- You took too long. Bank authentication pages and checkout sessions expire.
2. The merchant's checkout
Some failures have nothing to do with you or your bank:
- The payment method or card type isn't enabled for that merchant, such as international cards or a particular wallet.
- The checkout session expired, or the page sent an amount or order that no longer matched.
- The merchant's system blocked what looked like a duplicate attempt for the same order.
3. The payment provider
The gateway or aggregator behind the checkout can have a bad moment: an outage, a slow connection to a particular bank, or a risk rule that stops a payment it considers unusual. Customers see a generic failure. Merchants who use more than one provider can route around this; our explainer on smart payment routing shows how failover works and why it differs from simply retrying.
4. The network between banks
Card payments pass through a card network, and UPI payments through NPCI, between the merchant's bank and yours. Each step has a deadline. In UPI, for example, banks must respond to a payment request within 15 seconds; when a reply misses its window, the payment can't be confirmed and ends up failed or pending. These timeouts are more likely at busy times, which NPCI identifies for UPI as roughly 10 am to 1 pm and 5 pm to 9:30 pm.
5. Your bank
Your bank (the issuer, for cards) makes the final call. It declines a payment when:
- There isn't enough money in the account, or the card's available limit is too low.
- The payment would go over a limit: your bank's own daily limit, UPI's per-payment or daily limit, or a limit for that merchant category. Our guide to UPI transaction limits lays these out.
- The card isn't enabled for this kind of use. Many cards come with online or international use switched off until you turn it on in your banking app or with your bank.
- The card is expired, blocked, or replaced by a new one.
- Its fraud checks flag the payment: an unusual amount, a new device, a new merchant, or a pattern it doesn't like.
- Its own systems are down or slow, often during scheduled maintenance at night.
What the error message usually means
Apps and checkouts word things differently, but most messages fall into a handful of groups. Treat this as a guide to the likely cause; your bank's or app's own message is the final word. If your bank declined the payment, our guide to payment declined errors explains each decline reason and when retrying makes sense.
| You see something like | Usually means | Try |
|---|---|---|
| Insufficient funds / insufficient balance | Your bank declined for lack of money or limit | Add funds or use another account or card |
| Transaction limit exceeded | You've hit a per-payment, daily or category limit | Wait for the limit to reset, split if allowed, or use another rail |
| Incorrect PIN / invalid OTP | Authentication failed | Re-enter carefully; reset your PIN if you've forgotten it |
| Card not enabled / transaction not permitted | Online, international or contactless use is off, or the merchant type is blocked | Enable the usage in your banking app, then retry |
| Declined by bank / do not honour | Your bank refused, often a fraud or risk check | Call your bank's official number or check its app, then retry |
| Payment timed out / bank not responding | A system in the chain didn't reply in time | Check you weren't debited, wait a few minutes, retry |
| Session expired | You took too long, or the checkout page went stale | Start the payment again from the cart |
| Method unavailable | The merchant or its provider can't take this method right now | Use another method |
Before you retry: a two-minute checklist
Retrying is often fine. Retrying blindly is how people end up paying twice.
- Check whether you were debited: look at your bank SMS or balance, not only the merchant's page.
- If you were debited, check whether the order or booking actually went through: your order history, a confirmation email or SMS, or the biller's status. If it did, the payment didn't really fail.
- If you were debited and the order didn't go through, don't pay again for the same thing until you're sure. The debit should be reversed by RBI's deadline, which this guide sets out.
- If you weren't debited, fix the likely cause from the table above, or switch method. UPI, a card and net banking take different routes, so one often works when another doesn't.
- If the same payment fails repeatedly with the same message, stop and contact your bank. Repeated attempts can trip fraud checks and make things worse.
Why the same payment works in one place and fails in another
A card that works in a shop but fails online usually has online use turned off, or fails the extra authentication step online, which in-store tap payments of up to ₹5,000 can skip. A UPI payment that fails in one app but works in another may have hit a problem with the first app's bank (its PSP) rather than yours. And a payment that fails on one website but works on another may be down to that merchant's checkout or provider, not you at all.
If you run the checkout
From the merchant's side, failed payments are lost sales, and many are recoverable. A few habits make the biggest difference:
- Separate declines from technical failures in your reporting. Declines (insufficient funds, wrong PIN) are mostly the customer's to fix; technical failures (timeouts, provider errors) are yours.
- Track failure rates by payment method, bank and provider, so a spike points straight at its cause.
- Don't mark an order failed on the strength of the browser's return page. Check the payment's status through your provider and wait for its webhook; some "failures" turn out to be successful payments whose confirmation was late.
- Show the customer a useful message ("your bank declined this card; try another method") rather than a generic error, and tell them not to pay twice if they've been debited.
- Offer more than one method, and, if you can, more than one provider for the method that matters most to you. Our payment gateway guide covers why payments fail from the merchant's side and how to handle each case.
Frequently asked questions
My payment failed but money was debited. What now?
Don't pay again for the same thing until you've checked whether the order went through. If it didn't, your bank must reverse the debit within RBI's deadline for that payment type and pay you ₹100 a day if it's late. Our guide to money debited but transaction failed has the deadlines and the complaint process.
Is it safe to retry a failed payment?
Yes, once you've confirmed you weren't debited, or that the first attempt didn't complete the order. If the same payment keeps failing with the same message, stop and check with your bank instead of retrying again and again.
Why does my card work in shops but fail online?
Usually because online use is switched off on the card, or because online payments need an extra authentication step, such as an OTP, that tap payments in shops can skip for small amounts. Check the card's usage settings in your banking app.
Why does a payment fail in one UPI app but work in another?
Each UPI app works through its own bank (its PSP). If that bank is having trouble, payments through that app fail even though your own bank is fine. Another app uses a different route to the same account.
Who can tell me exactly why my payment was declined?
Your bank, for a decline it made, since it saw the reason. The merchant usually sees only a general code. Use your bank's app or official customer care, and have the date, amount and merchant name ready.
Go deeper
Official sources
- NPCI — UPI Consolidated Circular, Version 1.0, NPCI/UPI/CC/01 (18 Sep 2026)UPI response times: 15 seconds for payment requests and 10 seconds for status checks and reversals (12.1); peak hours (Annexure A); conditions in which a transaction is treated as failed (12.5, Annexure C).
- RBI — Harmonisation of Turn Around Time and customer compensation for failed transactions (20 Sep 2019)Reversal deadlines by payment type and ₹100 per day compensation after them.
- RBI — Card transactions in contactless mode: relaxation in requirement of additional factor of authentication (4 Dec 2020)Contactless card payments up to ₹5,000 without an additional factor of authentication, from 1 January 2021.
- RBI — Authentication mechanisms for digital payment transactions Directions, 2025Additional factor of authentication for digital payments and its listed exemptions.
Last reviewed . Examples, amounts and screens marked illustrative are not LILPE figures.
