Introduction
ActionCodes are returned by BGateway and RESTful Payment Gateway when performing financial transactions.
Transactions will only be marked as approved if the returned code from issuer is 000. There are four ActionCodes that SaltPay does returns, the rest are exclusively from issuers
- 904: Malformed XML or incorrect data in insent XML
- 909: System error or network connection to schema is lost
- 953: Host timeout (can also come from network, but then sporadically)
There are four more ActionCodes that are specific to the RESTful Payment Gateway and are not returned by the BGateway service: 997, 998, 999.
The difference between 909 and 953 is minimal, if 953 then the system will send the request and wait for response, if 909 then the system knows that the line is down and there is no reason to send the request. If there are problems, then they start with 953 and then change to 909 until the the problem is fixed.
Note that 904, 909, 953 can also come from issuers or the card schema network. 904 should always be looked into.
ActionCode table
| Action Code | Explanation | ISO Reply |
|---|---|---|
| 000 | Accepted | 00 |
| 100-199 | Reason for transaction dismissal by issuer, card pick-up not required. | |
| 100 | Do not honor (Not accepted) | 05 |
| 101 | Expired card | 54 |
| 102 | Suspected card forgery (fraud) | |
| 103 | Merchant call acquirer | 01, 66, 08 |
| 104 | Restricted card | 62 |
| 106 | Allowed PIN retries exceeded | 75, 76 |
| 109 | Merchant not identified | 03 |
| 110 | Invalid amount | 13, 64 |
| 111 | Invalid card number | 14 |
| 112 | PIN required | |
| 116 | Not sufficient funds | 51 |
| 117 | Invalid PIN | 55 |
| 118 | Unknown card | |
| 119 | Transaction not allowed to cardholder | 57 |
| 120 | Transaction not allowed to terminal | 12, 58 |
| 121 | Exceeds limits to withdrawal | 61, 65 |
| 125 | Card not valid | |
| 126 | False PIN block | |
| 129 | Suspected fraud | |
| 130 | Customer Authentication Required | |
| 131 | Invalid Expiration Date | |
| 161 | DCC transaction not allowed to cardholder | |
| 162 | DCC cardholder currency not supported | |
| 163 | DCC exceeds time limit for withdrawal | |
| 164 | DCC transaction not allowed to terminal | |
| 165 | DCC not allowed to merchant | |
| 166 | DCC unknown error | |
| 200-299 | Reason for transaction dismissal by issuer, card pick-up required. | |
| 200 | No not honor | 04 |
| 201 | Card not valid | 33 |
| 202 | Suspected card forgery (fraud) | |
| 203 | Merchant contact acquirer | 37 |
| 204 | Limited card | 36 |
| 205 | Merchant contact police | |
| 206 | Allowed PIN-retries exceeded | 38 |
| 207 | Special occasion | |
| 208 | Lost card | 41 |
| 209 | Stolen card | 43 |
| 210 | Suspected fraud | |
| 902 | False transaction | 89, 06 |
| 904 | Form error | 30 |
| 907 | Issuer not responding | |
| 908 | Message can not be routed | 15, 80, 81, |
| 909 | System error | 83, 96 |
| 910 | Issuer did not respond | 68 |
| 911 | Issuer timed out | 82 |
| 912 | Issuer not reachable | 91 |
| 913 | Double transaction transmission | 94 |
| 914 | Original transaction can not be traced | |
| 916 | Merchant not found | |
| 950 | No financial record found for detail data | |
| 951 | Batch already closed | |
| 952 | Invalid batch number | |
| 953 | Host timeout | |
| 954 | Batch not closed | |
| 955 | Merchant not active | |
| 956 | Transaction number not unique | |
| 980 | Action code exclusive to RPG and indicates a data form error. | |
| 981 | Action code exclusive to RPG and indicates an invalid token. | |
| 982 | Action code exclusive to RPG and indicates an invalid payment method. | |
| 983 | Action code exclusive to RPG and indicates that MPI result does not allow transaction to continue. | |
| 997 | Action code exclusive to RPG and indicates a network communication problem. | |
| 998 | Action code exclusive to RPG and indicates a form error (See ActionCode: 904). | |
| 999 | Action code exclusive to RPG and indicates a system error. |