---
title: "Validation"
url: "https://docs.adyen.com/errors/validation"
source_url: "https://docs.adyen.com/errors/validation.md"
canonical: "https://docs.adyen.com/errors/validation"
last_modified: "2023-03-20T13:56:00+01:00"
language: "en"
---

# Validation

[View source](/errors/validation.md)

## 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](https://docs.adyen.com/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\_014 - Account holder closed

**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\_015 - Account holder suspended

**Cause**: The account holder is suspended so all capabilities are blocked.\
**Solution**: Activate the account holder to unblock its capabilities and allow modifications to its underlying resources before retrying any request related to associated balance accounts.

***

### 30\_016 - Account misses capabilities

**Cause**: The account holder is missing required capabilities or capabilities are blocked.\
**Solution**: Check the `detail` parameter for the specific validation error, request the missing capability, upload any missing documents to enable the required capability, 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\_121 - Invalid pagination values for request that requires pagination

**Cause:** The pagination parameters are invalid.\
**Solution:** Check the `offset` and `limit` parameters. The values must be greater than or equal to zero.

***

### 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.

***

### 31\_010 - The request is missing required fields or contains invalid data

**Cause**: The request does not include the required data to process this request or the request cannot be processed because the underlying data cannot be modified via this request.\
**Solution**: Check the underlying resources associated to the data included in the request, 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.