A capability is an action that a user can perform in your platform, for example, receiving payments.
In most cases, Adyen configures default capabilities for your business during the design phase. These capabilities are automatically requested for your users when you create account holders for them. If a user needs a specific capability that is not part of their default configuration, you must request the additional capability.
It is possible that requesting additional capabilities prompts additional KYC checks on your users.
Capabilities
Depending on your settings, capabilities are requested automatically for new account holders, or you have to request them separately when needed.
Capability name |
Display name in Customer Area |
Description |
|
|---|---|---|---|
| receiveFromBalanceAccount | Receive funds from balance accounts | Allows users to receive funds from other balance accounts in your platform. This capability is only required if the balance accounts are not under the same account holder. | |
| receiveFromTransferInstrument | Receive funds from transfer instruments | Allows users to receive funds from verified bank accounts. This capability is only required if the account holder uses the top-up balance account feature. Requesting this capability triggers upfront verification. | |
| receiveFromPlatformPayments | Receive funds from split payments | Allows users to receive funds from split payments. | |
| receivePayments | Receive payments | Allows users to receive payments using a payment method. | |
| sendToBalanceAccount | Send funds to balance accounts | Allows users to transfer funds to other balance accounts in your platform. This capability is only required if the balance accounts are not under the same account holder. | |
| sendToTransferInstrument | Send funds to transfer instruments | Allows users to transfer funds to verified bank accounts. For example, when paying out to your users. |
Financial product capabilities
If your business offers financial products, your users can access additional capabilities related to the respective financial products.
The following tabs show the capabilities corresponding for each financial product, with corresponding names in the Customer Area and the API. Depending on your capability settings, these capabilities are either requested automatically for new account holders, or you have to request them separately when needed.
Verification status of a capability
Verification status of a capability indicates whether a user has passed KYC checks and meets requirements to use a specific capability. To get updates about the verification status of a capability, you can:
- Listen to balancePlatform.accountHolder.created and balancePlatform.accountHolder.updated webhooks
- Make a GET /accountHolders/{id} request
Here are the possible values for the capability verification status.
Status |
Description |
|---|---|
pending |
The pending status indicates that the verification is in progress. At this verification phase, a capability requested for the first time is set to
requested
: true and
allowed
: false. If the capability has already been allowed, but some user data has changed and needs to be verified, you may see that the capability verification status is pending and the capability is
allowed
: true. This means that the user is still allowed to use capability while Adyen performs the checks. |
valid |
The valid status indicates that the verification is successfully completed and that the user meets the requirements to use a capability. With this verification status, the user can use the capability. Adyen sets the capability to
allowed
: true. |
invalid |
The invalid status indicates that the verification failed, for example due to incorrect information or missing documents. In this case, the webhook or the API response contains the problems object, including the verificationErrors, subErrors, and remediatingActions arrays returned on the linked legal entity. If there are verification errors, you must resolve them. With this verification status, Adyen sets the capability to
allowed
: false. This means the user is not permitted to use the capability until all verification errors are resolved and the verification process is completed successfully. If any user data changes or is missing after the previous verification has been completed successfully, Adyen reverts the capability verification status to invalid. In such a scenario, the user must provide the necessary information within a specific deadline. During this period, the user can continue using the capability, and its setting remains as
allowed
: true. |
rejected |
The rejected status indicates that Adyen completed verification, but the user does not meet the requirements to use a capability based on the submitted information. This status is final and any errors cannot be resolved by updating data or uploading documents. With this verification status, Adyen prohibits the user from performing the action and sets the capability to
allowed
: false. |
Capability settings
The settings of a capability determine if it is available to a user and they can use it. To get updates about the capability settings, you can:
- Listen to balancePlatform.accountHolder.created and balancePlatform.accountHolder.updated webhooks
- Make a GET /accountHolders/{id} request. The API response contains the capabilities object that shows whether the capability is
requested,allowed, andenabled. Below are the explanations for each setting.
| Setting | Possible values | Description | ||
|---|---|---|---|---|
|
true, false |
|
|||
|
true, false |
|
|||
|
true, false |
This setting allows you to manage your users’ access to capabilities. Changing this setting does not trigger verification checks or prevent a capability from being requested. |