On this page
Key takeaways
- Code 05 declines happen when the bank refuses a charge without giving a reason, often to hide a fraud rule or because its systems cannot send a specific code.
- Visa allows up to 20 retries in 30 days on an 05, while on Mastercard the advice code sent with it decides whether you may retry at all.
- An 05 cluster on a few card prefixes, one merchant account or one processing bank usually points to routing or card mix rather than to the cardholder.
- You fix an 05 by reading the advice code, spacing retries, asking for a card update after repeated rebill 05s and escalating clusters through your processor.
Who this helpsSubscription billing owners, RevOps and payments engineers who see 05 do not honor declines on rebills and want a retry, card-update or stop rule built on network rules instead of folklore.
Code 05 is the bank saying no without saying why. In recent subscription datasets from Churnkey and Redux Payments, it is the second most common reason subscription payments fail. One 05 can hide a fraud rule, a blocked card, a stale credential or a bad route. Each cause needs a different response: retry, update, reroute or stop. This guide turns the 05 into a rule. It shows which advice codes make an 05 retryable and how many attempts each network allows. It also shows how to tell a one-off 05 from a pattern. Check for that pattern in your BIN mix (bank identification numbers, the card prefixes that name the issuer), your merchant ID (MID) and your routing.
Do not honor (response code 05) is a generic decline. The card issuer (the bank that gave the customer the card) refused the charge and chose not to say why. Visa files it under Category 4, “Generic response codes”. Visa allows up to 20 retries in 30 days. On Mastercard, the merchant advice code (MAC) sent with the 05 decides whether a retry is allowed at all.
What does decline code 05, 'do not honor', actually mean?
Code 05 means the issuing bank declined the charge and kept the reason to itself. It says nothing specific about funds, card data or fraud. Under Visa’s current Core Rules (24 October 2026 edition), 05 appears on no named list. It therefore falls into Category 4, “Generic response codes”. That makes it a soft, retryable decline.
Some processors and UK banks write it as “do not honour”. Stripe labels it do_not_honor and describes it as a decline “for an unknown reason”. For the codes around it, see the credit card decline code guide. Behind the single label, six causes come up again and again:
- Not enough money or credit: a balance or limit problem the bank could have sent as 51 or 61, which matters because those codes come with clearer retry timing.
- Wrong card data: an address (AVS) or security code (CVV) mismatch. Adyen notes a failed CVV2 often still returns 05 even though Visa has a dedicated N7 code, so the same data will fail again.
- A fraud or velocity rule: the charge broke the cardholder’s usual spending, location or frequency, or arrived too soon after another attempt, so an instant retry tends to trip the same rule.
- A blocked or restricted card: a restriction on the card itself, which no retry will clear until the cardholder or bank lifts it.
- A cross-border charge: Redux Payments reports that a US merchant account billing a UK customer can draw a defensive 05, which makes it a routing question as much as a card question.
- A technical fault: issuer or switch outages can produce 05 alongside 96 and 91, so a burst of 05s next to system errors is a systems problem, not a risk decision.
How common is it? Recent subscription datasets put 05 in second place, not first. Churnkey’s State of Retention 2025 data covers 6 million failed payments. In that data, do not honor was 8.1% of failures, against 42.3% for insufficient funds. Redux Payments studied business-to-consumer (B2C) subscriptions. Its dataset of 1,168,245 failed B2C subscription payments (April 2025 to March 2026) put 05 at 11.3%. Insufficient funds led at 31.7%. The share used to be higher. In 2021, Braintree reported that close to 50% of decline responses were do not honor. In the US, the figure was over 60%. That was before the networks began policing generic codes.
The right response depends on where the card is. At a terminal, the cardholder stands in front of you. Ask for another card, or ask them to call the number on the back. Issuers discuss decline specifics only with their cardholders. Online and on stored-credential rebills, nobody is present. The next step has to come from the code, the advice code and your history with that issuer. The cardholder’s own fix is the same in both cases. They should call the bank, check daily and per-transaction limits, and confirm the card is not blocked. Airwallex gives the same advice and adds one option: pay with a different method.
Why do issuers send a generic 05 instead of the real decline reason?
Issuers send 05 for three reasons, and only one is deliberate. First, they hide fraud logic so card testers cannot learn which rule they tripped. Second, some issuer systems cannot map a specific reason, so 05 is the default. Third, other codes become 05 in transit. Either the network converts them, or the acquirer (the bank that processes card payments for you) cannot receive the original code.
Hiding the rule is deliberate. Issuers use generic declines partly so fraudsters cannot see which risk rules they tripped. Adyen says banks reach for 05 when a charge does not match the shopper’s usual spending, location or frequency. Missing mapping is the quieter cause. Primer (April 2026) traces many 05s to issuer technology limits. Some banks never built systems able to send specific reasons, and some upgraded banks have mapping errors. Xendit puts it in one line: issuers use 05 when they don’t trust a transaction or failed to map a more specific error.
Merchants rarely hear about conversion. Visa stand-in processing (STIP) answers on the issuer’s behalf when the issuer cannot respond. Visa says it can convert some issuer and STIP codes to 05, including fraud-indicative ones. The conversion depends on whether your acquirer is set up to receive the original codes. In practice, your acquirer can decide whether you see the real reason or an 05.
The networks treat overuse of 05 as a data-quality problem. Visa’s rules require the issuer to send the code that most accurately reflects the reason. The rules allow Category 4 codes only when no other value applies. Mastercard’s Data Integrity Monitoring Program expects 05 to stay at or below 5% of an issuer’s card-not-present declines per month. Mastercard has charged assessments under the program since 28 August 2022. Since 25 April 2026, codes Visa reclassifies for misuse count toward the issuer’s Generic Response Codes System Integrity Fee.
Is do not honor a soft or hard decline, and how many times can you retry it?
Do not honor is a soft decline on both networks, but the retry budgets differ. Visa allows up to 20 reattempts in 30 days on Category 4 codes like 05. Visa charges fees from the 21st attempt. Mastercard allows 10 retries in 24 hours and 35 in 30 days on soft declines. The exception is an 05 whose advice code says stop.
Visa’s hard stop lives elsewhere. Its Category 1 “Issuer will never approve” codes are 04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1 and R3. These codes carry a permanent no-resubmit rule for the same credential. Code 05 is not on that list. The soft decline versus hard decline guide covers the full split. For an 05, these limits apply:
| Rule | Limit on an 05 | What it means for you |
|---|---|---|
| Visa Category 4 (current) | Up to 20 retries in 30 days | Fees start on the 21st reattempt. CIT and MIT retries have been counted separately since 25 May 2025. |
| Visa Category 4 (before 25 May 2025) | 15 reattempts in 30 days | This limit is historical. Some processor docs, such as Adyen’s, still print 15. |
| Mastercard soft decline | 10 in 24 hours, 35 in 30 days | Retries beyond 35 cost $0.50 each in the US. |
| Mastercard 05 with no advice code | 15 in 30 days | This is dLocal’s conservative guidance, not a network rule. |
| Mastercard 05 with MAC 03 or 21 | No retry | In the US and Canada, a retry within 30 days is billable whatever the amount. |
| Stripe recommendation | At most 8 retries | Stripe warns that extra retries can read as fraud and raise declines on good charges. |
PayPal (May 2026) lists Visa excessive-retry fees of $0.10 per domestic and $0.25 per cross-border retry.
Spacing matters as much as count. Stripe warns that an immediate retry on a soft decline can trigger a card lock or fraud flag. Adyen advises against retrying an 05 straight away with the same details. A same-second retry sends an identical request into the rule that just refused it. The usual result is a second 05 and one fewer attempt in your budget. Adyen’s wait for a Mastercard MAC 02 is 72 hours. Using that wait as the floor for a first 05 retry is our assumption, not a network rule.
The fees add up across a subscription book. On 25 April 2026, Visa raised its cross-border System Integrity Fee to $0.25 per non-compliant reattempt in the US and Canada. The fee applies after Category 1 to 4 codes, so it covers 05. Set your retry ceiling below 20 on Visa. On Mastercard, read the advice code before you count attempts.
Which merchant advice code turns an 05 into a retry, a card update, or a full stop?
On Mastercard, the merchant advice code (MAC) sent with the 05 decides the next step. The MAC overrides the 05 itself. MAC 01 means fetch updated card details before retrying. MAC 02 means retry later. MAC 03 means do not try again. MAC 21 means the cardholder canceled the recurring payment. Visa sends no MACs at all.
Stop. A retry within 30 days is billable, whatever the amount.
Do not retryFetch the updated card, then charge it.
Fixable without the customerBring the customer back to authenticate, instead of resending the same request.
Needs the customerWait, then retry.
Retry allowedThe precedence rule is documented. dLocal’s docs say a MAC takes precedence over the network response code. Their example pairs 05 “Do not honor” with MAC 03 “Do not try again”. Stripe’s Mastercard table lists 05 only with MAC 01, 03 or 21. An 05 that arrives with an advice code is therefore in most cases an update, a stop or a cancellation. It is not an invitation to retry.
The timed-retry MACs do not apply here. MACs 24 to 30 mean retry after a set wait, from 1 hour up to 10 days. The documentation pairs them only with response code 51, insufficient funds. That is why the code 51 retry guide can schedule retries to the day, and an 05 cannot. Two other Mastercard signals are worth catching. MAC 04 means token requirements were not fulfilled, so you need a credential fix before the next attempt. Heartland notes that an 05 can come back with a “retry with EMV 3DS” signal, where EMV 3DS is the online check in which the cardholder confirms the payment with their bank. In that case, authenticating the cardholder is the route to approval.
Ignoring a stop costs money on every attempt. Mastercard’s revised MAC rules took effect on 1 May 2025 in Europe and 1 January 2026 in the US and Canada. Under them, a card-not-present (CNP) retry on the same card at the same merchant is billable. The window is 30 days after a MAC 03 or 21 decline. For these fees, the amount no longer matters, so lowering the price does not avoid the fee. Canadian acquirer TD Merchant Solutions raised its Mastercard CNP Advice Decline Fee from $0.05 to $0.78 per transaction on 1 February 2026.
Visa has no advice-code system, so you have to classify a Visa 05 from other signals. Slicker points to issuer history and card type. Stripe suggests checking the card verification code (CVC) and address verification service (AVS) results on generic declines. If you bill through Stripe, its advice_code field takes the values do_not_try_again, try_again_later and confirm_card_data. Read advice_code and network_advice_code next to the decline code before you schedule anything.
Why does 05 concentrate on subscription rebills and stored credentials?
05s concentrate on rebills because nobody is present to reassure the bank. A stored-credential charge looks unusual to the issuer’s fraud model in three cases. It arrives without its link to the original transaction, after a long gap, or under an unfamiliar descriptor (the merchant name on the statement). Checkout.com says up to 10% of recurring-payment declines come from basic policy, security and message formatting errors.
- Missing reference ID: Visa and Mastercard both require merchant-initiated charges to carry a reference to the original transaction (Visa’s Transaction Identifier, Mastercard’s Trace ID), and without it the rebill reads like a stranger’s charge.
- Trial conversions and long gaps: Stripe says issuers flag charges from merchants they do not recognize, especially right after a free trial converts to paid, so the first paid rebill is the riskiest one.
- Descriptor drift: Checkout.com recommends the same merchant descriptor on each merchant-initiated request, because a changed descriptor removes the recognition the issuer relied on.
- Stale credentials: Mastercard’s Credential Continuity Program charges $0.09 per recurring transaction in the US (since 1 April 2025) when outdated credentials are sent and an update was available at least 10 days earlier.
- Gateway migrations: the Merchant Risk Council recommends validating reference-ID mapping during gateway migrations, so an 05 spike that starts the week you switch processors points first at IDs that did not carry over.
Network tokens (stand-in card numbers that the card network issues and keeps current) work on the same recognition problem. Visa reports that tokenized card-not-present transactions had a 4.8% higher authorization rate than transactions on the raw card number (PAN) in 2025. Checkout.com reports a 3% to 6% lift, depending on merchant category code (MCC) and region. Deactivated Visa tokens now return 46, a Category 1 code, instead of 05. A token-heavy book can therefore see its 05 share fall while its hard declines rise.
Before acting, split your 05s by transaction type. An 05 on a first-time charge and an 05 on a recurring payment that normally clears usually have different root causes. Report them as two separate lines, first-time charges and recurring charges, before you set any retry rule.
What do you do about a subscriber who returns 05 every billing cycle?
Stop treating it as a retry problem after the second cycle. A card that returns 05 on consecutive rebills is telling you the stored credential is the issue, not the timing. Ask for a card update. Bring the customer on-session (present in your app or checkout) so the next charge is cardholder-initiated. Close the subscription if a stop code arrives.
- Cycle one: retry within the cap, spaced out, and read the MAC on each attempt. A MAC 21, or a Visa R0, R1 or R3, means the cardholder stopped the payment, and all three Visa codes are Category 1.
- Cycle two: send a card-update request before the rebill date and offer another payment method, instead of spending more of Visa’s 20 attempts on the same credential.
- Bring the customer back on-session: a cardholder-initiated payment with 3DS gives the issuer a fresh, authenticated signal, and Visa has counted CIT and MIT retries separately since 25 May 2025.
- Cycle three with no response: pause or cancel. In Redux’s data, 05s recovered 21% of the time with intelligent retries, so about four in five did not come back through retries alone.
Here retry logic ends, and the wider work of recovering failed subscription payments begins. That work covers dunning emails (reminders that ask the customer to fix the payment), card updates and a fallback payment method. Set the cut-off at three cycles and write it into your billing rules.
How do you diagnose an 05 spike across BINs, MIDs and processors?
Count 05s by card. Group them by BIN, MID and acquirer, and compare each slice with its own baseline. If one or a few BINs jump while the rest stay flat, the cause sits with the issuer. If 05s rise everywhere, check your integration or processor. If the same BIN approves better through another acquirer, the cause is routing.
A 28-point gap on the same cards points to the acquirer pairing. Equal rates on both routes would point to the issuer.
Yuno’s hypothetical example (vendor data).
- Deduplicate first: Stripe recommends counting declines by card fingerprint, not charge ID, so retries of one card do not inflate the 05 count.
- Normalize labels: the network 05 is the same everywhere, but Stripe can surface it as generic_decline and Checkout.com as 20005, so compare processors only after mapping both to one code.
- Group by BIN range: Visa’s June 2026 merchant guidance tells merchants to aggregate do not honor and other decline codes across BIN ranges.
- Set a baseline per slice: the Payments & Risk playbook suggests starting alerts at a code spike above 2x normal volume, or one issuer more than 10 percentage points above its baseline, and says these are starting points, not industry limits.
- Compare the same BIN across acquirers: IXOPAY’s rule is that the same pattern on every provider points to the issuer, and one provider doing materially better points to routing.
- Check card and country mix: a shift toward Amex or toward high-05 countries can create a spike with no change in issuer behavior (figures below).
Mix alone moves the number. Churnkey’s sampled data puts do not honor at about 11% of Visa declines, 4% of Mastercard and 7% of Discover. The same data puts it at up to 92% of Amex declines. By issuer country, its share of failures peaks at 24.7% in India and 24.2% in the Philippines. It falls to 4.7% in the Netherlands and 4.6% in Australia. Churnkey’s explanation for the high-05 markets is partly less granular issuer codes, not more risk.
When the slice that moved is a MID rather than a BIN, look at your own setup. Solidgate says a misaligned MCC sets an approval ceiling that no retry logic or routing can lift. Solidgate also says cross-border traffic often reaches the issuer through an acquirer, path and descriptor the issuer does not recognize. Stripe links higher decline rates to cards issued outside the merchant account’s country and suggests processing locally. Yuno looks at 05s on returning customers with clean fraud histories, routed cross-border through a single acquirer. Yuno says these 05s usually signal an issuer-acquirer pairing mismatch rather than fraud. In Yuno’s hypothetical, one European issuer BIN approves at 91% through one acquirer and 63% through another. That is a 28-point gap on the same cards.
Here is the method applied to one book. Say you run Fernway, a coffee subscription billing 50,000 renewals a month. Your 05 count doubles from 600 to 1,200 in one week (illustrative numbers, not a customer’s result). You count by card fingerprint (a stable ID for each card number) and find the 1,200 declines come from 700 cards. Retries inflated the spike. Grouped by BIN, 450 of those cards sit in three BINs from one UK issuer. You bill all of them through your US acquirer. The same BINs approve normally on your EU MID. That points to a routing fix for future first attempts, not 450 bad cards.
A wall of 05s across a whole BIN deserves escalation, not more retries. Visa prohibits issuers from declining systematically by BIN, geography or channel outside listed exceptions. Primer suggests taking concentrated clusters to those issuers through your processor. Send the counts by BIN, the dates and the approval rate on your other routes.
How do you tell 05 apart from 51, 54 and 61?
Each neighboring code names its reason, and 05 does not. Code 51 is insufficient funds, and code 61 is an exceeded amount limit. Both sit in Visa Category 2, “Issuer cannot approve at this time”. Code 54 is an expired card in Category 3, and a credential update fixes it. Code 05 is Category 4, generic. On Mastercard, a 51 usually carries a timing advice code, and an 05 does not.
| Code | What the bank said | Visa category | Usual next step |
|---|---|---|---|
| 05 Do not honor | No reason given | Category 4, generic | Read the MAC on Mastercard; on Visa, space retries within 20 in 30 days. |
| 51 Insufficient funds | Not enough money right now | Category 2, cannot approve at this time | Retry when the balance refills; Mastercard may send timed MACs 24 to 30. |
| 54 Expired card | The expiry date has passed or is missing | Category 3, cannot approve with these details | Update the credential before retrying, because the same data will fail again. |
| 61 Exceeds amount limit | An issuer-set limit was hit | Category 2, cannot approve at this time | Retry later, or ask the customer to raise the limit. |
Is your 05 really a disguised 51? Look at the clues around it. Debit cards made up 58.1% of 05 declines in Redux’s dataset. An 05 on debit that clears a few days later at the same amount behaves like a funds problem. An 05 with an AVS or CVC mismatch behaves like a data problem. An 05 that persists across cycles and acquirers behaves like a stop. For how banks reach these decisions in the first place, see why issuers decline. Then tag each 05 with the code it most resembles.
- Log the raw network response code and the MAC in separate fields on each failed rebill.
- Stop on Mastercard MAC 03 or 21, and on Visa Category 1 codes, including R0, R1 and R3.
- Fetch updated card details before retrying an 05 that came with MAC 01.
- Keep Visa retries on an 05 below 20 in 30 days, and space the first retry instead of repeating it in the same session.
- Count 05s by card fingerprint, then group them by BIN, MID and acquirer before calling it a spike.
- Compare the same BIN across acquirers before blaming the cardholder.
- Send a card-update request and an alternative payment option after the second consecutive 05 on one subscriber.
- Confirm that merchant-initiated charges carry the original transaction reference (Visa Transaction ID, Mastercard Trace ID) after any gateway migration.
Frequently Asked Questions
Is do not honor a soft decline or a hard decline?
Do not honor is a soft decline under Visa’s rules. Visa files 05 in Category 4, generic response codes, which allows up to 20 retries in 30 days. On Mastercard, the advice code decides: an 05 with MAC 03 or MAC 21 behaves like a hard decline, and retrying it within 30 days is billable.
Can you retry a do not honor transaction, and how many times?
Yes, in most cases you can retry a do not honor decline. Visa allows up to 20 reattempts in 30 days, with fees from the 21st. Mastercard allows 10 in 24 hours and 35 in 30 days unless the advice code says stop. Stripe recommends at most eight retries, spaced out rather than immediate.
Why does my bank say do not honor when I have money in my account?
Your bank declined for a reason other than funds and chose not to say which one. Common causes are a fraud or velocity rule, a mismatched security code or address, a block on the card, or a cross-border charge. Call the number on the back of the card, because issuers discuss the specific reason only with the cardholder.
How do merchants reduce do not honor declines on recurring payments?
Merchants reduce do not honor declines on recurring payments by making each rebill look familiar to the issuer. Send the original transaction reference on merchant-initiated charges, keep one consistent descriptor, use network tokens and refresh stale credentials. Then route by issuer results, since in Yuno’s example one BIN approves at 91% on one acquirer and 63% on another.
What is the difference between decline code 05 and 51?
Code 51 tells you the reason, insufficient funds, and code 05 does not. Visa puts 51 in Category 2, “Issuer cannot approve at this time”, and 05 in Category 4, generic. In Redux’s subscription data, 05s recovered 21% of the time against 37.9% for insufficient funds, so a 51 is typically easier to win back.
Why are do not honor declines so common?
Do not honor declines are common because 05 is the code issuers fall back on when they will not, or cannot, send a specific reason. Some 05s are also created in transit when the network or acquirer converts the original code. In recent subscription datasets, 05 is 8.1% to 11.3% of failed payments, second to insufficient funds.