What Does Code 91: Issuer or Switch Unavailable Mean?
The decline code 91, which reads “Issuer or switch unavailable,” in a credit card transaction indicates that the transaction could not be processed because the card issuer or the payment switch used in the transaction was temporarily unavailable. This could be due to system maintenance, technical issues, or network problems preventing communication with the issuer at the time the transaction was attempted. As a result, the transaction cannot be authorized until the issue is resolved. It’s usually recommended to retry the transaction later or use an alternative payment method if the problem persists.
Key Takeaways
- Code 91 usually means the issuer, switch, or authorization path did not respond.
- It is normally a temporary availability or timeout issue.
- It does not prove insufficient funds, fraud, or a bad card.
- Wait briefly, then make one clean retry if appropriate.
- If Code 91 repeats often, review processor, gateway, network, and routing patterns.
Code 91 is the payment system saying, “We could not reach the party that needs to answer.” It is less like a customer being denied and more like the phone line going quiet during the approval call.
For merchants, the job is to keep the sale moving without creating a messy trail of repeated attempts.
What Code 91 Means in Plain English
Every card transaction needs an authorization response. Your business sends the request. The processor and card network route it. The issuing bank or switch is supposed to answer approve, decline, or give another response.
With Code 91, that answer does not arrive. The issuer may be offline, the switch may be unavailable, the request may time out, or stand-in processing may not be available for that transaction.
That makes Code 91 different from declines based on customer behavior, card status, or available balance. It is usually a system-availability problem.
Common Reasons Code 91 Happens
Code 91 can happen even when the customer and the card are legitimate.
- The issuing bank is temporarily unavailable
- The issuer processor or switch does not answer in time
- Network communication times out during authorization
- Stand-in processing is not available for the transaction
- A gateway or processor route is having issues
- The card network cannot complete the path to the issuer
- Issuer maintenance or temporary downtime affects approvals
- A batch of transactions is hitting a weak route or issuer group
One Code 91 event is usually just bad timing. A cluster can show where your payment route is fragile.
What the Merchant Should Do
Handle Code 91 as a temporary authorization failure, not a hard customer decline.
- Pause before retrying. Give the issuer or switch a short window to recover.
- Make one clean retry if the sale is still active. Avoid rapid repeated attempts.
- Offer another payment method. A different card, ACH, wire, or approved alternate option may save the sale.
- Do not blame the customer. Explain that the bank or network could not respond.
- Check your gateway report. Look for repeated timeouts, issuer groups, countries, or card brands.
- Contact your processor if it keeps happening. Repeated Code 91 events may need routing or gateway review.
What Not To Do
Because Code 91 often feels like a vague decline, many businesses respond the wrong way.
- Do not assume the customer has no money.
- Do not accuse the customer of fraud.
- Do not hammer the same card with repeated retries.
- Do not treat Code 91 like Code 05, 51, 59, or 62.
- Do not ignore repeated events from the same issuer, country, card brand, or gateway route.
- Do not ship goods based on a failed authorization.
A controlled retry is reasonable. A retry loop is not. The difference matters for customer trust, processor risk signals, and operational cleanup.
When Merchants Should Look Deeper
A single Code 91 decline may not mean much. Repeated Code 91 declines can expose a payment availability problem.
- Multiple customers hit Code 91 within a short period
- The same issuer or card brand appears often
- One gateway, terminal, or ecommerce route has most of the failures
- Cross-border transactions fail more often than domestic sales
- Subscription rebills show a sudden spike in Code 91
- High-ticket transactions time out more often
- Retry attempts create duplicate-looking activity
- Approval rates drop without a clear change in customer demand
Those patterns can point to processor routing, gateway uptime, issuer availability, network path issues, or weak fallback options.
How Durango Merchant Services Can Help
Durango Merchant Services helps merchants read decline codes as business signals, not just short technical messages.
For high-risk, ecommerce, MOTO, subscription, travel, nutraceutical, CBD, large-ticket, and cross-border merchants, Code 91 can cost revenue when payment routes are fragile. The fix may be better gateway support, smarter payment-method mix, processor review, improved routing, or backup processing options.
If Code 91 keeps appearing in your reports, contact Durango Merchant Services. We can help review the pattern, protect legitimate sales, and build a more resilient payment path.
FAQs For Decline Code 91
It means the issuer, switch, or authorization path was unavailable or timed out, so the payment could not receive an approval response at that moment.
No. Code 91 is usually an availability or timeout issue. It does not prove the cardholder lacks funds or that the card is invalid.
A short wait followed by one clean retry is usually reasonable. Avoid rapid repeated retries and offer another payment method if the sale is urgent.
Investigate when Code 91 appears repeatedly across many customers, issuers, countries, channels, or gateway routes. That pattern may point to processor, gateway, network, issuer, or routing availability problems.