ISO Response Code
| Code | Description | Additional info | Recommended actions |
|---|---|---|---|
| 000 | Approved | The transaction has been approved and has been successfully completed. | |
| 100 | Authorization Denied (Generic) | The transaction has been declined for an unknown reason. | The cardholder will need to contact the issuer of their payment card for further information. |
| 101 | Expired card or invalid expiration date | The transaction was declined due to an invalid card expiration date | The cardholder will need to use another payment method to complete the purchase. |
| 102 | Suspected fraud | The payment was declined because suspicious fraud activity was detected. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same outcomes of a generic error. |
| 104 | Restricted card | The card number is incorrect or the card has restrictions. | The cardholder can try using another payment method or should contact the issuer of their payment card for further information. |
| 106 | Allowable PIN tries exceeded | The maximum number of allowed PIN attempts has been reached. | The cardholder will need to use another payment method to complete the purchase. |
| 109 | Invalid merchant | The merchant profile is not active. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 110 | Invalid amount | The transaction value is not acceptable or exceeds the maximum allowed amount. | If the amount appears to be correct, the cardholder is advised to consult the issuer of the card to verify if they are authorized to make purchases for that amount. |
| 111 | Invalid card number | The card number is incorrect. | The cardholder can try using another payment method or should contact the issuer of their payment card for further information. Alternatively, they should verify the entered data. |
| 112 | PIN Required | The card payment was rejected as it requires PIN entry. | The cardholder should try again by inserting their card and entering the correct PIN. |
| 114 | No account of type requested | The card or the account associated with the card is not valid. | The cardholder will need to contact the issuer of their payment card for further information or use another payment method. Alternatively, they should verify the entered data. |
| 115 | Requested function not supported | Transaction type not supported. | The cardholder will need to use another payment method to complete the purchase. |
| 116 | Not sufficient funds | The transaction cannot be completed due to insufficient funds on the card. | The cardholder is required to use an alternative payment method. |
| 117 | Incorret PIN | The PIN entered is incorrect. This rejection code applies exclusively to transactions made through a card reader. | The customer can try again using the correct PIN. |
| 118 | No card record | The card or the account associated with the card is not valid. | The cardholder will need to contact the issuer of their payment card for further information or use another payment method. Alternatively, they should verify the entered data. |
| 119 | Transaction not permitted to cardholder | The cardholder has not been authorized to use this card for payment; it may have been suspended or have usage restrictions. | The cardholder will need to contact the issuer of their payment card for further information. |
| 120 | Transaction not permitted to terminal | The transaction has been declined for an unknown reason. | The cardholder will need to contact the issuer of their payment card for further information. |
| 121 | Exceeds withdrawal amount limit | The transaction value is not acceptable, exceeds the maximum allowed amount, or authentication is required. | The cardholder will need to use another payment method to complete the purchase. |
| 122 | Transaction not permitted | The transaction was declined due to usage constraints or other unknown reasons | The cardholder will need to contact the issuer of their payment card for further information. |
| 123 | Exceeds withdrawal frequency limit | Soft Decline - transaction declined because the issuer requires Strong Customer Authentication (SCA). | Reprocess the transaction requesting Strong Customer Authentication (SCA). |
| 124 | Violation of law | The transaction has been declined due to issuer rule violation. | The cardholder will need to contact the issuer of their payment card for further information. |
| 125 | Card not effective | The card or the account associated with the card is not valid. | The cardholder will need to contact the issuer of their payment card for further information. |
| 126 | Invalid PIN block | The card payment was rejected as it requires PIN entry. | The cardholder should try again by inserting their card and entering the correct PIN. |
| 129 | Suspected counterfeit card | The payment was rejected because suspicious fraud activity was detected. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same outcomes of a generic error. |
| 142 | Incorrect CVV2. | The payment was declined because authentication failed due to incorrect CVV. | The cardholder should try again by correctly entering the CVV. |
| 159 | Incorrect PIN | The payment was declined because authentication failed due to incorrect CVV. | The cardholder should try again by entering the CVV correctly. |
| 165 | Inactive Account | The card or the account associated with the card is not valid. | The cardholder will need to contact the issuer of their payment card for further information or use another payment method. Alternatively, they should verify the entered data. |
| 167 | Lyfe cycle (MasterCard Use Only) | The transaction has been declined for an unknown reason. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 172 | Additional Customer Authentication Required (to be used for physical POS and EComm) | The transaction cannot be completed due to the cardholder's failed authentication. | The cardholder must correctly authenticate to complete the payment. |
| 178 | Invalid cryptogram | The payment was declined because authentication failed due to incorrect CVV. | The cardholder should try again by entering the CVV correctly. |
| 182 | Invalid Card | The card number is incorrect or the card has restrictions. | The cardholder can try using another payment method or should contact the issuer of their payment card for further information. |
| 187 | Installment not supported by the card. | The transaction has been declined due to issuer rule violation. | The cardholder will need to contact the issuer of their payment card for further information. |
| 188 | Invalid CVV2 / CVC2 | The payment was declined because authentication failed due to incorrect CVV. | The cardholder should try again by entering the CVV correctly. |
| 190 | Cryptographic failure | The payment was declined because authentication failed due to incorrect CVV. | The cardholder should try again by entering the CVV correctly. |
| 200 | Do not honour | Card Blocked - The transaction was declined for an unknown reason. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same outcomes of a generic error. |
| 202 | Suspected fraud | Card Blocked - The payment was declined because suspicious fraud activity was detected, and the card has been blocked. | It is recommended not to provide more detailed information to the cardholder. Instead, it is advised to communicate the same generic error outcome. |
| 204 | Invalid card | Card Blocked - The cardholder has exceeded the available balance or credit limit on the card. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same generic error outcome. |
| 206 | Exceeded PIN attempts | Card Blocked - The cardholder has exceeded the PIN attempts limit. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same generic error outcome. |
| 208 | Lost card | Card Blocked - The transaction was declined because the card is reported lost or blocked. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same generic error outcome. |
| 209 | Stolen card | Card Blocked - The payment was declined because suspicious fraud activity was detected. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same generic error outcome. |
| 210 | Suspected counterfeit card | Card Blocked - The payment was declined because suspicious fraud activity was detected. | It is suggested not to provide more detailed information to the cardholder. Instead, it is recommended to communicate the same generic error outcome. |
| 413 | Excess Reattempts | Attempt to resubmit the same transaction that was previously denied, so the circuits prohibit the repetition. | The cardholder will need to use another payment method to complete the purchase. |
| 888 | Pending | The transaction was declined for an unknown reason. | The cardholder will need to contact the issuer of their payment card for further information. |
| 902 | Invalid transaction | The transaction was declined for an unknown reason. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 903 | Re-enter transaction | The transaction was declined for an unknown reason. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 904 | Format error | The transaction was declined for an unknown reason. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 906 | Cutover in process | The transaction was declined for an unknown reason. | It is suggested to try the payment again. |
| 907 | Card issuer or switch inoperative | The transaction was declined due to issuer not found or unavailable. | Retry or ask the cardholder to verify the entered data. |
| 908 | Transaction destination cannot be found for routing | The transaction was declined due to issuer not found or unavailable. | Retry or ask the cardholder to verify the entered data. |
| 909 | System malfunction | The transaction was declined due to a technical issue. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 911 | Card issuer timed out | The transaction was declined due to no response from the issuer's authorization systems. | Retry or ask the cardholder to use another payment method. |
| 913 | Duplicate transmission | The transaction was declined for an unknown reason. | The cardholder will need to contact the issuer of their payment card for further information. |
| 921 | Internal Error | The transaction was declined for an unknown reason. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 938 | Generic Error | The transaction was declined for an unknown reason. | Contact support. It is suggested to provide a generic outcome to the cardholder. |
| 999 | Agreement error during creation due to merchant's parameters | The transaction was declined due to errors in the request. | Please verify the parameters and provide the cardholder with a generic error. |
It is advisable not to detail the to the cardholder, in that providing the reason for a denial means providing ill-intentioned persons with an instrument to commit fraud. We suggest distinguishing between positive and negative outcome alone and, possibly, advising the cardholder to repeat the transaction carefully checking entered details or contacting his/her bank immediately.