Response Codes
Approval Codes
|
00 Approved |
||
|
08 Approved |
|
|
Decline Codes
|
01 Refer to Card Issuer |
Account may be overdrawn or frozen |
Contact cardholder |
|
02 Refer to Issuer’s Special Conditions |
Not generally used for CNP transactions |
Contact cardholder to confirm details |
|
03 Invalid Merchant |
Possible problem in Bank systems |
Retry transaction or contact Bank |
|
04 Pick Up Card |
Account may be frozen due to fraud reported on card or other security reason |
Contact cardholder to confirm details
|
|
05 Do Not Honour |
Account may be overdrawn or frozen |
Contact cardholder to confirm details |
|
06 Error |
Possible transfer problem in network |
Check transaction data and try again |
|
07 Pick Up Card, Special Conditions |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
12 Invalid Transaction |
Possible error in card issuer system |
Check transaction data and try again |
|
13 Invalid Amount |
Generally not used for CNP transactions |
Check transaction data and try again |
|
14 Invalid Card Number |
Card number may be incorrect |
Check transaction data and try again |
|
15 No Such Issuer |
Card number may be incorrect |
Check transaction data and try again |
|
17 Customer Cancellation |
Generally not used for CNP transactions |
Contact cardholder to confirm details |
|
18 Customer Dispute |
Generally not used for CNP transactions |
Contact cardholder to confirm details |
|
19 Re-enter Transaction |
Generally not used for CNP transactions |
Check transaction data and try again |
|
20 Invalid Response |
Generally not used for CNP transactions |
Check transaction data and try again |
|
21 No Action Taken |
Possible transfer problem in network |
Check transaction data and try again |
|
22 Suspected Malfunction |
Generally not used for CNP transactions |
Check transaction data and try again |
|
24 File Update not Supported by Receiver |
Generally not used for CNP transactions |
Retry transaction or contact Bank |
|
25 Unable to Locate Record on File |
Generally not used for CNP transactions |
Check transaction data and try again |
|
26 Duplicate File Update Record |
Generally not used for CNP transactions |
Check transaction data and try again |
|
27 File Update Field Edit Error |
Generally not used for CNP transactions |
Check transaction data and try again |
|
28 File Update File Locked Out |
Generally not used for CNP transactions |
Check transaction data and try again |
|
29 File Update not Successful |
Generally not used for CNP transactions |
Check transaction data and try again |
|
30 Format Error |
Possible transfer problem in network |
Check transaction data and try again |
|
31 Bank not Supported by Switch |
Possible transfer problem in network |
Retry transaction or contact Bank |
|
33 Expired Card—Pick Up |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
34 Suspected Fraud—Pick Up |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
35 Contact Acquirer—Pick Up |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
36 Restricted Card—Pick Up |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
37 Call Acquirer Security—Pick Up |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
39 No CREDIT Account |
Card may be invalid or account closed |
Retry transaction or contact Bank |
|
43 Stolen Card—Pick Up |
“Pick up” response used generically |
Contact cardholder to confirm details |
|
44 No Investment Account |
Generally for EFTPOS only |
Retry transaction or contact Bank |
|
51 Insufficient Funds |
Account may be overdrawn |
Contact cardholder or retry next day |
|
54 Expired Card |
Card may have been replaced – this can occur even for recurring transactions if a new card number has been issued |
Contact cardholder to confirm details
|
|
56 No Card Record |
Account may be closed or card invalid |
Contact cardholder to confirm details |
|
57 Trans. not Permitted to Cardholder |
Card issuer systems have deemed the transaction to be an unacceptable risk |
Contact cardholder to confirm details
|
|
58 Transaction not Permitted to Terminal |
Card issuer systems have deemed the transaction to be an unacceptable risk |
Do not retry – contact Bank
|
|
59 Suspected Fraud |
Card issuer systems have deemed the transaction to be an unacceptable risk |
Contact cardholder to confirm details
|
|
60 Card Acceptor |
Contact Acquirer Card issuer systems have deemed the transaction to be an unacceptable risk |
Do not retry – contact Bank
|
|
62 Restricted Card |
Account may be ‘frozen’ due to fraud reported on card or other security reason |
Contact cardholder to confirm details
|
|
63 Security Violation |
Account may be ‘frozen’ due to fraud reported on card or other security reason |
Do not retry – contact Bank |
|
64 Original Amount Incorrect |
Generally not used for CNP transactions |
Check transaction data and try again |
|
66 Card Acceptor Call Acquirer Security |
Account may be ‘frozen’ due to fraud reported on card or other security reason |
Do not retry – contact Bank |
|
68 Response Received Too Late |
Possible transfer problem in network |
Retry transaction
|
|
91 Issuer or Switch is Inoperative |
Possible transfer problem in network |
Retry transaction or contact Bank |
|
92 Financial Institution not Found |
Possible transfer problem in network |
Retry transaction or contact Bank |
|
93 Trans Cannot be Completed |
Possible transfer problem in network |
Retry transaction or contact Bank |
|
96 System Malfunction |
Possible problem in Bank systems |
Retry transaction
|
|
100 Invalid Transaction Amount |
If payment transaction amount is non-integer, negative, or zero |
Correct the transaction amount & retry |
|
101 Invalid Card Number |
If credit card number contains characters other digits, or bank does not recognize this number as a valid credit card number |
Correct the card number & retry |
|
102 Invalid Expiry Date Format |
If expiry date does not follow the format MM/YY or contains an invalid date |
Correct the expiry date & retry
|
|
103 Invalid Purchase Order |
If purchase order is an empty string |
Correct the Transaction Reference & retry |
|
104 Invalid Merchant ID |
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 Bank’s database. |
Correct the Merchant ID/Client ID & retry
|
|
106 Card type unsupported |
Merchant is not configured to accept payment from this particular Credit Card type |
Check that you are enabled for this particular card type (e.g. Amex, Diners) – contact Bank |
|
109 Invalid credit card CVV number format
|
CVV Number contains character other than digits or contains more than 6 characters |
Correct the CVV & retry |
|
110 Unable To Connect To Server |
Produced by Bank Client API when unable to establish connection to Bank Payment Gateway |
Retry transaction or contact Bank
|
|
111 Server Connection Aborted During Transaction
|
Produced by Bank Client API when connection to Bank Payment Gateway is lost after the payment transaction has been sent |
Retry transaction or contact Bank
|
|
112 Transaction timed out By Client |
Produced by Bank Client API when no response to payment transaction has been received from Bank Payment Gateway within predefined time period (default 80 seconds) |
Retry transaction or contact Bank
|
|
113 General Database Error |
Payment Gateway was unable to read or write information to the database while processing the transaction |
Retry transaction or contact Bank
|
|
114 Error loading properties file |
Payment Gateway encountered an error while loading configuration information for this transaction |
Retry transaction or contact Bank
|
|
115 Fatal Unknown Server Error |
Transaction could not be processed by the Payment Gateway due to unknown reasons |
Retry transaction or contact Bank
|
|
116 Function unavailable through Bank |
The bank doesn’t support the requested transaction type |
Retry transaction or contact Bank
|
|
117 Message Format Error |
Bank Payment Gateway couldn’t correctly interpret the transaction message sent |
Retry transaction or contact Bank
|
|
118 Unable to Decrypt Message |
Bank’s security methods were unable to decrypt the message |
Retry transaction or contact Bank
|
|
119 Unable to Encrypt Message |
Bank’s security methods were unable to encrypt the message |
Retry transaction or contact Bank |
|
123 Gateway Timeout |
Produced by Bank Payment Gateway when no response to the transaction has been received from bank gateway within predefined time period |
Contact Bank – do not retry transaction
|
|
124 Gateway Connection Aborted During Transaction |
Produced by Bank Payment Gateway when connection to bank gateway is lost after the payment transaction has been sent |
Contact Bank – do not retry transaction
|
|
125 Unknown Error Code |
Produced by the bank gateway, textual description of the actual problem is stored in the database |
Contact Bank – do not retry transaction
|
|
126 Unable to Connect to Gateway |
Bank Payment Gateway couldnt establish a connection to Bank Gateway |
Contact Bank – do not retry transaction
|
|
131 Invalid Number Format |
A sting entered cannot be parsed as an integer. I.e. string must contain only digits, or preceding ‘ -‘ sign Correct the integer string and retry 132 Invalid Date Format 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 |
Correct the date & retry
|
|
133 Transaction for refund not in database |
Refund operation requested, and the original approved transaction is not found in the database |
Correct the Transaction Reference and/or Bank Transaction ID and retry
|
|
134 Transaction already fully refunded/ Only $x.xx available for refund
|
Refund operation is requested, and the given transaction has already been fully or partially refunded |
The transaction cannot be processed |
|
135 Transaction for reversal not in database
|
Reversal operation requested, and the original approved transaction is not found in the database |
The transaction cannot be processed
|
|
136 Transaction already reversed |
Reversal operation requested, and the given transaction has already been reversed |
The transaction cannot be processed
|
|
137 Pre-auth transaction not found in database
|
Complete operation requested, and the matching approved pre-auth transaction is not found in the database |
Correct the Transaction Reference and/or Pre-auth code and retry
|
|
138 Pre-auth already completed |
Complete operation requested, and the given pre-auth has already been completed |
The transaction cannot be processed |
|
139 No authorisation code supplied |
Client performing Complete transaction did not provide Pre- auth Code from original pre-auth transaction |
Correct the Pre-auth code and retry
|
|
140 Partially refunded, Do refund to complete
|
Reversal operation is requested, and the given transaction has already been partially refunded |
|
|
141 No transaction ID supplied |
Client performing refund/Reversal transaction did not provide original Bank Transaction ID |
Correct the Bank Transaction ID and retry
|
|
142 Pre-auth was done for smaller amount
|
Complete operation was requested but the amount specified is greater the pre-authorised amount |
Correct the amount & retry
|
|
143 Payment amount smaller than minimum
|
The payment amount was smaller than the minimum accepted by the merchant
|
Correct the amount & retry or contact Bank to change minimum payment amount |
|
144 Payment amount greater than maximum |
The payment amount was greater than the maximum accepted by the merchant |
Correct the amount & retry or contact Bank to change minimum payment amount |
|
145 System maintenance in progress |
The system maintenance is in progress and the system is currently unable to process transactions |
|
|
146 Duplicate Payment Found |
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 |
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 |
If track 2 Data is invalid length |
|
|
149 Track 2 Data Not Supplied |
Track 2 Data was not supplied and the transaction cannot be complete (Refers to Card Present transactions only at present). |
|
|
151 Invalid Currency Code |
The Currency Code supplied does not match the format required by BankTransact. Check the list of accepted currency codes. |
|
|
152 Multi-currency not supported by bank |
The financial institution used for this payment only accepts payments in Australian dollars (AUD). |
Contact Bank if you believe your facility should support non-AUD processing
|
|
153 External Database Error |
A database error has occurred outside the Bank Transact Payment Server |
Contact Bank – do not retry
|
|
157 Fraud Check Passed |
Fraud check successful. No suspected fraud. |
|
|
158 Fraud Check Error |
Cannot evaluate transaction for fraud. |
|
|
159 Suspected Fraud |
Transaction suspected to be fraudulent |
|
|
160 Cardholder could not be authenticated
|
Customer entered their Verified by Visa or MasterCard SecureCode password incorrectly, or an error occurred while authenticating the customer. |
|
|
175 No Action Taken |
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. |
Contact Bank – do not retry
|
|
176 Merchant Not Enrolled in 3D Secure |
Please call BankTransact to be added to our 3D Secure service. |
|
|
177 Unable to connect to MPI for 3D Secure |
An internal connectivity error occurred preventing 3D Secure authentication at this time. |
|
|
178 3D Secure MPI Configuration Error |
An internal connectivity error occurred preventing 3D Secure authentication at this time. |
|
|
179 User Cancelled Payment
|
The user chose to exit the payment process before completion. |
|
|
190 Merchant Gateway Not Configured |
The gateway for the merchant has been reserved, but not yet configured to be live by Bank staff. |
Contact Bank
|
|
195 Merchant Gateway Disabled |
Bank has disabled the merchant gateway. |
Contact Bank
|
|
199 Merchant Gateway Discontinued |
Bank has discontinued the merchant gateway. |
Contact Bank
|
|
504 Invalid Merchant ID |
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 Bank database. |
Check transaction data and try again
|
|
505 Invalid URL |
The URL passed to either the Echo, Query, or Payment object is invalid. |
Check transaction data and try again
|
|
510 Unable To Connect To Gateway |
Produced by the Bank Client API when unable to establish connection to the Bank Payment Gateway |
Retry transaction. Contact Bank if still not working.
|
|
511 Gateway Connection Aborted During Transaction |
Produced by the Bank Client API when connection to the Bank Payment Gateway is lost after the payment transaction has been sent |
Retry transaction. Contact Bank if still not working.
|
|
512 Transaction timed out by the Client API |
Produced by the Bank Client API when no response to the payment transaction has been received from the Bank Payment Gateway within the predefined time period (default 80 seconds) |
Retry transaction. Contact Bank if still not working.
|
|
513 General Database Error |
Unable to read information from the database. Retry transaction. |
Contact Bank if still not working. |
|
514 Error loading properties |
The Payment Gateway encountered an error while loading configuration information for this transaction |
Check transaction data and try again
|
|
515 Fatal Unknown Error |
Transaction could not be processed by the Payment Gateway due to unknown reasons |
Check transaction data and try again
|
|
516 Request type unavailable |
The Bank Payment Gateway does not support the requested transaction type |
Check transaction data and try again. Contact Bank if still not working. |
|
517 Message Format Error |
The Bank Payment Gateway could not correctly interpret the transaction message sent |
Retry transaction. Contact Bank if still not working. |
|
524 Response not received |
The client could not receive a response from the Payment Gateway |
Retry transaction. Contact Bank if still not working. |
|
545 System maintenance in progress |
The system maintenance is in progress and the system is currently unavailable and unable to process transactions |
Retry transaction. Contact Bank if still not working.
|
|
550 Invalid password |
The Client API has attempted to process a request with an invalid password. |
Check transaction data and try again
|
|
575 Not implemented |
This functionality has not yet been implemented |
Check transaction data and try again |
|
577 Too Many Records for Processing |
The maximum number of allowed events in a single message has been exceeded. |
Check transaction data and try again
|
|
580 Process method has not been called |
The process method on either the Echo, Payment or Query object has not been called |
Check transaction data and try again
|
|
594 Duplicate Transmission |
A transaction with the same details has already been processed. |
|
|
595 Merchant Disabled |
Bank has disabled the merchant and the requests from this merchant will not be processed. |
Contact Bank
|
Issuer Decline Codes and Text Comments Action
Response Code and Text Description Action
0 Comments