---
title: "Error codes and messages"
description: "Learn about the meaning of API error codes."
url: "https://docs.adyen.com/development-resources/error-codes"
source_url: "https://docs.adyen.com/development-resources/error-codes.md"
canonical: "https://docs.adyen.com/development-resources/error-codes"
last_modified: "2020-04-25T16:42:00+02:00"
language: "en"
---

# Error codes and messages

Learn about the meaning of API error codes.

[View source](/development-resources/error-codes.md)

When you make an API call to Adyen and there is an error, you will receive a response with [HTTP status code](/development-resources/response-handling) different from `2xx`. This response includes `errorCode` and `message` fields that help you diagnose and resolve the error.

All integrations can receive generic error codes. There are also error codes specific to an integration type or a payment method.

## Requirements

| Requirement          | Description                                                                 |
| -------------------- | --------------------------------------------------------------------------- |
| **Integration type** | An [online payments](/online-payments/build-your-integration/) integration. |

## Example error response

**Error details in an API response**

```json
{
   "status" : 422,
   "errorCode" : "101",
   "message" : "Invalid card number",
   "errorType" : "validation",
   "pspReference" : "F7WCWRG6JPHR8HG2"
}
```

| Parameter   | Description                                                                                                                                                                                                                                                         |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `status`    | Specifies the [HTTP status code](/development-resources/response-handling) for the API request. For a value of **422**, the request is well-formed (syntactically correct), but semantically incorrect: the receiving server can read it, but cannot understand it. |
| `errorCode` | The Adyen code that is mapped to the error message. For a value of **101**, the request contains an incorrect card number or length.                                                                                                                                |
| `message`   | A short explanation of the error. For a value of **Invalid card number**, the request contains an incorrect card number or length.                                                                                                                                  |
| `errorType` | The category of the error: **internal**, **validation**, **security**, or **configuration**. For a value of **validation**, the request is missing required fields or contains invalid data.                                                                        |

## Generic error codes

### 000 - Multiple messages

The **000** error code is a generic error code with several possible messages and causes; for example:

* Unknown: Unauthorised: The API key or Auth credentials are incorrect.
* Unable to parse message.

***

### 010 - Not allowed

**Cause**:

