Decline code · Soft decline
Decline code 28: File Temporarily Unavailable
The issuer's account file, the database it must consult to authorize the transaction, is momentarily unreachable. The bank is not rejecting the customer; it simply cannot check the account right now. These windows are usually brief, tied to maintenance or a transient outage.
Should you retry?
Retrying is appropriate and usually succeeds once the issuer's file is back, often within minutes. Space attempts sensibly, and for batch billing, move the retry hours away rather than hammering during the same maintenance window.
Why code 28 happens
- The issuer is running scheduled maintenance on its authorization systems, common in overnight windows for the issuer's local time zone.
- A transient outage or failover event at the issuer took the account file offline mid-transaction.
- The network's stand-in processing could not cover this transaction type while the issuer was unreachable.
- Heavy load at the issuer caused file access timeouts.
What to do about it
- Retry after a short delay; many of these windows last minutes, not hours.
- For recurring billing, reschedule the attempt rather than burning retries in a maintenance window, and note the issuer's time zone since overnight maintenance follows local hours.
- If a specific issuer BIN returns 28 repeatedly at the same time of day, shift your batch billing schedule away from that window.
- Give real-time customers a graceful message and invite them to try again shortly rather than implying their card failed.
Frequently asked questions
- How long does file temporarily unavailable last?
- Typically minutes to a few hours. It reflects issuer maintenance or a transient outage. Retrying after a short wait usually succeeds, and repeated failures at the same time of day point to a scheduled maintenance window.
- Is decline code 28 a problem with my payment processor?
- No, the unavailable system is at the card-issuing bank. Your processor delivered the request; the issuer could not access its account records to answer it. No processor change or routing adjustment reaches around that.
Related decline codes