Skip to content

Decline code 05: Do Not Honor

Jay StevensBy Jay Stevens · Principal EngineerReviewed by Jordan MederichUpdated 2 min read
Summarize with AI

Quick answer

Decline code 05 — “Do Not Honor” — is a generic decline from the cardholder’s issuing bank: the bank refused the charge without returning a specific reason. Under the ISO 8583 standard it’s treated as a hard decline, so an immediate retry rarely clears it. It’s the same issuer decision Stripe reports as do_not_honor and that Authorize.net and NMI return as a generic “Declined.” Recovering it takes customer outreach and a timed retry, not re-attempts.

What code 05 means

Hard declineDo not retry

Blind, immediate retries almost never clear a 05 — the issuer is refusing the charge for an unstated reason. Recover it with customer outreach plus a retry timed 24–72 hours later, not back-to-back re-attempts.

Cross-processor equivalents

The same issuer decision surfaces under a different code on every processor. Here is how code 05 maps across the stacks Revatto recovers on.

ISO 8583
Code05
CalledDo Not Honor
Stripe
Codedo_not_honor
CalledDo not honor
Braintree
Code2000
CalledDo Not Honorgeneric issuer decline
Authorize.net
Code5
CalledDo not honorresponseReasonCode 5
NMI
Code201
CalledDo not honor
Chargebee
Codedo_not_honor
CalledDo not honor
Recurly
Codecall_issuer
CalledCall issuer
IxoPay
Code05
CalledDo not honorISO 8583 adapterCode 05 (refer to issuer)
Shopify
CodeDO_NOT_HONOR
CalledDo not honor
Whop
Codedo_not_honor
CalledDo not honornormalized — no processor-specific code (free-text categorized)
Fanbasis
Codedo_not_honor
CalledDo not honornormalized — matched by substring rule, no processor-specific code

Why it happens

  • The issuer’s fraud or risk heuristics flagged the transaction (unusual amount, location, or merchant category).
  • An account limit or insufficient funds the bank chose not to itemize — some issuers return 05 instead of 51.
  • Card restrictions on recurring or card-not-present charges, international use, or specific merchant categories.
  • Outdated card details, or a recently reissued card the network has not fully propagated.
  • A temporary issuer-side hold the bank will release once the cardholder confirms the charge.

How to recover it

  1. 1Don’t re-run the same charge right away — repeated 05s trip issuer velocity rules and inflate your decline ratio.
  2. 2Reach the customer on a channel they actually answer — email and SMS — explain the bank declined the charge, and ask them to confirm it or call their issuer.
  3. 3Time the retry to land 24–72 hours later, once the cardholder has had a chance to clear the hold or update the card.
  4. 4
    When it persists, a real person — not another automated email — works the card update directly. That AI-plus-human handoff is exactly what Revatto does for you: we recover the payment end to end, and you only pay if it works (20% of the first recovered payment, $0 setup).See how Revatto recovers 05declines →

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

Frequently asked questions