Add the required fields or make sure that the data is valid and in the right format.<\/li>\n<\/ul>\nError codes<\/h2>\n
Find the specific cause and solution for each error code.<\/p>\n
30_001 - Invalid Balance Platform information provided<\/h3>\n
Cause<\/strong>: The balance platform ID is incorrect.
\nSolution<\/strong>: Check the balance platform ID, update the request, and try again.<\/p>\n
\n30_003 - Balance platform not active<\/h3>\n
Cause<\/strong>: The balance platform in the request is not active.
\nSolution<\/strong>: Check the balance platform ID, update the request, and try again.<\/p>\n
\n30_004 - Balance account not active<\/h3>\n
Cause<\/strong>: The balance account in the request is not active.
\nSolution<\/strong>: Check and make sure the balance account in the request is active, update the request, and try again.<\/p>\n
\n30_005 - Balance account closed<\/h3>\n
Cause<\/strong>: The request cannot be performed because the balance account in the request is already closed.
\nSolution<\/strong>: None. A closed balance account can no longer be used.<\/p>\n
\n30_006 - Cannot close Account Holder because of non-closed balance accounts<\/h3>\n
Cause<\/strong>: The request cannot be performed because the account holder has balance accounts that are not closed.
\nSolution<\/strong>: Close the account holder's balance accounts then try again.<\/p>\n
\n30_007 - Account Holder not active<\/h3>\n
Cause<\/strong>: The request cannot be performed because the account holder status is not active.
\nSolution<\/strong>: If possible, change the status of the account holder to active and try again.<\/p>\n
\n30_011 - Invalid Account Holder information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_014 - Account holder closed<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_015 - Account holder suspended<\/h3>\n
Cause<\/strong>: The account holder is suspended so all capabilities are blocked.
\nSolution<\/strong>: Activate the account holder to unblock its capabilities and allow modifications to its underlying resources before retrying any request related to associated balance accounts.<\/p>\n
\n30_016 - Account misses capabilities<\/h3>\n
Cause<\/strong>: The account holder is missing required capabilities or capabilities are blocked.
\nSolution<\/strong>: Check the detail<\/code> parameter for the specific validation error, request the missing capability, upload any missing documents to enable the required capability, and try again.<\/p>\n
\n30_021 - Invalid Balance Account information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_022 - Invalid sweep configuration information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_023 - Balance Account has open balances<\/h3>\n
Cause<\/strong>: The request cannot be performed because the balance account has available balances.
\nSolution<\/strong>: Transfer available balances then try again.<\/p>\n
\n30_031 - Invalid Payment Instrument information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_041 - Invalid Payment Instrument Group information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_051 - Invalid Card Manufacturing information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_061 - Invalid Transaction Rule information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields for a transaction rule resource, contains invalid data, or failed our rule logic validation.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_072 - Invalid Public Key information<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_074 - Invalid pin reveal information<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_075 - Invalid pin change information<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_081 - Invalid transfer information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_091 - Invalid claim information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_101 - Invalid chargeback information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_102 - Invalid legal entity information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_103 - Invalid legal entity relation information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_104 - Invalid business line information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n30_121 - Invalid pagination values for request that requires pagination<\/h3>\n
Cause:<\/strong> The pagination parameters are invalid.
\nSolution:<\/strong> Check the offset<\/code> and limit<\/code> parameters. The values must be greater than or equal to zero.<\/p>\n
\n30_131 - Invalid onboarding link information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n31_003 - Invalid webhook information provided<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n31_004 - Invalid allowed origin information provided<\/h3>\n
Cause<\/strong>: The request contains invalid data or the user does not have access.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n31_005 - Invalid merchant information provided<\/h3>\n
Cause<\/strong>: The request contains invalid data or the user does not have access.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n31_006 - Invalid API Credential information provided<\/h3>\n
Cause<\/strong>: The request contains invalid data or the user does not have access.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n31_007 - Invalid user information provided<\/h3>\n
Cause<\/strong>: The request contains invalid data or the user does not have access.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n31_010 - The request is missing required fields or contains invalid data<\/h3>\n
Cause<\/strong>: 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.
\nSolution<\/strong>: Check the underlying resources associated to the data included in the request, update the request, and try again.<\/p>\n
\n32_001 - Invalid parameters<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>\n
\n33_008 - Invalid parameters<\/h3>\n
Cause<\/strong>: The request is missing required fields or required query parameters, or contains invalid data.
\nSolution<\/strong>: Check the requirements, update the request, and try again. For example:<\/p>\n\n- To get a terminal logo, the
model<\/code> query parameter is required if you are not sending the request to a specific payment terminal.<\/li>\n- To add a terminal logo, the logo size must not be too large for the terminal model.<\/li>\n<\/ul>\n
\n33_009 - Invalid parameters<\/h3>\n
Cause<\/strong>: The request is missing required fields or contains invalid data.
\nSolution<\/strong>: Check the invalidFields<\/code> array for the specific validation error, update the request, and try again.<\/p>","url":"https:\/\/docs.adyen.com\/pt\/errors\/validation","articleFields":{"id":"47485174","robots":"index,follow","type":"page","_expandable":{"operations":""},"status":"current","last_edit_on":"20-03-2023 13:56","feedback_component":true,"filters_component":false,"page_id":"ffa597a2-dccf-4d7d-a537-a3fb306e1974","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/errors\/validation","title":"Validation","content":"Cause\nAdyen APIs return a validation error when:\n\nThe request is missing required fields.\nThe request contains invalid data.\nThe 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.\n\nSolution\nTo resolve a validation error:\n\nCheck 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\nFind the required fields, format, and supported values on API Explorer.\nAdd the required fields or make sure that the data is valid and in the right format.\n\nError codes\nFind the specific cause and solution for each error code.\n30_001 - Invalid Balance Platform information provided\nCause: The balance platform ID is incorrect.\nSolution: Check the balance platform ID, update the request, and try again.\n\n30_003 - Balance platform not active\nCause: The balance platform in the request is not active.\nSolution: Check the balance platform ID, update the request, and try again.\n\n30_004 - Balance account not active\nCause: The balance account in the request is not active.\nSolution: Check and make sure the balance account in the request is active, update the request, and try again.\n\n30_005 - Balance account closed\nCause: The request cannot be performed because the balance account in the request is already closed.\nSolution: None. A closed balance account can no longer be used.\n\n30_006 - Cannot close Account Holder because of non-closed balance accounts\nCause: The request cannot be performed because the account holder has balance accounts that are not closed.\nSolution: Close the account holder's balance accounts then try again.\n\n30_007 - Account Holder not active\nCause: The request cannot be performed because the account holder status is not active.\nSolution: If possible, change the status of the account holder to active and try again.\n\n30_011 - Invalid Account Holder information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_014 - Account holder closed\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_015 - Account holder suspended\nCause: The account holder is suspended so all capabilities are blocked.\nSolution: Activate the account holder to unblock its capabilities and allow modifications to its underlying resources before retrying any request related to associated balance accounts.\n\n30_016 - Account misses capabilities\nCause: The account holder is missing required capabilities or capabilities are blocked.\nSolution: 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.\n\n30_021 - Invalid Balance Account information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_022 - Invalid sweep configuration information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_023 - Balance Account has open balances\nCause: The request cannot be performed because the balance account has available balances.\nSolution: Transfer available balances then try again.\n\n30_031 - Invalid Payment Instrument information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_041 - Invalid Payment Instrument Group information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_051 - Invalid Card Manufacturing information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_061 - Invalid Transaction Rule information provided\nCause: The request is missing required fields for a transaction rule resource, contains invalid data, or failed our rule logic validation.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_072 - Invalid Public Key information\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_074 - Invalid pin reveal information\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_075 - Invalid pin change information\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_081 - Invalid transfer information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_091 - Invalid claim information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_101 - Invalid chargeback information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_102 - Invalid legal entity information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_103 - Invalid legal entity relation information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_104 - Invalid business line information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n30_121 - Invalid pagination values for request that requires pagination\nCause: The pagination parameters are invalid.\nSolution: Check the offset and limit parameters. The values must be greater than or equal to zero.\n\n30_131 - Invalid onboarding link information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n31_003 - Invalid webhook information provided\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n31_004 - Invalid allowed origin information provided\nCause: The request contains invalid data or the user does not have access.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n31_005 - Invalid merchant information provided\nCause: The request contains invalid data or the user does not have access.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n31_006 - Invalid API Credential information provided\nCause: The request contains invalid data or the user does not have access.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n31_007 - Invalid user information provided\nCause: The request contains invalid data or the user does not have access.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n31_010 - The request is missing required fields or contains invalid data\nCause: 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.\nSolution: Check the underlying resources associated to the data included in the request, update the request, and try again.\n\n32_001 - Invalid parameters\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.\n\n33_008 - Invalid parameters\nCause: The request is missing required fields or required query parameters, or contains invalid data.\nSolution: Check the requirements, update the request, and try again. For example:\n\nTo get a terminal logo, the model query parameter is required if you are not sending the request to a specific payment terminal.\nTo add a terminal logo, the logo size must not be too large for the terminal model.\n\n\n33_009 - Invalid parameters\nCause: The request is missing required fields or contains invalid data.\nSolution: Check the invalidFields array for the specific validation error, update the request, and try again.","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Errors","lvl2":"Validation"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/errors","lvl2":"\/pt\/errors\/validation"},"levels":3,"category":"","category_color":"","tags":["Validation"]}}