--- title: "Verification process" description: "Learn how Adyen verifies the users in your platform." url: "https://docs.adyen.com/issuing/verification-overview" source_url: "https://docs.adyen.com/issuing/verification-overview.md" canonical: "https://docs.adyen.com/issuing/verification-overview" last_modified: "2023-12-29T17:35:00+01:00" language: "en" --- # Verification process Learn how Adyen verifies the users in your platform. As required by payment industry regulations, Adyen must verify the cardholders in your issuing integration before you can pay out their funds. During this process, Adyen verifies that your cardholders provide accurate information about their businesses. Based on the results of the verification checks, Adyen decides if a cardholder can perform any action on your issuing integration. These actions are known as [*capabilities* ](/issuing/verification-overview/capabilities). On this page, we describe: * [When Adyen verifies cardholders](#when-the-verification-process-happens) * [How the verification process works](#verification-workflow) ## When does Adyen verify users Adyen verifies cardholders before allowing them to use capabilities on your issuing integration. The following events all trigger verification checks. ** ### Requesting capabilities for your user In the [design phase](/issuing/get-started##design-implementation), you set the default capabilities for your issuing integration. These capabilities are requested every time you onboard a new cardholder and create an account holder for them. Adyen verifies the cardholder and if they successfully complete the verification checks, they are allowed to use the capabilities. If a user needs a specific capability that is not requested by default, you must [request the additional capability](/issuing/manage-account-holders#request-capability). In some cases, this requires more verification. ** ### When cardholders change their data When cardholders change their data after they are already allowed to use capabilities, Adyen verifies them again. If the updated data fails verification checks, Adyen may set a verification deadline by which the cardholder needs to resolve the issues. The cardholder is allowed to continue using the capabilities while the verification deadline is active. If the cardholder does not resolve the verification issues in a timely manner, their capabilities will be disallowed. Note that [balancePlatform.accountHolder.updated](https://docs.adyen.com/api-explorer/balanceplatform-webhooks/latest/post/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. ### Verification deadlines Verification deadlines are only available in v3 and v4 of the [Legal Entity Management API](https://docs.adyen.com/api-explorer/legalentity/latest/overview). 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 [accept Terms of Service](/issuing/onboard-users/terms-of-service). 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. The specific verification deadline varies depending on the capabilities involved. The following table outlines the standard verification deadlines for each capability. | Verification deadline | Capability API name | Capability display name in the Customer Area | | --------------------- | ------------------------------------ | ----------------------------------------------- | | **30-day period** | sendToBalanceAccount | Send funds to balance accounts | | | sendToTransferInstrument | Send funds to transfer instruments | | | receiveFromTransferInstrument | Receive funds from transfer instruments | | **60-day period** | receiveFromBalanceAccount | Receive funds from balance accounts | | | issueCard | Issue cards for payments | | | useCard | Use cards for payments | | | useCardInRestrictedCountries | Use cards for payments in restricted countries | | | useCardInRestrictedIndustries | Use cards for payments in restricted industries | | | withdrawFromAtm | Withdraw cash from ATMs | | | withdrawFromAtmInRestrictedCountries | Withdraw cash from ATMs in restricted countries | 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. Users are allowed to continue using the capabilities while the deadline is active. To see the verification deadlines, you can either: * [View the details of the account holder](/issuing/manage-account-holders?tab=ah-customer-area_1#get-account-holders) in your Customer Area. * Make a GET [/accountHolders/id](https://docs.adyen.com/api-explorer/balanceplatform/2/get/accountHolders/_id_) request. **Response - With verification deadline** ```json { "balancePlatform":"YOUR_BALANCE_PLATFORM", "capabilities":{ "sendToTransferInstrument":{ "allowed":"true", "enabled":"true", "requested":"true", "verificationStatus":"invalid" } }, "description":"Test Account holder", "id":"AH00000000000000000000001", "legalEntityId":"LE00000000000000000000001", "reference":"YOUR_INTERNAL_IDENTIFIER", "status":"active", "verificationDeadlines":[ { "expiresAt":"2022-05-01T00:00:00Z", "capabilities":[ "sendToTransferInstrument" ] }, { "expiresAt":"2022-06-01T00:00:00Z", "capabilities":[ "receiveFromPlatformPayments", "receivePayments" ] } ], "verificationErrors":[ { "entity":{ "id":"LE00000000000000000000001", "type":"LegalEntity" }, "code":"1_14", "message":"Capability not allowed for type individual", "remediatingActions":[], "type":"invalidInput", "capabilities":[ "sendToTransferInstrument", "receivePayments" ] } ] } ``` The diagrams in the next section show the process and the corresponding capability verification statuses and capability settings. ## How the verification process works In the following diagrams, you can see the process for events that trigger verification checks and the relationship between capability verification statuses and capability settings. ### Tab: You request capabilities for users [![](/user/pages/reuse/pfs-verification/verification-overview/verification-workflow/request-capabilities.svg)](/user/pages/reuse/pfs-verification/verification-overview/verification-workflow/request-capabilities.svg) The illustrated verification process is as follows: 1. You create an account holder or request new capabilities for your cardholder. 2. Adyen asynchronously checks if there are verification requirements that your cardholder must fulfill.\ When there are several verification checks in progress, the user may receive verification errors while the overall status of the capability remains `pending`. Before reaching out to your Adyen contact, we recommend waiting until all checks are completed and the status becomes `invalid`. 3. If the verification fails, the cardholder can fix the issues by providing new or updated data.\ If the verification is successful, the cardholder is allowed to use the capability. 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 `rejected` and the capability will not be allowed. ### Tab: Users change data If the cardholder 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. [![](/user/pages/reuse/pfs-verification/verification-overview/verification-workflow/data-updated.svg)](/user/pages/reuse/pfs-verification/verification-overview/verification-workflow/data-updated.svg) The illustrated verification process is as follows: 1. Your cardholder changes their data. They are still allowed to use the capability while Adyen verifies the updated data. 2. Adyen asynchronously checks if there are verification requirements that your cardholder must fulfill resulting from the change in data.\ When there are several verification checks in progress, the user may receive verification errors while the overall status of the capability remains `pending`. Before reaching out to your Adyen contact, we recommend waiting until all checks are completed and the status becomes `invalid`. 3. If the verification fails, the cardholder must provide the new or updated information within a deadline.\ If the verification is successful, the cardholder is allowed to use continue using the capability and the deadline is cleared. Adyen sends all verification-related updates through webhooks. If the cardholder does not provide new or updated information within the deadline, or if the new data fails the KYC checks, the capabilities are disallowed. ## Next steps Find out which information your users need to provide. [User capabilities](/issuing/verification-overview/capabilities) [Learn what capabilities your cardholders can have in your platform](/issuing/verification-overview/capabilities) [required](/issuing/onboard-users) [Collect verification information](/issuing/onboard-users) [Learn to move your users through the verification process](/issuing/onboard-users)