Stripe decline code

issuer_not_available

Stripe couldn't reach the issuing bank to get an authorization decision — a temporary connectivity problem rather than a declined card.

Primary source: Stripe’s official decline codes reference

Why it happens

  • The issuing bank's authorization system was briefly unreachable.
  • A network route to the issuer timed out.
  • Scheduled maintenance on the issuer side.

Should you retry it?

Yes — retrying usually recovers it

Once the issuer is reachable again, the same card usually authorizes normally, so a prompt retry is effective.

How to recover it

Retry on a short schedule until the issuer is reachable. No customer action is typically required.

Stripe's own retries usually clear temporary errors like this. Recoverly watches what's left: if the invoice is still unpaid after Stripe's retry schedule ends, it opens a case and — with your approval — emails the customer a Stripe-hosted payment page to finish the payment.

See how much failed-payment revenue you can recover

Connect Stripe (we only read) and Recoverly shows your recoverable revenue in 30 seconds.

Related decline codes

Written by the Recoverly team · Published June 25, 2026 · Last reviewed July 17, 2026

Recoverly finds invoices Stripe’s retries left unpaid and — with your approval — sends payment-update emails, then verifies what actually came back. This page is informational and not affiliated with Stripe.