False Declines: Why Good Customers Get Rejected and How to Fix It

On this page 8 sections

1. What a False Decline Costs Your Business
2. Why Was the Card Declined? Common Decline Codes and What They Really Mean
3. Issuer Declines vs. Your Own Fraud Filters
4. Tuning AVS and CVV Rules Without Inviting Fraud
5. Retry Logic and Account Updaters for Recurring Billing
6. Helping Customers Complete a Declined Purchase
7. A Checklist to Reduce False Declines
8. Next Steps

Key takeaways

• A false decline costs you the sale and often the customer, and you rarely see it happen because good buyers leave without complaining.
• Find out whether a decline came from the card issuer or from your own gateway and platform rules, because each one has a different fix.
• Layered AVS, CVV and fraud rules reduce false declines more safely than single hard stops, especially for travel, international and gift orders.
• For recurring billing, smart retry timing, account updater services and correct stored-credential flags recover many renewals that would otherwise fail.

A customer fills a cart, types in their card and sees "Payment declined." Their card is fine and their bank account has money in it. The order still fails, and they go buy from someone else. This guide explains why good customers get rejected and how to reduce false declines in your online, keyed and recurring transactions. It covers what common decline codes really mean, how to tell issuer declines from your own fraud filters, and how to tune AVS and CVV rules without opening the door to fraud.

A false decline is a legitimate transaction that gets rejected. The rejection might come from the card issuer, your processor or the fraud settings in your own gateway. You control more of these than you might think.

What a False Decline Costs Your Business

The obvious cost is the lost sale. The larger costs are harder to see:

• Lost lifetime value. A first-time buyer who gets rejected rarely tries again. A subscriber whose renewal fails may never update their card.
• Silent losses. Customers who are declined usually don't email you. They leave. Your reports show a declined transaction, not an angry customer.
• Support time. Phone and email follow-ups take staff time, especially for high-ticket orders like travel bookings.
• Ad spend wasted at the finish line. You paid to bring the buyer to checkout, and the payment step turned them away.

Illustrative example: Picture a store with a $90 average order and 40 declined orders in a month. If even a quarter of those buyers were legitimate, that's 10 lost orders, or about $900 in revenue. That figure doesn't count repeat purchases those customers would have made. The numbers here are made up. Run the same math with your own decline report.

If your checkout already converts below where you'd like, declines are worth checking alongside the other fixes in our guide to checkout abandonment payment fixes that recover lost sales.

Why Was the Card Declined? Common Decline Codes and What They Really Mean

Every decline comes back with a response code. The exact codes and wording vary by processor, gateway and card network, so check your own provider's documentation. The table below covers widely used codes and how often they hide a good customer.

For a fuller list, see our breakdown of credit card decline codes and what each one means.

The Do Not Honor Decline Code

The do not honor decline code (usually 05) is the issuer's catch-all. It means the bank said no and won't tell you why. Common triggers include:

• The issuer's fraud model flagged the purchase as unusual for that cardholder
• A cross-border purchase, such as a U.S. store charging a foreign card
• A large purchase compared with the cardholder's normal spending
• Several attempts in a short window
• The card isn't enabled for online or card-not-present use

You can't override a do not honor response, and retrying the same card right away rarely works. Retrying can also look like card testing to the issuer. The fastest fix is usually the customer: they can approve the charge in their banking app or call the number on the back of the card, then try again.

Soft Declines vs. Hard Declines

• Soft declines are temporary, such as insufficient funds, issuer unavailable or a request for extra authentication. A later retry or a different step can succeed.
• Hard declines are permanent for that card, such as lost, stolen, closed account or invalid number. Retrying won't help, and repeated attempts can create problems with the card networks.

Issuer Declines vs. Your Own Fraud Filters

Not every decline comes from the bank. A transaction can be stopped at several points:

1. The issuer declines the authorization.
2. Your gateway's fraud filters reject a transaction the issuer approved, based on AVS, CVV, velocity, IP or amount rules.
3. Your e-commerce platform or a fraud plugin cancels the order after payment based on its own risk score.

Your gateway's transaction detail usually shows which one happened. An issuer decline shows the bank's response code. A filter decline names the rule that triggered it, such as "AVS mismatch" or "velocity limit."

When your gateway rejects a transaction the issuer already approved, the authorization can stay on the customer's card as a pending charge until it drops off. Customers often think they were charged twice. Tell them this in your decline message and support scripts.

Signs Your Fraud Filter Is Too Strict

Your fraud filter may be too strict if you see any of these:

• Many declines show an issuer approval followed by a gateway rejection
• Repeat customers get blocked
• International or gift orders fail far more often than domestic ones
• Customers complain about pending charges on failed orders
• Your chargeback rate is very low while your decline rate is high, which can mean you're blocking far more than fraud

A near-zero chargeback rate isn't automatically a win if it costs you a lot of good orders. Watch both numbers together, and know where your limits sit using our guide to chargeback ratio thresholds.

Factors That Shape Issuer Approvals

Issuers decide using the data you send. You can improve your approval odds by:

