Update an account holder
Updates an account holder. When updating an account holder resource, if a parameter is not provided in the request, it is left unchanged.
The unique identifier of the account holder.
The unique identifier of the balance platform to which the account holder belongs. Required in the request if your API credentials can be used for multiple balance platforms.
Contains key-value pairs that specify the actions that an account holder can do in your platform. The key is a capability required for your integration. For example, issueCard for Issuing. The value is an object containing the settings for the capability.
Contact details of the account holder.
Your description for the account holder, maximum 300 characters.
The unique identifier of the legal entity associated with the account holder. Adyen performs a verification process against the legal entity of the account holder.
The ID of the account holder's primary balance account. By default, this is set to the first balance account that you create for the account holder. To assign a different balance account, send a PATCH request.
Your reference for the account holder, maximum 150 characters.
The status of the account holder.
Possible values:
-
Active: The account holder is active. This is the default status when creating an account holder.
-
Inactive: The account holder is temporarily inactive due to missing KYC details. You can set the account back to active by providing the missing KYC details.
-
Suspended: The account holder is permanently deactivated by Adyen. This action cannot be undone.
-
Closed: The account holder is permanently deactivated by you. This action cannot be undone.
The time zone of the account holder. For example, Europe/Amsterdam. Defaults to the time zone of the balance platform if no time zone is set. For possible values, see the list of time zone codes.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
200 - OK
The request has succeeded.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.
500 - Internal Server Error
The server could not process the request.