Error codes for single card payments
What types of response codes does Kushki return?
processorError and code. The code field returns generic messages. On the other side, the field processorError indicates that the transaction has passed through the processor and has probably been mapped by Kushki in order to provide a specific explanation of the reason why your transaction could not be completed.Codes returned by Kushki for one-time card payments
processorError field will not appear in the response and you will only see the code field.An example of a message returned by Kushki's API is shown below:
{"message": "ID de comercio o credencial no válido",
"code": "K004" }code field are summarized.| code | message | What to do? |
|---|---|---|
| 006 | Abandoned transaction | - |
| 017 | Invalid card | Try another card |
| 201 | Invalid merchant ID | Check submitted credentials and retry |
| 228 | Processor unreachable | Unable to communicate with processor |
| 228 | Processor unreachable | Unable to communicate with processor |
| 577 | The transaction token is invalid | Submit the data again to obtain a new token |
| 621 | Transaction canceled by user | - |
| 622 | Session timeout | Retry transaction |
| 703 | Transaction amount is required | Make sure to submit the amount and retry |
| K001 | Invalid request body | Check request body |
| K002 | An unexpected error has occurred | Retry the transaction; in case the error persists, get in touch with Kushki's support team so that we can review your case. |
| K003 | Processor does not exist | Contact Kushki's support team, so we can review your case |
| K004 | Invalid merchant ID | Check public merchant ID or private merchant ID and retry |
| K005 | Invalid processor ID | Contact Kushki's support team, so we can review your case |
| K007 | Card blocked by the issuer | Try another card |
| K008 | Incorrect token | Fill in the data again and retry |
| K009 | Check SSM variables | Fill in the data again and retry |
| K011 | Invalid BIN | Try another card |
| K012 | Invalid capture amount | Check amount to capture and retry |
| K013 | Error en integración con un tercero | Este error podría haberse originado porque la transacción excedió el tiempo de espera |
| K015 | CVV2_REJECTED_TRANSACTION | Check the CVV and retry |
| K016 | Method not implemented | Contact Kushki's support team, so we can review your case |
| K020 | ERROR_REJECTED_TRANSACTION | Retry the transaction; in case the error persists, contact Kushki's support team, so we can review your case |
| K021 | ERROR_REJECTED_TRANSACTION | Retry the transaction; in case the error persists, contact Kushki's support team, so we can review your case |
| K023 | Void amount higher than sale | This message is displayed when trying to make a partial void, but the amount is higher than the sale amount |
| K025 | Invalid card | Try another card |
| K026 | Processor Declined | Contact Kushki's support team, so we can review your case |
| K027 | The transaction went into timeout, please try again | Retry the transaction |
| K028 | The merchant does not have the deferred option enabled | - |
| K029 | Invalid card BIN | Try another card |
| K030 | Processor unreachable | Retry the transaction |
| K038 | Partial void cannot be performed without specifying the value to be deducted | Specify the amount object |
| K039 | The sum of the values of the amount property must be greater than 0 | An amount greater than 0 must be submitted in the amount property. |
| K040 | The merchant ID does not match the credential submitted | An amount greater than 0 must be submitted in the amount property. |
| K041 | Transaction not allowed | Contact Kushki's support team, so we can review your case |
| K042 | The currency code is different from that of the initial transaction. | This message is displayed when a currency code other than that of the initial transaction is submitted. Submit the correct currency code. |
| K047 | An unexpected error has occurred | Retry the transaction |
| K048 | Token expired | Submit the data and retry the transaction |
| K049 | Previously used token | Submit the data and retry the transaction |
| K051 | Capture transaction already processed | Capture cannot be performed again |
| K220 | The transaction amount is different to the initial sale amount | The amount submitted in the token must be equal to that of the purchase. It will be necessary to ensure that the amount to pay is correct. |
| K322 | Rejected Transaction | The transaction was declined by a Kushki's security rule. Contact Kushki's support team so that we can review your case |
Error codes when transaction goes to the processor
processorError field, so that you can use them to map your application messages.Tip
K006 error through the processorError field, contact our support team, so that we can verify the cause.| processorError | message | What to do? |
|---|---|---|
| 501 | Rejected transaction. Contact your card issuer | The cardholder must contact his/her card issuer to understand why the transaction was rejected |
| 503 | The business number is not registered | The endpoint number or business code is not registered or enabled in the payment processor. Contact Kushki's support team so we can review your case. |
| 504 | The card entered has been reported. | The cardholder must use a different card to process the transaction and contact their card issuer for them to review the case. |
| 505 | The transaction was declined by the processor or issuer. | The cardholder must wait a couple of minutes and retry; otherwise, their must use an alternative card. |
| 512 | Transaction not allowed by the issuer. | The transaction is not allowed by the payment processor or the card issuer. The cardholder should use an alternative card. |
| 513 | The amount entered contains an invalid syntax | It is necessary to verify the amount entered and retry. For example, it is possible that unallowed characters have been entered in the amount field, as , instead of . to separate decimals. |
| 514 | The card number entered is not valid | The cardholder must verify that the card number has been entered correctly and retry. |
| 515 | The card issuer cannot authorize this transaction | The payment processor or card network rejected the submitted BIN. The cardholder should use another card. |
| 518 | An expired card has been entered | The card is expired or the date is incorrect. The cardholder must check that the date is correct or retry using another card. |
| 519 | An error occurred when processing the operation. Try again | The cardholder must retry the transaction. |
| 520 | The cardholder name entered is not correct | Enter again the cardholder name and retry. |
| 521 | The cardholder last name entered is not correct | Enter again the cardholder last name and retry. |
| 522 | The email address entered is not valid. | Enter again the cardholder's email address and retry. |
| 523 | The IP address number is incorrect. | Verify that the transaction is taking place from a valid IP address. |
| 524 | The identification number entered is incorrect. | Enter again the cardholder's type and identification number and retry. |
| 525 | The encrypted information is not valid | The process of information encryption was not correctly completed. Contact Kushki's support team so we can review your case. |
| 526 | This business has no permission to process transactions | This is caused by a restriction of a business by the payment processor. Contact Kushki's support team so we can review your case. |
| 527 | The entered amount cannot be zero | The amount for this transaction cannot be zero. A different amount must be entered and retry. |
| 528 | The transaction amount is different to the initial sale amount | The amount entered in the token must be equal to that of the purchase. It will be necessary to ensure that the amount to pay is correct. |
| 529 | It has not been possible to find the transaction | When reversing or cancelling a transaction it was not possible to find the original message. Contact Kushki's support team so we can review your case. |
| 530 | Transaction rejected due to a formatting error | At the time of making the transaction a format error occured. Contact Kushki's support team so we can review your case. |
| 541 | This card has been reported as lost | The cardholder must use a different card to process the transaction and contact the card issuer to review the case. |
| 543 | This card has been reported as stolen | The cardholder must use a different card to process the transaction and contact the card issuer to review the case. |
| 551 | There are not enough funds to complete the operation. | The cardholder must use a different card to process the transaction as the card entered does not have enough funds the transaction to be processed. |
| 552 | The type of account entered is not valid | The cardholder must verify the type of account selected and try again. |
| 553 | The card is not compatible | The card brand entered is not compatible for its authorization. The cardholder must use a different card to process the transaction. |
| 554 | The type of currency is not valid | The payment processor or card issuer does not accept transactions in the selected currency. Contact Kushki's support team so we can review your case. |
| 555 | The request is not valid | A request issue has occurred for the transaction made. Contact Kushki's support team so we can review your case. |
| 556 | The transaction has been canceled | The transaction that is being reverted or cancelled has already been cancelled |
| 557 | The card issuer cannot authorize this transaction | Due to some issuer restrictions, it is not possible to authorize the transaction. The cardholder must change the card or payment method and get in touch with the card issuer to review the case. |
| 558 | Transaction not allowed for this business | Due to restrictions by the payment processor it is not possible to authorize the transaction for this business. Contact Kushki's support team so we can review your case. |
| 559 | The transaction has been considered as potentially fraudulent | The transaction made was declined by the payment processor or card issuer due to fraud suspicions. |
| 560 | The amount entered is lower or greater than allowed | The amount in the transaction is lower or greater than the limits that have been established. The cardholder must verify the transaction amount and retry. |
| 561 | The daily transaction limit has been exceeded | The cardholder has exceeded the activity limit in number or amount of daily transactions |
| 562 | Card restricted by the issuing bank | The card issuer has declined the transaction because it has applied restrictions to the cardholder. The cardholder must contact the card issuing bank to review his/her case. |
| 563 | Operation rejected due to security breach | The card issuer or payment processor declined the transaction because a security breach occurred. |
| 564 | The entered token is not valid or has expired | The token that is being used does not have a valid format, it does not exist or was already used in a transaction |
| 565 | The transaction was declined according to security rules | The transaction is being declined because security rules have been established for the card or the merchant |
| 566 | The token is not valid, or was already used in another transaction | The token that is being used does not have a valid format, it does not exist or was already used in a transaction. Contact Kushki's support team so we can review your case. |
| 567 | The transaction amount is required | It is mandatory to enter a value in the field “amount”. |
| 568 | The transaction ticket number is not valid | Enter again the ticket number; if the issue persists, contact Kushki's support team so we can review your case. |
| 579 | The expiration date entered is incorrect | The cardholder must enter again the expiration date and try again. |
| 580 | The deferred payment is not correct | The type or format of the deferred payment that is being used is not correct. Contact Kushki's support team so we can review your case. |
| 581 | Credentials are not correct | Verify your entered credentials and try again |
| 582 | The security number (CVV2) is not correct | The cardholder must enter again the security code and retry the transaction. |
| 583 | The operation was already cancelled or the maximum time for reversal has been reached | It is not possible to cancel or reverse the transaction because it has been already canceled, the original transaction was not found, or the maximum time allowed to reverse the transaction has ended. Contact Kushki's support team so we can review your case. |
| 591 | Unauthorized Transaction. Inoperative card issuer | The cardholder must wait a couple of minutes and retry; otherwise, an alternative card should be used. |
| 594 | The rejected transaction seems to be a duplicate operation | The transaction was declined because a coincidence was found with another previous transaction. This usually happens because a repeated reference number is being entered. |
| 596 | The card issuer has had a problem when authorizing the transaction. | The cardholder must wait a couple of minutes and retry; otherwise, an alternative card should be used, or the cardholder should get in contact with the card issuer to verify the case. |
Modificado en 2026-09-25 15:05:22