False Declines in Ecommerce: Why Good Customers' Cards Fail at Checkout

On this page 8 sections

1. What False Declines Cost an Ecommerce Store
2. Why Cards Are Declined Online: Issuer, Processor or Fraud Filter
3. Common Decline Codes and What Each One Means
4. Checkout Data That Helps Issuers Approve Orders
5. Strict Fraud Rules: Why Legitimate Orders Get Declined
6. Retry Logic and Customer Messaging for Declined Payments
7. How to Track and Improve Your Payment Approval Rate
8. Next Steps: Getting Help With Online Approvals

Key takeaways

• A decline can come from the card issuer, your processor or your own gateway fraud rules, and each source needs a different fix.
• "Do Not Honor" is the issuer's catch-all response. You can't override it, but sending more complete checkout data can make it less likely.
• Strict AVS, geography and velocity rules commonly block legitimate orders, so sending borderline orders to review instead of declining them can recover sales.
• Track issuer declines and filter declines separately each month, and count unique customers so retries don't skew the numbers.

False declines in ecommerce happen when a legitimate customer pays with a valid card and the transaction is rejected anyway. The customer did nothing wrong, and their account is in good standing. Somewhere in the payment chain, a system decided the order looked risky or incomplete.

In a store, a declined customer can hand over another card while the cashier waits. Online, they usually leave. This guide explains why cards are declined online, how to tell who actually declined the order and what common codes like Do Not Honor mean. It also covers the checkout and fraud-rule changes that can help you recover real sales.

What False Declines Cost an Ecommerce Store

The lost order is the obvious cost. The hidden costs are often larger:

• Wasted acquisition spend. You already paid for the ad click, email or affiliate referral that brought the shopper to checkout.
• Lost lifetime value. A customer declined on a first order may buy from a competitor and never return.
• Support load. Declined customers email, call and leave reviews asking why their card "doesn't work" on your site.
• Misread data. If you count every decline as fraud stopped, your reports will make your fraud rules look effective even while they turn away good customers.

Illustrative example (not real data): A store gets 1,000 checkout attempts a month with a $60 average order. Suppose 20 of those attempts come from good customers who are wrongly declined and don't retry. That's $1,200 in lost revenue for the month, before counting any repeat purchases. Your numbers will differ, but the point holds: a small decline problem adds up quickly.

Why Cards Are Declined Online: Issuer, Processor or Fraud Filter

Before you fix anything, find out where the decline happened. An online card payment passes through several decision points, and any of them can say no. For a refresher on how the pieces fit together, see the difference between a payment gateway and a merchant account.

To tell them apart, open the transaction detail in your gateway. Issuer declines come back with a response code from the card network. Filter declines are usually labeled as such, often with the name of the rule that triggered. If you use the Authorize.Net gateway or the NMI gateway, check its transaction reports and documentation to see how it labels each type.

The distinction matters because you fully control one category and can only influence the other.

Common Decline Codes and What Each One Means

Response codes and their wording vary by network, processor and gateway. The codes below are common, but check your gateway's documentation for the exact labels it uses.

What the Do Not Honor Decline Code Really Means

Code 05 is the issuer's generic "no." It can reflect the bank's fraud scoring, unusual activity on the account, a merchant type the cardholder rarely uses, or thin transaction data. The issuer doesn't tell you which.

You can't override a Do Not Honor response, but you can make it less likely by sending the issuer more complete information, as the next section explains. If one issuer declines your transactions far more often than others, raise it with your processor. That pattern sometimes points to a configuration or data problem rather than to the customers themselves.

Checkout Data That Helps Issuers Approve Orders

Issuers approve what they can verify. The more legitimate signals your checkout passes along, the fewer reasons the bank has to decline.

• Full billing address and ZIP code. Collect both so Address Verification Service (AVS) can run. Don't truncate fields, and allow apartment and suite numbers.
• CVV on every new card. A matching security code is a strong signal that the buyer has the card in hand.
• Cardholder name, email and phone. These feed issuer and gateway risk models.
• 3-D Secure. Authentication shares device and transaction data with the issuer and lets the customer verify their identity. Set up thoughtfully, it can help issuers approve orders they might otherwise decline. MannyPay supports 3-D Secure authentication for online payments.
• Correct stored-credential flags. For saved cards and repeat billing, the gateway should mark transactions as customer-initiated or merchant-initiated. Missing or incorrect flags can lead to declines.
• Card updater and network tokens. For card-on-file customers, these services can refresh expired or reissued card details. Ask your provider which ones your setup supports.
• Accurate business classification. Your merchant account should reflect what you actually sell, and issuers use that category in their decisions. Accurate coding is a network requirement, not a setting to adjust for better approvals.
• Recognizable billing descriptor. A descriptor customers recognize mainly reduces disputes. It also cuts down on "I don't recognize this" calls to issuers, which can lead to blocks.

