Is Do Not Honor a soft or hard decline?

Hard. ISO 8583 classifies code 05 as a hard decline, meaning the issuer is refusing the charge rather than reporting a transient error. An immediate blind retry almost never succeeds; recovery needs customer action.

Why do banks use Do Not Honor instead of a specific code?

Issuers prefer not to disclose certain decline reasons — fraud-risk flags, undisclosed limits, or internal holds. Code 05 lets them refuse the charge without revealing the underlying cause.

What is the Stripe equivalent of Do Not Honor?

Stripe surfaces it as the do_not_honor decline_code on a card_declined error, occasionally as generic_decline. The underlying issuer decision is identical to ISO 8583 code 05.

Can I retry after a Do Not Honor decline?

Yes, but not immediately. Retrying the same charge right away almost never clears a 05. Wait 24-72 hours and reach the customer first — ask them to confirm the charge with their bank or update their card.

How does Revatto handle Do Not Honor declines?

Revatto detects the decline, reaches the customer via email and SMS under your brand, and times the retry for when recovery is likely. A human follows up when automation stalls. You only pay when the payment is recovered.

What is Do Not Honor? (decline code 05 explained)

By Jay Stevens · Founding EngineerReviewed by Jordan MederichUpdated July 11, 20263 min read

Summarize with AI

Quick answer

Do Not Honor (decline code 05) is a catch-all refusal from the cardholder's issuing bank: the charge was declined, but the bank did not return a specific reason. Under ISO 8583, code 05 is technically a hard decline, meaning an immediate retry rarely succeeds. The issuer may have flagged the transaction for fraud risk, hit an internal limit, or simply chosen not to disclose the actual cause. Stripe surfaces it as do_not_honor; Authorize.net and NMI return it as a generic Declined. Recovery requires customer outreach — asking the cardholder to confirm the charge or contact their bank — plus a timed retry 24-72 hours later.

What Do Not Honor means

Do Not Honor is a decline code that says the least while covering the most ground. The cardholder's bank refused the charge, but the response reveals nothing about why — no insufficient funds flag, no expired card notice, no fraud alert. Just a generic refusal.

Under ISO 8583 it is code 05. Processors translate it into their own labels: Stripe calls it do_not_honor (or generic_decline), while Authorize.net and NMI return a two-digit response code 2 with Declined as the reason text. The underlying issuer decision is identical.

Why banks return Do Not Honor

Issuers use code 05 when they decline a charge but prefer not to disclose the reason. Common triggers include:

Fraud or risk heuristics flagged the transaction — unusual amount, location, or merchant category.
Account limits or insufficient funds the bank chose not to itemize (some issuers return 05 instead of 51).
Card restrictions on recurring, card-not-present, or international charges.
A recently reissued card whose new details have not fully propagated through the network.
A temporary issuer-side hold awaiting cardholder confirmation.

How to recover a Do Not Honor decline

Because the bank gives no actionable reason, recovery depends on the customer. Reach them on a channel they answer — email and SMS — explain the bank declined the charge, and ask them to confirm it with their issuer or update their card.

Time the retry 24-72 hours later, once the cardholder has had a chance to clear any hold. Repeated immediate retries trip issuer velocity rules and inflate your decline ratio without recovering the payment.

Revatto runs this sequence end to end — AI-timed retries plus human outreach under your brand — and you only pay if the payment comes back: 20% of the first recovered payment, $0 monthly.

See what Revatto would recover for you

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential