What Does 'Do Not Honor' Mean? Decline Code 05 Explained
A do not honor decline code means the issuer refused the sale without saying why. Learn what to tell customers and when frequent 05s point to your setup.
On this page 5 sections
A do not honor decline code (response code 05) means the cardholder's bank refused the transaction and gave no reason. A single 05 almost never points to a problem with your terminal, and the code does not say the card is stolen or the account is empty. It says the issuer said no. Most customers clear it by calling their bank or by switching cards.
One decline is the customer's problem to solve. A cluster of them is yours to investigate. The sections below cover both: the words to use at the counter, and the checks to run when 05s start to spike.
What the Do Not Honor Decline Code Means
Every card sale starts with an authorization request. Your terminal or gateway sends it to your processor, the processor passes it across the card network, and the bank that issued the card answers with a response code. One code means approved. The rest are some form of no.
Most decline codes name a cause. An expired card has its own code, and so does a card reported lost or stolen. Code 05, "do not honor," names nothing. It is the issuer's generic decline: a refusal with the reason withheld.
Many terminals never display the number itself. Staff see a word like "Declined" or "Call Issuer" on the screen. The raw code lives in the transaction detail inside your gateway or processor reporting, and that is where to look when you need to know what happened. If you're unsure which company in your setup holds that data, our guide to how a payment processor differs from an acquirer and a gateway sorts out who does what.
Two misunderstandings cause most of the friction at checkout:
- A 05 doesn't accuse anyone of fraud. The issuer's reason could be fraud screening, or it could be something as ordinary as a daily spending limit. Neither you nor your cashier knows which, so nobody at the counter should guess out loud.
- Running the card again rarely changes the answer. The issuer returns the same decline seconds later, and repeated attempts make the account look more suspicious, not less. The card networks also have rules that penalize excessive retries on declined cards. Ask your processor which limits apply to your account and how they are enforced.
Why Issuers Send a Generic Decline Instead of a Reason
The main reason is fraud screening. When a bank's risk model flags a purchase as unusual, a decline that said "suspected fraud" would tell a criminal at your counter exactly what tripped the alarm. A generic decline gives away nothing.
Privacy is the second reason. A frozen balance or a past-due payment is between the bank and its customer. The same goes for restrictions the cardholder asked for. None of it is the merchant's business, so none of it appears in the response.
Common triggers behind a 05 include:
- Activity outside the cardholder's normal pattern, such as a ticket far larger than usual or a purchase in a city they've never shopped in
- Restrictions on the card, including blocks the cardholder set on online or international use
- A replacement card the customer hasn't activated yet
- Internal spending or velocity limits the issuer doesn't disclose
- An issuer system problem that defaults to "no"
Issuers differ in how freely they use 05. One bank returns a specific code where another sends the generic one, which is why the same customer's card can come back 05 at your shop and with a clearer code somewhere else.
Nearly all of these causes sit on the customer's side. The exceptions, covered in the last section, are cases where your setup gives the issuer less confidence than it should have.
Card Declined "Do Not Honor": What to Tell the Customer
Your goal is to keep the sale while sparing the customer embarrassment. Keep your voice low and don't guess at the reason. Then give the customer something to do. Here is a script your staff can use word for word:
"Your bank didn't approve this one and didn't send us a reason. Banks do this when they want to confirm a purchase with you, and some send an alert to your phone right away. You're welcome to check, or we can try another card."
The script blames nobody, and it gives the customer two ways forward. Adjust the delivery to the setting:
Restaurants and bars. Bring the card back to the table discreetly instead of announcing it across a crowded bar. If the guest's bank sent a fraud alert, they can approve it in their banking app, and then you run the card once more. Don't hold a second card "just in case" without asking first.
Retail stores. Big-ticket sales like jewelry or a furniture deposit are where unusual-amount flags show up. Offer to hold the merchandise at the counter while the customer calls the number on the back of their card.
Salons and spas. Declines here hit cards on file, such as a deposit or a late-cancellation fee charged weeks after the card was saved. Send the client a short, neutral message asking them to update their card. Don't assume they're dodging the charge.
E-commerce stores. Your checkout error message does the cashier's job. "Your bank declined this payment. Please contact your bank or try a different card" is accurate and keeps the buyer moving. Avoid any message that mentions fraud or calls the card invalid.
Two things to never do: run the card over and over, or split the purchase into smaller charges to sneak it through. Card network rules prohibit breaking one sale into several authorizations to get around a decline, and your processor can point you to the exact language. For broader front-of-house training, see our guide on what cashiers should say and do when a card is declined at checkout.
Example: A Rush of Code 05 Declines on a Busy Friday Night
The numbers below are illustrative. They show how to read a cluster of declines. They are not a benchmark for how often 05s occur.
Assumptions: a neighborhood restaurant and bar runs two countertop terminals plus one handheld for tableside payment. On a normal Friday it processes 180 card transactions and sees 3 declines, or 1 in every 60 (180 ÷ 3). This Friday, the batch report shows 22 declines on the same 180 transactions, more than seven times the usual count (22 ÷ 3 ≈ 7.3). Of those 22, 17 came back as 05.
One declined card tells you about one customer. Seventeen 05s in a single night tell you to look for a common thread. Pull the decline detail and sort it:
| If the 05s cluster by... | It points to... | What to do |
|---|---|---|
| One terminal or the handheld only | That device: outdated software or a bad configuration | Compare it with the other terminals, then call your processor's support line with the terminal ID |
| One issuing bank (the same bank identification number at the start of the card number) | That issuer's systems or risk rules | Nothing on your side in most cases; note it and check whether it clears by morning |
| One card network | A network-level or routing issue | Contact your processor, which can see network status you can't |
| Many banks, devices and brands at once | Something about your merchant account itself | Work through the checklist in the next section |
Now suppose 15 of the 17 came from the handheld, which received a software update that afternoon, while the countertop units ran normally. The handheld is the problem, not 15 unlucky customers. The fix is a call to support, and your servers don't need a new script.
Run this sort on any spike before you change anything else. A decline problem that looks mysterious from the floor tends to have an obvious cause once the data is lined up by device and issuer.
When Frequent 05s Signal a Problem on Your End
Steady, elevated 05s are different from a one-night blip. When the pattern persists, the issuer is reacting to how your transactions look. Check these in order:
- Card testing on your website. Fraudsters run stolen card numbers through small online authorizations to find out which ones work. The signature is a burst of tiny charges, most of them declined, from new accounts or a narrow range of IP addresses. Add CAPTCHA or velocity limits at checkout and tell your processor right away.
- Missing data on card-not-present sales. Online and keyed transactions sent without the CVV or billing address give the issuer less to verify, so more of them get a cautious no. Confirm your gateway collects both fields and passes them along.
- No 3-D Secure on online orders. Authentication lets the issuer verify the cardholder during checkout, which gives the bank grounds to approve. Our page on 3-D Secure authentication for online payments explains how it works.
- Your merchant category code. The MCC tells issuers what kind of business you run, and cardholders or issuers block certain categories. A code that doesn't match what you sell hurts approvals. Read how merchant category codes affect your account for the details. Correcting a wrong code goes through your processor's underwriting; never assign yourself a different one.
- Your billing descriptor. When the name on a customer's statement doesn't look like your business, cardholders dispute charges and issuers grow wary. Make sure it matches your storefront or website name.
- International cards. Some issuers decline cross-border purchases by default. If foreign buyers are a real share of your sales, ask whether your account is set up for international payment processing.
- Terminal software and settings. Outdated firmware or a misconfigured device sends malformed requests. Keep devices updated and log the date of every change so you can match it against your decline history.
Bring your sorted decline data and this list to your processor. You'll get a faster, more specific answer than you would by reporting "a lot of declines."
If you've worked through the list and your provider still can't explain the pattern, get a second opinion. You can request a free processing quote from MannyPay, and a specialist will respond within one business day. Start with this week's batch report, though: sort the declines by device first, then by issuing bank. That two-step sort tells you whether the problem is yours to fix.
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.

