Failed transactions explained: causes, decline codes, and fixes

Failed payments cost the global economy billions annually. Behind that are thousands of individual incidents, including declined cards at checkout, subscriptions that didn't renew, and payouts that never arrived, each eroding conversion rates, customer trust, and revenue.

In customer success, you develop a sharp eye for payment failure patterns: the approval rate that dipped after a routing change, the subscription cohort with unusually high involuntary churn, the payout batch that stalled without a clear error code. What these situations have in common is that the root cause is rarely obvious at first glance, but once you know what to look for, the patterns repeat. And most of them are preventable.

In this article, I'll break down the most common reasons why transactions fail, from soft and hard declines to 3DS friction and issuer-side restrictions, and set out what payment teams can do to reduce them systematically.

What is a failed transaction?

A failed transaction is a payment attempt that does not result in a successful transfer of funds. This includes a card declined at checkout, a subscription charge that doesn't go through, a payout rejected by the receiving bank, or a bank transfer that times out before settlement⁠.

The failure can originate at any point in the payment flow from the moment a customer submits their details to the final confirmation from the issuing bank.

Failed transactions are sometimes confused with pending or reversed payments. Still, the distinction matters operationally: a failed transaction never completes, whereas a reversal or refund involves funds that were initially authorised or settled.

Why do transactions fail: top reasons and ways to cope

Every failed transaction falls into one of two categories, and the distinction determines what happens next.

• A soft decline means the transaction was rejected, but the issue is resolvable. The card itself is valid; the problem is situational — a fraud flag triggered by an unusual purchase pattern, a spending limit temporarily exceeded, or a bank requiring additional authentication. Soft declines can often be recovered by retrying, changing routing, or prompting the customer to contact their bank.
• A hard decline is permanent. The issuing bank will not authorise this transaction under any circumstances — the card has expired, is reported stolen, or the account is closed. Retrying a hard decline wastes resources and risks further friction. The right response is to ask the customer to use another payment method.

Not all failed transactions deserve the same response. Treating a soft decline like a hard one means leaving recoverable revenue on the table. Treating a hard decline like a soft one means burning customer goodwill with repeated failed attempts.

Below are the most common causes I see behind both categories, and what payment teams can do about each.

3D Secure authorisation friction

3DS errors are among the most common causes of failed payments and often the most fixable. They typically occur when a user doesn't receive the one-time code, enters it incorrectly, or abandons the flow before the authentication page fully loads. The requirements for 3D Secure authorisation vary by bank and transaction risk level, so it's worth aligning with your PSP and card issuers on where friction is highest and which transaction types qualify for frictionless flow exemptions under SCA rules⁠.

💳Maximise your acceptance rates

This 101 guide explains the concept of payment routing, its best practices, and how to it helps boost payment acceptance rates.

Learn more

Insufficient funds

Insufficient funds are a hard stop on the customer's side; the merchant can hardly resolve it directly. But businesses can reduce the impact: real-time decline notifications with clear messaging give customers a chance to top up and return, while offering alternative payment methods⁠ at the point of failure captures sales that would otherwise be lost entirely. For subscription businesses, smart retry logic timed around likely payday cycles recovers a meaningful share of these declines.

Block by antifraud systems

Quite often, declines occur due to suspicious payers' behaviour, fraudulent activity, and blocklisting. Usually, these are fraud-prevention measures or fraud-detection algorithms that track unusual behaviour or activity and take further action, such as declining a transaction or adding the cardholder to a blocklist. While these fraud prevention systems are effective, they can sometimes mistakenly decline legitimate transactions, impacting customer experience. Merchants can utilise smart anti-fraud tools⁠ with customised blocklists and allowlists, or monitor specific payments and process them manually.

🛡Fight fraud efficiently

Learn more

Recurring payment failures

Subscription and recurring billing⁠ failures behave differently from one-off transaction declines. The most common causes are expired cards, updated account details that the merchant was never notified about, and bank-side blocks on recurring charges. Unlike a checkout decline, where the customer is present and can act immediately, a failed recurring payment often goes unnoticed until the customer loses access to a service.

The recovery toolkit here is specific: account updater services automatically refresh stored card credentials before a charge attempt; smart retry logic spaces retries around likely payday windows rather than retrying immediately; dunning sequences notify customers early enough to act. Businesses that address recurring failures systematically typically recover 20–30% of initially failed subscription charges.

