Error codes for card-present transactions

October 14, 2024

Here are the common errors in card-present transactions and how to resolve them

HTTP Status codes

Below, we present the most common HTTP status codes, their associated standard messages, and a description of the response.

Here are the codes you might receive.

Code	Message	Detail
200	OK	The process was successful; it worked as expected, according to the HTTP method.
400	Bad Request	The server cannot interpret the request (incorrect syntax, too large size, missing parameters).
401	Authorization Required	The credentials must be authenticated, or authentication failed.
403	Forbidden	You do not have the necessary permissions to perform this action.
404	Not Found	Resource or page not found.
409	Conflict	The request cannot be processed due to a conflict with the resource (e.g., multiple simultaneous updates).
410	Gone	The requested resource has been deleted from the server and will no longer be available.
412	Precondition failed	It indicates that access to the target resource has been denied.
429	Too Many Requests	Too many requests have been sent in a short period of time.
430	Request Header Fields Too Large	This status code indicates that the server is unwilling to process the request because its header fields are too large.
500	Internal Server Error	An unexpected error occurred on the server.
502	Bad Gateway	The server (acting as a proxy or gateway) received an invalid response from the upstream server.
503	Service Temporarily Unavailable	The server is not available (usually because it is undergoing maintenance or because it is overloaded).
504	Gateway Timeout	The server (acting as a proxy or gateway) did not receive a timely response from the other server.

Codes returned by Kushki in card-present transactions

The response codes received from processors and issuers will appear in thekushki_response object, as shown in the following example.

“kushki_response": {
        "code": "01",
        "message": "Refer to card issuer"
    },

Below is the information about the codes and messages sent by Kushki to describe the response codes of the request made with card-present transactions. In the “What to do?” column, you will find a detailed explanation of the causes and the procedure you should follow.

Code	Message	What to do?
000	Approved or completed successfully	Indicates that the transaction was successfully approved.
01	Refer to card issuer \	The cardholder should contact their card issuer to understand why the transaction was declined.
04	Capture card	The cardholder should use a different card to process the transaction and contact their card issuer for further review.
05	Do not honor	The cardholder should retry the transaction.
06	Error	The cardholder needs to call the issuing bank to clarify the issue (and increase their credit if the issue is the credit limit).
09	Request in process (duplicate)	The transaction is not allowed by the payment processor or the card issuer. The cardholder should use an alternative card.
10	Approved partial	The cardholder should use an alternative card from a different issuer.
12	Invalid transaction	The cardholder has requested to cancel the transaction.
15	The issuer cannot authorize this transaction	The cardholder should use another card.
17	No such issuer	At the time of the transaction, a format error occurred.
1A	Additional customer authentication required	The cardholder should use a different card to process the transaction and contact their card issuer to review the case.
32	Expired card	The cardholder should use a different card to process the transaction and contact their card issuer to review the case.
34	Suspected fraud	The cardholder should use a different card to process the transaction and contact their card issuer to review the case.
35	Card acceptor contact acquirer	The cardholder should use a different card to process the transaction and contact their card issuer to review the case.
37	Card acceptor call acquirer security	Should use another card.
39	No credit account	The cardholder should use a different card to process the transaction and contact their card issuer to review the case
41	Lost card	The cardholder should contact their card issuer to understand why the transaction was declined.
51	Not sufficient funds	The cardholder should use another card.
54	Expired card	The cardholder should use another card.
57	Transaction not permitted to cardholder	The cardholder should use a different card to process the transaction and contact their card issuer to review the case.
59	Suspected fraud	The issuer requested a PIN change, but it was not completed successfully.
61	Exceeds withdrawal amount limit	The cardholder should use another card.
62	Restricted card	The cardholder should try again or use an alternative card.
6P	Verification data failed	The cardholder should try again or use an alternative card from a different issuer.
75	Allowable number of PIN tries exceeded	Please contact the issuer for further information.
78	Invalid/nonexistent account specified (general)	The transaction was rejected because a match was found with another previous transaction.
80	No financial impact	The cardholder should try again or use an alternative card from a different issuer.
81	Cryptographic error found in PIN There was a cryptographic error in the PIN (used for the cryptographic error condition found by the security module during PIN decryption).	The cardholder should use an alternative card.
86	Cannot verify PIN; for instance, no PVV	A message from Visa requesting additional authentication from the cardholder.
89	Unacceptable PIN— Transaction Declined— Retry	Retry the transaction.
91	Authorization System or issuer system inoperative	Retry the transaction or use a different card.
92	Unable to route transaction
93	Transaction cannot be completed- violation of law.
U1	Security module parameter error.

Response codes returned by Kushki for cancellations and reversal attempts

The response codes received from processors and issuers will appear in the kushki_response object, as shown in the following example.

"kushki_response": {
        "code": "01",
        "message": "Refer to card issuer"
    },

Below you will find information on the codes and messages sent by Kushki to describe the response codes for requests made with card-present transactions. In the “What to Do?” column, you will find a detailed explanation of the causes and the procedure you should follow.

Code	Message	Detail
000	Approved Transaction	Indicates that the transaction was successfully approved.
01	Refer to card issuer	The cardholder should contact their card issuer to understand why the transaction was declined.
04	Capture card	The cardholder should try the transaction again.
05	Do not honor	The cardholder should try the transaction again.
12	Invalid transaction	The transaction is not allowed by the payment processor or the card issuer. Please contact the card issuer.
32	Expired card	The cardholder should use an alternative card.
41	Lost card	The cardholder should contact their card issuer to review the case.
57	Transaction not permitted to cardholder	The cardholder should contact their card issuer to review the case.
62	Restricted card	The cardholder should contact their card issuer to review the case.
91	Authorization System or issuer system inoperative )	The cardholder should try the transaction again.
92	Unable to route transaction	The cardholder should try again or contact the issuer.
6P	Verification data failed	Retry the transaction.
E016	Refund not available	Check that the refund is within the allowed timeframe.

Test Data

Make any necessary adjustments to your system using the test data.