Every declined transaction represents more than a failed payment; it is direct revenue leakage. When genuine customers are stopped at checkout, you lose the sale, future lifetime value, and sometimes the relationship altogether. Studies across global e-commerce estimate that false declines cost businesses billions annually, with a significant portion coming from legitimate payments incorrectly rejected by issuing banks.
Payment authorisation rate is the percentage of transactions approved by the card issuing bank out of the total submitted transactions. The formula is simple: divide approved transactions by total attempted transactions and multiply by 100. If you submit 10,000 transactions and 8,800 are approved, your authorisation rate is 88%. Even a 2% improvement can translate into substantial incremental revenue at scale.
A major contributor to low approval performance is network declines. These occur when the issuing bank rejects a transaction after it has already passed your internal validations and fraud checks. Unlike gateway errors or internal fraud blocks, network declines originate from the issuer’s systems or card network risk models. Many are triggered by generic risk signals, technical disconnects, or outdated card credentials rather than actual fraud.
Key takeaways
- Network declines are transaction rejections issued directly by the cardholder’s bank, distinct from gateway errors or fraud blocks, and often represent the final hurdle to securing revenue.
- Optimisation strategies must clearly separate soft declines (temporary, retryable failures) from hard declines (permanent errors that must never be retried).
- A healthy authorisation rate for domestic e-commerce typically ranges between 85% and 95%; falling below this benchmark signals avoidable revenue leakage.
- Implementing network tokenisation and smart routing can significantly improve payment success by keeping credentials updated and directing traffic through the best-performing acquiring banks.
What Are Network Declines?
Network declines are transaction rejections issued by the cardholder’s bank (issuer) or the card network (such as Visa, Mastercard, or RuPay) after the payment has passed your system’s initial checks. They differ from other failures in both their source and how they must be resolved.
Recognising the differences between decline types is essential for effective optimisation:
| Decline Type | Where It Happens | Typical Cause | Who Controls It |
| Gateway Declines | Payment gateway stage | Invalid CVV, incorrect expiry, format error | Merchant data handling |
| Fraud Blocks | Merchant risk engine | High risk score, blacklisted IP | Merchant fraud settings |
| Network Declines | Issuer or card network | Insufficient funds, risk flags, timeouts | Issuer decision systems |
Network declines happen at the final step in the transaction lifecycle. The payment request travels from your checkout to the payment gateway, then to the acquirer, onward to the card network, and finally to the issuer. If rejected at this stage, you are dealing with an issuer rejection.
Common triggers include insufficient funds, unusual spending patterns, expired cards, cross-border flags, and technical timeouts between the acquirer and issuer. Because they occur after internal checks, they represent the last barrier to payment success and therefore the largest opportunity for optimisation.
Categorising Declines: Soft vs. Hard
Accurately categorising decline types is essential for effective optimisation. Your response should depend on whether the decline is temporary (soft) or permanent (hard). Misclassifying them can harm your standing with card networks and lower approval rates over time.
What Are Hard Declines?
Hard declines are permanent errors indicating that the card or account is fundamentally invalid for processing. No amount of retry logic will convert these into approvals.
Examples include:
- Stolen or lost card reported
- Invalid account number
- Closed account
- Restricted card
- Pick up card instructions
Retrying hard declines can lead to fines from card networks, reduced merchant trust scores, and lower future approval rates. Issuers track merchant behaviour, and repeated attempts on permanently invalid cards damage issuer reputation.
What Are Soft Declines?
Soft declines are temporary failures caused by situational factors. The underlying account remains valid, but approval is blocked at that moment.
Examples include:
- Insufficient funds
- Generic “Do Not Honor”
- Network timeout
- Issuer system unavailable
- Daily limit exceeded
These represent the primary opportunity for payment retries and recovery strategies. Intelligent retry logic, alternate routing, or additional authentication can convert many soft declines into successful transactions.
Soft vs. Hard Declines Comparison
| Category | Definition | Examples | Recommended Action |
| Soft Decline | Temporary issue; approval may succeed later | Insufficient funds, timeout | Retry strategically |
| Hard Decline | Permanent invalidity of account or card | Closed account, stolen card | Do not retry |
Decoding Common Network Decline Codes
Issuers communicate decline reasons using numeric response codes. These codes, known as decline codes or response codes, signal why a transaction was rejected. Some are clear and specific; others are intentionally vague to protect customer privacy.
Merchants should map raw response codes into actionable categories. Without structured mapping, automation becomes impossible and recovery opportunities are lost.
Common Decline Codes Cheat Sheet
| Code | Meaning | Category | Suggested Action |
| 51 | Insufficient funds | Soft decline | Retry after pay cycle |
| 05 | Do Not Honor | Soft decline | Apply 3DS or customer contact |
| 54 | Expired card | Lifecycle issue | Use account updater |
Code 51: Insufficient Funds
Code 51 means the cardholder does not have enough available balance or credit. This is a classic soft decline.
Optimisation strategy: trigger a dunning email asking for a different card or retry after common pay periods, such as the beginning of the month. Subscription businesses often recover a significant portion of these declines with structured retry schedules.
Code 05: Do Not Honor
Code 05 is a generic refusal. The issuer declines but does not provide a specific explanation. It is often linked to suspicious velocity, location mismatch, or unusually high transaction values.
Optimisation strategy: encourage the customer to contact their bank or introduce 3DS 2.0 authentication. Additional data exchange increases issuer confidence and can convert a generic decline into approval.
Code 54: Expired Card
Code 54 indicates the card expiry date has passed.
Optimisation strategy: prevent this entirely using account updater services. Updating credentials before submission ensures valid data reaches the issuer.
Explore Razorpay’s Payment Solutions
Strategies to Reduce Network Declines
Reducing network declines requires technical upgrades that influence issuer perception and processing logic. These strategies either update payment data, improve trust signals, or optimise the technical transaction path.
Implement Network Tokenisation
Network tokenisation replaces the Primary Account Number with a token issued by the card scheme. These tokens update automatically if the underlying card changes.
Benefit one: automatic lifecycle updates prevent declines caused by expired or replaced cards.
Benefit two: issuers trust network tokens more than stored PAN data, often resulting in a 2–3% uplift in approval rates.
Leverage Smart Routing
Smart routing dynamically selects the best acquiring bank for each transaction in real time.
Some issuers approve transactions more frequently when routed through specific acquirers due to regional proximity or historical trust. If one acquirer experiences downtime, the system reroutes instantly to a healthier provider, preventing technical network declines.
Enable Real-time Account Updaters
Account updater services query card network databases for updated credentials before submitting a transaction.
The gateway automatically refreshes expiry dates or card numbers, submits valid information, and prevents declines tied to outdated data. This is particularly powerful for recurring revenue models.
Adopt 3D Secure 2.0
Many “Do Not Honor” declines stem from issuer uncertainty about fraud risk. 3DS 2.0 solves this by sending over 100 data points, including device information, browser behaviour, and transaction history.
With richer context, issuers gain confidence in the transaction’s legitimacy and are more likely to approve rather than default to decline.
Optimise Merchant Category Codes (MCC)
Every merchant has a four-digit MCC describing their business type. Issuers use this code to determine risk appetite.
Misclassification can trigger unnecessary issuer rejection. Audit and correct MCC assignments with your processor to align your business activity accurately with issuer risk models.
How to Calculate Authorisation Rate?
Authorisation rate measures approval performance.
Formula:
Authorisation Rate = (Total Approved Transactions ÷ Total Attempted Transactions) × 100
For deeper insight, calculate gross auth rate and net auth rate. Gross includes all attempts. Net excludes user errors like wrong PIN entries. Domestic e-commerce benchmarks typically exceed 85–90%.
How Razorpay Optimiser Maximises Payment Success
Razorpay Optimizer uses artificial intelligence and machine learning to analyse transactions in real time and route payments through the most reliable path. By evaluating over 50 parameters for each transaction, it helps improve approval rates by up to 10%.
Its optimisation strategy rests on three key mechanisms. First, it tracks real-time health scores of payment providers, detecting downtime or performance issues and automatically rerouting transactions to stable alternatives. This reduces technical failures that often cause network declines. Second, it applies smart retry logic for soft declines, timing repeat attempts based on decline reasons and past recovery trends.
The platform also integrates network tokenisation, automatically converting card details into secure tokens. These tokens stay updated even if cards expire or are replaced, reducing avoidable declines. This feature is especially useful for subscription businesses or merchants storing customer payment details.
Ready to streamline your payments?
Scale your business with a gateway that supports 100+ payment methods, including UPI, Credit Cards, and Netbanking. Transition to a reliable infrastructure designed to improve transaction success rates and automate your daily reconciliation.
Conclusion
Network declines require more than basic processing fixes. Improving authorisation rates starts with a mindset shift: treat each decline as useful data that highlights gaps in your payment setup. When addressed systematically, small improvements across multiple areas can compound into meaningful gains.
Modern optimisation blends technology, clean data, and smart strategy. Tools like network tokenisation, intelligent routing, and stronger authentication can turn payments from a cost centre into a growth driver. Even modest gains matter—a 2% lift in authorisation rates on ₹10 crore in monthly volume can generate significant additional annual revenue.
Optimisation is ongoing. Issuer rules, technology, and customer behaviour continue to change, so regular monitoring is essential. Begin by setting clear baseline metrics and analysing decline codes to spot high-impact areas. Prioritise soft decline recovery and credential updates for quick wins. Continuous, focused improvements in approval rates strengthen revenue, customer trust, and long-term performance.
FAQs
1. What is the difference between a soft decline and a hard decline?
A soft decline is a temporary failure where the payment method is still valid but blocked by short-term issues such as insufficient funds, issuer timeouts, or transaction limits. These may be resolved through retries, alternate routing, or customer action.
A hard decline signals permanent invalidity. For example, a stolen card, closed account, or incorrect card number. Retrying hard declines breaches card network rules and can harm your merchant standing, increasing future decline rates and penalties.
2. What does the ‘Do Not Honor’ decline code mean?
‘Do Not Honor’ (Code 05) is a generic decline issued by the bank without a specific reason. It usually reflects risk checks triggered by unusual activity, location mismatches, high amounts, or spending patterns that differ from the cardholder’s normal behaviour. Resolution typically requires the customer to contact their bank or complete additional authentication, such as 3D Secure, to verify the transaction.
3. What is considered a good payment authorisation rate?
Good authorisation rates depend on transaction type and market. Domestic e-commerce typically sees 85–95% approvals, while international transactions average 75–85% due to cross-border factors. Subscription businesses should aim for 90–95%, and high-risk categories often operate at 70–85%. The key is benchmarking against your own industry and transaction mix rather than relying on generic averages.
4. How does smart routing reduce network declines?
Smart routing reduces network declines by using real-time data to choose the payment path most likely to succeed. It tracks approval rates between acquirers and issuers, system availability, and response times. If a provider shows higher declines or technical issues, transactions are automatically redirected to stronger alternatives. This approach can raise approval rates by 3–8%, while also adding redundancy and helping control transaction costs.
5. Is it safe to retry a declined transaction?
Retry safety depends on the decline type and reason code. Soft declines, such as insufficient funds, timeouts, or temporary authentication failures, can be retried after suitable delays, like 24–72 hours for funding issues or immediately for technical errors. Hard declines, including stolen cards, closed accounts, or invalid numbers, must not be retried under card network rules. Excessive retries harm your reputation, raise costs, and may lead to penalties or suspension. Use intelligent retry logic that classifies declines and applies retries only where allowed.
