{"title":"Verification process","category":"default","creationDate":1572022620,"content":"<p>As required by payment industry regulations, Adyen must verify the users in your platform before you can process payments, pay out their funds, and offer financial products to them. These verification checks are also called <em>Know Your Customer<\/em> (KYC) checks.<\/p>\n<p>During this process, Adyen verifies that your users provide accurate information about their businesses. Based on the results of the verification checks, Adyen decides if a user can perform any action on your platform. These actions are known as <a href=\"\/pt\/platforms\/verification-overview\/capabilities\">\n  <em>capabilities<\/em>\n<\/a>.<\/p>\n<div class=\"notices green\">\n<p>To see whether a user can use a specific capability on your platform, check the <a href=\"\/pt\/platforms\/verification-overview\/capabilities#capability-settings\">capability settings<\/a>.<\/p>\n<\/div>\n<p>On this page, we describe:<\/p>\n<ul>\n<li><a href=\"#when-the-verification-process-happens\">When Adyen verifies users<\/a><\/li>\n<li><a href=\"#verification-workflow\">How the verification process works<\/a><\/li>\n<\/ul>\n<h2 id=\"when-the-verification-process-happens\">When does Adyen verify users<\/h2>\n<p>Adyen verifies users before allowing them to use capabilities on your platform. The following events all trigger verification checks.<\/p>\n<div class=\"accordion-shortcode adl-accordion adl-accordion--max-height-transition\" data-expand=\"true\" data-ignore=\"anchorjs-link\">\n    \n    <div class=\"adl-accordion__item\" style=\"\">\n        <div tabindex=\"0\" role=\"item\" aria-expanded=\"false\" class=\"adl-accordion__header\">\n            <i class=\"adl-accordion__toggle adl-icon-chevron-down\"><\/i>\n            <div class=\"adl-accordion__title-wrapper\" data-accordion=\"#requesting-capabilities-for-your-user\">\n                                    <h3 class=\"adl-accordion__title\">Requesting capabilities for your user<\/h3>\n                            <\/div>\n        <\/div>\n        <div role=\"region\" class=\"adl-accordion__content\">\n            \n<p>In the <a href=\"\/pt\/platforms\/get-started##design-implementation\">design phase<\/a>, you set the default capabilities for your platform. These capabilities are requested every time you onboard a new user and create an account holder for them. Adyen verifies the user and if they successfully complete the verification checks, they are allowed to use the capabilities.<\/p>\n<p>If a user needs a specific capability that is not requested by default, you must <a href=\"\/pt\/platforms\/manage-account-holders#request-capability\">request the additional capability<\/a>. In some cases, this requires more verification.<\/p>\n\n        <\/div>\n    <\/div>\n<\/div>\n\n<div class=\"accordion-shortcode adl-accordion adl-accordion--max-height-transition\" data-expand=\"true\" data-ignore=\"anchorjs-link\">\n    \n    <div class=\"adl-accordion__item\" style=\"\">\n        <div tabindex=\"0\" role=\"item\" aria-expanded=\"false\" class=\"adl-accordion__header\">\n            <i class=\"adl-accordion__toggle adl-icon-chevron-down\"><\/i>\n            <div class=\"adl-accordion__title-wrapper\" data-accordion=\"#when-user-s-change-their-data\">\n                                    <h3 class=\"adl-accordion__title\">When users change their data<\/h3>\n                            <\/div>\n        <\/div>\n        <div role=\"region\" class=\"adl-accordion__content\">\n            \n<p>When users change their data after they are already allowed to use capabilities, Adyen verifies them again.<\/p>\n<p>If the updated data fails verification checks, Adyen may set a verification deadline by which the user needs to resolve the issues. The user is allowed to continue using the capabilities while the verification deadline is active.<\/p>\n<p>If the user does not resolve the verification issues in a timely manner, their capabilities will be disallowed.<\/p>\n<div class=\"notices yellow\">\n<p>Note that  <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> are only triggered for capability-related changes to the account holder. Data changes to the legal entity of the account holder do not trigger webhooks.<\/p>\n<\/div>\n\n        <\/div>\n    <\/div>\n<\/div>\n\n<div class=\"accordion-shortcode adl-accordion adl-accordion--max-height-transition\" data-expand=\"true\" data-ignore=\"anchorjs-link\">\n    \n    <div class=\"adl-accordion__item\" style=\"\">\n        <div tabindex=\"0\" role=\"item\" aria-expanded=\"false\" class=\"adl-accordion__header\">\n            <i class=\"adl-accordion__toggle adl-icon-chevron-down\"><\/i>\n            <div class=\"adl-accordion__title-wrapper\" data-accordion=\"#periodic-data-reviews-required-by-adyen\">\n                                    <h3 class=\"adl-accordion__title\">Periodic data reviews required by Adyen<\/h3>\n                            <\/div>\n        <\/div>\n        <div role=\"region\" class=\"adl-accordion__content\">\n            \n<p>Adyen occasionally requires your users to <a href=\"\/pt\/platforms\/verification-overview#when-adyen-requires-data-reviews\">review and confirm<\/a> that their data is up-to-date. You also can choose to <a href=\"\/pt\/platforms\/verification-overview\/data-review-process#proactive-review\">proactively request the data review<\/a> for your user.<\/p>\n<p>After a data review is triggered, Adyen immediately runs verification checks on the existing data of the user. This data includes information about their legal entity\/legal arrangement and all entities associated with it, such as their ultimate beneficial owners (UBOs) and signatories.<\/p>\n<p>Adyen sets a verification deadline by which the user must confirm their data and update it (if needed). If there are no verification errors, the user must only review and confirm their data. If there are any errors from the verification checks, the user must also resolve them and confirm the data. If you proactively request the data review, Adyen still provides a verification deadline during which the user can continue using their capabilities that were allowed.<\/p>\n<p>If the user updates their data, Adyen verifies the updated data again. While the deadline is active, the user can continue using their capabilities that were allowed prior to the review request. If the user does not confirm the data and resolve any verification errors, their capabilities will be disallowed. The review is only considered finalized when the user has both confirmed the data <strong>and<\/strong> resolved all verification errors.<\/p>\n\n        <\/div>\n    <\/div>\n<\/div>\n\n<h3>Verification deadlines<\/h3>\n<div class=\"notices green\">\n<p>Verification deadlines are only available in v3 and v4 of the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/legalentity\/latest\/overview\" class=\" external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Legal Entity Management API<\/a>.<\/p>\n<\/div>\n<p>For the events mentioned above that require additional verification checks, Adyen may set a deadline to give users extra time to resolve any verification issues before certain capabilities are disallowed. This allows users to correct any missing or incorrect information to complete verification checks or fulfill their contractual obligations, such as <a href=\"\/pt\/platforms\/onboard-users\/terms-of-service\">accept Terms of Service<\/a>.<\/p>\n<p>The verification deadline is the final date by which all required information and documents must be submitted and verified by Adyen. Users are allowed to continue using the capabilities while the deadline is active.<\/p>\n<p>The specific verification deadline varies depending on the capabilities involved. The following table outlines the standard verification deadlines for each capability.<\/p>\n<table>\n<thead>\n  <tr>\n    <th>Verification deadline<\/th>\n    <th>Capability API name<\/th>\n    <th>Capability display name in the Customer Area<\/th>\n  <\/tr>\n<\/thead>\n<tbody>\n  <tr>\n    <td rowspan=\"7\"><b>30-day period<\/b><\/td>\n    <td>\n<p>sendToBalanceAccount<\/p>\n<\/td>\n    <td>\n<p>Send funds to balance accounts<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>sendToTransferInstrument<\/p>\n<\/td>\n    <td>\n<p>Send funds to transfer instruments<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>receiveFromTransferInstrument<\/p>\n<\/td>\n    <td>\n<p>Receive funds from transfer instruments<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>issueBankAccount<\/p>\n<\/td>\n    <td>\n<p>Issue bank accounts<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>sendToThirdParty<\/p>\n<\/td>\n    <td>\n<p>Send funds to third-party bank accounts<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>getGrantOffers<\/p>\n<\/td>\n    <td>\n<p>Receive grant offers<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>receiveGrants<\/p>\n<\/td>\n    <td>\n<p>Receive grants<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td rowspan=\"10\"><b>60-day period<\/b><\/td>\n    <td>\n<p>receiveFromBalanceAccount<\/p>\n<\/td>\n    <td>\n<p>Receive funds from balance accounts<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>receiveFromPlatformPayments<\/p>\n<\/td>\n    <td>\n<p>Receive funds from split payments<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>receivePayments<\/p>\n<\/td>\n    <td>\n<p>Receive payments<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>issueCard<\/p>\n<\/td>\n    <td>\n<p>Issue cards for payments<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>useCard<\/p>\n<\/td>\n    <td>\n<p>Use cards for payments<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>useCardInRestrictedCountries<\/p>\n<\/td>\n    <td>\n<p>Use cards for payments in restricted countries<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>useCardInRestrictedIndustries<\/p>\n<\/td>\n    <td>\n<p>Use cards for payments in restricted industries<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>withdrawFromAtm<\/p>\n<\/td>\n    <td>\n<p>Withdraw cash from ATMs<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>withdrawFromAtmInRestrictedCountries<\/p>\n<\/td>\n    <td>\n<p>Withdraw cash from ATMs in restricted countries<\/p>\n<\/td>\n  <\/tr>\n  <tr>\n    <td>\n<p>receiveFromThirdParty<\/p>\n<\/td>\n    <td>\n<p>Receive funds from third-party bank accounts<\/p>\n<\/td>\n  <\/tr>\n<\/tbody>\n<\/table>\n<p>Verification deadlines may be adjusted based on ongoing account monitoring and subsequent verification checks. In accordance with our internal due diligence processes, designed to ensure platform security and comply with regulatory obligations, a standard deadline could be shortened or removed in specific situations.<\/p>\n<p>Users are allowed to continue using the capabilities while the deadline is active. To see the verification deadlines, you can either:<\/p>\n<ul>\n<li><a href=\"\/pt\/platforms\/manage-account-holders?tab=ah-customer-area_1#get-account-holders\">View the details of the account holder<\/a> in your Customer Area.<\/li>\n<li>Make a GET <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform\/2\/get\/accountHolders\/_id_\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/accountHolders\/id<\/a> request.<\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Response - With verification deadline'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n  \\\"balancePlatform\\\":\\\"YOUR_BALANCE_PLATFORM\\\",\\n  \\\"capabilities\\\":{\\n     \\\"sendToTransferInstrument\\\":{\\n        \\\"allowed\\\":\\\"true\\\",\\n        \\\"enabled\\\":\\\"true\\\",\\n        \\\"requested\\\":\\\"true\\\",\\n        \\\"verificationStatus\\\":\\\"invalid\\\"\\n     }\\n  },\\n  \\\"description\\\":\\\"Test Account holder\\\",\\n  \\\"id\\\":\\\"AH00000000000000000000001\\\",\\n  \\\"legalEntityId\\\":\\\"LE00000000000000000000001\\\",\\n  \\\"reference\\\":\\\"YOUR_INTERNAL_IDENTIFIER\\\",\\n  \\\"status\\\":\\\"active\\\",\\n  \\\"verificationDeadlines\\\":[\\n     {\\n        \\\"expiresAt\\\":\\\"2022-05-01T00:00:00Z\\\",\\n        \\\"capabilities\\\":[\\n          \\\"sendToTransferInstrument\\\"\\n        ]\\n     },\\n     {\\n        \\\"expiresAt\\\":\\\"2022-06-01T00:00:00Z\\\",\\n        \\\"capabilities\\\":[\\n           \\\"receiveFromPlatformPayments\\\",\\n           \\\"receivePayments\\\"\\n        ]\\n     }\\n  ],\\n  \\\"verificationErrors\\\":[\\n    {\\n       \\\"entity\\\":{\\n          \\\"id\\\":\\\"LE00000000000000000000001\\\",\\n          \\\"type\\\":\\\"LegalEntity\\\"\\n       },\\n       \\\"code\\\":\\\"1_14\\\",\\n       \\\"message\\\":\\\"Capability not allowed for type individual\\\",\\n       \\\"remediatingActions\\\":[],\\n       \\\"type\\\":\\\"invalidInput\\\",\\n       \\\"capabilities\\\":[\\n          \\\"sendToTransferInstrument\\\",\\n          \\\"receivePayments\\\"\\n       ]\\n    }\\n  ]\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<p>The diagrams in the next section show the process and the corresponding capability verification statuses and capability settings.<\/p>\n<h2 id=\"verification-workflow\">How the verification process works<\/h2>\n<p>In the following diagrams, you can see the process for events that trigger verification checks and the relationship between <a href=\"\/pt\/platforms\/verification-overview\/capabilities#verification-status-of-a-capability\">capability verification statuses<\/a> and <a href=\"\/pt\/platforms\/verification-overview\/capabilities#capability-settings\">capability settings<\/a>.<\/p>\n\n<div id=\"tabJBvWD\">\n    <div data-component-wrapper=\"tabs\">\n        <tabs\n                        :items=\"[{&quot;title&quot;:&quot;You request capabilities for users&quot;,&quot;content&quot;:&quot;\\n&lt;p&gt;&lt;a rel=\\&quot;lightbox\\&quot; href=\\&quot;\\\/user\\\/pages\\\/reuse\\\/pfs-verification\\\/verification-overview\\\/verification-workflow\\\/request-capabilities.svg\\&quot; src=\\&quot;\\&quot;&gt;\\n  &lt;img alt=\\&quot;\\&quot; src=\\&quot;\\\/user\\\/pages\\\/reuse\\\/pfs-verification\\\/verification-overview\\\/verification-workflow\\\/request-capabilities.svg\\&quot; \\\/&gt;\\n&lt;\\\/a&gt;&lt;\\\/p&gt;\\n&lt;p&gt;The illustrated verification process is as follows:&lt;\\\/p&gt;\\n&lt;ol&gt;\\n&lt;li&gt;You create an account holder or request new capabilities for your user.&lt;\\\/li&gt;\\n&lt;li&gt;Adyen asynchronously checks if there are verification requirements that your user must fulfill.&lt;br \\\/&gt;\\nWhen there are several verification checks in progress, the user may receive verification errors while the overall status of the capability remains &lt;code&gt;pending&lt;\\\/code&gt;. Before reaching out to your Adyen contact, we recommend waiting until all checks are completed and the status becomes &lt;code&gt;invalid&lt;\\\/code&gt;.&lt;\\\/li&gt;\\n&lt;li&gt;If the verification fails, user can fix the issues by providing new or updated data.&lt;br \\\/&gt;\\nIf the verification is successful, the user is allowed to use the capability.&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&lt;p&gt;Adyen sends all verification-related updates through webhooks. If Adyen has found reasons to not allow the capability, the capability verification status is set as &lt;code&gt;rejected&lt;\\\/code&gt; and the capability will not be allowed.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;you_request_capabilities_for_users_0_1&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;Users change data&quot;,&quot;content&quot;:&quot;\\n&lt;p&gt;If the user changes their data after they are already allowed to use capabilities, Adyen verifies them again. If the verification fails, Adyen might also set a deadline for updating the data.&lt;\\\/p&gt;\\n&lt;p&gt;&lt;a rel=\\&quot;lightbox\\&quot; href=\\&quot;\\\/user\\\/pages\\\/reuse\\\/pfs-verification\\\/verification-overview\\\/verification-workflow\\\/data-updated.svg\\&quot; src=\\&quot;\\&quot;&gt;\\n  &lt;img alt=\\&quot;\\&quot; src=\\&quot;\\\/user\\\/pages\\\/reuse\\\/pfs-verification\\\/verification-overview\\\/verification-workflow\\\/data-updated.svg\\&quot; \\\/&gt;\\n&lt;\\\/a&gt;&lt;\\\/p&gt;\\n&lt;p&gt;The illustrated verification process is as follows:&lt;\\\/p&gt;\\n&lt;ol&gt;\\n&lt;li&gt;Your user changes their data. They are still allowed to use the capability while Adyen verifies the updated data.&lt;\\\/li&gt;\\n&lt;li&gt;Adyen asynchronously checks if there are verification requirements that your user must fulfill resulting from the change in data.&lt;br \\\/&gt;\\nWhen there are several verification checks in progress, the user may receive verification errors while the overall status of the capability remains &lt;code&gt;pending&lt;\\\/code&gt;. Before reaching out to your Adyen contact, we recommend waiting until all checks are completed and the status becomes &lt;code&gt;invalid&lt;\\\/code&gt;.&lt;\\\/li&gt;\\n&lt;li&gt;If the verification fails, the user must provide the new or updated information within a deadline.&lt;br \\\/&gt;\\nIf the verification is successful, the user is allowed to use continue using the capability and the deadline is cleared.&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&lt;p&gt;Adyen sends all verification-related updates through webhooks. If the user does not provide new or updated information within the deadline, or if the new data fails the KYC checks, the capabilities are disallowed.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;users_change_data_1_2&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;Adyen requires data review&quot;,&quot;content&quot;:&quot;\\n&lt;p&gt;Adyen occasionally requires your users to &lt;a href=\\&quot;\\\/pt\\\/platforms\\\/verification-overview#when-adyen-requires-data-reviews\\&quot;&gt;review and confirm&lt;\\\/a&gt; that their data is up-to-date. You also can choose to &lt;a href=\\&quot;\\\/pt\\\/platforms\\\/verification-overview\\\/data-review-process#proactive-review\\&quot;&gt;proactively request the data review&lt;\\\/a&gt; for your user.&lt;\\\/p&gt;\\n&lt;p&gt;After a data review is triggered, Adyen immediately runs verification checks on the existing data of the user. This data includes information about their legal entity\\\/legal arrangement and all entities associated with it, such as their ultimate beneficial owners (UBOs) and signatories.&lt;\\\/p&gt;\\n&lt;p&gt;Adyen sets a verification deadline by which the user must confirm their data and update it (if needed). If there are no verification errors, the user must only review and confirm their data. If there are any errors from the verification checks, the user must also resolve them and confirm the data. If you proactively request the data review, Adyen still provides a verification deadline during which the user can continue using their capabilities that were allowed.&lt;\\\/p&gt;\\n&lt;p&gt;If the user updates their data, Adyen verifies the updated data again. While the deadline is active, the user can continue using their capabilities that were allowed prior to the review request. If the user does not confirm the data and resolve any verification errors, their capabilities will be disallowed. The review is only considered finalized when the user has both confirmed the data &lt;strong&gt;and&lt;\\\/strong&gt; resolved all verification errors.&lt;\\\/p&gt;\\n&lt;p&gt;&lt;a rel=\\&quot;lightbox\\&quot; href=\\&quot;\\\/user\\\/pages\\\/reuse\\\/pfs-verification\\\/verification-overview\\\/verification-workflow\\\/review-required.svg\\&quot; src=\\&quot;\\&quot;&gt;\\n  &lt;img alt=\\&quot;\\&quot; src=\\&quot;\\\/user\\\/pages\\\/reuse\\\/pfs-verification\\\/verification-overview\\\/verification-workflow\\\/review-required.svg\\&quot; \\\/&gt;\\n&lt;\\\/a&gt;&lt;\\\/p&gt;\\n&lt;p&gt;The illustrated verification process is as follows:&lt;\\\/p&gt;\\n&lt;ol&gt;\\n&lt;li&gt;Adyen informs you through a webhook when a data review is required or you &lt;a href=\\&quot;\\\/pt\\\/platforms\\\/verification-overview\\\/data-review-process#proactive-review\\&quot;&gt;proactively request the data review for your user&lt;\\\/a&gt;. The webhook also includes a verification deadline. The user is still allowed to use their capabilities while the deadline is in place.&lt;\\\/li&gt;\\n&lt;li&gt;The user needs to confirm their data is up-to-date, or update their data if needed and then confirm it, within the verification deadline.&lt;\\\/li&gt;\\n&lt;li&gt;Adyen asynchronously checks the data and sends all verification-related updates through webhooks. If the verification is successful, they can continue using their capabilities and the deadline is lifted.&lt;\\\/li&gt;\\n&lt;li&gt;If the user does not confirm they reviewed the data within the deadline or the new data fails the verification checks, the capabilities are disallowed.&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;adyen_requires_data_review_2_3&quot;,&quot;relation&quot;:&quot;&quot;}]\"\n            :should-update-when-url-changes='false'>\n        <\/tabs>\n    <\/div>\n<\/div>\n\n","url":"https:\/\/docs.adyen.com\/pt\/platforms\/verification-overview","articleFields":{"description":"Learn how Adyen verifies the users in your platform.","feedback_component":true,"next_steps_description":"Find out which information your users need to provide.","next_steps":[{"title":"Verification types","description":"Learn when to collect verification information from your users","url":"\/platforms\/verification-overview\/verification-types","required":false},{"title":"User capabilities","description":"Learn what capabilities your users can have in your platform","url":"\/platforms\/verification-overview\/capabilities","required":false},{"title":"Onboard your users","description":"Learn to move your users through the verification process","url":"\/platforms\/onboard-users","required":true}],"parameters":{"directoryPath":"\/platforms","model":"platform"},"cache_enable":false,"last_edit_on":"29-12-2023 17:35","filters_component":false,"page_id":"1e6f0d8f-3cd9-4e7b-85e5-24417fd908f2","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/platforms\/verification-overview","title":"Verification process","content":"As required by payment industry regulations, Adyen must verify the users in your platform before you can process payments, pay out their funds, and offer financial products to them. These verification checks are also called Know Your Customer (KYC) checks.\nDuring this process, Adyen verifies that your users provide accurate information about their businesses. Based on the results of the verification checks, Adyen decides if a user can perform any action on your platform. These actions are known as \n  capabilities\n.\n\nTo see whether a user can use a specific capability on your platform, check the capability settings.\n\nOn this page, we describe:\n\nWhen Adyen verifies users\nHow the verification process works\n\nWhen does Adyen verify users\nAdyen verifies users before allowing them to use capabilities on your platform. The following events all trigger verification checks.\n\n    \n    \n        \n            \n            \n                                    Requesting capabilities for your user\n                            \n        \n        \n            \nIn the design phase, you set the default capabilities for your platform. These capabilities are requested every time you onboard a new user and create an account holder for them. Adyen verifies the user and if they successfully complete the verification checks, they are allowed to use the capabilities.\nIf a user needs a specific capability that is not requested by default, you must request the additional capability. In some cases, this requires more verification.\n\n        \n    \n\n\n\n    \n    \n        \n            \n            \n                                    When users change their data\n                            \n        \n        \n            \nWhen users change their data after they are already allowed to use capabilities, Adyen verifies them again.\nIf the updated data fails verification checks, Adyen may set a verification deadline by which the user needs to resolve the issues. The user is allowed to continue using the capabilities while the verification deadline is active.\nIf the user does not resolve the verification issues in a timely manner, their capabilities will be disallowed.\n\nNote that  balancePlatform.accountHolder.updated are only triggered for capability-related changes to the account holder. Data changes to the legal entity of the account holder do not trigger webhooks.\n\n\n        \n    \n\n\n\n    \n    \n        \n            \n            \n                                    Periodic data reviews required by Adyen\n                            \n        \n        \n            \nAdyen occasionally requires your users to review and confirm that their data is up-to-date. You also can choose to proactively request the data review for your user.\nAfter a data review is triggered, Adyen immediately runs verification checks on the existing data of the user. This data includes information about their legal entity\/legal arrangement and all entities associated with it, such as their ultimate beneficial owners (UBOs) and signatories.\nAdyen sets a verification deadline by which the user must confirm their data and update it (if needed). If there are no verification errors, the user must only review and confirm their data. If there are any errors from the verification checks, the user must also resolve them and confirm the data. If you proactively request the data review, Adyen still provides a verification deadline during which the user can continue using their capabilities that were allowed.\nIf the user updates their data, Adyen verifies the updated data again. While the deadline is active, the user can continue using their capabilities that were allowed prior to the review request. If the user does not confirm the data and resolve any verification errors, their capabilities will be disallowed. The review is only considered finalized when the user has both confirmed the data and resolved all verification errors.\n\n        \n    \n\n\nVerification deadlines\n\nVerification deadlines are only available in v3 and v4 of the  Legal Entity Management API.\n\nFor the events mentioned above that require additional verification checks, Adyen may set a deadline to give users extra time to resolve any verification issues before certain capabilities are disallowed. This allows users to correct any missing or incorrect information to complete verification checks or fulfill their contractual obligations, such as accept Terms of Service.\nThe verification deadline is the final date by which all required information and documents must be submitted and verified by Adyen. Users are allowed to continue using the capabilities while the deadline is active.\nThe specific verification deadline varies depending on the capabilities involved. The following table outlines the standard verification deadlines for each capability.\n\n\n  \n    Verification deadline\n    Capability API name\n    Capability display name in the Customer Area\n  \n\n\n  \n    30-day period\n    \nsendToBalanceAccount\n\n    \nSend funds to balance accounts\n\n  \n  \n    \nsendToTransferInstrument\n\n    \nSend funds to transfer instruments\n\n  \n  \n    \nreceiveFromTransferInstrument\n\n    \nReceive funds from transfer instruments\n\n  \n  \n    \nissueBankAccount\n\n    \nIssue bank accounts\n\n  \n  \n    \nsendToThirdParty\n\n    \nSend funds to third-party bank accounts\n\n  \n  \n    \ngetGrantOffers\n\n    \nReceive grant offers\n\n  \n  \n    \nreceiveGrants\n\n    \nReceive grants\n\n  \n  \n    60-day period\n    \nreceiveFromBalanceAccount\n\n    \nReceive funds from balance accounts\n\n  \n  \n    \nreceiveFromPlatformPayments\n\n    \nReceive funds from split payments\n\n  \n  \n    \nreceivePayments\n\n    \nReceive payments\n\n  \n  \n    \nissueCard\n\n    \nIssue cards for payments\n\n  \n  \n    \nuseCard\n\n    \nUse cards for payments\n\n  \n  \n    \nuseCardInRestrictedCountries\n\n    \nUse cards for payments in restricted countries\n\n  \n  \n    \nuseCardInRestrictedIndustries\n\n    \nUse cards for payments in restricted industries\n\n  \n  \n    \nwithdrawFromAtm\n\n    \nWithdraw cash from ATMs\n\n  \n  \n    \nwithdrawFromAtmInRestrictedCountries\n\n    \nWithdraw cash from ATMs in restricted countries\n\n  \n  \n    \nreceiveFromThirdParty\n\n    \nReceive funds from third-party bank accounts\n\n  \n\n\nVerification deadlines may be adjusted based on ongoing account monitoring and subsequent verification checks. In accordance with our internal due diligence processes, designed to ensure platform security and comply with regulatory obligations, a standard deadline could be shortened or removed in specific situations.\nUsers are allowed to continue using the capabilities while the deadline is active. To see the verification deadlines, you can either:\n\nView the details of the account holder in your Customer Area.\nMake a GET \/accountHolders\/id request.\n\n\n    \n\nThe diagrams in the next section show the process and the corresponding capability verification statuses and capability settings.\nHow the verification process works\nIn the following diagrams, you can see the process for events that trigger verification checks and the relationship between capability verification statuses and capability settings.\n\n\n    \n        \n        \n    \n\n\n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Platforms","lvl2":"Verification process"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/platforms","lvl2":"\/pt\/platforms\/verification-overview"},"levels":3,"category":"Platforms","category_color":"green","tags":["Verification","process"]}}