* The API credential is missing required roles.
* The user API is incorrect.
* You are making a [third-party](/point-of-sale/shopper-engagement/third-party-interactions#security-and-requirements) payment or card acquisition request to your terminals.

***

### 100 - Required object 'amount' is not provided

**Cause**: Missing parameter\
**Solution**:

* Add the missing parameter(s) `amount` or `originalReference`.
* Compare your request with a standard request for that endpoint, and identify missing parameters.

***

### 101 - Invalid card number

**Cause**:

* Incorrect card number or length.
* Incorrect capitalization of `PaRes`.

***

### 102 - Unable to determine variant

**Cause**: The card number field contains an incorrect value.

***

### 103 - CVC is not the right length

**Cause**:

* The Card Validation Code (CVC) is not valid.
* The CVC is alphanumeric instead of numeric-only.
* There are more than three digits.
* (American Express) There are more than four digits.

***

### 104 - Billing address problem

**Cause**: Missing a required field under `billingAddress`.\
**Solution**: Check the `billingAddress` object for missing fields.

***

### 105 - Invalid paRes from issuer

* **Cause**: The issuer returns an URL-encoded `PaRes` or `MD`.\
  **Solution**: URL-decode the `PaRes` and `MD` before submitting them in the [/payments/details](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments/details) request.
* **Cause**: The issuer returns the correct `PaRes` value, but the parameter name is different from `PaRes`, for example `PaResponse` or `paRes`\
  **Solution**: Adyen only accepts this parameter as `PaRes`. If the issuer has returned something different, make sure that you change it to `PaRes` before submitting it in the [/payments/details](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments/details) request.
* **Cause**: The `PaRes` parameter is empty, or some other reason different from the above.\
  **Solution**: Ask your shopper to contact the issuing bank to report the error.

***

### 106 - This session was already used previously

***

### 107 - Recurring is not enabled

**Cause**: Missing user permission.\
**Solution**: Add the **Merchant Recurring** role to the associated web service user.

***

### 108 - Invalid bankaccount number

**Cause**: The IBAN is incorrect.

***

### 109 - Invalid variant

**Cause**: Missing `txvariant` details.\
**Solution**: Check the `requestData` and pass the details correctly.

***

### 110 - BankDetails missing

**Cause**:

* The IBAN is missing.
* The IBAN is incorrect.

***

### 111 - Invalid BankCountryCode specified

**Cause**:

* The parameter name is spelled incorrectly.
* The value passed for `countryCode` is not following the ISO standard.

**Solution**:

* Confirm the parameter name spelling in the Adyen API Explorer.
* Check that the `countryCode` value corresponds to a country and is spelled correctly; for example, use **DE** for Germany.

***

### 112 - This bank country is not supported

**Cause**:

* `countryCode` length does not follow the ISO standard.
* `countryCode` does not exist.

***

### 113 - No InvoiceLines provided

**Cause**: Invoice lines are missing in the `requestData`.

***

### 114 - Received an incorrect InvoiceLine

**Cause**: Incorrect currency used, or the `lineReference` is **null**.\
**Solution**: Check the invoice line against the `requestData`.

***

### 115 - Total amount is not the same as the sum of the lines

**Cause**: `linesTotalQuantity` is not equal to `request.getAmount().getValue()`.

***

### 116 - Invalid date of birth

**Cause**: The `dateOfBirth` format is incorrect.\
**Solution**: Check the date and format in the `dateOfBirth` parameter.

***

### 117 - Invalid billing address

**Cause**: The `billingAddress` object does not contain all the required fields.\
**Solution**: Check the required parameters in the API Explorer.

***

### 118 - Invalid delivery address

**Cause**:

* The `deliveryAddress` is **null**.
* The `deliveryAddress` format is invalid.

***

### 119 - Invalid shopper name

**Cause**: The `shopperName` is **null**.

***

### 120 - Required field 'shopperEmail' is not provided

**Cause**:

* The `shopperEmail` is missing.
* The `shopperEmail` format is invalid.

***

### 121 - Required field 'shopperReference' is not provided

**Cause**:

* The `shopperReference` is **null**.
* Recurring requires `shopperReference`

***

### 122 - Required field 'telephoneNumber' is not provided.

**Cause**: The `phoneNumber` or `telephoneNumber` is **null**.

***

### 124 - Invalid PhoneNumber

***

### 125 - Invalid recurring contract specified

**Cause**: The recurring object is not passed correctly.\
**Solution**: Check the `requestData` and make sure the recurring object is correct.

***

### 126 - Bank Account or Bank Location Id not valid or missing

***

### 127 - Required field 'accountHolderName' is not provided

***

### 128 - Required field 'card.holderName' is not provided

***

### 129 - Expiry Date Invalid

**Cause**:

* The value is not numeric.
* The value contains an empty space.
* The expiry month is not set.
* The month value is not between **1** and **12**.

**Solution**: Check the input passed into field.

***

### 130 - Reference Missing

**Cause**:

* The `reference` parameter is missing.
* The `requestData` is missing multiple parameters.

**Solution**: Check if the `reference` parameter is passed correctly.

***

### 131 - Required field 'billingAddress.city' is not provided

***

### 132 - Required field 'billingAddress.street' is not provided

***

### 133 - Required field 'billingAddress.houseNumberOrName' is not provided

***

### 134 - Billing address problem (Country)

***

### 135 - Required field 'billingAddress.stateOrProvince' is not provided

***

### 136 - Failed to retrieve OpenInvoiceLines

***

### 137 - Field 'amount' is not valid

**Cause**:

* The `amount` passed is greater than the limit.
* The `amount` passed is not a positive number.

**Solution**: Check the input.

***

### 138 - Field 'currency' is not valid

**Cause**: The provided currency is not supported.

***

### 139 - Recurring requires 'shopperEmail' and 'shopperReference'

**Cause**: The `shopperReference` and `shopperEmail` are missing.

***

### 140 - Invalid expiryMonth\[1..12] / expiryYear\[>2000], or before now

***

### 141 - Invalid expiryMonth\[1..12] / expiryYear\[>2000]

***

### 142 - Bank Name or Bank Location not valid or missing

***

### 143 - Submitted total iDEAL merchantReturnUrl length is {0}, but max size is {1} for this request

***

### 144 - Invalid startMonth\[1..12] / startYear\[>2000], or in the future

***

### 145 - Invalid issuer countryCode

***

### 146 - Invalid social security number

***

### 147 - Required field 'deliveryAddress.city' is not provided

***

### 148 - Required field 'deliveryAddress.street' is not provided

* **Cause**: You are not sending all parameters.\
  **Solution**: Pass all required parameters.
* **Cause**: You are sending all parameters, but the value is empty.\
  **Solution**: Make sure that you pass data in each parameter.

***

### 149 - Required field 'deliveryAddress.houseNumberOrName' is not provided

***

### 150 - Delivery address problem (Country)

***

### 151 - Required field 'deliveryAddress.stateOrProvince' is not provided

**Cause**: `stateOrProvince` field is missing in delivery address and is required for the selected country.

***

### 152 - Invalid number of installments

**Cause**:

* Installment value is zero.
* The payment method is not set up with **installment**.

**Solution**:

* Check the `requestData`.
* Configure **installment** under the specific payment method; for example, Visa.

***

### 153 - Invalid CVC

**Cause**:

* The Card Validation Code (CVC) is not numeric.
* The CVC contains invalid values.

**Solution**: Check the CVC input.

***

### 154 - No additional data specified

***

### 155 - No acquirer specified

***

### 156 - No authorisation mid specified

***

### 157 - No fields specified

***

### 158 - Required field {0} not provided

**Cause**: One of the following fields is missing:

* `initialPspReference`
* `orderReference`
* `ownerName`
* `reference`

**Solution**: Supply the missing value.

***

### 159 - Invalid number of requests

***

### 160 - Not allowed to store Payout Details

***

### 161 - Invalid iban

**Cause**:

* The IBAN is incorrect.
* There is a mismatch between IBAN and country.
* The bank does not support SEPA direct debit.

**Solution**:

* Verify the IBAN number.
* Check if IBAN is supported for the specified `countryCode`.

***

### 162 - Inconsistent iban

**Cause**:

* Swift Code / BIC does not exist - SEPA/Giro/Direct Debit.
* Payout party/account BIC/Swift invalid.
* Bank/mt940 - Invalid BIC/Swift in co-relation to `countryCode`.
* Exceeded IBAN characters/digits.

***

### 163 - Invalid bic

***

### 164 - Auto capture delay invalid or out of range

***

### 165 - MandateId does not match pattern

***

### 166 - Amount not allowed for this operation

***

### 167 - Original pspReference required for this operation

**Cause**: The original PSP in the `requestData` field is missing.

***

### 168 - AuthorisationCode required for this operation

***

### 170 - Generation Date required but missing

***

### 171 - Unable to parse Generation Date

***

### 172 - Encrypted data used outside of valid time period

**Cause**: Your server-side date/time is not set up correctly. For example, your server side is set to 1975 when it is 2020, or the date is not within 24 hours of the current time.\
**Solution**: Check the server-side date/time configuration.

***

### 173 - Unable to load Private Key for decryption

***

### 174 - Unable to decrypt data

**Cause**:

* Using `HTTP GET` instead of `HTTP POST`.
* Environment mismatch (LIVE or TEST).
* The Origin key/Client key was not generated correctly.
* API key should match the API key from the web service user, and should match the environment.

**Solution**: If you are seeing this using a plugin, generate a new web service user with the relevant permissions.

***

### 175 - Unable to parse JSON data

**Cause**: Make sure that the parameters sent are formatted correctly in JSON.\
**Solution**: Read through the `requestData` to find the error.

***

### 180 - Invalid shopperReference

**Cause**: `shopperReference` is empty, doesn't exist, or is not found.

***

### 181 - Invalid shopperEmail

**Cause**: `shopperEmail` is empty, doesn't exist, or is not found.

***

### 182 - Invalid selected brand

**Cause**: The selected brand is not equal to the brand on the stored token, or empty.

***

### 183 - Invalid recurring contract

**Cause**: Not found in Recharge.

***

### 184 - Invalid recurring detail name

**Cause**:

* Value is empty or **null**.
* The name doesn't match with the `recurringDetail` name.

***

### 185 - Invalid additionalData

* **Cause**: Too many fields/entries.\
  **Solution**: Make sure that the number of items in the object is less than 1000.
* **Cause**: The `splitPayment` is missing or invalid.\
  **Solution**: Check the `additionalData` object for errors or missing data. If any `additionalData` is not valid, remove it from modification processing. For example, a payment can go through, but a split will not.
* **Cause**: `adyenGivingAccount` is not specified, cannot be retrieved, or does not exist.\
  **Solution**: When using Adyen for Platforms, make sure `itemReference` is unique.

***

### 186 - Missing additionalData field

***

### 187 - Invalid additionalData field

**Cause**:

* Too many fields/entries.
* SplitPayment missing/not valid.
* AdyenGivingAccount not specified, cannot be retrieved or does not exist.

***

### 188 - Invalid pspEchoData

**Cause**: The previous `recurringDetail` token was not saved correctly or does not exist.

***

### 189 - Invalid shopperStatement

**Cause**: Empty value passed in `requestData`.

***

### 190 - Invalid shopper IP

**Cause**: The `shopperIP` is empty.

***

### 191 - No params specified

***

### 192 - Invalid field {0}

**Cause**: `shopperInteraction` is invalid.

***

### 193 - Bin Details not found for the given card number

**Cause**:

* Not sending in correct parameters.
* Not passing applicable value.

***

### 194 - Billing address missing

**Cause**: Required object `billingAddress` is missing.

***

### 195 - Could not find an account with this key: {0}

***

### 196 - Invalid Mcc

**Cause**:

* Check MCC length.
* Should be a numeric value.
* An alphanumeric value is provided.

***

### 198 - Reference may not exceed 79 characters

**Cause**: The reference contains more than 80 characters.

***

### 199 - The cryptographic operation could not proceed, no key configured

***

### 200 - Invalid country code

**Cause**: Incorrect `countryCode`.\
**Solution**: Use ISO 3166-1 alpha-2 format.

***

### 203 - Invalid Bank account holder name

**Cause**:

* Account holder name is inconsistent with FATF 16 recommendations.
* Name may not contain numbers.

***

### 205 - Missing or invalid networkTxReference

**Cause**:

* Only digits provided.
* Incorrect format.
* Must have an alphanumeric combination.
* Can also occur if recurring value is **null**.

***

### 213 - Required field 'socialSecurityNumber' is not provided.

**Cause**: The `socialSecurityNumber`, which is required for the payment method, is missing.

***

### 217 - Field 'shopperInteraction' is missing or invalid

***

### 218 - Recurring shopper lookup failed

***

### 600 - No InvoiceProject provided

***

### 601 - No InvoiceBatch provided

***

### 602 - No creditorAccount specified

***

### 603 - No projectCode specified

***

### 604 - No creditorAccount found

***

### 605 - No project found

***

### 606 - Unable to create InvoiceProject

***

### 607 - InvoiceBatch already exists

***

### 608 - Unable to create InvoiceBatch

***

### 609 - InvoiceBatch validity period exceeded

***

### 690 - Error while storing debtor

***

### 691 - Error while storing invoice

***

### 692 - Error while checking if invoice already exists for creditorAccount

***

### 693 - Error while searching invoices

***

### 694 - No Invoice Configuration configured for creditAccount

***

### 695 - Invalid Invoice Configuration configured for creditAccount

***

### 700 - No method specified

***

### 701 - Server could not process request

**Cause**:

* Incorrect POST / Content Type.
* Might be sending XML, HTTP etc.
* Using Pay by Link with incorrect `shopperReference`.
* API version not specified.
* RequestURL is not valid.

**Solution**:

* Send JSON formatted, send HTTP POST.
* Pay by Link: make sure the web service user has the required permissions.

***

### 702 - Problem parsing request

**Cause**:

* The request contains a field that is not recognized, or the format is not valid. This validation was introduced in [API v64](/online-payments/release-notes#releaseNote=2020-08-09-checkout-api-64).
* Empty input which would have resulted in a null result: you might be using `requestData` from the API Explorer without populating your merchant account details.
* Internal Error.

***

### 703 - Required resource temporarily unavailable

**Cause**: The [data store](/development-resources/api-idempotency/#designing-for-resilience) is not available to compare the request against.\
**Solution**: Retry your request later or do not include the `idempotency-key` HTTP header in your request.

***

### 704 - Request already processed or in progress

**Cause**: The web service user is sending multiple authorised requests.\
**Solution**: Check that you send in requests only once.

***

### 705 - Rate limited

**Cause**: The rate limit for API requests has been exceeded.\
**Solution**: Throttle your API requests. Wait for a short duration before retrying the request.

***

### 800 - Contract not found

**Cause**:

* `shopperReference` does not exist.
* The `requestData` is creating a contract and using the `recurringDetailReference` at the same time.

**Solution**: Check if the details were saved previously, check the `shopperReference`.

***

### 801 - Too many PaymentDetails defined

**Cause**: The root cause of these timeouts is too many `paymentDetails`, or an incorrect integration for the same recurring or shopper reference.

***

### 802 - Invalid contract

**Cause**: There are no valid contract types (recurring or OneClick), or the contract type is not one of RECURRING, ONECLICK, or PAYOUT.\
**Solution**: Check the data that is sent in on the PAL, and then the data that is sent in on the PAL. Check the recharge service under the recurring field.

***

### 803 - PaymentDetail not found

**Cause**:

* `recurringDetailReference/storedPaymentMethodId` does not exist.
* It has been disabled.
* `requestData` is missing; for example, open invoice `lineItems` for Klarna.
* The payment method specified in your request varies from the one in your created token.

**Solution**: Check if the values being passed are correct and valid.

### 803\_3 - No active payment details found for shopper reference

**Cause**:

* Either the shopper reference is not valid, or all details have been disabled.

**Solution**: Check if the values being passed are correct and valid.

***

### 804 - Failed to disable

***

### 805 - RecurringDetailReference not available for provided recurring-contract

***

### 806 - No applicable contractTypes left for this payment-method

**Cause**: The `txvariant` Maestro cannot have recurring. The scheme mandates 3D Secure for all Maestro transactions, which is why recurring transactions are not possible.\
**Solution**: Recreate the contract, check the contract creation parameters or change current `requestData`.

***

### 807 - Invalid combination of shopper interaction and recurring-contract

**Cause**: Recurring contract was not set up with `shopperInteraction`.

***

### 820 - CVC is required for OneClick card payments

**Cause**: The Card Validation Code (CVC) was not supplied\
**Solution**: Supply the CVC number

***

### 901 – Invalid Merchant Account

**Cause**:

* You sent an incorrect `merchantAccount`.
* The merchant data (MD) value is incorrect when running the 3D Secure flow.
* The web service is not permitted for the specified `merchantAccount`.
* The company is not active.
* The `merchantAccount` value is passed with incorrect casing (the value is case-sensitive).

**Solution**:\
Make sure that:

* The MD value is not reused.
* The `merchantAccount` in the request exists and matches exactly, including casing.
* The web service you are calling is enabled for the `merchantAccount`.

***

### 902 - Invalid or empty request data

***

### 903 - Internal error

***

### 904 - Unable To Process

**Cause**: Error communicating with Adyen.

***

### 905 - Payment details are not supported

The **905** error code is a generic error code with several possible messages and causes. These errors are visible in your Customer Area, and occur when your account is not configured to support the payment method, currency, or the country.

**Cause**:

* Missing `paymentMethod` in your Customer Area.
* `paymentMethod` not set up for `countryCode`.

**Solution**: Make sure that the `countryCode` in `requestData` matches the `paymentMethod` txvariant in your Customer Area. For example, **bankTransfer\_DE** should match with `countryCode` **DE** in `requestData`.

***

### 905\_1 - Could not find an acquirer account for the provided txvariant ({0}), currency ({1}), and action ({2})

In the context of this error code, acquirer account refers to your merchant account.

**Cause**: The payment method is not set up in this merchant account.

**Solution**: [Add the payment method](/payment-methods/add-payment-methods) in your Customer Area.

***

### 905\_2 - No specified acquirer account found for '{0}' for specified acquirer '{1}' with variant '{2}' for unit '{3}' for Action '{4}'

In the context of this error code, acquirer account refers to your merchant account.

**Cause**: You specified merchant plug-in (MPI) data without specifying an acquirer code.

**Solution**: Set the `defaultToAcquirerSelectionRegardlessOfMPIData` account data property (ADP) to **true**. This defaults to an acquirer account if you have multiple configured. Contact the [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to modify ADPs.

***

### 905\_3 - Could not find an acquirer account for the provided currency ({0})

In the context of this error code, acquirer account refers to your merchant account.

* **Cause**: The payment type (`shopperInteraction`) is not supported.\
  **Solution**: Make sure that the payment method supports the shopper interaction that you are trying to use, and adjust the shopper interaction on your request or payment method settings.

* **Cause**: The payment method is set up for a specific store, and the store was not specified in the request.\
  **Solution**: Adjust the request (send the store number) or the payment method (remove the store restriction).

* **Cause**: The minimum amount is set too low.\
  **Solution**: Check the payment method's constraints and adjust your API request.

* **Cause**: There is a transaction rule set up that does not allow this amount or payment method.\
  **Solution**: Adjust your request or the transaction rules.

* **Cause**: The currency is not configured or supported.\
  **Solution**: Set up the payment method in the desired currency.

* **Cause**: There is a `customRoutingFlag` set up in the payment method, and you are not sending it in your request body.\
  **Solution**: Send the `customRoutingFlag` in the `additionalData` object.

* **Cause**: The bank identification number (BIN), country, currency, or issuer is restricted.\
  **Solution**: Adjust the request or the payment method; for example, prompt the customer for a different payment method, or remove the store restriction.

  Under certain circumstances related to this error, the payment cannot be processed.

***

### 905\_4 - Cashback and Cashout are not allowed for the configured acquirer account

In the context of this error code, acquirer account refers to your merchant account.

**Cause**: Your merchant account does not allow the cashback or cashout options. This functionality is specific to EFTPOS (Electronic Funds Transfer at Point Of Sale), which is a card scheme available only in Australia and New Zealand.\
**Solution**: To perform cashbacks or cashouts, contact the [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other).

***

### 905\_5 - No acquirer account active and configured for Klarna

In the context of this error code, acquirer account refers to your merchant account.

**Cause**: You have not configured your merchant account to accept Klarna payments.\
**Solution**: [Add the payment method](/payment-methods/add-payment-methods) in your Customer Area.

***

### 905\_6 - Both 'KlarnaPayments' and 'Klarna' platforms have been configured for the merchant account. Only one of two is allowed

**Cause**: You have configured both KlarnaPayments and Klarna as payment methods.\
**Solution**: Remove one of the Klarna payment methods.

***

### 906 - Invalid Request: Original pspReference is invalid for this environment

**Cause**:

* LIVE/TEST PSP mismatch.
* Sending TEST PSP to LIVE endpoint.

**Solution**: Pass the correct PSP or check environment you are testing in.

***

### 907 - Payment details are not supported for this country/ MCC combination

**Cause**:

* `paymentMethod` in Customer Area is missing or not configured for a specific country.
* There are MCC restrictions.
* Did not pass `className: TxScreening` (the transaction fails card number check on prepaid cards specifically).
* There are restrictions on the issuer bank used for the payment, which is sanctioned by Adyen.

**Solution**: Check `paymentMethod` configuration for logical errors.

***

### 908 - Invalid request

**Cause**:

* Using incorrect endpoint
* Incorrect `requestData` is sent to incorrect endpoint

**Solution**: Check what the goal of the request is and fix the `requestData`. Make sure that you are sending to the correct endpoint.

***

### 910 - Invalid Store

**Cause**: The specified store does not match any of the store references or store IDs for the merchant account.

**Solution**: Using API calls or your Customer Area, find the merchant account and the ID or reference of the store you want to use, and try again.

***

### 912 - The TX Variant does not support the redemption type

***

### 916 - The transaction amount exceeds the allowed limit for this type of card

***

### 918 - Required object 'card' is not provided

***

### 919 - The 'additionalAmount' currency should be the same currency as the payment

***

### 920 - Total payment amount should be equal or greater than zero

***

### 921\_1 - Object 'mpiData' is missing, required due to threeDReference

***

### 921\_2 - Object 'mpiData' is not valid. Reason: 'authenticationResponse' missing

***

### 921\_2 - Object 'mpiData' is not valid. Reason: 'directoryResponse' mismatch

***

### 922 - Account updater connection only supported for Visa & MasterCard

***

### 923 - No registered account for AccountUpdater

***

### 924 - Not allowed to change the shopperInteraction

***

### 926 - Invalid iDEAL issuer provided

***

### 927 - Missing payment details

***

### 928 - Invalid forex type specified

***

### 929 - Invalid base currency specified

***

### 930 - Invalid target currency specified

***

### 931 - There is no merchant with the code {0}

***

### 950 - Invalid AcquirerAccount

***

### 951 - Configuration Error (acquirerIdentification)

***

### 952 - Configuration Error (acquirerPassword)

***

### 953 - Configuration Error (apiKey)

***

### 954 - Configuration Error (redirectUrl)

***

### 955 - Configuration Error (AcquirerAccountData)

***

### 956 - Configuration Error (currencyCode)

***

### 957 - Configuration Error (terminalId)

***

### 958 - Configuration Error (serialNumber)

***

### 959 - Configuration Error (password)

***

### 960 - Configuration Error (projectId)

***

### 961 - Configuration Error (merchantCategoryCode)

***

### 962 - Configuration Error (merchantName)

***

### 963 - Invalid company registration number

***

### 964 - Invalid company name

***

### 965 - Missing company details

***

### 966 - Configuration Error (privateKeyAlias)

***

### 967 - Configuration Error (publicKeyAlias)

***

### 1000 - Card number cannot be specified for Incontrol virtual card requests

***

### 1001 - Recurring not allowed for Incontrol virtual card requests

***

### 1002 - Invalid Authorisation Type supplied

***

### 2000 - Bank account details do not meet instruction format

**Cause**:

* Not passing bank details required for Payout.
* Using `selectedRecurringDetailReference` as LATEST which may or may not correspond to bank details.

***

### 29\_001 - Field '{0}' may not exceed {1} characters.

**Cause**:

* The value provided in the field exceeded the allowed number of characters.
* The value is provided in the wrong field. For example, the field must be `PaReq` instead of `PaRes`.
* For generated or encrypted values, something might have gone wrong in the generation process which caused the value to be too long.

**Solution**:

* Check the values that you are providing in the fields.
* If you confirm that the fields and values are correct but the error persists, contact our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other).

***

### 29\_003 - Field 'fraudOffset' must be between -999 and 999

***

### 29\_100 - The request is larger than the allowed maximum of {0} bytes

**Cause**:

* The request's body contained more bytes than the maximum allowed for that endpoint.

## Checkout error codes

### 14\_002 - paymentData has not been provided in the request

***

### 14\_003 - Invalid paymentData

***

### 14\_004 - Missing payment method details

***

### 14\_005 - Invalid payment method details

**Cause**:\
One reason could be that the recurring contract on a token might be missing. For example, a payment method only supports creating a `RECURRING` contract, but you are trying to use a `ONECLICK` contract.

***

### 14\_006 - paymentMethod object has not been provided in the request

***

### 14\_007 - Invalid payment method data

**Cause**:\
There is an error with information in the `paymentMethod` object. For example, the `paymentMethod.type` might be missing.

***

### 14\_008 - Session has expired

***

### 14\_010 - The request contains no sdkVersion although the channel is set to Web

***

### 14\_011 - The provided channel is conflicting the provided parameters

**Solution**: Provide the correct `token` for iOS or Android, or `sdkVersion` for Web. Do not provide both `token` and `sdkVersion`.

***

### 14\_012 - The provided SDK token could not be parsed

***

### 14\_013 - For HTML Response; origin has to be provided

***

### 14\_014 - This end point requires the version to be specified

***

### 14\_015 - Token is missing

***

### 14\_016 - Invalid sdkVersion provided

***

### 14\_017 - The provided SDK Token has an invalid timestamp

***

### 14\_018 - Invalid payload provided

***

### 14\_019 - The request does not contain sdkVersion or token

***

### 14\_020 - No issuer selected

***

### 14\_022 - Missing uniqueTerminalId

***

### 14\_023 - Installments were not configured in setup request

***

### 14\_024 - Invalid open invoice request

***

### 14\_026 - The selected flow is invalid

***

### 14\_027 - The provided returnUrlQueryString is invalid

***

### 14\_028 - 3D Auth Data is incomplete

**Solution**: Provide both `PaRes` and `MD` fields.

***

### 14\_029 - CVC is required for this payment but not provided

***

### 14\_030 - Return URL is missing

***

### 14\_031 - Bank account is missing

***

### 14\_032 - Provide either threeds2.fingerprint or threeds2.challengeResult

***

### 14\_033 - The provided fingerprint is invalid

***

### 14\_034 - The provided fingerprint is invalid. Field affected: **FIELD\_NAME**

**Cause**: If the affected field is `threeDSCompIn`, the cause is that the device fingerprint is not forwarded to the `/payments/details` API call with the payment response.\
**Solution**: Check that you receive the device fingerprint data, and that you pass the data in the `/payments/details` API call.

***

### 14\_035 - 'origin' or 'notificationURL' must be provided

***

### 14\_036 - Missing required field 'channel'

***

### 14\_037 - Provided orderData is invalid

***

### 14\_0378 - Provided recurringExpiry format is invalid. Required format: yyyy-MM-dd'T'HH:mm:ssX, for example 2019-12-31T23:59:59+02:00

***

### 14\_0379 - expiresAt is greater than the allowed date, max allowed: **VALUE**

***

### 14\_0380 - PaymentData and MD belong to different requests, please submit the correct MD

***

### 14\_0381 - Missing or invalid clientKey/originKey

***

### 14\_0382 - Missing or invalid checkoutAttemptId

***

### 14\_0383 - Missing or invalid shopperStage

***

### 14\_0384 - Missing or invalid details for provided shopperStage

***

### 14\_0385 - PaymentLink is expired

***

### 14\_0386 - Hosted Session is expired

***

### 14\_0387 - PaymentLink is already paid

***

### 14\_0388 - Field 'description' is too long

***

### 14\_0389 - Pos to PayByLink QR Code is expired

***

### 14\_0390 - Missing required field 'redirectResult'

***

### 14\_0391 - Invalid redirectResult provided

When a shopper will be redirected for 3D Security authentication, provide a URL for where the shopper must be returned to after authentication is complete.

**Cause**:

* The format of the [returnUrl](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments#request-returnUrl) value is incorrect for the applicable channel (web, iOS, or Android).

**Solution**:

* Make sure that the correct format for the applicable channel is used in the `returnUrl` parameter.

***

### 14\_0392 - Payment details are incomplete. Please provide both PaRes and MD.

This error can only occur in the [authentication-only](/online-payments/3d-secure/standalone-authentication) flow.

***

### 14\_0393 - storingMethod.type **VALUE** is invalid

***

### 14\_0394 - Required field recurringProcessingModel is not provided

**Cause**:

* When creating a token to store payment details or when using stored payment details, [recurringProcessingModel](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments#request-recurringProcessingModel) is not provided.

**Solution**:

* Include the `recurringProcessingModel` parameter in the `/payments` request.

***

### 14\_0395 - Storing method is incomplete

***

### 14\_0396 - Push account receipt is invalid

***

### 14\_0397 - Order Data is expired

***

### 14\_0398 - Order Data Does Not Have Access To MerchantAccount

***

### 14\_0399 - Invalid field 'pushAccountData'

***

### 14\_0400 - The provisioning request was declined

***

### 14\_0401 - Authentication of a 3DS2 payment has failed

***

### 14\_0402 - Missing 3DS2 fingerprint

***

### 14\_0403 - Missing delegated authentication result

***

### 14\_0404 - Client data is not allowed to be passed during payment link creation.

***

### 14\_0405 - Donation token or Donation Original Psp Reference or Both are missing

***

### 14\_0406 - Parent PSP Ref missing for donation.

***

### 14\_0407 - Missing required field 'donationAccount'

***

### 14\_0408 - There are no payment methods available for the given parameters.

***

### 14\_0410 - Unable to generate a redirect url for the 3DS transaction.

***

### 14\_0411 - The gift card provided for the order has 0 balance.

***

### 14\_0412 - The field 'paymentMethod.type' is required for non-recurring payments.

***

### 14\_0413 - The 'paymentMethod.type' could not be retrieved from recurring details.

***

### 14\_0414 - The provided 3DS2 result is invalid.

***

### 14\_0415 - Missing required field 'threeDSResult'

***

### 14\_0416 - Unable to retrieve the total weight of a package.

***

### 14\_0417 - The carbon credit project id is not configured.

***

### 14\_0418 - Invalid response from the terminal or missing parameters

***

### 14\_0419 - Donation Token is expired.

***

### 14\_0420 - Both installmentOptions.values and installmentOptions.maxValue can't be specified in the request

***

### 14\_0421 - Invalid platform for Voucher Pass.

***

### 14\_0422 - The provided session identifier or data is invalid.

***

### 14\_0423 - The session has expired.

***

### 14\_0424 - A product has a negative quantity.

***

### 14\_0425 - Terminal with uniqueTerminalId '{0}' was not found

***

### 14\_0426 - Terminal with uniqueTerminalId '{0}' is not deployed

***

### 14\_0427 - Insufficient permissions for terminal with uniqueTerminalId '{0}'

***

### 14\_0428 - Merchant account is missing Pay by Link permission(s)

***

### 14\_0429 - Donations are not supported for this payment method.

***

### 14\_0430 - Provided merchant unknown

***

### 14\_0431 - Unknown terminal

***

### 14\_0432 - Unknown terminal

***

### 14\_0433 - A theme and terms of service must be configured to send emails to the shopper.

***

### 14\_0434 - An internal error occurred when sending the link to the shopper.

***

### 14\_0435 - The theme name is already in use.

***

### 14\_0436 - Field **FIELD\_NAME** is too long.

***

### 14\_0438 - A default theme must be configured for the account.

***

### 14\_0439 - This theme is default. Please select another default theme before deleting it.

***

### 14\_0444 - No terms and condtions were configured for this account.

***

### 14\_0445 - The specified theme does not exist.

***

### 14\_0446 - The file specified for the field **FIELD\_NAME** must be a valid JPG/JPEG image.

***

### 14\_0447 - no `bin` or `encryptedBin` provided.

***

### 14\_0448 - Provided paymentData and MD don't belong to the same payment.

***

### 14\_0449 - The field **FIELD\_NAME** is not supported when mode: **MODE**.

***

### 14\_0450 - The provided request cannot be processed as the session is in **STATE** state.

***

### 14\_0451 - Subset of options was not specified for field **FIELD\_NAME**.

***

### 14\_0452 - Subset of options was specified for field **FIELD\_NAME** but all options were selected.

***

### 14\_0453 - No options are expected when fillMode is empty for field **FIELD\_NAME**.

***

### 14\_0454 - Options mode was not specified for field **FIELD\_NAME**.

***

### 14\_0455 - The fill mode of the field **FIELD\_NAME** must be mandatory.

***

### 14\_0456 - Country **COUNTRY\_CODE** is invalid.

***

### 14\_0457 - Options mode for **FIELD\_NAME** should be subset.

***

### 14\_0458 - **FIELD\_NAME** with flexible validity should not contain quantity or unit.

***

### 14\_0459 - **FIELD\_NAME** with fixed validity should contain quantity and unit.

***

### 14\_0460 - The provided redirect data is invalid.

***

### 14\_0461 - The provided redirectId is invalid.

***

### 14\_0462 - The provided return query string is invalid.

***

### 14\_0463 - Invalid field 'recurringProcessingModel'

***

### 14\_0464 - The provided request cannot be processed as the sessionID in the returnURL is different from the current sessionID.

***

### 14\_0465 - Missing or invalid field 'sessionId'

***

### 14\_0466 - Invalid field 'sessionId'

***

### 14\_0467 - Missing or invalid field 'Forward-Url'

***

### 14\_0468 - Metadata value size exceeds limit

***

### 14\_0469 - Option not supported for new shopper field **FIELD\_NAME**.

***

### 14\_0470 - Invalid paymentMethodData. Contains both raw and encrypted card details.

***

### 14\_0471 - Field 'expireAfterRefusal' is not allowed.

***

### 14\_0472 - qrCodeExpiresAt is greater than the allowed date, max allowed: **VALUE**

***

### 14\_0473 - The details have expired.

***

### 14\_0474 - Klarna lineItems fields `taxAmount` and `amountExcludingTax` are missing or not valid

***

### 14\_0475 - shopperInteraction Moto not allowed due to PCI regulations

**Error details in an API response**

```json
{
   "status" : 403,
   "errorCode" : "14_0475",
   "message" : "shopperInteraction Moto not allowed due to PCI regulations.",
   "errorType" : "security",
   "pspReference" : "F7WCWRG6JPHR8HG2"
}
```

**Cause**:

* The [Mail Order/Telephone Order (MOTO)](/unified-commerce/mail-order-telephone-order) payment cannot be processed, because the PCI compliance of your MOTO integration has not been validated.

**Solution**:

* Contact our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to validate your PCI compliance and enable your MOTO integration.

***

### 14\_0476 - `amount.value` cannot be less than the `amount.value` of the original request.

***

### 14\_0477 - User is not allowed to update the shipping address

***

### 14\_0478 - Sum of selected deliveryMethod amount and original offer amount does not match the total amount.

***

### 14\_0479 - Only 1 deliveryMethod should be selected.

***

### 14\_0480 - Order can only be updated if payment is still pending.

***

### 14\_0481 - The value 'amount.currency' provided in the request does not match the `amount.currency` of the original request.

***

### 14\_0482 - Invalid parameter 'returnUrl'

***

### 14\_0483 - Invalid field 'sessionResult'

***

### 14\_0484 - Missing required field 'UPI ID / VPA'

***

### 14\_0485 - Missing exchange rate token

***

### 14\_0486 - Invalid exchange rate token

***

### 14\_0487 - Exchange rate has expired

***

### 14\_0488 - Missing required field 'shopperTaxInfo.taxId'

***

### 14\_0489 - Invalid field 'shopperTaxInfo.taxId'

***

### 14\_0490 - Transaction amount exceeds the maximum allowed amount

***

### 14\_0491 - Conflicting data found on request fields and sdkData field

***

### 14\_0492 - Invalid tax-id type for the merchant

***

### 14\_0493 - Invalid field 'paymentMethod'. UPI Collect transactions using Android are no longer supported. Please use UPI Intent or UPI QR instead.

***

### 14\_0494 - The encrypted card details in 'paymentMethod' are invalid.

## 3DS2 error codes

### 15\_002 - Required field **FIELD\_NAME** missing for device channel **DEVICE\_CHANNEL\_NAME**

***

### 15\_003 - Field **FIELD\_NAME** should not be present for device channel **DEVICE\_CHANNEL\_NAME**

***

### 15\_004 - Invalid value in field **FIELD\_NAME**

***

### 15\_005 - Unexpected field **FIELD\_NAME**

***

### 15\_006 - messageCategory shall be present

***

### 15\_007 - Value of **FIELD\_NAME** is too long (**VALUE** > **MAX\_ALLOWED\_VALUE**)

***

### 15\_008 - Invalid merchant configuration for 3DS 2.0

***

### 15\_009 - threeDS2Token is required

***

### 15\_010 - Invalid deviceChannel value. Must be 'app', 'browser' or 'TRI'.

***

### 15\_011 - pspReference is not a valid pspReference

***

### 15\_012 - Result not present

***

### 15\_013 - Cannot add 3DS2 authentication values because addRawThreeDSecureDetailsResult is not enabled

***

### 15\_014 - Invalid threeDS2Token

***

### 15\_015 - Invalid browserInfo provided

***

### 15\_016 - Language must be a valid tag according to IETF BCP47 definition

***

### 15\_017 - Cannot perform an authorisation on a 3DS2 transaction more than 12 hours after the transaction began

***

### 15\_018 - colorDepth must be 1, 4, 8, 15, 16, 24, 32 or 48 bit

***

### 15\_019 - stateOrProvince invalid

***

### 15\_020 - invalid transStatus

**Cause**: Check the `requestData`. It is likely that the `transStatus` is **Null**.\
**Solution**: Check what is being passed in the request, and check with the issuer. The `transStatus` is defined by the issuer.

***

### 15\_021 - notificationURL cannot be localhost

**Cause**: You are most likely using a custom browser implementation, and trying to test your implementation on your localhost.\
**Solution**: Deploy a public notification server if you are testing or using a browser-based 3D Secure flow.

***

### 15\_022 - invalid authenticationOnly field

***

### 15\_023 - threeDS2RequestData is not supported for threeDS2InMDFlow

**Cause**: You are most likely using a deprecated flow: you are sending in the `threeDS2RequestData` object inside the payments request, and at the same time you request the `threeDS2InMDFlow` in the `additionalData` or via your account data settings.\
**Solution**: Either remove the `threeDS2RequestData` object from the `/payments` request, or use the native flow. Do not rely on the redirect flow.

***

### 15\_024 - Result not present - Authentication older than 60 days

***

### 15\_026 - Error during 3DS authentication process

There are two possible causes for this error:

* **Cause**: When [redirecting a shopper](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/3d-secure-1/#step-2-redirect-to-the-card-issuer) to the card issuer for 3DS verification, an incorrect value is contained in the redirect form's hidden field `paReq`.\
  **Solution**: Make sure that the redirect form's hidden input field `paReq` contains the correct `paRequest` value that you get from the [/authorise](https://docs.adyen.com/api-explorer/Payment/latest/post/authorise) response.

* **Cause**: Incorrect value contained in the `paResponse` parameter of the [authorise3d](https://docs.adyen.com/api-explorer/Payment/latest/post/authorise3d) request.\
  **Solution**: When the card issuer redirects the shopper back to the merchant's website, the HTTP call contains `paRes` data that you must pass in the `paResponse` parameter of the `/authorise3d` request.

## Amazon Pay error codes

### 5\_601 - Unknown error for Amazon Pay

**Cause**: Amazon responded with errorMessage: Null.

***

### 5\_602 - Amazon Pay token doesn't exist for Amazon Pay

**Cause**: The `amazonPayToken` is missing.

***

### 5\_603 - Amazon Pay signature corrupt

***

### 5\_604 - Invalid Amazon Pay value supplied: **VALUE**

***

### 5\_605 - Could not find Merchant Private Key

**Cause**: The Encryption Key hasn't been set up on the web service user for your merchant account.

***

### 5\_606 - Amazon Pay token is not chargeable

**Cause**: The `amazonPayToken` is not correct.

***

### 5\_607 - Invalid account

***

### 5\_608 - Invalid refund status

***

### 5\_609 - Missing header fields

***

### 5\_610 - Amazon Pay is not available

***

### 5\_611 - Rejected by Amazon

***

### 5\_612 - Amazon Pay internal error

***

### 5\_613 - Amazon Pay timeout

***

### 5\_614 - Amazon Pay sent invalid response

***

### 5\_615 - Authentication Notification to Amazon Pay failed

## Apple Pay error codes

### 5\_001 - Apple Pay token amount-mismatch

**Cause**: The amount that you have configured in the Drop-in for the Apple Pay component is different from the final amount that you are sending in the `/payments` request.\
**Solution**: Make sure that the amount in the front-end mirrors the amount you send in the `/payments` request. Check that you are sending the correct [currency code and minor units](/development-resources/currency-codes#page-introduction) for that specific currency.

***

### 5\_002 - Invalid Apple Pay token

**Cause**: Your web service user and/or merchant account set up is incorrect.

***

### 5\_003 - Incorrect Apple Pay token version

**Cause**: There is an Apple Pay version mismatch. You may have to regenerate your token and set up your web service user again.

***

### 5\_004 - Could not find Merchant Private Key

**Cause**: The CSR is not valid, you most likely provided a different certificate compared to the certificate that is registered on the Apple Pay developer portal.\
**Solution**: Do the PEM certificate exchange flow again, and provide the same certificate.

***

### 5\_005 - Could not find Merchant Public Key

**Cause**: The CSR is not valid, you most likely provided a different certificate compared to the certificate that is registered on the Apple Pay developer portal.\
**Solution**: Do the PEM certificate exchange flow again, and provide the same certificate.

***

### 5\_006 - Apple Pay signature corrupt

**Cause**: There is a signature mismatch, the signature cannot be read.

***

### 5\_007 - Missing certificate for Apple Pay signature

**Cause**: The signature is empty, there is no certificate or the certificate is missing.\
**Solution**: Set up the web service user again, and configure the Apple Pay token.

***

### 5\_008 - Our Test system does not accept Live tokens

## Google Pay error codes

### 5\_202 - Invalid Google Pay token

**Cause**:

* You are not passing the correct token, or there is an incorrect merchant account in the request data.
* Incorrect payment method MID setup.
* Android App not registered with Google in case of Android integration.

**Solution**: Make sure that you are sending in the correct token. Do not escape the stringified JSON; send it as it is.

***

### 5\_208 - Google Pay token already expired

**Cause**: The token expired. Troubleshoot with Google, as the error is mapped directly with the Google response.

***

### 5\_210 - Google Pay token already used

**Cause**: The data in the token that you sent has been used before and cannot be reused.\
**Solution**: Make sure that you use a new Google Pay token for each shopper initiated transaction.

## Network token error codes

### 26\_002 - The network token is suspended/deactivated

***

### 26\_003 - The detokenization request has been declined

**Cause**: Adyen's request to the scheme to fetch the cryptogram for the network token was declined.

***

### 26\_004 - The network token PAN is missing

**Cause**: No [Primary Account Number (PAN)](/get-started-with-adyen/adyen-glossary#card-number-pan) was found for the network token.

***

### 26\_005 - The network token is not active yet

***

### 26\_006 - The network token is not found

**Cause**: No network token was found to complete the payment. This might be caused, for example, because the network token was deleted.

***

### 26\_007 - The detokenization request timed out

**Cause**: Adyen's request to the scheme to fetch the cryptogram for the network token timed out.

***

### 26\_008 - **PARAMETER\_NAME**

**Cause**: One or more of the required fields for the request is missing. The missing fields are returned in the error message.\
**Solution**: Add the missing fields to your request and try again.

***

### 26\_010 - Unsupported variant for network tokenization: **VALUE**

***

### 6\_012 - The tokenization request timed out

***

### 26\_017 - Operation **ACTION** is not allowed for network token

**Cause**: The attempted action is not allowed for this network token. **ACTION** can be **Delete**, **Suspend**, or **Resume**.

***

### 26\_020 - The detokenization request failed

**Cause**: Adyen's request to the scheme to fetch the cryptogram for the network token failed.

## See also

* [HTTP status codes](/development-resources/response-handling/)
