How to manage card declines and recover lost sales
Login

How to manage card declines and recover lost revenue

Credit card on a blue background with card decline codes: Insufficient funds, Authentication failed, Processing issue

More and more online businesses are waking up to a simple fact: every declined payment is a missed sale—and in the case of subscriptions, possibly a churned customer. You simply can’t obsess over customer acquisition while ignoring decline recovery and payment acceptance.

Recovering just a fraction of declined payments can drive millions in additional revenue annually. Imagine an EdTech subscription business with 100,000 monthly subscription renewal attempts, each priced at $30. With an average payment decline rate of 6%, they would encounter approximately 6,000 soft declines monthly—$180,000 in potential lost monthly revenue.

With the right recovery strategies in place, this EdTech company could win back $90,000 in lost revenue at a 50% recovery rate—money that would have otherwise slipped through the cracks. Pushing that rate to 70% means $126,000 back in their pocket every month.

That’s a major revenue boost, all without acquiring a single new customer. However, many merchants take the wrong approach to dealing with declines: over-aggressive retries, poor routing, and missing authentication steps don’t help the cause, or worse— trigger scheme fines.

At Solidgate, our job is to help online merchants push their acceptance rates beyond 90%. We know that fixing failed payments is one of the highest ROI levers you can pull— most businesses just don’t know where to start. That’s why we’re breaking it down: why declines happen, how to work with soft and hard declines, and how to build a strategy that turns lost payments into revenue.

The problem with scattered decline codes

Before you can fix declines, you need to understand them. But here’s the challenge: decline codes aren’t standardized. While major payment schemes like Visa or Mastercard generally use the same numbering and format for the most common decline codes, many differ. For example: 

  • Visa’s N7 (Invalid CVV) might appear as 63 on Mastercard or “Security Code Invalid” on Amex.
  • A transaction declined due to an expired card could return as code 6 on Adyen or expired_card on Stripe.

Inevitably, when working with payment schemes and payment service providers (PSP), you immediately run into a problem. Receiving different codes for the same issue is confusing and forces merchants to analyze each provider’s codes individually. With a high transactional volume, this becomes an operational nightmare, where tracking patterns and devising effective solutions to each scenario are nearly impossible.

Major payment service providers try to solve this problem by mapping each decline code from schemes to a standardized set of internal codes within their ecosystems. This simplifies matters if you use only one PSP, such as Stripe or Adyen, as you’ll receive a consistent decline format across all transactions. 

But once you start using more than one processor, the problem returns. This forces merchants to spend hours interpreting these codes and consolidating this data for analysis and reporting—which, besides being a massive resource drain, is also prone to human error. 

Furthermore, without a standardized approach, you will likely display vague error messages like “Payment Failed,” leaving customers confused and unsure of what to do. 

As a payment orchestrator, Solidgate consolidates all the decline codes from payment schemes and major PSPs into one unified format. For simplicity’s sake, we’ll use our internal reason codes later in the article. But first, let’s understand the types of card declines and their strategies.

Soft declines vs. hard declines & strategies for each type

Every card decline falls into one of two categories: 

1. Soft declines (temporary & recoverable)

These happen when the payment method is valid, but temporary issues—like insufficient funds, authentication failures, or network errors—prevent the transaction from going through. You can resolve these problems either without involving the customer or with their minimal involvement.  

Depending on your industry, soft declines can account for 80-90% of all declines. In the subscription e-commerce sector, four of the top five decline reasons are soft declines, such as “Insufficient Funds” and “Temporary Hold.” Soft declines are easier to resolve since you have more control over them; they also have a higher recovery ceiling, reaching ≈40-70%, depending on your strategies. 

