96 | System malfunction
This code indicates the transaction failed due to a system malfunction in the processing chain.
What This Code Means
Response code 96 (“System malfunction”) is returned when a system error prevents proper processing of the transaction. This may occur within the issuer environment, the network, the processor, or another component in the authorization path. The code reflects a technical processing failure rather than a decline decision based on funds, permissions, or card validity. It does not imply anything specific about the account status. It indicates the authorization could not be completed due to an internal error condition. The underlying defect is not specified in the response code.
Where Users Usually See This Code
- Payment gateway declines categorized as system errors
- Processor incident reports during degraded service periods
- Transaction logs showing non-decision technical failures
Why This Code Appears
- Processor or network experienced an internal error
- Issuer systems returned an error response rather than an approval/decline decision
- Data validation failed in a way mapped to “malfunction”
- Temporary infrastructure issues disrupted transaction processing
What Typically Happens Next
- Authorization fails and does not complete
- Merchant sees a technical error decline code
- Subsequent attempts may succeed if the malfunction clears
What This Code Is Not
- It is not an issuer policy decline (see 05/57/62)
- It is not an expired card outcome (see 54)
- It is not an insufficient funds response (see 51)
Troubleshooting Checklist
- □ Review incident timelines and correlation across multiple transactions
- □ Compare failure rates by processor route, issuer, or channel
- □ Record detailed transaction identifiers for troubleshooting through official workflows
- □ Use official processor/acquirer support escalation paths for repeated malfunctions
Notes And Edge Cases
Code 96 can represent multiple technical failures, including intermittent defects that appear only under certain transaction types or routing paths. Some processors map a variety of internal exceptions to 96 for standardization. During widespread disruptions, 96 may increase alongside issuer unavailable responses. Because the code is non-specific, correlating by timestamp, route, and transaction type is often necessary to identify patterns.