Issuer Unavailable Decline
An "issuer unavailable" decline occurs when the cardholder's issuing bank cannot be reached by the card network at the time of the transaction. The bank's systems are offline, undergoing maintenance, or experiencing technical difficulties. Like network timeouts, this is entirely an infrastructure issue — the customer's card and account are perfectly fine. This soft decline has a 95%+ recovery rate because the bank will come back online and the retry will succeed.
Affected Percentage
~3% of all declines
Recovery Rate
95%+ recoverable
Recommended Action
Retry with strategy
Common Causes
Scheduled bank maintenance
Banks perform system maintenance, often during off-peak hours (late night/early morning). During these windows, their authorization systems may be temporarily offline.
Bank system outage
Unplanned outages at the issuing bank can take their authorization systems offline. These are usually resolved within hours.
Regional banking infrastructure issues
In some regions, banking infrastructure is less reliable. Power outages, telecommunications issues, or natural disasters can take bank systems offline for extended periods.
Card network routing disruption
Occasionally the issue is not with the bank itself but with the network path between the card network (Visa/Mastercard) and the specific issuing bank.
Recommended Retry Strategy
Timing
Retry after 1-4 hours. If that fails, retry again after 6-12 hours. Most bank outages resolve within a few hours.
Max Retries
3-4 retries over 24-48 hours
Reasoning
Bank unavailability is almost always short-lived. Waiting a few hours and retrying is nearly guaranteed to succeed. There's no need for customer outreach — this resolves itself.
Best Practices
- 1
Wait 1-4 hours before the first retry. Issuer outages are typically resolved within this window.
- 2
If the first retry fails, extend the wait to 6-12 hours — the bank may be undergoing extended maintenance.
- 3
Do not contact the customer. This issue has nothing to do with their account and will resolve on its own.
- 4
Monitor for patterns — if many transactions from the same BIN range are failing simultaneously, it confirms a bank-side outage.
- 5
Ensure your payment processor provides specific response codes that distinguish "issuer unavailable" from other generic errors so you can route to the correct retry logic.
How Rezoki Handles This Automatically
Rezoki recognizes issuer unavailable declines as transient infrastructure issues and applies a rapid retry schedule. The first retry fires after 2 hours, with subsequent retries at 6-hour intervals. Rezoki also performs cross-customer analysis — if multiple customers sharing the same issuing bank BIN range all fail simultaneously, Rezoki identifies it as a bank outage and queues all affected transactions for batch retry once one succeeds, indicating the bank is back online. No customer notification is sent for issuer unavailable declines.