Click here for the PDF to determine all the gateway responses for failed transaction for those clients that are using Securepay to process their transactions (Australia only).
Response codes are supplied by the merchant’s bank to SecurePay after making contact with the customer’s card issuer. After receiving the payment information from SecurePay your bank contacts your customer’s bank to confirm the details of the transaction (card #, expiry date, amount, card valid, etc.). Depending on that interaction, the customer’s bank will reply to your bank with a response code – this message will then be returned to your website by SecurePay. Common types of responses from the banks include:
- Transaction approved: Your customer’s transaction was processed successfully.
- Insufficient funds: The customer’s bank noted that there was not enough money available on the card.
- Card expired: The card used is expired. Has the card been replaced?
- Refer to issuer: This can mean many different things, ultimately you will need to tell your customer to contact their card issuing bank. Do they have another card they can use?
Please find below a more complete list of the Response Codes you may receive from your merchant bank, plus a description on what those responses mean.
Bank Response Codes 00-99
| Code | Response Text | Result | Explanation |
| 00 | Transaction Approved | Successful | The transaction was successful. |
| 08 | Honour with Identification | Successful | The transaction was successful. Some Banks use this code instead of ‘00’. |
| 11 | Approved VIP (not used) | Successful | The transaction was successful. (This code is not used in Australia.) |
| 16 | Approved, update Track 3 | Successful | The transaction was successful. |
| 77 | Approved (ANZ only) | Successful | |
| 01 | Refer to Issuer | Fail | The customer’s bank (Card Issuer) has indicated there is a problem with the credit card number. The customer should contact their bank. The customer should use an alternate credit card. |
| 02 | Refer to Issuer, special | Fail | The customer’s bank (Card Issuer) has indicated there is a problem with the credit card number. The customer should contact their bank. The customer should use an alternate credit card. |
| 03 | No Merchant | Fail | The Merchant ID is invalid, you should contact your Bank and ensure you have provided the correct Merchant Account Number to SecurePay. |
| 04 | Pick Up Card | Fail | The customer’s bank (Card Issuer) has declined the transaction and requested that your customer’s credit card be retained. (card reported lost or stolen). The customer should use an alternate credit card. |
| 05 | Do Not Honour | Fail | The customer’s bank has declined the transaction as the credit card number has failed a security check, or the funds have been frozen or depleted. The customer should use an alternate credit card. |
| 06 | Error | Fail | The customer’s bank (Card Issuer) has declined the transaction as there is a problem with the credit card number. The customer should contact their bank. The customer should use an alternate credit card. |
| 07 | Pick Up Card, Special | Fail | The customer’s bank (Card Issuer) has declined the transaction and requested that your customer’s credit card be retained. (card reported lost or stolen) The customer should use an alternate credit card. |
| 09 | Request In Progress | Fail | The customer’s bank (Card Issuer) has indicated there is a problem with the credit card number. The customer should contact their bank. The customer should use an alternate credit card. |
| 12 | Invalid Transaction | Fail | The customer’s bank (Card Issuer) has declined the transaction because of an invalid format or field. Check the transaction information and try processing the transaction again. |
| 13 | Invalid Amount | Fail | An invalid character (e.g. a dollar sign or a space) may be being passed to the gateway. Check your website’s code. |
| 14 | Invalid Card Number | Fail | The customer’s bank (Card Issuer) has declined the transaction as the Credit Card number does not exist. Check the credit card information and try processing the transaction again. |
| 15 | No Issuer | Fail | The customer’s bank (Card Issuer) does not exist. Check the credit card information and try processing the transaction again. |
| 17 | Customer Cancellation | Fail | |
| 18 | Customer dispute | ||
| 19 | Re-enter Last Transaction | Fail | The transaction has not been processed and the customer should attempt to process the transaction again. |
| 21 | No Action Taken | Fail | The customer’s bank (Card Issuer) has indicated there is a problem with the credit card number. The customer should contact their bank. The customer should use an alternate credit card. |
| 22 | Suspected Malfunction | Fail | The customer’s bank (Card Issuer) cannot be contacted during the transaction. The customer should check the credit card information and try processing the transaction again. |
| 23 | Unacceptable Transaction Fee | Fail | An unspecified error has occurred. |
| 25 | Unable to Locate Record On File | Fail | The customer’s bank (Card Issuer) does not recognise the credit card details. The customer should check the credit card information and try processing the transaction again. |
| 30 | Format Error | Fail | The customer’s bank (Card Issuer) does not recognise the transaction details. The customer should check the transaction information and try processing the transaction again. |
| 31 | Bank Not Supported By Switch | Fail | The customer’s bank (Card Issuer) has declined the transaction as it does not allow transactions originating through mail / telephone, fax, email or Internet orders. This error is associated customers attempting to use a Discover Card. The customer should use an alternate credit card. |
| 33 | Expired Card, Capture | Fail | The customer’s bank (Card Issuer) has declined the transaction as Credit Card has expired or the date is incorrect. Check the expiry date in the transaction and try processing the transaction again. |
| 34 | Suspected Fraud, Retain Card | Fail | The customer’s bank (Card Issuer) has declined the transaction as there is a suspected fraud on this Credit Card number. |
| 35 | Card Acceptor, Contact Acquirer, Retain Card | Fail | The customer’s bank (Card Issuer) has declined the transaction and requested that the customer’s credit card be retained (card reported lost or stolen). The customer should use an alternate credit card. |
| 36 | Restricted Card, Retain Card | Fail | The customer’s bank (Card Issuer) has declined the transaction and requested that the customer’s credit card be retained. (card reported lost or stolen) The customer should use an alternate credit card. |
| 37 | Contact Acquirer Security Department, Retain Card | Fail | The customer’s bank (Card Issuer) has declined the transaction and requested that your customer’s credit card be retained. (card reported lost or stolen) The customer should use an alternate credit card. |
| 38 | PIN Tries Exceeded, Capture | Fail | The customer’s bank (Card Issuer) has declined the transaction as the customer has entered the incorrect PIN three times. The customer’s bank (Card Issuer) has requested you retain the credit card. The customer should use an alternate credit card and contact their bank. |
| 39 | No Credit Account | Fail | The customer’s bank has declined the transaction as the Credit Card number used is not a credit account. The customer should use an alternate credit card. |
| 40 | Function Not Supported | Fail | The customer’s bank (Card Issuer) has declined the transaction as it does not allow this type of transaction. The customer should use an alternate credit card. |
| 41 | Lost Card | Fail | The customer’s bank (Card Issuer) has declined the transaction as the card has been reported lost. The customer should use an alternate credit card. |
| 42 | No Universal Account | Fail | The customer’s bank (Card Issuer) has declined the transaction as the account type selected is not valid for this credit card number. The customer should use an alternate credit card. |
| 43 | Stolen Card | Fail | The customer’s bank (Card Issuer) has declined the transaction as the card has been reported stolen. The customer should use an alternate credit card. |
| 44 | No Investment Account | Fail | The customer’s bank (Card Issuer) has declined the transaction as the account type selected is not valid for this credit card number. The customer should use an alternate credit card. |
| 51 | Insufficient Funds | Fail | The customer’s bank (Card Issuer) has declined the transaction as the credit card does not have sufficient funds. The customer should use an alternate credit card. |
| 52 | No Cheque Account | Fail | The customer’s bank (Card Issuer) has declined the transaction as the credit card number is associated to a cheque account that does not exist. The customer should use an alternate credit card. |
| 53 | No Savings Account | Fail | The customer’s bank (Card Issuer) has declined the transaction as the credit card number is associated to a savings account that does not exist. The customer should use an alternate credit card. |
| 54 | Expired Card | Fail | The customer’s bank (Card Issuer) has declined the transaction as the credit card appears to have expired. The customer should check the expiry date entered and try again, or use an alternate credit card. |
| 55 | Incorrect PIN | Fail | The customer’s bank (Card Issuer) has declined the transaction as the customer has entered an incorrect PIN. The customer should re-enter their PIN, otherwise use an alternate credit card. |
| 56 | No Card Record | Fail | The Customer’s bank has declined the transaction as the credit card number does not exist. The customer should use an alternate credit card. |
| 57 | Function Not Permitted to Cardholder | Fail | The Customer’s bank has declined the transaction as this credit card cannot be used for this type of transaction. The customer should use an alternate credit card. |
| 58 | Function Not Permitted to Terminal | Fail | The Customer’s bank has declined the transaction as this credit card cannot be used for this type of transaction. This may be associated with a test credit card number. The customer should use an alternate credit card. |
| 59 | Suspected Fraud | Fail | The customer’s bank has declined this transaction as the credit card appears to be fraudulent. |
| 60 | Acceptor Contact Acquirer | Fail | The customer’s bank (card issuer) has declined the transaction. The customer should contact their bank and retry the transaction. |
| 61 | Exceeds Withdrawal Limit | Fail | The customer’s bank has declined the transaction as it will exceed the customer’s card limit. The customer should use an alternate credit card. |
| 62 | Restricted Card | Fail | The customer’s bank has declined the transaction as the credit card has some restrictions. The customer should use an alternate credit card. |
| 63 | Security Violation | Fail | The customer’s bank has declined the transaction. The customer should use an alternate credit card. |
| 64 | Original Amount Incorrect | Fail | The customer’s bank has declined the transaction due to the amount attempting to be processed. The customer should check the transaction amount and try again. |
| 65 | Exceeds withdrawal | Fail | The customer’s bank has declined the transaction as the customer has exceeded the withdrawal frequency limit. The customer should use an alternate credit card. |
| 66 | Acceptor Contact Acquirer, Security | Fail | The customer’s bank has declined the transaction and request the Merchant to contact the bank. The customer should use an alternate credit card. |
| 67 | Capture Card | Fail | The customer’s bank has declined the transaction as the card is suspected to be counterfeit. The customer’s bank (Card Issuer) has requested that your customer’s credit card be retained. The customer should use an alternate credit card. |
| 75 | PIN Tries Exceeded | Fail | The customer’s bank has declined the transaction as the customer has entered the incorrect PIN more than three times. The customer should use an alternate credit card. |
| 82 | CVV Validation Error | Fail | The customer’s bank has declined the transaction as the CVV is incorrect. The customer should check the CVV details and try again. If not successful, the customer should use an alternate credit card. |
| 90 | Cut off In Progress | Fail | The customer’s bank is temporarily not able to process this customer’s credit card. The customer should attempt to process this transaction again. |
| 91 | Card Issuer Unavailable | Fail | The customer’s bank is unable to be contacted to authorise the transaction. The customer should attempt to process this transaction again. |
| 92 | Unable To Route Transaction | Fail | The customer’s bank cannot be found for routing. This response code is often returned when the customer is using a test credit card number. The customer should attempt to process this transaction again. |
| 93 | Cannot Complete, Violation Of The Law | Fail | The customer’s bank has declined the transaction and request the customer to contact their bank. The customer should use an alternate credit card. |
| 94 | Duplicate Transaction | Fail | The customer’s bank has declined the transaction as this transaction appears to be a duplicate transmission. No action required. |
| 96 | System Error | Fail | The customer’s bank was not able to process the transaction. The customer should attempt to process this transaction again. |
| 97 | Reconciliation Totals Reset | Fail | The reconciliation totals have been reset |
| 98 | MAC Error | Fail | |
| 99 | Reserved for National Use | Fail |
SecurePay Payment Server Response Codes
| Code | Response Text | Result | Description |
| 100 | Invalid Transaction Amount | Fail | If payment transaction amount is non-integer, negative, or zero |
| 101 | Invalid Card Number | Fail | If credit card number contains characters other digits, or bank does not recognize this number as a valid credit card number |
| 102 | Invalid Expiry Date Format | Fail | If expiry date does not follow the format MM/YY or contains an invalid date |
| 103 | Invalid Purchase Order | Fail | If purchase order is an empty string |
| 104 | Invalid Merchant ID | Fail | If Merchant ID does not follow the format XXXDDDD, where X is a letter and D is a digit, or Merchant ID is not found in SecurePay’s database. |
| 106 | Card type unsupported | Fail | Merchant is not configured to accept payment from this particular Credit Card type |
| 109 | Invalid credit card CVV number format | Fail | CVV Number contains character other than digits or contains more than 6 characters |
| 110 | Unable To Connect To Server | Fail | Produced by SecurePay Client API when unable to establish connection to SecurePay Payment Gateway |
| 111 | Server Connection Aborted During Transaction | Fail | Produced by SecurePay Client API when connection to SecurePay Payment Gateway is lost after the payment transaction has been sent |
| 112 | Transaction timed out By Client | Fail | Produced by SecurePay Client API when no response to payment transaction has been received from SecurePay Payment Gateway within predefined time period (default 80 seconds) |
| 113 | General Database Error | Fail | Payment Gateway was unable to read or write information to the database while processing the transaction |
| 114 | Error loading properties file | Fail | Payment Gateway encountered an error while loading configuration information for this transaction |
| 115 | Fatal Unknown Server Error | Fail | Transaction could not be processed by the Payment Gateway due to unknown reasons |
| 116 | Function unavailable through Bank | Fail | The bank doesn’t support the requested transaction type |
| 117 | Message Format Error | Fail | SecurePay Payment Gateway couldn’t correctly interpret the transaction message sent |
| 118 | Unable to Decrypt Message | Fail | SecurePay’s security methods were unable to decrypt the message |
| 119 | Unable to Encrypt Message | Fail | SecurePay’s security methods were unable to encrypt the message |
| 123 | Gateway Timeout | Fail | Produced by SecurePay Payment Gateway when no response to the transaction has been received from bank gateway within predefined time period |
| 124 | Gateway Connection Aborted During Transaction | Fail | Produced by SecurePay Payment Gateway when connection to bank gateway is lost after the payment transaction has been sent |
| 125 | Unknown Error Code | Fail | Produced by the bank gateway, textual description of the actual problem is stored in the database |
| 126 | Unable to Connect to Gateway | Fail | SecurePay Payment Gateway couldn’t establish a connection to Bank Gateway |
| 131 | Invalid Number Format | Fail | A sting entered cannot be parsed as an integer. I.e. string must contain only digits, or preceding ‘-‘ sign |
| 132 | Invalid Date Format | Fail | Date entered does not follow the format DD/MM/YYYY, where DD is the 2-digit day of the month, MM is the 2-digit month number, and YYYY is the 4-digit year number; also if month is < 1 or > 12, or date is < 0 or > maximum days in that month |
| 133 | Transaction for refund not in database | Fail | Refund operation requested, and the original approved transaction is not found in the database |
| 134 | Transaction already fully refunded / Only $x.xx available for refund | Fail | Refund operation is requested, and the given transaction has already been fully or partially refunded |
| 135 | Transaction for reversal not in database | Fail | Reversal operation requested, and the original approved transaction is not found in the database |
| 136 | Transaction already reversed | Fail | Reversal operation requested, and the given transaction has already been reversed |
| 137 | Pre-authorisation transaction not found in database | Fail | Complete operation requested, and the matching approved pre-auth transaction is not found in the database |
| 138 | Pre-authorisation already completed | Fail | Complete operation requested, and the given pre-auth has already been completed |
| 139 | No authorisation code supplied | Fail | Client performing Complete transaction did not provide Pre-auth Code from original pre-auth transaction |
| 140 | Partially refunded, undertake refund to complete | Fail | Reversal operation is requested, and the given transaction has already been partially refunded |
| 141 | No transaction ID supplied | Fail | Client performing Refund/Reversal transaction did not provide original payment’s Bank Transaction ID |
| 142 | Pre-auth was done for smaller amount | Fail | Complete operation was requested but the amount specified is greater the pre-authorised amount |
| 143 | Payment amount smaller than minimum | Fail | The payment amount was smaller than the minimum accepted by the merchant |
| 144 | Payment amount greater than maximum | Fail | The payment amount was greater than the maximum accepted by the merchant |
| 145 | System maintenance in progress | Fail | The system maintenance is in progress and the system is currently unable to process transactions |
| 146 | Duplicate Payment Found | Fail | The system located a transaction that seems to be a duplicate of the current attempt. Transaction is not passed to bank, and customer should contact their merchant before making payment. (Used in SecureBill / IVR only at present.) |
| 147 | No Valid MCC Found | Fail | The merchant does not have a valid MCC (Merchant Category Code) set up to complete this transaction (Refers to Recurring transactions only at present). |
| 148 | Invalid Track 2 Data | Fail | If track 2 data is invalid length. |
| 149 | Track 2 Data Not Supplied | Fail | Track 2 data was not supplied and the transaction cannot be completed (Refers to Card Present transactions only at present). |
| 151 | Invalid Currency Code | Fail | The currency code supplied does not match the format required by SecurePay. Check the list of accepted currency codes. |
| 152 | Multi-currency not supported by bank | Fail | The financial institution used for this payment only accepts payments in Australian dollars (AUD). |
| 153 | External Database Error | Fail | A database error has occurred outside the SecurePay Payment Server (e.g. DEFT, etc) |
| 157 | Fraud Check Passed | Fail | Fraud check successful. No suspected fraud. |
| 158 | Fraud Check Error | Fail | Cannot evaluate transaction for fraud. |
| 159 | Suspected Fraud | Fail | Transaction suspected to be fraudulent. |
| 160 | Cardholder could not be authenticated | Fail | Customer entered their Verified by Visa or MasterCard SecureCode password incorrectly, or an error occurred while authenticating the customer |
| 175 | No Action Taken | Fail | The payment was held in the processing queue too long and was rejected without processing. Usually a symptom of slow bank responses. Additional terminal IDs may help solve this problem if it occurs frequently. |
| 176 | Merchant Not Enrolled in 3D Secure | Fail | Please call SecurePay to be added to our 3D Secure service |
| 177 | Unable to connect to MPI for 3D Secure | Fail | An internal connectivity error occurred preventing 3D Secure authentication at this time |
| 178 | 3D Secure MPI Configuration Error | Fail | An internal configuration error occurred preventing 3D Secure authentication at this time |
| 179 | User Cancelled Payment | Fail | The user chose to exit the payment process before completion |
| 190 | Merchant Gateway Not Configured | Fail | The gateway for the merchant has been reserved, but not yet configured to be live by SecurePay staff. |
| 195 | Merchant Gateway Disabled | Fail | SecurePay has disabled the merchant gateway. |
| 199 | Merchant Gateway Discontinued | Fail | SecurePay has discontinued the merchant gateway. |
| 000 | Normal | Approved | Message processed correctly (check transaction response for details). |
| 504 | Invalid Merchant ID | Fail | If Merchant ID does not follow the format XXXDDDD, where X is a letter and D is a digit, or Merchant ID is not found in SecurePay’s database. |
| 505 | Invalid URL | Fail | The URL passed to either Echo, Query or Payment object is invalid. |
| 510 | Unable To Connect To Server | Fail | Produced by SecurePay Client API when unable to establish connection to SecurePay Payment Gateway |
| 511 | Server Connection Aborted During Transaction | Fail | Produced by SecurePay Client API when connection to SecurePay Payment Gateway is lost after the payment transaction has been sent |
| 512 | Transaction timed out By Client | Fail | Produced by SecurePay Client API when no response to payment transaction has been received from SecurePay Payment Gateway within predefined time period (default 80 seconds) |
| 513 | General Database Error | Fail | Unable to read information from the database. |
| 514 | Error loading properties file | Fail | Payment Gateway encountered an error while loading configuration information for this transaction |
| 515 | Fatal Unknown Error | Fail | Transaction could not be processed by the Payment Gateway due to unknown reasons |
| 516 | Request type unavailable | Fail | SecurePay system doesn’t support the requested transaction type |
| 517 | Message Format Error | Fail | SecurePay Payment Gateway couldn’t correctly interpret the transaction message sent |
| 524 | Response Format Error | Fail | The client could not understand the response message. |
| 545 | System maintenance in progress | Fail | The system maintenance is in progress and the system is currently unable to process transactions |
| 550 | Invalid password | Fail | The merchant has attempted to process a request with an invalid password. |
| 575 | Not implemented | Fail | This functionality has not yet been implemented |
| 577 | Too Many Records for Processing | Fail | The maximum number of allowed events in a single message has been exceeded. |
| 580 | Process method has not been called | Fail | The process() method on either Echo, Payment or Query object has not been called |
| 594 | Duplicate Transmission | Fail | A transaction with the same details has already been processed. |
| 595 | Merchant Disabled | Fail | SecurePay has disabled the merchant and the requests from this merchant will not be processed. |
SecurePay Direct Entry Response Codes
| Code | Response Text | Result | Description |
| 00 | Transaction Received | Approved | The transaction was received and will be sent off for processing at the end of the day. |
| 200 | Invalid Transaction Amount | Fail | |
| 201 | No DDA Found | Fail | |
| 203 | Invalid Reference Number | Fail | |
| 204 | Invalid Merchant ID | Fail | If Merchant ID does not follow the format XXXDDDD, where X is a letter and D is a digit; or if Merchant ID is not found in the merchant database. |
| 205 | DDA Expired | Fail | |
| 213 | General Database Error | Fail | Direct Debit Server was unable to read or write information to the database while processing the transaction |
| 217 | Message Format Error | Fail | Direct Debit Server received a message with invalid data. |
| 225 | Transaction Rejected (Unknown response) | Fail | |
| 228 | No DDA With Merchant | Fail | DDA is inactive. |
| 243 | Amount Lower Than Minimum | Fail | The payment amount was lower than the minimum accepted. |
| 244 | Amount Higher Than Maximum | Fail | The payment amount was higher than the maximum accepted. |
| 246 | Duplicate Payment Found | Fail | The system located a transaction that seems to be a duplicate of the current attempt. Transaction is not passed to bank, and customer should contact their merchant before making payment. (Used in SecureBill / IVR only at present.) |
| 249 | Invalid Payor ID | Fail |
SecurePay Periodic Server Response Codes
| Code | Response Text | Result | Description |
| 300 | Invalid Amount | Fail | If payment transaction amount is non-integer, negative, or zero. (May be zero (0) for “trigger” actions, when default amount will be used.) |
| 301 | Invalid Credit Card Number | Fail | Credit card number is not supplied, wrong length, or does not pass Luhn algorithm. |
| 302 | Invalid Expiry Date | Fail | Expiry date does not follow format MM/YY, where MM is the 2-digit month (01-12) and YY is the 2-digit year. |
| 303 | Invalid Periodic Client ID | Fail | Client ID not provided, longer than 20 characters, or contains spaces. |
| 304 | Invalid Merchant ID | Fail | Merchant ID does not follow format XXXDDDD for credit card payments, or XXXDD for direct entry, where X is a letter and D is a digit; or merchant ID not in database. |
| 305 | Invalid BSB Number | Fail | BSB does not follow format DDDDDD, or DDD-DDD, where D is a digit. |
| 306 | Invalid Account Number | Fail | Account number not provided, greater than 9 digits, or contains non-digit characters. |
| 307 | Invalid Account Name | Fail | Account Name is mandatory for DE Credit payments, and optional for DE Debits. Must be less than 32 characters if supplied. |
| 308 | No Matching DDA Found | Fail | A periodic DE Debit payment must match an existing DDA stored in our database for the merchant. DDAs can be added via the Merchant Login. DDA expiry date must be after the final periodic payment date. |
| 309 | Invalid CVV Number | Fail | CVV is optional for credit card payments, but if provided, must be either 3 or 4 digits. |
| 313 | General Database Error | Fail | A database error occurred while processing your request. Retry, or contact SecurePay. |
| 314 | Unable to Read Properties File | Fail | A properties file was not found or could not be read. Retry, or contact SecurePay. |
| 316 | Invalid Action Type Requested | Fail | The server does not support the action type requested. Check user manual for allowed values. |
| 318 | Unable to Decrypt Account Details | Fail | The card number or account details could not be decrypted. Retry, or contact SecurePay. |
| 327 | Invalid Periodic Payment Type | Fail | The Periodic type requested is not supported. Check user manual for allowed values. |
| 328 | Invalid Periodic Frequency | Fail | The Periodic frequency requested is not valid. Check user manual for allowed values. |
| 329 | Invalid Number of Payments | Fail | Number of payments must be 1 or more for day-based and calendar-based payments. |
| 332 | Invalid Date Format | Fail | A supplied date does not follow format YYYYMMDD, where values conform to standard calendar rules; or the server could not correctly interpret a date. |
| 333 | Triggered Payment Not Found | Fail | Triggered payment Client ID requested does not match a stored triggered payment for the merchant. |
| 346 | Duplicate Client ID Found | Fail | Client ID being added is not unique for the merchant. |
Bank Gateway Response Codes
| Code | Response Text | Result |
| 900 | Invalid Transaction Amount | Fail |
| 901 | Invalid Credit Card Number | Fail |
| 902 | Invalid Expiry Date Format | Fail |
| 903 | Invalid Transaction Number | Fail |
| 904 | Invalid Merchant/Terminal ID | Fail |
| 905 | Invalid E-Mail Address | Fail |
| 906 | Card Unsupported | Fail |
| 907 | Card Expired | Fail |
| 908 | Insufficient Funds | Fail |
| 909 | Credit Card Details Unknown | Fail |
| 910 | Unable to Connect to Bank | Fail |
| 913 | Unable to Update Database | Fail |
| 914 | Power Failure | Fail |
| 915 | Fatal Unknown Gateway Error | Fail |
| 916 | Invalid Transaction Type Requested | Fail |
| 917 | Invalid Message Format | Fail |
| 918 | Encryption Error | Fail |
| 919 | Decryption Error | Fail |
| 922 | Bank is Overloaded | Fail |
| 923 | Bank Timed Out | Fail |
| 924 | Transport Error | Fail |
| 925 | Unknown Bank Response Code | Fail |
| 926 | Gateway Busy | Fail |
| 928 | Invalid Customer ID | Fail |
| 932 | Invalid Transaction Date | Fail |
| 933 | Transaction Not Found | Fail |
| 936 | Transaction Already Reversed | Fail |
| 937 | Transaction Cannot Be Authorised | Fail |
| 938 | Pre-auth Already Completed | Fail |
| 939 | Invalid Auth Code | Fail |
| 941 | Invalid Transaction ID Supplied | Fail |
| 946 | Reference Number Currently In Use | Fail |
| 951 | Transaction Not Permitted To Terminal | Fail |
| 958 | Fraud Check Error | Fail |
| 960 | Contact Card Issuer | Fail |
| 961 | Transaction Pending | Fail |
| 962 | Transaction Voided | Fail |
| 970 | File Access Error | Fail |
| 971 | Invalid Flag Set | Fail |
| 972 | Pin-pad/Gateway Offline | Fail |
| 973 | Invoice Unavailable | Fail |
| 974 | Gateway Configuration Error | Fail |
| 975 | No Action Taken | Fail |
| 976 | Unknown Currency Code | Fail |
| 977 | Too Many Records for Processing | Fail |
| 978 | Merchant Blocked | Fail |