No momento, esta página não está disponível em português
Issuin icon

Manage account holders

Learn how to manage account holders on your platform.

Here we explain how to manage your account holders and what they can do in your platform.

View account holders

To view account holder details, you can either make an API request or use your Balance Platform Customer Area. The following tabs explain both methods.

To get account holders, use the following endpoints:

View KYC summary and timeline

You can view information about the verification process for account holders in your issuing. This includes an overview of the current verification status for associated legal entities and a timeline of KYC-related events. You can use this information to help your users troubleshoot issues they experience during the onboarding process.

  1. In your Balance Platform Customer Area, go to Accounts & balances > Account holders.
  2. On the Account holders page, select Search at the top right corner to search by account holder ID, reference, legal entity ID or name.
  3. In the search window, select View account holder to open the Account holder details page.
  4. Select KYC timeline.

The KYC summary section shows the current status of the KYC checks separated by the type of check, for example Identity. If there are multiple legal entities linked to the account holder, the type of each legal entity is specified, for example Individual.

Here are possible values of the KYC verification status of the legal entity.

Verification status
Awaiting data The KYC information for the legal entity has not yet been submitted.
In review The KYC information for the legal entity is being reviewed by Adyen.
Verified The KYC verification checks for the legal entity have passed.
Unsuccessful The KYC verification checks for the legal entity have failed. For example, because of an invalid document or ID number.
Review the KYC Timeline for more information about the verification errors and recommended remediating actions. To be verified, all the errors must be resolved.
Rejected The legal entity has been rejected by Adyen. For example, because the organization is in a sanctions list.
This status is final and any errors cannot be resolved by updating data or uploading documents.

To view more detailed information about the order of the KYC checks and events that affected the verification process, look at the KYC timeline. You can filter events by the type of check, legal entity ID, and legal entity name. The timeline also includes any verification errors and the corresponding remediating action codes.

View capabilities

View an account holder's capabilities and their verification status in your Balance Platform Customer Area or by making a GET /accountHolders/{id} request. The following tabs explain both methods.

When you make a GET /accountHolders/{id} request, refer to the following response parameters in the capabilities object:

  • allowed: Boolean that indicates whether the capability is allowed.
  • verificationStatus: The status of the checks. The possible values are invalid, pending, rejected, or valid.
  • problems array: When this array is not empty, this means that there are errors that you need to address. Refer to verification error codes for a list of verification errors.

Request a capability

Some capabilities are automatically requested when you create an account holder However, your account holders may need additional capabilities if, for example, your business expands its financial product offering. In these cases, you must request the additional capabilities.

The following tabs show how to request a capability.

Default capabilities are automatically requested when you create an account holder. However, if you need to request a specific capability, you must update the account holder and include the capabilities map.

In your PATCH /accountHolders/{id} request, set the capability that you are requesting as the key, and specify the following fields in the object:

Here is an example of how to update an existing account holder to request the withdrawFromAtm capability with level medium. If you're requesting for multiple capabilities, add another set of key-value object.

You receive a response informing you that the capability has been requested and the verification status is pending.

Enable or disable a capability

To allow or prevent an account holder from using a capability, update the capability in your Balance Platform Customer Area or request a PATCH /accountHolders/{id}. The following tabs explain both methods.

To disable a capability, make a PATCH /accountHolders/{id} request to update the capability. Set the enabled field to false.

Update an account holder

After you create an account holder resource, you might need to update the resource at a later time. For example, an account holder that has several balance accounts might want to change their primary balance account.

To update an account holder, make a PATCH /accountHolders/{id} request.

The example below shows how you can change the primary balance account of an account holder by sending the primaryBalanceAccount field.

Permanently deactivate account holders and their balance accounts

When an account holder discontinues their business, you can permanently deactivate them from your issuing.

In some scenarios, you might also want to close a balance account but keep the account holder active. For example, an account holder that has separate balance accounts for their businesses might want to only close one of their businesses.

To close balance accounts and account holders:

  1. Check if they have zero balance in their balance accounts. You can only close empty balance accounts, so if there are funds left, transfer any remaining balance.
  2. Close balance accounts by updating each balance account and setting the status to Closed. Start with those that are not the primary balance account. You can only close a primary balance account if the account holder's other balance accounts are already closed.
  3. Finally, permanently deactivate the account holder by updating the account holder and setting the status to Closed.