Why payment failure happens, and how to recover lost revenue
Payments 101
Updated 10 Jul 2026
10 min
Andrii Kononenko
Head of Merchant Operations, Solidgate
Here's why online payments really fail – and the specific fixes that turn declined transactions back into revenue.
Picture a grocery store checkout. Out of every ten card payments, it's rare for even one to fail – the customer is standing right there with a funded account.
Online payments are a different story. A payment failure can happen for a dozen reasons – an expired card, a fraud flag, a cross-border friction point – and the cost compounds fast. A single failed subscription payment doesn't just cost you $100. It ends a customer relationship that was worth $1,200 a year.
A 100% success rate isn't realistic – product type, industry, and traffic quality all shift how many payments get through. But realistic is cutting your failure rate enough that it stops draining revenue.
This guide covers why online payments fail, what the most common decline codes signal, and the specific fixes that recover failed payments before they turn into lost customers.
TL;DR
- A payment failure is any unsuccessful transaction; a decline is the issuer's specific rejection. Knowing which one you got determines whether to retry.
- Soft declines – insufficient funds, temporary flags – are worth retrying. Hard declines – expired, frozen, or stolen cards – need a new payment method instead.
- Failed payments trace back to three root causes: issuer decisions, technology limits, and customer-side errors.
- Seven specific fixes cover every failure type: instant notifications and smart retries, local payment methods, local acquiring and intelligent routing, 3DS2 and 3RI authentication, antifraud tools, tokenization and account updater, and AVS.
Payment failure vs decline
A payment failure is a broader term that covers all unsuccessful transactions, including declines, as well as issues caused by technical glitches, connectivity problems, or errors in processing.
A payment decline is a specific type of failed payment where the card issuer rejects (declines) the transaction because of insufficient funds, expired cards, or fraud prevention measures.
Payment declines: Soft vs hard
All credit card declines fall under one of two categories: soft vs hard decline. That distinction decides whether retrying is worth it.
A soft decline signals a temporary issue: the card lacks funds right now, the issuer flagged the transaction for review, or a connection dropped mid-transaction. Adding details like address confirmation can sometimes save the payment on the spot.
A hard decline is permanent. The card has expired, the account is frozen, or the card was reported lost or stolen. No amount of retrying changes the outcome – the customer needs a different card or payment method.
| Decline type | What it signals | Worth retrying? |
| Soft | Temporary – insufficient funds, a fraud flag, a dropped connection | Yes, often clears with a scheduled retry |
| Hard | Permanent – expired, frozen, or stolen card, closed account | No, ask for a new payment method |
Core insight: Soft declines make up roughly 70–90% of all failed card-not-present payments, and most are worth retrying. Hard declines need a new payment method, not another attempt.
Most common card decline codes
These are the you are most likely to see on your transactions dashboard or API responses:
| Code | Meaning | What it tells you |
| 05 | Do not honor | The issuing bank rejected the transaction without a specific reason. The cardholder usually needs to contact their bank directly. |
| 14 | Incorrect card number | The entered number doesn't match the issuer's records, often a typo. |
| 41 | Lost card, pick up | The cardholder reported the card lost, blocking all transactions. |
| 43 | Stolen card, pick up | The cardholder reported the card stolen, triggering an immediate denial. |
| 51 | Insufficient funds | The account doesn't have enough money to cover the purchase. |
| 54 | Expired card | The card is past its expiration date. |
| 63 | Wrong CVC | The security code doesn't match the issuer's records. |
| 65 | Credit limit exceeded | The cardholder has hit their spending cap for the cycle. |
For the full breakdown of decline codes and how to act on them, see our guide on.
Core insight: 05 Do not honor, 51 Insufficient funds, and 54 Expired card are the three decline codes merchants see most often.
Why online payments fail – the three root causes
that 1 in 3 users cancel their subscriptions because of payment or billing frustrations. Understanding the root cause is what determines the fix.
Payment failure reasons split into three groups: decisions the issuer makes, limits in the payment technology, and errors on the customer's end.
Issuer-related declines
Issuer-related declines come from a decision made by the cardholder's bank.
Card is blocked / Internet spending limits
Many digital-only banks let customers set custom internet spending limits, which shows up as reason code 3.01 Card is blocked. For example, a user might successfully make several purchases online, but their payment for a mobile app subscription fails. In this case, this occurs because their card has reached the preset limit.
Local card brands
Local card brands cause the same problem in other markets. Nigeria's Verve accounts for of issued cards and transaction volume, ahead of international networks. Brazil's Elo shows a smaller but real version of the same gap – of cards issued nationally, with 56% of Elo holders using it as their only online payment method. A bank outside either region that can't process Verve or Elo will decline the payment regardless of available funds.
Unverified customer
It's quite common for authentication checks to mistakenly block genuine payments. In regions like Europe, the introduction of Strong Customer Authentication () has tightened the screws on compliance, pushing merchants to take a more cautious stance on customer verification. The result: more declines of genuine transactions and higher payment failure rates.
Technology-related declines
These declines stem from system issues or payment infrastructure limitations that can disrupt transaction processing and cause online payment failure scenarios.
Cross-border transactions
In cross-border scenarios, where the issuing bank, merchant, and acquiring bank are in different countries, faces more friction due to exchange rate losses, varied regulations, and fraud rules. Naturally, all these extra factors congest the payment route and make declines much more frequent.
Fraud triggers
Card-not-present transactions are inherently riskier than on-site payments and trigger fraud alerts much more often, leading to reasons for payment failure. Issuing banks carry all the risk and so tend to be over-cautious.
If you also operate in a high-risk industry or have been placed into a , losing sales due to low payment acceptance becomes your norm.
Customer-related declines
These declines are directly related to the customer or their payment method and represent common reasons why payment failed.
Insufficient funds
Insufficient funds is the most direct case: the account simply doesn't have enough money at the moment of the charge.
Canceled or expired card
Canceled or expired cards are a recurring problem for subscription businesses specifically. Customers hold an average of three to four active subscriptions and rarely think to update card details across all of them, leaving billing continuity in the merchant's hands.
Incorrect payment information
Sometimes, your customers enter payment details that don't match what their bank has on file, causing payment failures. Mistakes in the are the most common. When the address doesn't match the bank's records, the issuing bank flags the issue and lets you know.
From there, it's your call to either approve the transaction or play it safe and decline. In many cases, you might choose to go ahead with the payment, especially if the mismatch is minor, like a formatting issue, or the customer seems low-risk.
Core insight: Most payment failure reasons sort cleanly into issuer, technology, or customer causes, and each category needs a different fix.
How to recover lost revenue from failed payments
Recovering failed payments comes down to five levers:
Notify customers and schedule retries around insufficient funds
An instant notification right after an insufficient-funds decline catches the customer while they're still in a buying mindset. The message should offer an immediate alternative: a different card, a digital wallet, or a Buy Now Pay Later () option lets the customer complete the purchase without waiting for their balance to change.
For subscription businesses, the notification alone isn't enough. The customer may not act on it, which means the payment still needs to be retried automatically.
schedule the next attempt for the moment the customer is most likely to have funds available – typically the start or end of the month, when salaries clear. A retry fired too early hits the same empty balance and generates another decline. A retry timed to the customer's income cycle recovers the payment without the customer doing anything at all.
Offer the payment methods your market actually uses
If you target regions where local card brands dominate over international ones, not offering customers locally preferred (APMs) can seriously damage your conversions when payments fail.
To illustrate, in regions like Poland or Brazil, over half of the population prefers paying online with local APMs like BLIK and PIX. Local customers expect to see these APMs at the checkout.
If the option isn't there, they might either abandon the checkout or try paying with their local card brand, which is incompatible with your acquiring bank. Tailoring your checkout page to the target region helps you save conversions, secure sales, and increase loyalty in the target region.
Read more on .
Use local acquiring and intelligent routing to fix cross-border declines
removes cross-border friction at the source. When the issuing bank and acquiring bank are in the same country, the transaction clears under one regulatory framework with no exchange rate conversion and no cross-border fraud flags. Merchants consistently see higher approval rates in markets like India, Brazil, and Mexico once local acquiring is in place.
Opening a local entity in every market isn't realistic for most businesses – governments often require establishing legal entities locally, which takes time and cost. covers the same ground without that overhead.
It analyzes the available acquiring paths and picks the one most likely to succeed, then moves to the next-best option automatically if the first attempt fails. Our merchants using intelligent routing have reported a 5-10% increase in approval rates.
Prevent authentication declines with 3DS2 and 3RI
verifies transactions using the customer's device, location, and purchase history. A regular customer making a familiar purchase clears automatically. If something looks off, 3DS2 requests confirmation – a one-time password, fingerprint, or QR code – before approving.
For recurring payments or card-on-file purchases, we suggest using . 3RI lets merchants trigger the authentication step themselves, without involving the customer. Every recurring charge gets authenticated automatically – no OTP, no redirect, no friction at the moment of .
Reduce false declines with antifraud tools
Overcautious fraud rules sometimes decline genuine customers alongside fraudulent ones. separate the two by scoring each transaction against specific signals rather than applying blanket blocks.
For merchants with elevated fraud exposure in specific regions, monitoring or limiting traffic from those markets reduces losses – but alongside the tools below, not instead of them. Blocking entire regions removes genuine customers along with bad actors.
Fraud prevention works best when layered:
- Machine learning models score each transaction in real time, flagging suspicious patterns before the payment clears
- Behavioral analytics identify unusual session activity that doesn't match the account's normal patterns
- Blocklists of confirmed elements – flagged names, emails, IPs, device IDs, and phone numbers – stop known threats from retrying
- Custom risk rules let merchants tune review thresholds to their own transaction mix, rather than applying one generic standard across all payment types
Keep card credentials current with tokenization and account updater
removes the expired-card problem at the credential level. Instead of storing a raw card number, the merchant holds a network token – and when the underlying card is reissued or expires, Visa or Mastercard update the token automatically. The stored credential keeps working without any action from the merchant or the customer.
reports a 4.6% lift in card-not-present authorization rates for tokenized transactions.
For cards that aren't tokenized, use . It queries Visa or Mastercard for updated card details and pushes the new expiration date or PAN directly into your stored credentials – closing the same gap through a different path.
Verify billing address mismatches with AVS
Address Verification Service (AVS) reduces declines caused by billing address mismatches. It compares the numeric parts of the address your customer entered – street number, zip code – against the address their bank has on file, then returns a match level the merchant uses to decide the next step.
| AVS response | What it means |
| Full match | Address matches perfectly |
| Partial match | Some parts match, like the zip code, but not all |
| No match | Address doesn't align with the bank's records |
| Unavailable | Bank has no address data, or card doesn't support AVS |
AVS only works in the US, Canada, and the UK. A mismatch isn't always fraud – minor formatting differences often explain a partial match. For best results, combine AVS with 3D Secure or behavioral analytics rather than using it as a standalone block.
Core insight: Every failed payment has a matched fix. Notifications and smart retries recover insufficient-funds declines. Local payment methods and acquiring fix market and cross-border gaps. 3DS2 and 3RI resolve authentication blocks. Antifraud tools reduce false positives. Tokenization and account updater prevent expired-card failures before they start.
Most payment failures are fixable
Payment failures are a reality of online payments – but most have a specific fix. Understanding which root cause drove the decline is where recovery starts: pull your decline data, identify the pattern, and the right lever becomes clear.
- Work with your payment stack to address issuer-side declines with 3DS2, 3RI, and local acquiring
- Add and antifraud tools to cut technology-related failures
- Offer , network tokenization, and account updater to recover customer-side losses
With the right tools in place, failed payments stop being a revenue drain and start being a recoverable event.
If payment failure is quietly eating into your revenue, to map where the losses are actually happening.
From B2B to global B2C subscriptions
How DRESSX scaled digital fashion payments with Solidgate
Frequently asked questions
"Payment failed" means a transaction didn't complete, for any reason. It covers issuer declines, connectivity drops, and processing errors alike. Check the decline code, if there is one, before deciding whether to retry.
Payment decline reasons break down into three categories: the issuer blocked it (spending limit, fraud flag, expired card), a technology limit got in the way (cross-border friction, a dropped connection), or the customer entered incorrect details. Each category has a different fix – and the decline code tells you which one you're dealing with.
Businesses can reduce failed payments by combining instant customer notifications, local acquiring and intelligent routing, 3DS2/3RI authentication, network tokenization, account updater, and scheduled retries. Each lever targets a different failure type, so most businesses run several together.
Merchants prevent many failed payments with network tokenization and account updater, which stop expired-card failures before they happen. Local APMs and local acquiring cut failures tied to unsupported card brands or cross-border friction.
Recover failed with a mix of instant notifications, scheduled retries timed to paydays,, , and an account updater. Tokenization and account updater keep billing going when a card is reissued or expires, which is a top cause of involuntary churn.
Yes. finds the path a transaction is most likely to clear and retries the next best acquirer if the first declines. Solidgate merchants using it report a 5–10% increase in approval rates, with the biggest gains on cross-border payments.