Key solutions for soft declines:

  • Smart retries: Timing is everything. Scheduling retries at optimal times—such as after payday or during hours with lower fraud risk—can significantly improve approval rates. However, be strategic: Mastercard limits retries to 10 attempts within 24 hours, while Visa allows up to 15 retries within 30 days. Exceeding these limits could result in fees of $0.50 per additional retry, so prioritizing high-recovery potential transactions is crucial.
  • Intelligent transaction routing: Routing payments through the best-performing acquirer for the target region can boost approval rates by 5-10%. This method helps mitigate declines caused by bank-specific policies, fraud rules, or technical issues with certain acquirers.
  • Authentication optimization: Streamlining 3D Secure (3DS) flows and using  3RI (merchant-initiated) authentication ensures that transactions requiring extra verification go through smoothly. Implementing alternative verification methods can also help minimize authentication failures.
  • Card detail validation: Optimizing your checkout to detect and prompt users for typos or missing data before submission.
  • VTS/MDES Tokenization: Using network tokenization to prevent unnecessary failures due to expired or reissued cards to keep transactions seamless without customers having to update their payment information.
  • Pre-billing notifications: If you run a subscription-based business, notifying customers 3-7 days before renewal is one of the most effective ways to prevent declines due to insufficient funds or outdated payment details.

2. Hard declines (permanent failures)

Hard declines are permanently declined transactions that happen when something is wrong with the payment method or due to a merchant-side error. With hard declines, your strategy is never to retry the transaction, as it can lead to scheme fines and damage your MID (Merchant Identification Number) relationships with issuing banks, ultimately hurting your authorization rates. 

Hard declines make up 10-20% of all failed transactions, and their recovery ceiling is typically lower as well (20-30%).

Key solutions for hard declines:

  • Card update prompts: When transactions fail due to expired or blocked cards, set up automatic prompts for customers to update their payment details. This can be done via email, in-app notifications, or SMS reminders to minimize drop-offs.
  • Alternative payment methods: Offer popular APMs like PayPal, Apple Pay, Google Pay, or BNPL as fallback options to increase conversion.
  • Localized acquiring: Some declines happen due to regional restrictions or issuer-specific rules. If you see a pattern of location-based declines, check with your Payment Service Provider (PSP) to route transactions through a local acquirer that has a higher acceptance rate in the region.
  • Clear decline messaging: Confusing error messages can cause customers to abandon the transaction entirely. Instead, provide clear, actionable reasons for the decline and next steps (e.g., “Your card has expired. Please update your payment details.”).
  • Merchant setup checks: Ensure that your MID settings, routing configurations, and compliance requirements are correctly set up to avoid unnecessary hard declines. Periodic reviews with your PSP can help prevent avoidable failures.

Let’s look at the specific decline reason scenarios and how to deal with them.

Credit card decline reasons & solutions to them

In both soft and hard declines, customers tried to make a purchase but couldn’t, meaning both represent missed revenue opportunities and need addressing. What differs is the reasons and strategies you employ in each case.

As a payment orchestration platform, Solidgate is integrated with different payment processors, so for clarity, I’ll use reason codes from our internal error code logic.

Soft declines

Working with these declines should be your main focus.

A table with soft decline reason codes and solutions:
Reason
Description
Solution
0.01 General decline 

The issuing bank didn’t complete the transaction.
Ask the customer to retry the payment a few times; subsequent attempts may succeed.
0.02 Order expired

The transaction wasn’t completed within the allocated time.

Advise the customer to reattempt using the same card.
1.01 Authentication failed 

The cardholder’s authentication attempt failed.

Ask them to retry several times. Ensure your 3DS setup is working properly to reduce failures.
2.01 Invalid data/Order not found 

Missing or incorrect transaction details.
Ask the customer to double-check and correct their payment information. If the issue persists, verify the order's existence and accuracy before reattempting the transaction.
2.06 Invalid CVV2 code 
The CVV entered is incorrect.
If it is the first occasion, kindly ask the customer to try again. If the CVV code error recurs for the same customer, consider the potential for card fraud and advise them to contact their card issuer.
2.08 Invalid card number

The entered card number doesn’t exist.
Ask the customer to verify and re-enter the card details or suggest using an APM.
2.09 Invalid expiration date

 The card’s expiration date is invalid or expired.
