Kushki Error Catalog for POS transactions

This catalog outlines the possible API responses for various transaction scenarios, including status codes, messages, and descriptions. It covers declines from issuers and brands when transactions are externally evaluated, helping you understand approvals and rejections more effectively.

HTTP Status Codes

Kushki might return different HTTP status codes depending on the requests made. Below are the most common HTTP status codes, their associated standard message, as well as a more detailed description of the response.

Code	Message	Detail
200	OK	The process was successful. Everything 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	Credentials must be authenticated, or authentication has failed
403	Forbidden	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 because of 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	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 server-side error occurred
502	Bad Gateway	The server (acting as a proxy or gateway) received an invalid response from another server
503	Service Temporarily Unavailable	The server is unavailable (usually because it is under maintenance, or because it is overloaded)
504	Gateway Timeout	The server (acting as a proxy or gateway) has not received a response from the other server in time

Codes returned by Kushki in POS charges

The response codes received by processors and issuers will appear in the kushki_response object as in the next example

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

Error 006

This error code appears when Kushki blocks the card, for example if the brand is not supported.

"kushki_response": {
        "code": "006",
        "message": "Card brand not supported"
    },

In case this code comes from the Card franchises (Visa or Mastercard), it will have two digits. Below you will find the most common response codes, including declinations:

Mastercard

Visa

ISO Error Code	Description
00	Approved or completed successfully
01	Refer to card issuer
03	Invalid merchant
04	Capture card
05	Do not honor
08	Honor with ID
10	Partial Approval
12	Invalid transaction
13	Invalid amount
14	Invalid card number
15	Invalid issuer
30	Format error
41	Lost card
43	Stolen card
51	Insufficient funds/over credit limit
54	Expired card
55	Invalid PIN
57	Transaction not permitted to issuer/cardholder
58	Transaction not permitted to acquirer/terminal
61	Exceeds withdrawal amount limit
62	Restricted card
63	Security violation
65	Exceeds withdrawal count limit OR Identity Check Soft-Decline of EMV 3DS Authentication (merchant should resubmit authentication with 3DSv1)
70	Contact Card
71	Issuer PIN Not Changed
75	Allowable number of PIN tries exceeded
76	Invalid/nonexistent "To Account" specified
77	Invalid/nonexistent "From Account" specified
78	Invalid/nonexistent account specified (general)
79	Life cycle (Mastercard use only for 0110 messages)
81	Domestic Debit Transaction Not Allowed (Regional use only)
82	Policy (Mastercard use only for 0110 messages)
83	Fraud/Security (Mastercard use only for 0110 messages)
84	Invalid Authorization Life Cycle
85	Not declined Valid for all zero amount transactions.
86	PIN Validation not possible
87	Purchase Amount Only, No Cash Back Allowed
88	Cryptographic failure
89	Unacceptable PIN— Transaction Declined— Retry
91	Authorization System or issuer system inoperative
92	Unable to route transaction
94	Duplicate transmission detected
96	System error

CODE	MESSAGE	WHAT TO DO?
000	Approved or completed successfully	Indicates that the transaction was successfully approved.
01	Refer to card issuer	The cardholder must contact their card issuer to understand why the transaction was rejected
04	Capture card	The cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
05	Do not honor	The cardholder must retry the transaction
06	Error	The cardholder should call the issuing bank to clarify the problem (and increase their credit if the problem is the credit limit)
09	Request in progress (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	El emisor no puede autorizar esta transacción	The cardholder should use an alternative card
17	No such issuer	At the time of making the transaction a format error occured.
1A	Additional customer authentication required	he cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
32	Expired card	The cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
34	Suspected fraud	The cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
35	Card acceptor contact acquirer	The cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
37	Card acceptor call acquirer security	Use an alternative card
39	No credit account	The cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
41	Lost card	The cardholder must contact their card issuer to understand why the transaction was rejected
51	Not sufficient funds	The cardholder should use an alternative card
54	Expired card	The cardholder should use an alternative card
57	Transaction not permitted to cardholder	AThe cardholder must use a different card to process the transaction and contact their card issuer for them to review the case
59	Suspected fraud	The issuer requested to change the PIN but it was not completed successfully
61	Exceeds withdrawal amount limit	The cardholder should use an alternative card
62	Restricted card	The cardholder should retry or use an alternative card
6P	Verification data failed	The cardholder should retry or use an alternative card from a different issuer
75	Allowable number of PIN tries exceeded *	Contact the issuer for more information
78	Invalid/nonexistent account specified (general)	The transaction was declined because a coincidence was found with another previous transaction
80	No financial impact	The cardholder should retry or use an alternative card from a different issuer
81	Cryptographic error found in PIN (used for cryptographic error condition found by 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 by 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

Codes returned by Kushki in Voids and reverse attempts

The response codes received by processors and issuers will appear in the kushki_response object as in the next example.

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

In the code and message columns of the table below, the code and message sent by Kushki are shown. In the column What to do?, we provide you with a more detailed explanation of the causes and the possible procedure to follow.

An example of a message returned by Kushki's API is shown below:

code	message	What to do?
000	Transacción Aprobada.	Indicates that the transaction was successfully approved.
01	Refer to card issuer	The cardholder must contact their card issuer to understand why the transaction was rejected
04	Capture card	The cardholder must retry the transaction
05	Do not honor	The cardholder must retry the transaction
12	Invalid transaction	The transaction is not allowed by the payment processor or the card issuer. Contact the card issuer
32	Expired card	The cardholder should use an alternative card
41	Lost card	The cardholder should contact their card issuer for them to review the case
57	Transaction not permitted to cardholder	The cardholder should contact their card issuer for them to review the case
62	Restricted card	The cardholder should contact their card issuer for them to review the case
91	Authorization System or issuer system inoperative	The cardholder should retry the transation
92	Unable to route transaction	The cardholder should retry or contact the issuer
6P	Verification data failed	Retry the transaction
E016	Refund not available	Check that the refund is within the allowed period

Kushki Error Catalog for POS transactions

HTTP Status Codes#

Codes returned by Kushki in POS charges#

Error 006#

Codes returned by Kushki in Voids and reverse attempts#

HTTP Status Codes

Codes returned by Kushki in POS charges

Error 006

Codes returned by Kushki in Voids and reverse attempts