Cross-border transactions often get extra scrutiny from issuers, so expect more declines on foreign cards. If you sell to customers abroad, MannyPay offers international payment processing. For a broader look at building an online checkout, read our ecommerce payment processing setup guide.

Strict Fraud Rules: Why Legitimate Orders Get Declined

Many low-risk ecommerce merchants run default fraud settings, or rules written after one bad week, and never revisit them. These are the usual reasons good orders get blocked:

• Hard decline on AVS partial match. A ZIP match with a street mismatch is common among legitimate customers, often because of formatting ("Apt 4B" versus "#4B") or a recent move. Consider sending these orders to review instead of declining them.
• Billing and shipping address mismatch. Gifts, office deliveries and college students all trigger this. Blocking every mismatch turns away real buyers.
• Blanket country or IP blocks. U.S. customers travel, use VPNs and shop while abroad.
• Low velocity limits. A rule allowing two orders per card per day may be reasonable in March and costly during holiday sales or a product launch.
• Stale order amount caps. A maximum set when your average order was small may now block your best customers.
• Outright blocks on free email domains or prepaid cards. Plenty of legitimate shoppers use both.

How to Loosen Fraud Rules Safely

1. List every active rule and how many orders it declined or held last month.
2. Change rules that hard-decline borderline orders so they send those orders to manual review instead.
3. Review held orders promptly. Customers won't wait days for shipment.
4. Run the change for a few weeks, then compare approvals against chargebacks.
5. Keep tight controls on true red flags, such as rapid repeated attempts with different card numbers.

Don't loosen everything at once. Card networks run dispute and fraud monitoring programs, and a rising chargeback ratio creates its own problems. The goal is precision, not removing protection. MannyPay offers merchant accounts for low-risk ecommerce businesses. If you use Stripe, see our guide to Stripe Radar rules for small stores. If you accept PayPal, see what your store must do to qualify for PayPal Seller Protection.

Retry Logic and Customer Messaging for Declined Payments

Soft Declines and Hard Declines

Soft declines may succeed on a later attempt. These include issuer unavailable, system errors and sometimes insufficient funds. Hard declines won't succeed and shouldn't be retried. These include invalid number, lost or stolen card, pick-up card and closed account.

Card networks have rules that limit how often a declined card can be retried. Some decline categories are marked never-retry, and excessive reattempts can bring fees. Confirm the current rules and your gateway's retry settings with your processor before you turn on automatic retries.

Card Testing Inflates Your Decline Count

Fraudsters run stolen card numbers through small checkouts to see which ones work. Limit payment attempts per session and per IP address, and consider adding a CAPTCHA after repeated failures. Card testing also inflates your decline count, which distorts your approval reporting.

What to Tell the Customer

What you say after a decline can save the sale or lose it.

Avoid "Your card was declined for suspected fraud." Try something like: "Your bank didn't approve this payment. Please check your card details, try a different payment method, or contact your bank and try again."

Good practices:

• Keep the cart and form data so the customer doesn't have to start over.
• Show alternative payment methods on the error screen itself.
• If you have the customer's email, send a polite recovery message with a link back to the saved cart.
• For recurring billing, use a dunning sequence. Our guide to reducing failed subscription payments covers this in detail.

How to Track and Improve Your Payment Approval Rate

You can't improve your payment approval rate without measuring it consistently. Track these figures every month:

• Issuer approval rate: approved authorizations divided by authorizations sent to issuers.
• Filter decline rate: orders your own rules declined, divided by total checkout attempts.
• Review outcome rate: held orders you approved versus canceled.
• Unique-customer conversion: deduplicate retries so one customer trying three times counts as one attempt.

Then break the numbers down to find patterns:

Log every change you make, such as a new rule, a 3DS setting or a checkout redesign, so you can connect cause and effect. Watch for sudden decline spikes, which often signal a card-testing attack rather than a real drop in approvals.

Next Steps: Getting Help With Online Approvals

Many false declines come down to configuration: which gateway features are turned on, how fraud rules are set and what data your checkout sends. MannyPay provides online payment processing for ecommerce stores, with gateways including Authorize.Net and NMI and integrations with platforms such as Shopify, WooCommerce and BigCommerce. Results depend on your business, customers and setup, so no provider can promise a specific approval rate.

To review your online payment setup with a specialist, request a free quote or contact the MannyPay team.

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.