If the card has expired, ask the customer to update their card details or suggest using a different card. As a merchant, you can verify the card expiration date in the order details within the Solidgate HUB. 
2.13 Invalid IP 
The provided IP address is incorrect. 
Ensure a valid IP address is passed in the request. Double-check the IP address format and ensure it corresponds to the customer's actual IP.
2.10 Invalid 3DS flow on the merchant side 

3DS URL was not displayed to the cardholder during 3D Secure authentication attempts.
Ask the customer to describe the step-by-step payment flow they had and ensure all 3DS steps are displayed properly.

2.11 Invalid 3DS flow on the bank side 
The bank did not complete 3DS authentication.
Ask the customer to try the payment again or suggest using another card. Ensure that the 3DS setup is properly configured and communicate any recurring issues with the bank.
2.12 Invalid 3DS flow 
The customer hesitated during authentication.

Ask the customer to try again or suggest they use another card. Ensure the customer understands the importance of completing the 3DS authentication.
2.15 SCA requires 3D authentication 
The transaction was attempted without 3D Secure (3DS), which is required for Strong Customer Authentication (SCA) in the EU.

Retry the transaction with 3DS enabled. Ensure your payment processing system supports 3DS for all applicable transactions to avoid unnecessary declines.

2.14 Subscription error 
The customer already has an active subscription or multiple invoices in a processing state.
Verify the customer_account_id and ensure only one active subscription per product_id. Check for pending invoices, as some payment processors limit attempts to three per subscription.
2.16 Subscription is locked 
A previous subscription order is still processing.
Wait until the previous attempt is resolved before retrying. To prevent lock issues, monitor ongoing subscription processes and handle retries correctly in your system.

Hard declines

While hard declines generally have a lower recovery ceiling than soft declines, recovering even 20-50% of failed payments results in significant revenue gains.

Reason

Description

Solution
4.04 Lost card
The card was reported lost, and all transactions are blocked.
Show a general decline message (avoid alerting fraudsters). If fraud is suspected, block the account internally.
4.02 Stolen card
The card in use is stolen, all transactions are restricted.

Show a general decline message (avoid alerting fraudsters). If fraud is suspected, block the account internally.
2.09 Invalid expiration date
The entered or stored card expiration date is incorrect or has expired.
Ask the customer to verify and update their card details. As a merchant, you can verify the card expiration date in the order details within the Solidgate HUB. 
4.03 Restricted card
The card is restricted, possibly due to being reported as lost or stolen, or due to a restriction at the BIN or cardholder level.
Advise the customer to contact their bank. If restrictions are permanent, suggest an alternative payment method.
4.01 Card is in a blacklist
The card is listed on a security blacklist, often due to prior suspicions or fraud.
Show a generic decline message to avoid tipping off fraudsters. Internally, check the customer’s account for fraudulent activity before allowing another attempt.
4.05 PSP antifraud
The acquiring bank blocked the transaction due to possible fraud.
Show a generic decline message to avoid tipping off fraudsters. Internally, check the customer’s account for fraudulent activity before allowing another attempt.
4.08 AVS mismatch
The billing address provided by the customer doesn’t match the bank’s records.
Ask the customer to enter a valid billing address. If mismatches persist, assess the fraud risk and take necessary action.
3.11 Recurring payment canceled
The customer or issuer blocked recurring payments.
Contact the customer to confirm why payments stopped. If they didn’t cancel, have them check with their bank. Contact the customer to understand why recurring payments were stopped. If the customer didn’t initiate this action, advise them to check with their card issuer. 
3.12 Closed user account
The customer has blocked transactions via this card, or their account is closed, and transactions are no longer allowed.
Ask if the customer is aware of any restrictions. If not, suggest they contact their bank to resolve the issue.
5.04 Merchant is not configured correctly
Processing error.
 Verify the settings and configurations to ensure they are correct. 
