Transaction Failed Reasons
Below is a reference list of the most frequently encountered error messages returned by issuing bank gateways for unsuccessful transactions.
The failure message for a transaction is returned in the failure_reason parameter within the responses of the Get Payment Link Details and Get Transaction Details API endpoints.
Gateway Failure Reasons Table
| Failure Reason | Possible Causes & Recommended Actions |
|---|---|
| Insufficient funds | Attempting an online purchase that exceeds the credit card's available limit. Customer should try a different card or contact their bank. |
| 3DS authentication failed | User entered an incorrect OTP/password, the cardholder or issuing bank is not enrolled in 3DS, or a technical timeout occurred during 3DS challenge. |
| The issuer bank has declined the transaction | Incorrect card details, insufficient credit limit, fraud risk rejection, expired card, or card not enabled for online e-commerce transactions. |
| The transaction has been blocked from the gateway | Unsupported card BIN, merchant security filtering rules, or risk-scoring threshold exceeded. |
| Transaction canceled | Customer closed the 3DS verification window or cancelled the checkout session before completion. |
| Session timeout | Customer remained inactive on the bank authentication screen for longer than the permitted session window. |
| Wrong Security Code | The CVV/CVC entered by the customer does not match the issuing bank records. |
| The card is expired | The expiration date on the card has passed. |
| Denied by Risk | Blocked by automated risk management or anti-fraud security engine. |
| The card issuer doesn't respond | The issuing bank's authorization network timed out or is temporarily experiencing downtime. |
| Unspecified Failure | Generic bank authorization decline; recommend customer reattempts with an alternate payment card. |