Payment Declined: A Complete Guide to Decline Codes for Merchants
Highlights:
- Learn what payment decline codes are and how banks use them to communicate transaction failures.
- Discover the difference between Business Declines and Technical Declines in UPI payments.
- Understand RBI's auto-reversal rules and customer compensation for failed transactions.
- Find out how long refunds take and when to retry declined payments safely.
Introduction
A customer is ready to buy. They enter card details, click pay, and then see the dreaded message: payment declined. For shoppers, it is frustrating. For businesses, it can mean lost revenue and abandoned carts.
Behind every failed transaction is usually a decline code, a short response sent by the card issuer or payment processor explaining why the payment was not approved. Understanding these codes helps customers fix issues faster and helps merchants recover failed payments.
If you have ever wondered why your payment is being declined, this guide explains the most common reasons, what decline codes mean, and what to do next.
What Is a Payment Decline Code?
A payment decline code is a response code sent by the issuing bank, card network, or payment processor when a transaction is not approved. It explains why a payment failed and helps merchants or customers understand the reason behind the decline.
When a customer sees a payment declined message at checkout, the actual cause is often represented by a numeric or text-based decline code in the background. These codes are used across card payments, recurring billing, and online transactions.
Common examples include:
- 05: Do Not Honour
- 51: Insufficient Funds
- 54: Expired Card
- 57: Transaction Not Permitted
- 91: Issuer Unavailable
Some decline codes indicate customer-related issues, such as a low balance or wrong card details. Others point to technical problems, such as bank server downtime or network errors.
For businesses, payment decline codes are valuable because they help identify whether the payment should be retried, whether another payment method should be offered, or whether the customer needs to contact their bank.
Understanding decline codes can improve payment success rates, reduce cart abandonment, and create a smoother checkout experience.
Types of Payment Declines: Business vs Technical
Not every failed transaction happens for the same reason. In payment processing, declines are generally grouped into two categories: business declines and technical declines. Understanding the difference helps merchants improve payment success rates and respond correctly when customers see a payment declined message.
Business Declines
A business decline occurs when the issuing bank or payment provider intentionally rejects a transaction based on financial, security, or policy checks. These are rule-based decisions.
Common examples include:
- Insufficient funds
- Card expired
- Incorrect CVV or card number
- Credit limit exceeded
- International usage disabled
- Suspected fraud activity
- Recurring mandate failure
In these cases, the transaction usually requires customer intervention. The user may need to update card details, use another payment method, or contact their bank.
Technical Declines
A technical decline happens when the transaction fails due to infrastructure or connectivity issues rather than a financial decision. The bank may never complete the approval process.
Common examples include:
- Network timeout
- Payment gateway outage
- Bank server downtime
- OTP delivery failure
- API error
- Session timeout during checkout
These declines are often temporary and may succeed if retried after a short time.
Common Payment Decline Codes Merchants Encounter
Common payment decline codes include insufficient funds (51), expired cards (54), incorrect CVV (97), and "do not honour" (05), which indicates a general bank refusal. For security, codes 07 (fraud), 41 (lost card), and 59 (suspected fraud) are common, signalling, as explained in this guide to decline codes, potential risk. Merchants should distinguish between soft declines (retryable) and hard declines (permanent) to manage transactions.
Here is a breakdown of the most common decline codes:
Common Decline Codes and Meanings
- 01/02 – Refer to Issuer: The bank requires the cardholder to call them. This is often due to a security hold or a high-value purchase.
- 03 – Invalid Merchant: The merchant account is not configured correctly or is not recognised by the issuer.
- 04/07/41/43 – Pick Up Card/Fraud: The card is reported lost or stolen or is suspected to be used fraudulently.
- 05 – Do Not Honour: A generic message indicating the bank refuses to authorise the card, often due to a lack of funds, but sometimes a restriction.
- 12/13/14 – Invalid Transaction/Amount/Account: The request was formatted improperly, the amount is invalid, or the card number is invalid/misentered.
- 51 – Insufficient Funds: The most common code; the account lacks necessary funds or has hit its credit limit.
- 54 – Expired Card: The card's expiration date has passed.
- 57/58 – Transaction Not Permitted: The card or terminal is restricted from performing the requested transaction (e.g., trying to use a credit card at an ATM).
- 59 – Suspected Fraud: A bank-specific security check has flagged the transaction.
- 62 – Invalid/Restricted Service Code: The card is blocked for specific, often international, purchases.
- 65 – Exceeds Withdrawal Limit: The transaction exceeds the allowed frequency or amount of withdrawals.
- 91 – Issuer Unavailable: The bank's authorisation system is down. This is a common "soft" decline that often works if retried later.
- 96 – System Error: A technical error occurred, often with the payment gateway or bank, says this overview of decline codes.
- 97 – Invalid CVV/CCV: The security code provided does not match the bank's records.
UPI-Specific Decline Codes in India
UPI-specific decline codes are error messages shown when a UPI transaction fails. These codes are generated by the bank, UPI app, or NPCI network to explain why the payment was not completed.
Common UPI decline reasons include:
- Incorrect UPI PIN
- Insufficient balance
- Daily transaction limit exceeded
- Bank server unavailable
- Invalid UPI ID
- Network timeout
- User cancelled transaction
Examples of common codes or messages:
- U16: Security or risk restriction
- U17: Transaction declined by the bank
- Bank Down: Issuer bank unavailable
- PIN Error: Wrong UPI PIN entered
For businesses, understanding these decline codes helps reduce failed payments and improve checkout success.
Understanding Declines Improves Customer Experience
Payment decline codes transform cryptic error messages into actionable information. Knowing the difference between Business Declines requiring customer action and Technical Declines allowing retry helps you guide customers accurately. With RBI's auto-reversal protections and UPI's real-time refunds, Indian merchants can assure customers their money is safe even when payments fail.
FAQs
1. Why is my customer's UPI payment being declined despite a sufficient balance?
UPI declines occur when customers exceed daily transaction limits, enter the wrong PIN repeatedly, or face technical issues at their bank. Ask customers to verify their daily limit with their bank and retry. Most banks allow ₹1 lakh per transaction but may restrict the daily transaction count.
2. How long will my customer wait for a refund on a declined payment?
For UPI, reversals happen immediately within 1 hour maximum. For card or ATM transactions where the amount was debited, RBI mandates a refund within T+5 days with ₹100 daily compensation for delays. Customers should contact their bank if the refund exceeds these timelines.
3. Can I retry a declined transaction immediately, or should I wait?
For Technical Declines caused by system issues, wait 30-60 minutes before retry. For Business Declines like wrong PIN or limit exceeded, the customer must fix the issue first. Never retry suspected fraud declines. Wait 24 hours and ask the customer to verify with the bank.
4. What should I tell customers when payment is declined due to suspected fraud?
Inform customers that their bank flagged the transaction for security. They should contact their bank to confirm the transaction is legitimate. Banks often send SMS or app notifications for approval. Once verified, customers can retry immediately. This PCI security protection safeguards customer data.
5. If payment fails but the customer account is debited, what compensation applies?
RBI mandates banks to reverse failed transactions within T+5 days and pay ₹100 per day compensation for delays beyond this timeline. Compensation credits are automatically awarded without a customer claim. This applies to ATM, card, and PoS transactions.