Payers' errors due to complex UI/UX

Input errors are entirely preventable. A well-designed checkout with card number fields split into four-digit blocks, inline validation, and clear CVC code⁠ prompts removes the guesswork for customers and reduces this failure category close to zero. The fix is in the UI, not the payment stack.

🤓Thinking about a new checkout but not ready to invest blindly?

Test-drive our checkout before making a decision.

Learn more

Payment gateway issues

Some payment gateways⁠ may decline transactions. One reason is that certain merchant accounts have a transaction limit. If a transaction exceeds that amount, it gets declined. Issues with the payment provider or payment processor, such as downtime, technical errors, or connectivity problems, can also lead to failed transactions. In such cases, the payer can opt for another payment method⁠, such as an alternative card or a digital wallet, to complete the purchase. Another reason is payment gateway downtime. Routing transactions through different acquiring banks or payment providers can optimise approval rates and reduce failures.

🎯Discover our routing solution

Сompanies achieve up to 40% increase in conversion rates after implementing the routing technology.

Learn more

Security check issues

Issuers apply their own security logic independently of the merchant. Here are the triggers for declines with no warning:

• card flagged for domestic use, attempting an international transaction
• purchase pattern that deviates from the cardholder's history
• risk score that exceeds the bank's threshold

These declines are harder to prevent directly, but a routing strategy helps: sending transactions through acquirers with stronger relationships with issuers in specific regions improves authorisation rates for cross-border payments. Connectivity issues, such as timeouts and slow responses from the payment initiator, are a separate but related failure mode worth monitoring at the infrastructure level.

Payment method-related issues

These are among the most frequent culprits behind failed online payments. Payment method-related issues often stem from insufficient funds in the customer's bank account, expired cards, or incorrect payment information entered during checkout. For example, a simple typo in the card number or an outdated billing address can cause the payment to be declined, leading to frustration and a disrupted customer experience.

To reduce failed payments caused by payment method issues, businesses should offer multiple payment methods, such as credit and debit cards, bank transfers, and digital wallets⁠, so customers can choose the option that best suits them. This flexibility increases the likelihood of successful transactions and caters to diverse customer preferences across regions.

Additionally, providing clear, step-by-step prompts and validation checks during the payment process can help customers enter their payment details accurately.

For payment teams, this is the lowest-hanging fruit in the decline breakdown: fixable at the product level, with no PSP negotiation required.

Payment channels and error codes

Understanding how different payment channels behave and how to interpret their error codes is key to diagnosing failures and improving acceptance rates at scale.

Payment channels represent the routes through which transactions are processed — card payments, bank transfers, digital wallets, and alternative payment methods. To a customer, selecting a payment method at checkout feels like a simple choice. Under the hood, each channel operates under different rules, risk models, and technical dependencies, which directly affect how and why payments fail.

How payment channels influence failure patterns

Each payment channel has its own failure logic:

• Card payments are highly dependent on issuer decisions and fraud checks, making them more sensitive to declines related to risk scoring, authentication, and balance issues
• Bank transfers and local payment methods tend to fail due to user drop-off, incorrect input, or processing delays rather than issuer rejections
• Digital wallets typically reduce input errors and friction, but failures can still occur due to device authentication issues or tokenisation⁠ problems
• Alternative payment methods depend heavily on regional infrastructure and provider availability, which can introduce variability in performance

As a result, a high failure rate is rarely a universal issue; it is usually channel-specific.

What error codes actually tell you

When a transaction fails, payment providers return error codes that reflect the underlying issue. While these codes vary across providers, they generally fall into a few functional categories:

• Customer input or account issues (e.g. insufficient funds, invalid details) → typically require user action
• Issuer-side decisions (e.g. suspected fraud, spending limits, geographic restrictions) → often recoverable through retries, routing, or adjusted authentication
• Technical and infrastructure errors (e.g. timeouts, gateway downtime, integration issues) → indicate problems within the payment stack⁠
• Authentication failures (e.g. incomplete 3D Secure, failed verification) → highlight friction in the checkout flow

Exact codes vary by provider, but these are the patterns that appear consistently across card networks and acquirers:

Looking at error codes in isolation provides limited value. The real insight comes from analysing them in the context of payment channels, providers, and user flows.

Turning payment data into optimisation opportunities

