## TL;DR
issuer_not_available is a timeout between the acquirer and the issuer, a transient blip, not a rejection. The right move is a scheduled retry: put the invoice back in the retry queue and let Stripe Smart Retries or your own retry schedule try again. The card itself is almost certainly fine.

```text
issuer_not_available
```

## Use this when
- A subscription renewal invoice fails with decline code issuer_not_available.
- The same card succeeded before, so a sudden permanent decline is unlikely.
- You are tuning dunning or Smart Retries behavior for transient failures.

## Not for this skill when
- The decline is do_not_honor, insufficient_funds, or lost_card. Those need customer action.
- This is the first payment on a new card. Check the card details instead of assuming a blip.

## Steps
1. ('Confirm the decline code is issuer_not_available and the invoice is in retryable state. Verify: no customer action is pending on the invoice.', 'Leave the invoice in the retry flow; do not cancel or void it. Verify: the subscription stays active or past_due as configured, not canceled.', 'If you run your own retries, schedule the next attempt 12-24 hours out, not minutes. Verify: backoff is set so you do not hammer a timing-out network.', 'Notify the customer only if retries keep failing; a single blip needs no email. Verify: no dunning email fired for a transient timeout.', 'If it repeats across many customers at once, check the Stripe status page for network issues. Verify: your account shows no processor incident.')

## Variant phrasings
### stripe issuer_not_available retry
The standard follow-up question.

### issuer_not_available stripe meaning
Docs-style search.

### stripe subscription renewal timeout issuer
Symptom phrasing.


Compatibility: Stripe Payments and Billing. issuer_not_available is a network-level decline code on charges and payment intents.

## Why it happens
Card authorization is a live network conversation: acquirer asks the issuer over the card network. issuer_not_available means that conversation timed out, the issuer never answered. It is infrastructure, not judgment. It spikes during issuer maintenance windows and network congestion, and it clears when the network does, which is why waiting and retrying is the correct fix.

## Edge cases / pitfalls
- Do not email the customer "your card was declined" for one issuer_not_available. It was not.
- Aggressive same-day retries on a timing-out issuer waste attempts and look like card testing.
- If a single card hits issuer_not_available repeatedly across days, treat it as a real problem and ask the customer to check with their bank.
- Make sure Smart Retries is enabled; manual dunning often treats every decline the same.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Mys61RYmZij1lyXaN-qOAQ