Response Codes

Response codes are numerical codes (up to 3 digits) that indicate transaction outcomes. Use this guide to understand and handle different response codes in your integration.

Code Sample Disclaimer

Code samples within this document are provided for reference purposes only and are not intended for production use.

Overview

Response codes help identify why a transaction was approved, declined, or failed. They come from two sources:

• Bank Response Codes: Returned by the card issuer or acquiring bank
• Platform Response Codes: Generated by the Connected Payments platform

Bank Response Codes

Returned by the card issuer or acquiring bank to indicate why a transaction was approved or declined.

Bank Code Reference

View full bank code reference table (00–73)

CODE	RESPONSE TEXT	PROPOSED ACTION
00	Approved	Approve request.
01	Refer to Card Issuer	Contact cardholder – refer to bank
02	Refer to Issuer Special Conditions	Contact cardholder – refer to bank
03	Invalid Merchant	Contact CommBank Support
04	Pick Up Card	Contact cardholder – refer to bank
05	Do Not Honour	Review transaction request for errors. If error persists contact cardholder – refer to bank
06	Error	Retry transaction
08	Honour with ID	Approve request.
09	Request in Progress	Contact CommBank Support
10	Partial Amount Approved	Approve request.
11	Approved	Approve request.
12	Invalid Transaction	Review transaction request for errors.
13	Invalid Amount	Review transaction request for errors.
14	Invalid Card Number	Review transaction request for errors.
15	No Such Issuer	Review transaction request for errors. If error persists contact CommBank support.
16	Approved	Approve request.
17	Customer Cancellation	Contact Cardholder.
18	Customer Dispute	Contact Cardholder.
19	Re-enter Transaction	Retry transaction
21	No Action Taken	Retry transaction
22	Suspected Malfunction	Retry transaction
23	Unacceptable Transaction Fee	Review transaction request for errors. If error persists contact CommBank support.
24	File Update not Supported by Receiver	Retry transaction. If error persists contact CommBank support.
25	Unable to Locate Record on File	Retry transaction. If error persists contact CommBank support.
26	Duplicate File Update Record	Retry transaction. If error persists contact CommBank support.
27	File Update Field Edit Error	Retry transaction. If error persists contact CommBank support.
28	File Update File Locked Out	Retry transaction. If error persists contact CommBank support.
29	File Update not Successful	Retry transaction. If error persists contact CommBank support
31	Bank not Supported by Switch	Retry transaction. If error persists contact CommBank support.
32	Completed Partially	Approve request.
33	Expired Card-Pick Up	Contact cardholder – refer to bank
34	Suspected Fraud-Pick Up	Contact cardholder – refer to bank
35	Contact Acquirer-Pick Up	Contact cardholder – refer to bank
36	Restricted Card-Pick Up	Contact cardholder – refer to bank
37	Call Acquirer Security-Pick Up	Contact cardholder – refer to bank
38	Allowable PIN Tries Exceeded	Contact cardholder – refer to bank
39	No CREDIT Account	Retry transaction. If error persists contact cardholder
40	Requested Function not Supported	Retry transaction. If error persists contact CommBank support
42	No Universal Amount	Retry transaction. If error persists contact CommBank support
43	Stolen Card-Pick Up	Contact cardholder – refer to bank
44	No Investment Account	Retry transaction. If error persists contact CommBank support
45–50	Not in use - RESERVED	—
51	Insufficient Funds	Retry transaction. If error persists contact cardholder
52	No Cheque Account	Retry transaction. If error persists contact cardholder
53	No Savings Account	Retry transaction. If error persists contact cardholder
54	Expired Card	Contact cardholder – request updated card details
55	Incorrect PIN	Contact cardholder – request updated card details
56	No Card Record	Contact cardholder – request updated card details
57	Trans. Not Permitted to Cardholder	Retry transaction. If error persists contact cardholder
58	Transaction not Permitted to Terminal	Retry transaction. If error persists contact CommBank support.
59	Suspected Fraud	Contact Cardholder – suspected fraud
60	Card Acceptor Contact Acquirer	Contact Merchant acquirer
61	Exceeds Withdrawal Amount Limits	Retry transaction. If error persists contact cardholder
62	Restricted Card	Retry transaction. If error persists contact cardholder
64	Original Amount Incorrect	Review transaction request for errors.
65	Exceeds Withdrawal Frequency Limit	Retry transaction. If error persists contact cardholder
66	Card Acceptor Call Acquirer Security	Contact Merchant acquirer
67	Hard Capture-Pick Up Card at ATM	Contact cardholder – refer to bank
68	Response Received Too Late	Retry transaction. If error persists contact CommBank support
69–73	Not in use - RESERVED	—

Platform Response Codes

Generated by the Connected Payments platform for API request issues, authentication errors, or configuration problems.

Platform Code Reference

View full platform code reference table (700–799)

