Response Code 96: System malfunction
Generic system error in the processing chain. Could be acquirer, network, or issuer.
What Does Code 96 Mean?
Response code 96 is the system-level catch-all error. Something went wrong in the processing chain, whether at the acquirer, the card network switch, or the issuer, but the system can't identify the specific component that failed. The transaction was not processed.
Code 96 is similar to code 91 (issuer unavailable) but broader. While 91 specifically means the issuer was unreachable, 96 covers any infrastructure failure in the chain. It can also indicate data format errors that the system can't categorize into a more specific code.
In practice, code 96 is highly retriable. The underlying issues are almost always transient. If the code persists across multiple retries over several hours, it usually indicates a more serious infrastructure problem that your payment processor needs to investigate.
Should You Retry?
Transient by nature. Recovery rates are high when retry logic accounts for the failure source.
Common Causes
- Transient error in the acquirer's processing system
- Card network routing failure
- Timeout between network components
- Data format error that the system couldn't categorize
Network Behavior
The same response code can mean different things depending on the card network. Here is how each network treats Code 96:
Platform Mappings
This code surfaces under different names depending on the payment platform:
| ISO 8583 | 96 - System malfunction |
| Stripe | processing_error |
Related Decline Codes
See This Code in Action
Watch how response code 96 flows through a complete ISO 8583 authorization lifecycle.
Open Transaction Simulator