Validation

Cause

Adyen APIs return a validation error when:

• The request is missing required fields.
• The request contains invalid data.
• The request cannot be performed because the operation failed validation. For example, a request to close a balance account cannot be performed if a balance account has an available balance.

Solution

To resolve a validation error:

• Check the invalidFields array for the field name and the validation error message. The message provides solutions to fix the error. For example, Invalid date value provided. Expected format yyyy-MM-dd
• Find the required fields, format, and supported values on API Explorer.
• Add the required fields or make sure that the data is valid and in the right format.

Error codes

Find the specific cause and solution for each error code.

30_001 - Invalid Balance Platform information provided

Cause: The balance platform ID is incorrect.
Solution: Check the balance platform ID, update the request, and try again.

---

30_003 - Balance platform not active

Cause: The balance platform in the request is not active.
Solution: Check the balance platform ID, update the request, and try again.

---

30_004 - Balance account not active

Cause: The balance account in the request is not active.
Solution: Check and make sure the balance account in the request is active, update the request, and try again.

---

30_005 - Balance account closed

Cause: The request cannot be performed because the balance account in the request is already closed.
Solution: None. A closed balance account can no longer be used.

---

30_006 - Cannot close Account Holder because of non-closed balance accounts

Cause: The request cannot be performed because the account holder has balance accounts that are not closed.
Solution: Close the account holder's balance accounts then try again.

---

30_007 - Account Holder not active

Cause: The request cannot be performed because the account holder status is not active.
Solution: If possible, change the status of the account holder to active and try again.

---

30_011 - Invalid Account Holder information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_021 - Invalid Balance Account information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_022 - Invalid sweep configuration information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_023 - Balance Account has open balances

Cause: The request cannot be performed because the balance account has available balances.
Solution: Transfer available balances then try again.

---

30_031 - Invalid Payment Instrument information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_041 - Invalid Payment Instrument Group information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_051 - Invalid Card Manufacturing information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_061 - Invalid Transaction Rule information provided

Cause: The request is missing required fields for a transaction rule resource, contains invalid data, or failed our rule logic validation.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_072 - Invalid Public Key information

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_074 - Invalid pin reveal information

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_075 - Invalid pin change information

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_081 - Invalid transfer information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_091 - Invalid claim information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_101 - Invalid chargeback information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_102 - Invalid legal entity information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_103 - Invalid legal entity relation information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_104 - Invalid business line information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_131 - Invalid onboarding link information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

30_131 - Invalid onboarding link information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

31_003 - Invalid webhook information provided

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

31_004 - Invalid allowed origin information provided

Cause: The request contains invalid data or the user does not have access.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

31_005 - Invalid merchant information provided

Cause: The request contains invalid data or the user does not have access.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

31_006 - Invalid API Credential information provided

Cause: The request contains invalid data or the user does not have access.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

31_007 - Invalid user information provided

Cause: The request contains invalid data or the user does not have access.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

32_001 - Invalid parameters

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.

---

33_008 - Invalid parameters

Cause: The request is missing required fields or required query parameters, or contains invalid data.
Solution: Check the requirements, update the request, and try again. For example:

• To get a terminal logo, the model query parameter is required if you are not sending the request to a specific payment terminal.
• To add a terminal logo, the logo size must not be too large for the terminal model.

---

33_009 - Invalid parameters

Cause: The request is missing required fields or contains invalid data.
Solution: Check the invalidFields array for the specific validation error, update the request, and try again.