Code	Response Text	Example / Detailed Description
700	The associated transaction is pending approval. For more information please see the downstream response or contact support.	This is used when a transaction is pending approval.
701	The linked transaction attempt failed as the associated transaction could not be found.	An associated transaction cannot be found based on the details used/provided. IE incorrect transaction ID provided for a refund
702	The associated transaction has already been completed and as such cannot take place again.	Refund, void, or capture has already been completed
703	The associated transaction status is not as expected for the request function.	Attempting a refund on a declined transaction
704	The settlement date for the referenced transaction has passed.	The settlement date for a transaction has passed. This applies to voids and completes.
705	The target transaction details were unable to be found.	Downstream query failed and the attempted linked transaction could not take place - includes cases where the provided target transaction was unable to be found on the users account
706	The amount provided is invalid.	IE: Alpha characters are included in the amount field
707	Card holder details provided are invalid. Please check the expiry date, pan and any other associated details and try again.	IE: Incorrect CVV provided
708	The downstream service returned a configuration error which could not be resolved. Please refer to the downstream response or contact Support for more information.	The downstream service provided back an error relating to the misconfiguration of the service. This includes tokenisation configuration, floor limits etc.
709	Fraud rejection	The downstream fraud service declined the transaction
710	The transaction attempted was invalid. If this was a linked transaction (refund, void, capture) please ensure that the function has not already been completed.	Downstream linked transaction failure.
711	The disbursement transaction was attempted but was dishonoured or failed.	This is a catch all for disbursement failures.
712	The downstream credentials returned an authentication failure. Please contact support.	The downstream credentials are incorrect/invalid - includes usernames, passwords, certificates, mids or otherwise.
713	The transaction request is invalid and cannot be processed.	The transaction request is missing vital information and as such cannot be processed
714	Direct Entry Response.	This is a catch all place holder for DE
715	Charge Back.	This is a catch all place holder for charge backs
716	All transaction requests should use a unique merchant reference value.	Merchant reference provided is not unique.
717	Authentication credential verification failed.	Username, Password or other authentication failed. IE – Incorrect username provided
718	Permission denied.	IE – Refund request with an API user only has permission to perform payment transactions.
719	Field [fieldname] is required	Agent & IVRSecure API requests - indicates the missing field(s). IE startCapture request does not include
720	Field [fieldname] is invalid	For any Agent & IVRSecure API requests this indicates a field is not formatted properly. IE captureId is longer than the permitted length
721	Provided [fieldname] not found	For any Agent & IVRSecure API requests this indicates the provided correlationId or captureId cannot be found.
722	Card token does not exist.	Card token does not exist. Please double check the card token and try again.
723–788	Not in use - RESERVED	—
789	Client connection error	An error occurred with the clients connection. The transaction will be voided. Please try again.
790	Batch service error	Transaction service error
791–793	Not in use - RESERVED	—
794	Downstream fraud system failure.	The downstream fraud service returned a system error. This may be due to lack of information or an internal error.
795	Gateway Unavailable - The payment's processing path is not supported by your companies approved setup.	Confirm the transaction's payment path has been approved by your companies setup. If this is the case and the response code persists please contact [email protected] for further assistance
796	An unknown error occurred, please contact support for more information and reference error ID [unique id].	For Agent & IVRSecure API related unknown errors an error ID will be assigned to assist with troubleshooting
797	The downstream banking network is unavailable.	The downstream gateway's acquirer is unavailable – retry transaction if problems persist contact support
798	An unknown downstream error occurred. For more information please contact support.	Downstream error where the direct cause is unknown - retry transaction if problems persist contact support
799	An unknown error occurred. For more information please contact support.	Catch all for any unmapped or unintelligible responses from downstream services - retry transaction if problems persist contact support

How to use response codes

In API responses

All API responses include a responseCode field:

{
  "responseCode": "00",
  "message": "Success",
  "requestId": "b2bbc032-11"
}

Response code categories

Response codes can be categorized by their first digit:

• 0X: Approved or successful transactions
• 1X: Refer to issuer or retry
• 2X: Retry or system issues
• 3X: Card issues (expired, restricted, pick up)
• 4X: Declined - configuration or account issues
• 5X: Declined - insufficient funds or card issues
• 6X: Declined - security or limit issues

Handling Response Codes

Code Type	Codes	Action
Success	00, 08, 10, 11, 16, 32	Approve and fulfill order
Retry	06, 19, 21, 22, 24-29, 31, 40, 68	Retry with exponential backoff
Customer Action	51, 54, 55, 56, 57, 61, 65	Request customer to update card or contact bank
Fraud/Security	34, 43, 59	Flag for review - do not retry

Example implementation:

const SUCCESS_CODES = ["00", "08", "10", "11", "16", "32"];
const RETRY_CODES = [
  "06",
  "19",
  "21",
  "22",
  "24",
  "25",
  "26",
  "27",
  "28",
  "29",
  "31",
  "40",
  "68",
];
const CUSTOMER_ACTION_CODES = ["51", "54", "55", "56", "57", "61", "65"];
const FRAUD_CODES = ["34", "43", "59"];

if (SUCCESS_CODES.includes(responseCode)) {
  fulfillOrder();
} else if (RETRY_CODES.includes(responseCode)) {
  retryWithBackoff();
} else if (CUSTOMER_ACTION_CODES.includes(responseCode)) {
  showCustomerActionRequired(responseCode, message);
} else if (FRAUD_CODES.includes(responseCode)) {
  flagForFraudReview();
}

Testing

Use test cards to simulate different response codes in the sandbox environment. See Testing Guide for details.

Troubleshooting

For general API troubleshooting including authentication errors and rate limiting, see the Troubleshooting Guide in the FAQ & Support section. For reconciliation issues related to response codes 91, 99, 790, and 799, see Reconciliation issues.