ERR-TIMEOUT | Session timeout
This code indicates the session expired or timed out before the transaction could be completed.
What This Code Means
ERR-TIMEOUT appears when the system ends a user session due to inactivity, elapsed time, or a security timeout threshold. Many banking and payment systems require sessions to remain current while sensitive actions are performed. If the session expires during review, confirmation, or submission, the system may reject the request to prevent processing under an uncertain authentication state. This code reflects session-state management and security timing behavior. It does not automatically mean the payment failed permanently at the network level; it means the system did not confirm the action within the valid session window.
Where Users Usually See This Code
- After leaving a transfer or payment confirmation screen open too long
- During multi-step verification flows with delayed completion
- In apps or web portals when switching networks or backgrounding the app
Why This Code Appears
- Session expired due to inactivity
- Security timeout occurred during verification or confirmation
- Network interruption delayed completion beyond allowed time
- The app/browser lost state due to backgrounding or refresh
What Typically Happens Next
- The transaction is not submitted or is marked as not completed
- The user may be prompted to sign in again
- The system may return to the start of the transaction flow
What This Code Is Not
- It is not a decline based on funds or credit availability
- It is not an issuer outage code by itself
- It is not confirmation that the transaction posted and then reversed
Troubleshooting Checklist
- □ Check the transaction history to confirm whether a new entry was created
- □ Review whether the platform shows a draft, queued, or pending record
- □ Re-authenticate and re-check the status before initiating a duplicate transaction
- □ If uncertainty persists, use official support channels to confirm final posting status
Notes And Edge Cases
Session timeouts can occur even during active use if the platform uses strict absolute session lifetimes. Some systems invalidate sessions when risk signals change (device, IP, location), which can present as a timeout-like failure. In certain flows, a transaction might be submitted but the confirmation step fails; this can create user uncertainty. The most reliable indicator is the final transaction record shown in the account history, which may update after processing delays.