• Sending complete billing data, including full address, ZIP code and CVV
• Using a clear billing descriptor customers recognize
• Making sure your business is coded correctly with your processor
• Flagging recurring and stored-card transactions correctly
• Using authentication such as 3D Secure for online card payments on riskier orders, so the issuer can verify the cardholder instead of declining

Tuning AVS and CVV Rules Without Inviting Fraud

The Address Verification Service (AVS) compares the billing address the customer enters with the address the issuer has on file. CVV checks the security code. Neither one approves or declines a payment by itself. Your gateway settings decide what happens with each result. For a related change on the card network side, see our explainer on Discover's new card verification rule for online sellers.

How AVS Mismatch Declines Happen

An AVS mismatch decline often hits real customers because:

• Apartment or suite numbers are formatted differently ("Apt 4B" vs. "#4B")
• The customer recently moved and the bank has the old address
• The cardholder uses a business, PO box or family member's address
• Many non-U.S. issuers don't support AVS or return only partial results
• The buyer is shipping a gift to someone else and confuses the billing and shipping fields

AVS response codes vary by network, but the common categories look like this:

For a deeper look at each setting, read AVS and CVV settings: which mismatches your store should decline.

CVV Settings

A CVV mismatch is a stronger warning than a partial AVS mismatch. Declining it is usually reasonable. Let the customer re-enter the code once before you treat it as suspicious.

On keyed and phone orders through a virtual terminal for card-not-present payments, always collect the CVV and full billing address. Never write down or keep the code after the payment is authorized.

Use Layered Rules Instead of Single Hard Stops

A single partial mismatch shouldn't kill an order. Decide based on a combination of signals:

• Partial AVS match, returning customer, normal order size: accept
• Partial AVS match, new customer, unusually large order, rush shipping: manual review or 3D Secure
• AVS no match, CVV mismatch, several card attempts: decline

Change one rule at a time. Then track approval rate, manual review volume and chargebacks for a few weeks before you change the next one.

Industry Notes

• Travel and tourism: Travelers often book for other people, use foreign cards and make large, last-minute purchases. These are all classic fraud signals, so hard AVS rules hurt here. Use step-up authentication and manual review for large bookings. Check the name on the card against the traveler list instead of declining outright. For cross-border card mixes, see MannyPay's international payment processing options.
• Shopify stores: Your gateway filters and the platform's order risk indicators can both block the same order. Review both, and avoid auto-cancelling orders the platform marks as only moderately risky.
• Subscriptions and memberships: Apply your strictest checks at signup. On renewals, the card is already verified, so AVS rules built for new orders can block good charges.

Retry Logic and Account Updaters for Recurring Billing

Recurring billing has its own false decline problem. A card that worked last month fails this month because it expired, was reissued or hit a temporary limit. To recover more renewals:

1. Sort declines by type. Retry soft declines. Stop on hard declines and ask the subscriber for a new card.
2. Space your retries. Retrying a few days later, or around common paydays, tends to beat several attempts in one day. The card networks have rules on reattempting declined transactions, and some codes should never be retried. Ask your processor for the current limits.
3. Use an account updater. Card network updater services can deliver new card numbers and expiration dates when a card is reissued. Learn more about using a card account updater to keep subscribers billing.
4. Consider network tokens. Network tokens can stay current when the underlying card changes. See how network tokenization supports fewer failed renewals.
5. Flag merchant-initiated transactions. Renewals should be marked as recurring or stored-credential charges, not as new customer-present purchases.
6. Email before cards expire. Remind subscribers to update their card before a renewal fails, not after.

When retries run out, a structured outreach sequence takes over. Our guide to dunning management for failed subscription payments walks through it.

Helping Customers Complete a Declined Purchase

Your decline message is often the only chance to save the sale. Make it helpful without revealing how your fraud rules work.

Other ways to recover the sale:

• Keep the cart saved so customers don't have to rebuild it.
• Offer digital wallets. Wallet payments often carry stronger authentication data. See our guide to adding Apple Pay, Google Pay, and PayPal to your checkout.
• Give phone staff a script. It should explain do not honor declines, suggest the customer call their bank and offer to re-run the card once they confirm.
• Never split a declined charge into smaller transactions on the same card to get it through. This violates card network rules and can put your merchant account at risk.

A Checklist to Reduce False Declines

• Export a month of declines and separate issuer responses from gateway filter rejections
• Group issuer declines by code and note which are soft and which are hard
• Loosen any rule that auto-declines partial AVS matches or "unavailable" results
• Keep CVV mismatch declines on, with one re-entry allowed
• Add 3D Secure or manual review for high-value or unusual orders instead of hard declines
• Use separate rules for signup and renewal on subscriptions
• Turn on account updater and network tokens if your setup supports them
• Rewrite customer-facing decline messages and support scripts
• Review approval and chargeback rates monthly after each change

Next Steps

False declines rarely have one cause. They usually come from a mix of issuer caution, overly strict filters and missing data. Start with your decline report, fix the rules you control and measure the results. For more fixes, see our guide on how to improve authorization rates.

MannyPay offers online payment processing and gateways that work with Authorize.net, NMI and major e-commerce platforms, along with 3-D Secure authentication and international processing. Results depend on your business, card mix and underwriting. If you'd like help reviewing your setup, request a free quote and a MannyPay specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.