Error codes
Last updated: December 11, 2024
After sending an API request, you will receive a response containing:
- an HTTP status code
- a response object containing a
response_code
that indicates the status of the request, or an error object containing one or severalerror_codes
This page describes the possible error codes you might receive. View a list of the possible response codes.
The following table lists the error codes that exist for the /payments
endpoint.
Name | Description |
---|---|
| The specified currency is not configured.
|
| The specified scheme is not configured.
|
| 3DS has malfunctioned. |
| 3DS is not configured. |
| 3DS is not enabled for card. |
| 3DS is not supported. |
| 3DS payment required. |
| The 3DS version is invalid. |
| The 3DS version is not supported. |
| The quota of failed payment actions has been exceeded. |
| The shipping address is invalid. |
| Account funding transactions (AFTs) are not configured. A matching processor was not found. |
| The payment amount exceeds the balance. |
| The payment amount is invalid. |
| The transaction to this card exceeded the amount limit set by the scheme's velocity limit. |
| The quota for API calls has been exceeded. |
| The city from which the charge originated is invalid. |
| The city from which the charge originated is required. |
| The dynamic description of the charge is invalid. |
| A dynamic description of the charge is required. |
| The business settings are invalid. |
| The business settings are missing. |
| The capture value is greater than the authorized value. |
| The capture value is greater than the remaining authorized value. |
| The card authorization has failed. |
| The card is disabled. |
| The card is expired. |
| The two-digit expiry month is invalid. |
| A two-digit expiry month is required. |
| The four-digit expiry year is invalid. |
| A four-digit expiry year is required. |
| The cardholder is invalid. |
| The recipient cardholder’s account is not eligible for domestic money transfer card payouts. |
| The recipient cardholder’s account is not eligible for cross-border money transfer card payouts. |
| The recipient cardholder’s account is not eligible for domestic non-money transfer card payouts. |
| The recipient cardholder’s account is not eligible for cross-border non-money transfer card payouts. |
| The recipient cardholder’s account is not eligible for domestic online gambling card payouts. |
| The recipient cardholder’s account is not eligible for cross-border online gambling card payouts. |
| The card was not found. |
| The card number is invalid. |
| The card number is required. |
| The channel details are invalid. |
| The channel URL is missing. |
| The charge details are invalid. |
| The city from which the charge originated is invalid. |
| The first or second line of the payment source owner's billing address is invalid. |
| The two-letter ISO country code of the payment source owner's billing address is invalid. |
| The international country calling code is invalid. |
| The international country calling code length is invalid. |
| The three-letter ISO currency code is invalid. |
| The three-letter ISO currency code is required. |
| The customer details already exist. |
| The email address associated with the customer is invalid. |
| The customer identifier is invalid. |
| The customer's details cannot be found. |
| The customer number is invalid. |
| Editing the customer plan has failed. |
| The customer plan identifier is invalid. |
| The CVV is invalid. |
| Bank code not recognized. Ensure the provided bank code is valid. |
| Invalid bank details provided. Check the request payload and ensure correct formatting. |
| The email address is already in use. |
| The email address is invalid. |
| The email address is required. |
| The endpoint is invalid. |
| The expiry date format is invalid. |
| The failure URL is invalid. |
| The account holder's first name is required. |
| The account holder's last name is required. |
| The IP address used to make the payment is invalid. |
| The issuer network is unavailable. |
| The metadata key is invalid. |
| There are no authorization processors configured. |
| The parameter is invalid. |
| The password is invalid. |
| The payment has expired. |
| The payment is invalid. |
| The payment method is not supported. |
| The payment source linked to a specific customer is required. |
| The payment type is invalid. |
| The phone number associated with the shipping address is invalid. |
| The length of the phone number associated with the shipping address is invalid. |
| The previous payment identifier is invalid. |
| There was a general error when processing the request. If you encounter multiple failures, contact Checkout.com. |
| The processing key is required. |
| The processing value is required. |
| The recipient's account number is invalid. |
| The recipient's account number is required. |
| The recipient's date of birth is invalid. |
| The recipient's date of birth is required. |
| The recipient's last name is required. |
| The first part of the recipient's UK postcode is required. |
| The first part of the recipient's UK postcode is required. |
| The recurring plan exists. |
| The recurring plan does not exist. |
| Removing the recurring plan has failed. |
| The request is invalid. |
| The JSON in the request is invalid. |
| The risk check that is enabled is required. |
| The full API is not enabled on your sandbox account. To enable it, please contact our Support team at [email protected]. |
| The payment source owner's email address is invalid. |
| The payment source owner's email address is required. |
| The payment source identifier is invalid. |
| The payment source identifier or email address is required. |
| The payment source identifier is required. |
| The payment source identifier is unknown. |
| The payment source is invalid. |
| The payment source or destination is required. |
| The Checkout.com token is invalid. |
| The Checkout.com token number is required. |
| The source token type is required. |
| The source token type is invalid. |
| The payment source type is required. |
| This account type cannot request a split payment for multiple sub-entities. |
| The success URL provided is invalid. |
| The Checkout.com token has expired. |
| The Checkout.com token is in use. |
| The Checkout.com token is invalid. |
| The Checkout.com token is required. |
| The Checkout.com token type is required. |
| The Checkout.com token has already been used. |
| The transaction to this card exceeded the amount limit set by the scheme's velocity limit. |
| The transaction to this card exceeded the transaction count limit set by the scheme's velocity limit. |
| The void request amount is invalid. |
| The wallet identifier is invalid. |
| The first part of the UK postcode is invalid. |
When you send a request, Checkout.com validates the data type, format, and existence of the fields you provide to ensure they adhere to the specifications defined in the API reference.
If there is an issue with a field, you'll receive an error code with the format:
<OBJECT_NAME>_<VALIDATION_ERROR_TYPE>
For example, if the value you provide for the destination.account_holder.first_name
field contains too many characters, you'll receive the following error code:
destination_account_holder_first_name_too_long
The validation error types can be any of the following:
too_short
: the value you provided for the field contains too few characterstoo_long
: the value you provided for the field contains too many charactersrequired
: the field is required but you did not provide a valueinvalid_option
: you included a field in your request that is not a valid optioninvalid_format
: the value you provided for the field is not in the correct formatinvalid
: the field or value is invalid, due to factors not described by the other validation errors
The table below lists all the possible error codes you might receive when using the /accounts/entities
endpoint.
Name | Description |
---|---|
| The MCCs provided for the sub-entity are outside the processing scope of its PayFac/Marketplace. |
| The principal address country provided for the sub-entity is outside the processing scope of its PayFac/Marketplace. |
| The PayFac/Marketplace is not permitted to onboard new sub-entities. |
For example, | The specified field is mandatory but was not provided in the request: the field is null, contains empty strings, or contains white spaces. |
For example, | The specified field does not match the validation policies for minimum length, maximum length, or formatting. |
The following table lists the error codes that exist for the /tokens
endpoint.
Name | Description |
---|---|
| There is a processing error. |
| The request is invalid. |
| The service is unavailable. |
| The token type is invalid. |
| The token data is invalid. |
The following table lists the error codes that exist for the /instruments
endpoint.
Name | Description |
---|---|
| The bank account instrument identification type is invalid. |
| The bank account issuing country type is invalid. |
| The bank account date of birth type is invalid. |
| The bank account country of birth type is invalid. |
| The bank account country is required. |
| The bank account residential status is invalid. |
| The bank account type is invalid. |
| The bank account holder type is invalid. |
| The IBAN is invalid. |
| The SWIFT code is invalid. |
| The country code is invalid. |
| The token data is required. |
| A customer already exists for that instrument. |
| The entity ID is invalid. |