Skip to content

Decline code 01: Refer to Card Issuer

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

Quick answer

Decline code 01 — “Refer to Card Issuer” — is an issuer response under the ISO 8583 standard telling the merchant to contact the cardholder's bank before completing the charge. It's a hard decline: the bank hasn't approved the transaction, so an immediate retry returns the same result. Stripe surfaces the underlying issuer decision as the call_issuer / do_not_honor family, and Authorize.net returns it as a generic “Declined.” Recovering it takes customer outreach and a timed retry, not re-attempts.

What code 01 means

Hard declineDo not retry

Don't blind-retry a 01 — the issuer is asking the merchant to contact the bank rather than approving the charge, so re-running the same transaction returns the same response. Recover it with customer outreach (have the cardholder confirm or call their issuer) plus a retry timed once the hold is cleared, 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 01 maps across the stacks Revatto recovers on.

ISO 8583
Code01
CalledRefer to Card Issuer
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 placed a hold or flagged the transaction for manual review and wants to speak with the cardholder before authorizing.
  • Fraud or risk heuristics on the bank's side caught an unusual amount, location, merchant category, or first charge on a new card.
  • A card restriction the bank chose not to itemize — limits on recurring or card-not-present charges, international use, or specific merchants.
  • Outdated or recently reissued card details the network has not fully propagated to the issuer.
  • A temporary issuer-side condition the bank will clear once the cardholder confirms the charge or completes verification.

How to recover it

  1. 1Don't re-run the same charge right away — a 01 won't clear on a blind retry, and repeated attempts 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 wants to verify the charge, and ask them to confirm it or call their issuer.
  3. 3Time the retry to land once the cardholder has had a chance to clear the hold or update the card, not back-to-back.
  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, $0 monthly, cancel anytime).See how Revatto recovers 01declines →

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