{"title":"User capabilities","category":"default","creationDate":1671721620,"content":"<p>Every account holder has a list of capabilities that determine what they can do on your platform. You can edit a <a href=\"#capability-settings\">capability's settings<\/a> to change which actions the account holder has permission to do, for example, receive payments, send funds to a bank account, or <a href=\"#financial-product-capabilities\">use certain financial products<\/a>.<\/p>\n<p>In most cases, Adyen configures default capabilities for your business during the <a href=\"\/pt\/issuing\/get-started#design-implementation\">design phase<\/a>. 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 <a href=\"\/pt\/issuing\/manage-account-holders#request-capability\">request the additional capability<\/a>. <\/p>\n<div class=\"notices green\">\n<p>It is possible that requesting additional capabilities prompts additional <a href=\"\/pt\/issuing\/verification-overview\">KYC checks<\/a> on your users. <\/p>\n<\/div>\n<h2>General capabilities<\/h2>\n<p>Depending on your settings, capabilities are requested automatically for new account holders, or you have to request them separately when needed.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><div style=\"width:150px\">Capability name<\/div><\/th>\n<th style=\"text-align: left;\"><div style=\"width:250px\">Display name in Customer Area<\/div><\/th>\n<th style=\"text-align: left;\"><div style=\"width:50px\">Description<\/div><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>receiveFromBalanceAccount<\/strong><\/td>\n<td style=\"text-align: left;\">Receive funds from balance accounts<\/td>\n<td style=\"text-align: left;\">Allows users to receive funds from other balance accounts in your platform. <\/br>This capability is only required if the balance accounts are not under the same account holder.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>receiveFromTransferInstrument<\/strong><\/td>\n<td style=\"text-align: left;\">Receive funds from transfer instruments<\/td>\n<td style=\"text-align: left;\">Allows users to receive funds from verified bank accounts.<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>sendToBalanceAccount<\/strong><\/td>\n<td style=\"text-align: left;\">Send funds to balance accounts<\/td>\n<td style=\"text-align: left;\">Allows users to <a href=\"\/pt\/issuing\/add-manage-funds\">transfer funds to other balance accounts<\/a> in your platform. <\/br>This capability is only required if the balance accounts are not under the same account holder.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>sendToTransferInstrument<\/strong><\/td>\n<td style=\"text-align: left;\">Send funds to transfer instruments<\/td>\n<td style=\"text-align: left;\">Allows users to transfer funds to verified bank accounts. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Capabilities for card issuing<\/h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><div style=\"width:100px\">API name<\/div><\/th>\n<th style=\"text-align: left;\"><div style=\"width:250px\">Display name in Customer Area<\/div><\/th>\n<th style=\"text-align: left;\"><div style=\"width:50px\">Description<\/div><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>issueCard<\/strong><\/td>\n<td style=\"text-align: left;\">Issue cards for payments<\/td>\n<td style=\"text-align: left;\">Allows users to have an <a href=\"\/pt\/issuing\/create-cards\">Adyen-issued card<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>useCard<\/strong><\/td>\n<td style=\"text-align: left;\">Use cards for payments<\/td>\n<td style=\"text-align: left;\">Allows users to use an <a href=\"\/pt\/issuing\/create-cards\">Adyen-issued card<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>withdrawFromAtm<\/strong><\/td>\n<td style=\"text-align: left;\">Withdraw cash from ATMs<\/td>\n<td style=\"text-align: left;\">Allows users to withdraw cash from ATMs. <\/br>This capability has <a href=\"#capability-levels\">levels<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>withdrawFromAtmInRestrictedCountries<\/strong><\/td>\n<td style=\"text-align: left;\">Withdraw cash from ATMs in restricted countries<\/td>\n<td style=\"text-align: left;\">Allows users to withdraw cash from ATMs in restricted countries. <\/br>This capability has <a href=\"#capability-levels\">levels<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>receiveFromTransferInstrument<\/strong><\/td>\n<td style=\"text-align: left;\">Receive funds from transfer instruments<\/td>\n<td style=\"text-align: left;\">Allows users to receive funds from verified bank accounts.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>sendToTransferInstrument<\/strong><\/td>\n<td style=\"text-align: left;\">Send funds to transfer instruments<\/td>\n<td style=\"text-align: left;\">Allows users to transfer funds to verified bank accounts from balance accounts.<\/br><\/br>From LEM API v3, this capability is verified at the level of the transfer instrument. This means, for example, that transfers are possible to a verified card independently of the verification status of other transfer instruments that the legal entity has.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>useCardInRestrictedCountries<\/strong><\/td>\n<td style=\"text-align: left;\">Use cards for payments in restricted countries<\/td>\n<td style=\"text-align: left;\">Allows users to use an <a href=\"\/pt\/issuing\/create-cards\">Adyen-issued card<\/a> to pay for goods and services in restricted countries. <\/br>This capability has <a href=\"#capability-levels\">levels<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>useCardInRestrictedIndustries<\/strong><\/td>\n<td style=\"text-align: left;\">Use cards for payments in restricted industries<\/td>\n<td style=\"text-align: left;\">Allows users to use an <a href=\"\/pt\/issuing\/create-cards\">Adyen-issued card<\/a> to pay for goods and services from restricted industries. <\/br>This capability has <a href=\"#capability-levels\">levels<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>sendToBalanceAccount<\/strong><\/td>\n<td style=\"text-align: left;\">Send funds to balance accounts<\/td>\n<td style=\"text-align: left;\">Allows users to <a href=\"\/pt\/issuing\/add-manage-funds\">Transfer funds to other balance accounts<\/a> in your platform. <\/br>This capability is only required if the balance accounts are not under the same account holder.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>receiveFromBalanceAccount<\/strong><\/td>\n<td style=\"text-align: left;\">Receive funds from balance accounts<\/td>\n<td style=\"text-align: left;\">Allows users to receive funds from other balance accounts in your platform. <\/br>This capability is only required if the balance accounts are not under the same account holder.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Capability levels<\/h3>\n<p>Capabilities for card issuing can also have different levels: low, medium, or high. Levels increase the capability, but may also require more checks and increased monitoring. Adyen runs checks based on the requested capability and the capability level.<\/p>\n<p>The amounts below are the threshold amounts per card, per day.<\/p>\n<table>\n<thead>\n<tr>\n<th>API name<\/th>\n<th style=\"text-align: left;\"><div style=\"width:240px\">Display name in Customer Area<\/div><\/th>\n<th>Low level<\/th>\n<th>Medium level<\/th>\n<th>High level<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>withdrawFromAtm<\/strong><\/td>\n<td style=\"text-align: left;\">Withdraw cash from ATMs<\/td>\n<td>0<\/td>\n<td>Less than or equal to EUR&nbsp;750<\/td>\n<td>More than EUR&nbsp;750 and less than EUR&nbsp;1500<\/td>\n<\/tr>\n<tr>\n<td><strong>withdrawFromAtmInRestrictedCountries<\/strong><\/td>\n<td style=\"text-align: left;\">Withdraw cash from ATMs in restricted countries<\/td>\n<td>0<\/td>\n<td>Less than or equal to EUR&nbsp;500<\/td>\n<td>More than EUR&nbsp;500 and less than EUR&nbsp;1000<\/td>\n<\/tr>\n<tr>\n<td><strong>useCardInRestrictedCountries<\/strong><\/td>\n<td style=\"text-align: left;\">Use cards for payments in restricted countries<\/td>\n<td>0<\/td>\n<td>Less than or equal to EUR&nbsp;1500<\/td>\n<td>Greater than EUR&nbsp;1500<\/td>\n<\/tr>\n<tr>\n<td><strong>useCardInRestrictedIndustries<\/strong><\/td>\n<td style=\"text-align: left;\">Use cards for payments in restricted industries<\/td>\n<td>0<\/td>\n<td>Industry-specific limits apply<\/td>\n<td>Industry-specific limits apply<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Verification status of a capability<\/h2>\n<p>Verification status of a capability indicates whether a user has passed <a href=\"\/pt\/issuing\/verification-overview\">KYC checks<\/a> and meets requirements to use a specific capability. To get updates about the verification status of a capability, you can:<\/p>\n<ul>\n<li>Listen to <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/balanceplatform-webhooks\/latest\/post\/balancePlatform.accountHolder.created\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.accountHolder.created<\/a> and <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/balanceplatform-webhooks\/latest\/post\/balancePlatform.accountHolder.updated\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.accountHolder.updated<\/a> webhooks<\/li>\n<li>Make a GET <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/balanceplatform\/latest\/get\/accountHolders\/{id}\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/accountHolders\/{id}<\/a> request<\/li>\n<\/ul>\n<p>Here are the possible values for the capability verification status.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><div style=\"width:120px\">Status<\/div><\/th>\n<th style=\"text-align: left;\"><div style=\"width:50%\">Description<\/div><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>pending<\/code><a id=\"pending\"><\/a><\/td>\n<td style=\"text-align: left;\">The <code>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 <a href=\"#requested\">\n  <code>requested<\/code>\n<\/a>: <strong>true<\/strong> and <a href=\"#allowed\">\n  <code>allowed<\/code>\n<\/a>: <strong>false<\/strong>. <\/br><\/br>If the capability has already been allowed, but some <a href=\"\/pt\/issuing\/verification-overview#when-users-change-their-data\">user data has changed<\/a> and needs to be verified, you may see that the capability verification status is <code>pending<\/code> and the capability is <a href=\"#allowed\">\n  <code>allowed<\/code>\n<\/a>: <strong>true<\/strong>. This means that the user is still allowed to use capability while Adyen performs the checks.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>valid<\/code><a id=\"valid\"><\/a><\/td>\n<td style=\"text-align: left;\">The <code>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 <a href=\"#allowed\">\n  <code>allowed<\/code>\n<\/a>: <strong>true<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>invalid<\/code><a id=\"invalid\"><\/a><\/td>\n<td style=\"text-align: left;\">The <code>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  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform\/latest\/get\/accountHolders\/(id)#responses-200-capabilities-problems\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">problems<\/a> object, including the <code>verificationErrors<\/code>, <code>subErrors<\/code>, and <code>remediatingActions<\/code> arrays returned on the linked legal entity. If there are <a href=\"\/pt\/issuing\/kyc-verification-codes\">verification errors<\/a>, you must resolve them. <\/br><\/br> With this verification status, Adyen sets the capability to <a href=\"#allowed\">\n  <code>allowed<\/code>\n<\/a>: <strong>false<\/strong>. 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 <a href=\"\/pt\/issuing\/verification-overview#when-users-change-their-data\">user data changes or is missing<\/a> after the previous verification has been completed successfully, Adyen reverts the capability verification status to <code>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 <a href=\"#allowed\">\n  <code>allowed<\/code>\n<\/a>: <strong>true<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>rejected<\/code><a id=\"rejected\"><\/a><\/td>\n<td style=\"text-align: left;\">The <code>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 <a href=\"#allowed\">\n  <code>allowed<\/code>\n<\/a>: <strong>false<\/strong>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Capability settings<\/h2>\n<p>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:<\/p>\n<ul>\n<li>Listen to <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/balanceplatform-webhooks\/latest\/post\/balancePlatform.accountHolder.created\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.accountHolder.created<\/a> and <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/balanceplatform-webhooks\/latest\/post\/balancePlatform.accountHolder.updated\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.accountHolder.updated<\/a> webhooks<\/li>\n<li>Make a GET <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/balanceplatform\/latest\/get\/accountHolders\/{id}\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/accountHolders\/{id}<\/a> request. The API response contains the <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform\/latest\/get\/accountHolders\/_id_#responses-200-capabilities\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">capabilities<\/a> object that shows whether the capability is <code>requested<\/code>, <code>allowed<\/code>, and <code>enabled<\/code>. Below are the explanations for each setting.<\/li>\n<\/ul>\n<table class=\"tg\">\n<thead>\n <tr>\n   <th scope=\"col\">Setting<\/th>\n   <th scope=\"col\">Possible\u00a0values<\/th>\n   <th scope=\"col\">Description<\/th>\n <\/tr>\n<\/thead>\n<tbody>\n  <tr>\n   <td>\n<p><a id=\"requested\"><code>requested<\/code><\/a><\/p>\n<\/td>\n   <td>\n<p><strong>true<\/strong>, <strong>false<\/strong><\/p>\n<\/td>\n   <td>\n   <table>\n       <tr>\n           <td>\n<p><strong>true<\/strong>: the capability has been requested. Default capabilities are requested automatically when you <a href=\"\/pt\/issuing\/onboard-users\">create an account holder<\/a>. You can also <a href=\"\/pt\/issuing\/manage-account-holders\/#request-capability\">request additional capabilities<\/a> by including this setting in your API request.<\/p>\n<\/td>\n       <\/tr>\n       <tr>\n           <td>\n<p><strong>false<\/strong>: the capability has not been requested yet.<\/p>\n<\/td>\n       <\/tr>\n   <\/table>\n<\/td>\n<\/tr>\n  <tr>\n   <td>\n<p><a id=\"allowed\"><code>allowed<\/code><\/a><\/p>\n<\/td>\n   <td>\n<p><strong>true<\/strong>, <strong>false<\/strong><\/p>\n<\/td>\n   <td>\n   <table>\n       <tr>\n           <td>\n<p><strong>true<\/strong>: the <a href=\"#valid\">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.<br><br>  In some scenarios, such as <a href=\"\/pt\/issuing\/verification-overview#when-users-change-their-data\">when a user changes their information<\/a>, the capability is set to <strong>true<\/strong> while the verification status is <a href=\"#pending\">\n  <code>pending<\/code>\n<\/a> or <a href=\"#invalid\">\n  <code>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       <tr>\n           <td>\n<p><strong>false<\/strong>: the verification is <a href=\"#pending\">\n  <code>pending<\/code>\n<\/a>, <a href=\"#invalid\">\n  <code>invalid<\/code>\n<\/a>, or <a href=\"#rejected\">\n  <code>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  <tr>\n   <td>\n<p><a id=\"enabled\"><code>enabled<\/code><\/a><\/p>\n<\/td>\n   <td>\n<p><strong>true<\/strong>, <strong>false<\/strong><\/p>\n<\/td>\n   <td>\n<p>This setting allows you to <a href=\"\/pt\/issuing\/manage-account-holders\/?tab=ah-customer-area_2#deactivate-capability\">manage your users\u2019 access to capabilities<\/a>. Changing this setting does not trigger verification checks or prevent a capability from being requested. <br><br> Note that this capability can only be used if it is both enabled and allowed. <br><br> Set to <strong>true<\/strong> to offer the capability to the user. Set to <strong>false<\/strong> to prevent them from using the capability.<\/p>\n<\/td>\n <\/tr>\n<\/tbody>\n<\/table>\n<h2>See also<\/h2>\n<ul>\n<li><a href=\"\/pt\/issuing\/manage-account-holders\/#view-capabilities\">View capabilities<\/a><\/li>\n<li><a href=\"\/pt\/issuing\/manage-account-holders\/#request-capability\">Request a capability<\/a><\/li>\n<li><a href=\"\/pt\/issuing\/manage-account-holders\/#deactivate-capability\">Enable or disable a capability<\/a><\/li>\n<\/ul>","url":"https:\/\/docs.adyen.com\/pt\/issuing\/verification-overview\/capabilities","articleFields":{"description":"Learn what capabilities your users can have in your platform","feedback_component":true,"last_edit_on":"20-02-2024 15:43","cache_enable":false,"parameters":{"integrationType":"issuing","directoryPath":"\/issuing","model":"platform"},"filters_component":false,"page_id":"42800084-6aaf-473a-b2a9-63e757776294","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/issuing\/verification-overview\/capabilities","title":"User capabilities","content":"Every account holder has a list of capabilities that determine what they can do on your platform. You can edit a capability's settings to change which actions the account holder has permission to do, for example, receive payments, send funds to a bank account, or use certain financial products.\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 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. \n\nIt is possible that requesting additional capabilities prompts additional KYC checks on your users. \n\nGeneral capabilities\nDepending on your settings, capabilities are requested automatically for new account holders, or you have to request them separately when needed.\n\n\n\nCapability name\nDisplay name in Customer Area\nDescription\n\n\n\n\nreceiveFromBalanceAccount\nReceive funds from balance accounts\nAllows 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.\n\n\nreceiveFromTransferInstrument\nReceive funds from transfer instruments\nAllows users to receive funds from verified bank accounts.\n\n\n\nsendToBalanceAccount\nSend funds to balance accounts\nAllows 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.\n\n\nsendToTransferInstrument\nSend funds to transfer instruments\nAllows users to transfer funds to verified bank accounts. \n\n\n\nCapabilities for card issuing\n\n\n\nAPI name\nDisplay name in Customer Area\nDescription\n\n\n\n\nissueCard\nIssue cards for payments\nAllows users to have an Adyen-issued card.\n\n\nuseCard\nUse cards for payments\nAllows users to use an Adyen-issued card.\n\n\nwithdrawFromAtm\nWithdraw cash from ATMs\nAllows users to withdraw cash from ATMs. This capability has levels.\n\n\nwithdrawFromAtmInRestrictedCountries\nWithdraw cash from ATMs in restricted countries\nAllows users to withdraw cash from ATMs in restricted countries. This capability has levels.\n\n\nreceiveFromTransferInstrument\nReceive funds from transfer instruments\nAllows users to receive funds from verified bank accounts.\n\n\nsendToTransferInstrument\nSend funds to transfer instruments\nAllows users to transfer funds to verified bank accounts from balance accounts.From LEM API v3, this capability is verified at the level of the transfer instrument. This means, for example, that transfers are possible to a verified card independently of the verification status of other transfer instruments that the legal entity has.\n\n\nuseCardInRestrictedCountries\nUse cards for payments in restricted countries\nAllows users to use an Adyen-issued card to pay for goods and services in restricted countries. This capability has levels.\n\n\nuseCardInRestrictedIndustries\nUse cards for payments in restricted industries\nAllows users to use an Adyen-issued card to pay for goods and services from restricted industries. This capability has levels.\n\n\nsendToBalanceAccount\nSend funds to balance accounts\nAllows 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.\n\n\nreceiveFromBalanceAccount\nReceive funds from balance accounts\nAllows 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.\n\n\n\nCapability levels\nCapabilities for card issuing can also have different levels: low, medium, or high. Levels increase the capability, but may also require more checks and increased monitoring. Adyen runs checks based on the requested capability and the capability level.\nThe amounts below are the threshold amounts per card, per day.\n\n\n\nAPI name\nDisplay name in Customer Area\nLow level\nMedium level\nHigh level\n\n\n\n\nwithdrawFromAtm\nWithdraw cash from ATMs\n0\nLess than or equal to EUR&nbsp;750\nMore than EUR&nbsp;750 and less than EUR&nbsp;1500\n\n\nwithdrawFromAtmInRestrictedCountries\nWithdraw cash from ATMs in restricted countries\n0\nLess than or equal to EUR&nbsp;500\nMore than EUR&nbsp;500 and less than EUR&nbsp;1000\n\n\nuseCardInRestrictedCountries\nUse cards for payments in restricted countries\n0\nLess than or equal to EUR&nbsp;1500\nGreater than EUR&nbsp;1500\n\n\nuseCardInRestrictedIndustries\nUse cards for payments in restricted industries\n0\nIndustry-specific limits apply\nIndustry-specific limits apply\n\n\n\nVerification status of a capability\nVerification 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:\n\nListen to balancePlatform.accountHolder.created and balancePlatform.accountHolder.updated webhooks\nMake a GET \/accountHolders\/{id} request\n\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. To get updates about the capability settings, you can:\n\nListen to balancePlatform.accountHolder.created and balancePlatform.accountHolder.updated webhooks\nMake a GET \/accountHolders\/{id} request. The API response contains the capabilities object that shows whether the capability is requested, allowed, and enabled. Below are the explanations for each setting.\n\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 an account holder. You can also request additional capabilities by including this setting in your API request.\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\nSee also\n\nView capabilities\nRequest a capability\nEnable or disable a capability\n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Verification process","lvl3":"User capabilities"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/issuing","lvl2":"https:\/\/docs.adyen.com\/pt\/issuing\/verification-overview","lvl3":"\/pt\/issuing\/verification-overview\/capabilities"},"levels":4,"category":"Issuing","category_color":"green","tags":["capabilities"]}}