5.09 Merchant not found 
Acquirer error.
Double-check the merchant ID and ensure the account is active.
5.10 Processor does not support requested API method 
The selected API method isn’t supported by the processor.

Use only supported API methods. If the error occurs on a zero-amount payment, your processor may not support that type of transaction.

Hard declines

Hard declines are tougher to recover, but that doesn’t mean you completely should ignore them. Even bringing back 20-50% of failed payments can unlock significant revenue.

A table with soft decline reason codes and solutions:

Reason

Description

Solution
4.04 Lost card
The card was reported lost, and all transactions are blocked.
Show a general decline message (avoid alerting fraudsters). If fraud is suspected, block the account internally.
4.02 Stolen card
The card in use is stolen, all transactions are restricted.

Show a general decline message (avoid alerting fraudsters). If fraud is suspected, block the account internally.
2.09 Invalid expiration date
The entered or stored card expiration date is incorrect or has expired.
Ask the customer to verify and update their card details. As a merchant, you can verify the card expiration date in the order details within the Solidgate HUB. 
4.03 Restricted card
The card is restricted, possibly due to being reported as lost or stolen, or due to a restriction at the BIN or cardholder level.
Advise the customer to contact their bank. If restrictions are permanent, suggest an alternative payment method.
4.01 Card is in a blacklist
The card is listed on a security blacklist, often due to prior suspicions or fraud.
Show a generic decline message to avoid tipping off fraudsters. Internally, check the customer’s account for fraudulent activity before allowing another attempt.
4.05 PSP antifraud
The acquiring bank blocked the transaction due to possible fraud.
Show a generic decline message to avoid tipping off fraudsters. Internally, check the customer’s account for fraudulent activity before allowing another attempt.
4.08 AVS mismatch
The billing address provided by the customer doesn’t match the bank’s records.
Ask the customer to enter a valid billing address. If mismatches persist, assess the fraud risk and take necessary action.
3.11 Recurring payment canceled
The customer or issuer blocked recurring payments.
Contact the customer to confirm why payments stopped. If they didn’t cancel, have them check with their bank. Contact the customer to understand why recurring payments were stopped. If the customer didn’t initiate this action, advise them to check with their card issuer. 
3.12 Closed user account
The customer has blocked transactions via this card, or their account is closed, and transactions are no longer allowed.
Ask if the customer is aware of any restrictions. If not, suggest they contact their bank to resolve the issue.
5.04 Merchant is not configured correctly
Processing error.
 Verify the settings and configurations to ensure they are correct. 
5.09 Merchant not found 
Acquirer error.
Double-check the merchant ID and ensure the account is active.
5.10 Processor does not support requested API method 
The selected API method isn’t supported by the processor.

Use only supported API methods. If the error occurs on a zero-amount payment, your processor may not support that type of transaction.

Decline recovery isn’t just damage control—it’s a growth strategy

Payment decline recovery isn’t about patching holes—it’s about maximizing revenue from the customers you already have. 

Here’s where to start:

  • Use smart logic to retry soft declines at the right time;
  • Use network tokenization to prevent unnecessary card declines due to expired or reissued cards;
  • Ensure smooth 3DS and SCA processes to prevent unnecessary failures;
  • Give customers fallback choices like APMs;
  • Use local acquiring or intelligent payment routing to find the best route for a transaction;
  • Leverage account updaters and proactive prompts for expired or blocked cards;
  • Proactively and clearly communicate with customers about issues on their end;
  • If you have numerous PSPs, leverage a payment orchestrator that unifies the decline codes into a cohesive system.

At Solidgate, we make decline recovery and global payment processing effortless. To find out more about how we can help your business, book a call with one of our experts. 

Share article

Start accepting payments today

Let’s discuss your business needs and we'll give you better fees and conversion rates than you have with your current payment provider.

    By clicking "Get in touch" you agree to our Privacy Policy

    Thank you

    Thank you

    We will contact you shortly. If you have any further questions, please contact us at sales@solidgate.com