Businesses that systematically track payment channel performance alongside error code distribution stop firefighting individual failures and start engineering better outcomes.

In practice, this means:

• Identifying underperforming providers or channels and redistributing traffic accordingly

• Detecting patterns in issuer behaviour across regions, BINs, or payment methods

• Eliminating unnecessary retries by distinguishing between recoverable and non-recoverable failures

• Improving checkout UX where user-related errors are frequent

• Fine-tuning authentication and fraud settings to reduce avoidable declines

Instead of treating failed payments as isolated incidents, this approach treats them as structured signals that reveal where the payment flow breaks and how it can be improved.

Error codes are data. The teams that treat them as such consistently outperform those that don't.

📚How to turn raw payment data into actionable insights

Learn more

How to decrease payment failures

Reducing failed payments requires action at multiple levels — checkout design, payment infrastructure⁠, and post-failure recovery.

Here are the levers that move the needle most.

• Optimise the checkout experience. Card input errors are entirely preventable. Split card number fields into four-digit blocks with automatic cursor progression, visually mimic the card layout, and add inline validation so customers catch mistakes before submitting. Reduce form fields to the minimum required — every unnecessary field is a source of friction and a potential failure point.

• Offer multiple payment methods. When a card fails, the sale isn't necessarily lost if the customer has an alternative. Giving customers the option to switch to a digital wallet, bank transfer, or local payment method at the point of failure recovers transactions that would otherwise disappear entirely.

• Review your 3DS settings. Reducing friction from Strong Customer Authentication requires balance: fewer 3DS challenges improve conversion, but increase risk exposure. Work with your PSP to identify which transaction types qualify for frictionless flow exemptions and calibrate accordingly.

• Implement smart retry logic. Not all failed payments are permanent. For soft declines, particularly in subscription billing, automated retries timed around likely payday cycles recover a meaningful share of failures. Pair this with dunning emails that prompt customers to update card details or choose an alternative method before access is interrupted.

• Use notifications and grace periods strategically. Automated alerts for upcoming renewals, failed payments, and expiring cards give customers the chance to act before issues arise. When offering grace periods for overdue payments, set a duration that reflects your churn risk and clearly communicate the deadline.

• Track failures by channel and provider. A high decline rate on one payment method or acquirer rarely means all channels are underperforming. Identifying which provider or channel is driving failures lets you redistribute traffic, adjust routing rules, and avoid penalising customers for infrastructure problems they have no visibility into.

• Analyse and act on abandonment. Customers who drop off mid-checkout, whether due to a decline or friction, respond to well-timed reminders. Multiple follow-ups consistently outperform a single notification, particularly on mobile, where the majority of e-commerce sessions now originate.

Failed transaction rates and analysis

Failed transaction rate is the share of payment attempts that don't complete. It is one of the clearest signals of where a payment flow is breaking down. Tracking it regularly and by segment turns a vanity metric into an actionable diagnostic tool.

A single aggregate rate tells you little. Broken down by channel, provider, error code, and customer segment, it tells you exactly where to act:

• spike in insufficient funds declines may point to a UX issue at the payment method selection stage;
• cluster of authentication failures likely indicates a 3DS configuration problem;
• provider-specific drop in approval rates suggests a routing adjustment is overdue.

In practice, I'd recommend reviewing failure rate breakdowns at least weekly during any period of routing changes, PSP onboarding, or checkout updates — these are the moments when declines spike, and the cause isn't immediately obvious. A baseline period of stable performance gives you the reference point to spot anomalies fast.

The businesses that manage failure rates most effectively treat declined transactions as structured data. Each failure carries information: what went wrong, when, and whether it was recoverable. Building the habit of systematically reviewing that data is what separates teams that react to payment problems from those that prevent them.

How can Corefy help?

Most of what this article covers — routing logic, cascading, checkout optimisation, retry mechanisms, fraud rule calibration — is built into Corefy's payment orchestration platform⁠.

When a transaction fails, Corefy's routing engine⁠ can automatically redirect it to an alternative provider without the customer noticing. Manual verification remains available for edge cases where automated decisions need a human check. The checkout is customisable to match your brand and reduce the trust-related drop-off that contributes to payment abandonment.

Failed transactions are never entirely avoidable, but with the right infrastructure, the recoverable ones don’t have to remain failed.

If you'd like to see how this applies to your payment setup, get in touch⁠ with our team.