Why Do Online Payments Fail? Common Reasons and How to Fix Them

A failed payment is rarely just one problem. The customer sees a red error screen, but behind it there might be a bank server that did not reply, a UPI PIN typed wrong, an OTP that arrived 40 seconds late, or someone who simply changed their mind. Each of these needs a different fix, and some of them are not yours to fix at all.

This guide sorts the common causes into groups, so you can work out where your own failures come from and what to do about them.

What are the three types of payment failure?

Almost every failed online payment fits into one of three buckets. Knowing the split for your business is the first step, because only some of them respond to changes on your side.

1. Technical failures: the bank, card network, UPI app or payment gateway did not respond in time or returned an error.
2. Declines: the payment reached the bank and the bank said no, for example because of low balance or a wrong PIN.
3. Customer drop-offs: the customer left during the OTP, UPI app or net banking step.

Technical reasons online payments fail

Bank or UPI downtime

Issuing banks have scheduled maintenance and unplanned outages. When a customer's bank is down, their UPI and net banking payments fail no matter which gateway you use. You will often see failures cluster around one bank for a short period.

Payment gateway errors and timeouts

Gateways have bad moments too, especially under heavy load during sales. Timeouts are the tricky ones: the payment may still succeed at the bank a little later, which is why you should never mark a timed out payment as failed without checking its final status.

Network drops on the customer's phone

Switching from your app to a UPI app and back is a moment where weak mobile data causes trouble. The payment may go through while your page never hears about it, which is where webhooks matter.

Common decline reasons from banks

• Insufficient balance in the customer's account.
• Wrong UPI PIN or too many wrong attempts, which can temporarily block UPI for that account.
• Transaction limits. UPI has a per-transaction limit (₹1 lakh for most payments, higher for a few categories), and banks set their own daily limits. Some banks also cap the amount for the first day after a customer sets up UPI on a new phone.
• Card not enabled for online use. Since RBI's 2020 card security rules, new debit and credit cards are enabled only for domestic ATM and POS use by default. The cardholder has to switch on online and international payments in their banking app.
• Wrong card details or expired card.
• Risk checks. The bank or gateway may block a payment that looks unusual, such as a large amount from a new device.

You cannot change these decisions, but you can soften them. Show a clear message that says what went wrong in plain words, and offer a different payment method right there.

Why customers drop off during payment

• The OTP arrives late or not at all.
• The UPI collect request expires before they open the app.
• They get distracted while switching between apps.
• The checkout asks for too much, or shows an unexpected charge at the last step.
• They want to pay by a method you do not offer.

How can merchants reduce failed payments?

1. Measure success rate by method and by bank. A single overall number hides the story. A drop in UPI payments from one bank points to a very different cause than a drop across all cards.
2. Use UPI intent on mobile. Letting the customer pick their UPI app and opening it directly is usually smoother than asking them to type a UPI ID and wait for a collect request.
3. Offer a quick retry with another method. When a card fails, suggesting UPI on the same screen saves many orders.
4. Handle pending payments properly. Wait for the webhook or check status before telling the customer it failed. This alone avoids a lot of "money debited but order failed" complaints.
5. Keep a backup gateway. Gateway-side failures and timeouts drop sharply when you can route to a second gateway. This is the core idea behind a multi PG payment gateway.
6. Write better error messages. "Payment failed" is useless. "Your bank declined this card for online use. Try UPI or enable online payments in your bank app" actually helps.

Failure reasons and fixes at a glance

What happens when money is debited but the payment fails?

This is the case that worries customers most. The bank has taken the money, but the gateway or your system never got a success confirmation, so the order shows as failed. In most cases the payment is automatically reversed to the customer. RBI has set fixed turnaround times for these reversals and compensation if banks miss them, so tell customers that clearly instead of leaving them to guess.

On your side, keep listening for webhooks even after you show an error. If a success callback arrives late, you can either fulfil the order or refund it on purpose, rather than leaving the money in limbo.

Want to put a number on it? The calculator on our reduce payment failures page shows how much gateway-side failures cost you each month.

Where to start

Export a month of failed payments and tag each one as technical, decline or drop-off. If technical failures are a big share, a second gateway with payment routing is the most direct fix. If declines dominate, focus on messaging and alternative methods. If drop-offs dominate, look hard at your checkout flow.