What is an issuer unavailable decline? (code 91 explained)
By Jay Stevens · Founding EngineerReviewed by Jordan MederichUpdated 3 min readQuick answer
An issuer unavailable decline (ISO 8583 code 91, also called Issuer or Switch Inoperative) means the cardholder's issuing bank or a network switch routing to it was temporarily unreachable when the charge ran. It is a soft, transient processor-side error — not a problem with the card itself. The account is still valid and funded; the authorization request simply could not reach the issuer to get a decision. Stripe surfaces the same condition as a processing_error; Authorize.net and NMI return it as a top-level Error (response code 3). A retry timed after a short delay usually clears it once the system is back online.
What an issuer unavailable decline means
An issuer unavailable decline is the card network's way of saying the authorization request could not reach the cardholder's bank. The issuing bank was offline, a network switch in the routing path was unreachable, or a timeout occurred before a decision came back. Under ISO 8583 it is code 91, titled Issuer or Switch Inoperative.
It is a soft decline — a transient processor-side error, not a refusal of the card. The cardholder's account is still open, the card is still valid, and the balance or credit line is unchanged. The problem is on the infrastructure side, not the customer side.
Why issuer unavailable declines happen
The decline signals a temporary break in the authorization chain:
- The issuing bank was offline for maintenance, experiencing an outage, or had an overloaded authorization system.
- A network switch routing the request between the acquirer and issuer was unreachable or timed out.
- Intermittent connectivity dropped the request mid-route before a decision could return.
- High transaction volume caused the issuer or switch to refuse new requests rather than queue them.
- A processor-side timeout fired because no response came back within the allowed window.
How to recover an issuer unavailable decline
Do not hammer the card with immediate re-attempts. Back-to-back retries during an outage stack failures and inflate your decline ratio without any chance of success while the system is still down.
Wait for the issuer or switch to recover — a delay of a few minutes to a few hours — then re-run the same charge. The card details are still valid, so a timed retry after the outage window usually clears.
Revatto handles that timing for you: AI detects the decline, times the re-attempt to when the issuer is back, and runs email, SMS, and human follow-up if the outage persists. You only pay when the payment is recovered — 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.