Error codes for card-present transactions
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"},
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, Mastercard or Prosa (Mexico), it will have two digits. Below you will find the most common response codes, including declinations:
ISO Error Code | Description | Source |
---|---|---|
00 | Approved or completed successfully | Visa, Mastercard |
01 | Refer to card issuer | Visa, Mastercard |
02 | Refer to card issuer, special condition | Visa |
03 | Invalid merchant | Visa, Mastercard |
04 | Pick up card (no fraud) | Visa, Mastercard |
05 | Do not honor | Visa, Mastercard |
06 | Error | Visa |
07 | Pick up card, special condition (fraud account) | Visa |
08 | Honor with ID | Mastercard |
10 | Partial Approval | Visa, Mastercard |
11 | Approved (VIP) | Visa |
12 | Invalid transaction | Visa, Mastercard |
13 | Invalid amount | Visa, Mastercard |
14 | Invalid card number | Visa, Mastercard |
15 | Invalid issuer | Visa, Mastercard |
19 | Re-enter transaction | Visa |
21 | No action taken | Visa |
25 | Unable to locate record in file | Visa |
28 | File is temporarily unavailable for update or inquiry | Visa |
30 | Format error | Visa, Mastercard |
33 | Expired card | Visa |
34 | Suspected fraud | Visa |
35 | Card acceptor contact acquirer | Visa |
36 | Restricted card | Visa |
37 | Card acceptor call acquirer security | Visa |
38 | Allowable PIN tries exceeded | Visa |
39 | No credit account | Visa |
40 | Command rejected | Visa |
41 | Lost card | Visa, Mastercard |
43 | Stolen card | Visa, Mastercard |
46 | Closed account | Visa |
51 | Insufficient funds/over credit limit | Visa, Mastercard |
52 | No checking account | Visa |
53 | No savings account | Visa |
54 | Expired card or expiration date missing | Visa, Mastercard |
55 | Invalid PIN | Visa, Mastercard |
57 | Transaction not permitted to issuer/cardholder | Visa, Mastercard |
58 | Transaction not permitted to acquirer/terminal | Visa, Mastercard |
59 | Suspected fraud | Visa |
61 | Exceeds withdrawal amount limit | Visa, Mastercard |
62 | Restricted card | Visa, Mastercard |
63 | Security violation | Visa, Mastercard |
64 | Transaction does not fulfill AML requirement | Visa |
65 | Exceeds withdrawal count limit | Visa, Mastercard |
70 | PIN data required | Visa |
71 | Issuer PIN Not Changed | Mastercard |
74 | Different value than that used for PIN encryption errors | Visa |
75 | Allowable number of PIN-entry tries exceeded | Visa, Mastercard |
76 | Unsolicited reversal | Visa, Mastercard |
77 | Invalid/nonexistent ‘From Account’ specified | Mastercard |
78 | Blocked, first used or special condition | Visa, Mastercard |
79 | Reversed (by switch) | Visa |
80 | No financial impact | Visa |
81 | Cryptographic error | Visa, Mastercard |
82 | Policy / Negative online authentication failure | Visa, Mastercard |
83 | Fraud/Security | Mastercard |
84 | Invalid Authorization Life Cycle | Mastercard |
85 | Not declined, valid for all zero amount transactions | Visa, Mastercard |
86 | Cannot verify PIN | Visa, Mastercard |
87 | Purchase Amount Only, No Cash Back Allowed | Mastercard |
88 | Cryptographic failure | Mastercard |
89 | Unacceptable PIN | Mastercard |
91 | Authorization System or issuer system inoperative | Visa, Mastercard |
92 | Unable to route transaction | Visa, Mastercard |
93 | Transaction cannot be completed—violation of law | Visa |
94 | Duplicate transmission detected | Visa, Mastercard |
96 | System error | Visa, Mastercard |
N0 | Force STIP | Visa |
N3 | Cash service not available | Visa |
N4 | Cash request exceeds issuer or approved limit | Visa |
N7 | Decline for CVV2 failure | Visa |
N8 | Transaction amount exceeds pre-authorized approval amount | Visa |
R0 | Stop payment order | Visa |
R1 | Revocation of authorization order | Visa |
R2 | Transaction does not qualify for Visa PIN | Visa |
R3 | Revocation of all authorizations order | Visa |
Z3 | Unable to go online; offline-declined | Visa |
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.