{"title":"User capabilities","category":"default","creationDate":1791543439,"content":"

A capability is an action that a user can perform in your platform, for example, receiving payments.<\/p>\n

In most cases, Adyen configures default capabilities for your business during the design phase<\/a>. These capabilities are automatically requested for your users when you create merchant accounts<\/a> for them. If a user needs a specific capability that is not part of their default configuration, you must request the additional capability.<\/p>\n

\n

It is possible that requesting additional capabilities prompts additional KYC checks<\/a> on your users.<\/p>\n<\/div>\n

Depending on your settings, capabilities are requested automatically for new merchant accounts, or you have to request them separately when needed.<\/p>\n\n\n\n\n\n\n
Name<\/div><\/th>\n
Description<\/div><\/th>\n<\/tr>\n<\/thead>\n
receivePayments<\/strong><\/span><\/td>\nAllows users to process and receive payments using a payment method.<\/td>\n<\/tr>\n
sendToTransferInstrument<\/strong><\/span><\/td>\nAllows users to transfer funds to verified bank accounts. For example, when paying out to your users.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Verification status of a capability<\/h2>\n

The verification status of a capability indicates whether a user has passed KYC checks<\/a> and meets requirements to use a specific capability.<\/p>\n

To get updates about the verification status of a capability, you should listen to merchant.created<\/a> and merchant.updated<\/a> webhooks.<\/p>\n

Here are the possible values for the capability verification status.<\/p>\n\n\n\n\n\n\n\n\n
Status<\/div><\/th>\n
Description<\/div><\/th>\n<\/tr>\n<\/thead>\n
pending<\/code><\/a><\/td>\nThe pending<\/code> status indicates that the verification is in progress. <\/br><\/br> At this verification phase, a capability requested for the first time is set to \n requested<\/code>\n<\/a>: true<\/strong><\/span> and \n allowed<\/code>\n<\/a>: false<\/strong><\/span>. <\/br><\/br>If the capability has already been allowed, but some user data has changed<\/a> and needs to be verified, you may see that the capability verification status is pending<\/code> and the capability is \n allowed<\/code>\n<\/a>: true<\/strong><\/span>. This means that the user is still allowed to use capability while Adyen performs the checks.<\/td>\n<\/tr>\n
valid<\/code><\/a><\/td>\nThe valid<\/code> status indicates that the verification is successfully completed and that the user meets the requirements to use a capability. <\/br><\/br> With this verification status, the user can use the capability. Adyen sets the capability to \n allowed<\/code>\n<\/a>: true<\/strong><\/span>.<\/td>\n<\/tr>\n
invalid<\/code><\/a><\/td>\nThe invalid<\/code> 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<\/a> object, including the verificationErrors<\/code>, subErrors<\/code>, and remediatingActions<\/code> arrays returned on the linked legal entity. If there are verification errors, you must resolve them. <\/br><\/br> With this verification status, Adyen sets the capability to \n allowed<\/code>\n<\/a>: false<\/strong><\/span>. This means the user is not permitted to use the capability until all verification errors are resolved and the verification process is completed successfully. <\/br><\/br> If any user data changes or is missing<\/a> after the previous verification has been completed successfully, Adyen reverts the capability verification status to invalid<\/code>. 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 \n allowed<\/code>\n<\/a>: true<\/strong><\/span>.<\/td>\n<\/tr>\n
rejected<\/code><\/a><\/td>\nThe rejected<\/code> 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. <\/br><\/br> With this verification status, Adyen prohibits the user from performing the action and sets the capability to \n allowed<\/code>\n<\/a>: false<\/strong><\/span>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Capability settings<\/h2>\n

The settings of a capability determine if it is available to a user and they can use it.<\/p>\n

To get updates about the capability settings, you should listen to merchant.created<\/a> and merchant.updated<\/a> webhooks.<\/p>\n\n\n \n \n \n
Setting<\/th>\n Possible\u00a0values<\/th>\n Description<\/th>\n <\/tr>\n<\/thead>\n
\n

requested<\/code><\/a><\/p>\n<\/td>\n

\n

true<\/strong><\/span>, false<\/strong><\/span><\/p>\n<\/td>\n

\n \n \n \n \n
\n

true<\/strong><\/span>: the capability has been requested. Default capabilities are requested automatically when you create a merchant account<\/a>. <\/p>\n<\/td>\n <\/tr>\n

\n

false<\/strong><\/span>: the capability has not been requested yet.<\/p>\n<\/td>\n <\/tr>\n <\/table>\n<\/td>\n<\/tr>\n

\n

allowed<\/code><\/a><\/p>\n<\/td>\n

\n

true<\/strong><\/span>, false<\/strong><\/span><\/p>\n<\/td>\n

\n \n \n \n \n
\n

true<\/strong><\/span>: the verification is successful<\/a> and the user is permitted to use the capability. The capability can only be used when it is both allowed and enabled.

In some scenarios, such as when a user changes their information<\/a>, the capability is set to true<\/strong><\/span> while the verification status is \n pending<\/code>\n<\/a> or \n invalid<\/code>\n<\/a>. The user must provide updated information within the given deadline. During the deadline, the user can still use the capability while Adyen verifies the data.<\/p>\n<\/td>\n <\/tr>\n

\n

false<\/strong><\/span>: the verification is \n pending<\/code>\n<\/a>, \n invalid<\/code>\n<\/a>, or \n rejected<\/code>\n<\/a>. The user is not permitted to use the capability.<\/p>\n<\/td>\n <\/tr>\n <\/table>\n <\/td>\n <\/tr>\n

\n

enabled<\/code><\/a><\/p>\n<\/td>\n

\n

true<\/strong><\/span>, false<\/strong><\/span><\/p>\n<\/td>\n

\n

This setting allows you to manage your users\u2019 access to capabilities. Changing this setting does not trigger verification checks or prevent a capability from being requested.

Note that this capability can only be used if it is both enabled and allowed.

Set to true<\/strong><\/span> to offer the capability to the user. Set to false<\/strong><\/span> to prevent them from using the capability.<\/p>\n<\/td>\n <\/tr>\n<\/tbody>\n<\/table>","url":"https:\/\/docs.adyen.com\/managed-model\/verification-overview\/capabilities","articleFields":{"description":"Learn what capabilities your users can have in your platform","feedback_component":true,"cache_enable":false,"filters_component":false,"parameters":{"directoryPath":"\/managed-model","integrationType":"managed"}},"algolia":{"url":"https:\/\/docs.adyen.com\/managed-model\/verification-overview\/capabilities","title":"User capabilities","content":"A capability is an action that a user can perform in your platform, for example, receiving payments.\nIn most cases, Adyen configures default capabilities for your business during the design phase. These capabilities are automatically requested for your users when you create merchant accounts for them. If a user needs a specific capability that is not part of their default configuration, you must request the additional capability.\n\nIt is possible that requesting additional capabilities prompts additional KYC checks on your users.\n\nDepending on your settings, capabilities are requested automatically for new merchant accounts, or you have to request them separately when needed.\n\n\n\nName\nDescription\n\n\n\n\nreceivePayments\nAllows users to process and receive payments using a payment method.\n\n\nsendToTransferInstrument\nAllows users to transfer funds to verified bank accounts. For example, when paying out to your users.\n\n\n\nVerification status of a capability\nThe verification status of a capability indicates whether a user has passed KYC checks and meets requirements to use a specific capability.\nTo get updates about the verification status of a capability, you should listen to merchant.created and merchant.updated webhooks.\nHere are the possible values for the capability verification status.\n\n\n\nStatus\nDescription\n\n\n\n\npending\nThe pending status indicates that the verification is in progress. At this verification phase, a capability requested for the first time is set to \n requested\n: true and \n allowed\n: 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 \n allowed\n: true. This means that the user is still allowed to use capability while Adyen performs the checks.\n\n\nvalid\nThe 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 \n allowed\n: true.\n\n\ninvalid\nThe 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 \n allowed\n: 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 \n allowed\n: true.\n\n\nrejected\nThe 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 \n allowed\n: false.\n\n\n\nCapability settings\nThe settings of a capability determine if it is available to a user and they can use it.\nTo get updates about the capability settings, you should listen to merchant.created and merchant.updated webhooks.\n\n\n \n Setting\n Possible\u00a0values\n Description\n \n\n\n \n \nrequested\n\n \ntrue, false\n\n \n \n \n \ntrue: the capability has been requested. Default capabilities are requested automatically when you create a merchant account. \n\n \n \n \nfalse: the capability has not been requested yet.\n\n \n \n\n\n \n \nallowed\n\n \ntrue, false\n\n \n \n \n \ntrue: the verification is successful and the user is permitted to use the capability. The capability can only be used when it is both allowed and enabled. In some scenarios, such as when a user changes their information, the capability is set to true while the verification status is \n pending\n or \n invalid\n. The user must provide updated information within the given deadline. During the deadline, the user can still use the capability while Adyen verifies the data.\n\n \n \n \nfalse: the verification is \n pending\n, \n invalid\n, or \n rejected\n. The user is not permitted to use the capability.\n\n \n \n \n \n \n \nenabled\n\n \ntrue, false\n\n \nThis setting allows you to manage your users\u2019 access to capabilities. Changing this setting does not trigger verification checks or prevent a capability from being requested. Note that this capability can only be used if it is both enabled and allowed. Set to true to offer the capability to the user. Set to false to prevent them from using the capability.\n\n \n\n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Adyen for Platforms - Managed model","lvl2":"Verification process","lvl3":"User capabilities"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/managed-model","lvl2":"https:\/\/docs.adyen.com\/managed-model\/verification-overview","lvl3":"\/managed-model\/verification-overview\/capabilities"},"levels":4,"category":"","category_color":"","tags":["capabilities"]}}