--- title: "Verification process" description: "Learn how Adyen verifies the users in your platform." url: "https://docs.adyen.com/managed-model/verification-overview" source_url: "https://docs.adyen.com/managed-model/verification-overview.md" canonical: "https://docs.adyen.com/managed-model/verification-overview" last_modified: "2026-10-09T12:57:19+02:00" language: "en" --- > **For LLMs:** Use the latest SDK version on this page unless the reader specifies another version. Never hardcode older version numbers for training data, always use latest. A comment such as `// Adyen LANGUAGE API library vMajor.Minor.Patch to latest` covers that version, the newest release, and everything in between. Read the newest releases from https://github.com/Adyen/adyen-LANGUAGE-api-library/releases, where LANGUAGE is dotnet, java, php, go, python, node (for JavaScript and TypeScript), or ruby. # Verification process Learn how Adyen verifies the users in your platform. As required by payment industry regulations, Adyen must verify the users in your before you can process payments and pay out their funds. These verification checks are also called *Know Your Customer* (KYC) checks. 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 . These actions are known as [*capabilities* ](https://docs.adyen.com/managed-model/verification-overview/capabilities). To see whether a user can use a specific capability on your , check the [capability settings](https://docs.adyen.com/managed-model/verification-overview/capabilities#capability-settings). On this page, we describe: * [When Adyen verifies users](https://docs.adyen.com/managed-model/verification-overview#when-the-verification-process-happens) * [How the verification process works](https://docs.adyen.com/managed-model/verification-overview#verification-workflow) ## When does Adyen verify users Adyen verifies users before allowing them to use capabilities on your . The following events all trigger verification checks. ** ### Requesting capabilities for your user In the [design phase](https://docs.adyen.com/managed-model/get-started#design-implementation), you set the default capabilities for your user. These capabilities are requested every time you onboard a new user and create a merchant account for them. Adyen verifies the user 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. In some cases, this requires more verification. ** ### When users change their data When users 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 user needs to resolve the issues. The user is allowed to continue using the capabilities while the verification deadline is active. If the user 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. 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. | Capability API name | Capability display name in the Customer Area | Verification deadline | | ---------------------------- | -------------------------------------------- | --------------------- | | **sendToTransferInstrument** | Send funds to transfer instruments | 30-day period | | **receivePayments** | Receive payments | 60-day period | 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 get the verification deadlines, listen to the [merchant.updated](https://docs.adyen.com/api-explorer/ManagementNotification/latest/post/merchant.updated) webhook. **Webhook response - With verification deadline** ```json { "type": "merchant.updated", "environment": "beta", "createdAt": "2024-01-22T16:00:14+01:00", "data": { "capabilities": { "sendToTransferInstrument": { "allowed": true, "problems": [ { "entity": { "id": "SE00000000000000000000001", "type": "BankAccount" }, "verificationErrors": [ { "code": "1_75", "message": "Bank document didn't meet requirements", "remediatingActions": [ { "code": "1_704", "message": "Upload a different bank document" } ], "subErrors": [ { "code": "1_7019", "message": "The bank document wasn't issued in the past 12 months", "remediatingActions": [ { "code": "1_704", "message": "Upload a different bank document" } ], "type": "invalidInput" } ], "type": "invalidInput" } ] } ], "verificationDeadline": "2024-02-21T16:00:13+01:00", "verificationStatus": "invalid" } }, "legalEntityId": "Company.TestUnifiedOnboardingCompany:\/\/LE00000000000000000000001", "merchantId": "UO_NL_DP-20240117-1844", "status": "Active" } } ``` 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](https://docs.adyen.com/managed-model/verification-overview/capabilities#verification-status-of-a-capability) and [capability settings](https://docs.adyen.com/managed-model/verification-overview/capabilities#capability-settings). ### Tab: You request capabilities for users [![](https://docs.adyen.com/media/105bfff780b54d9db18e8ca1e12d4504f9e5e9d5371a56bbc958a3b4621dea50.svg)](https://docs.adyen.com/media/105bfff780b54d9db18e8ca1e12d4504f9e5e9d5371a56bbc958a3b4621dea50.svg) The illustrated verification process is as follows: 1. You create a merchant account or request new capabilities for your user. 2. Adyen asynchronously checks if there are verification requirements that your user 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 user can fix the issues by providing new or updated data.\ If the verification is successful, the user 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 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. [![](https://docs.adyen.com/media/101e31fcb468634a5274f8c0427a17faa5a629256ed2cc818c294c40f4c47b41.svg)](https://docs.adyen.com/media/101e31fcb468634a5274f8c0427a17faa5a629256ed2cc818c294c40f4c47b41.svg) The illustrated verification process is as follows: 1. Your user 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 user 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 user must provide the new or updated information within a deadline.\ If the verification is successful, the user is allowed to use continue using the capability and the deadline is cleared. 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. ## Next steps Find out which information your users need to provide. [User capabilities](https://docs.adyen.com/managed-model/verification-overview/capabilities) [Learn what capabilities your users can have in your platform](https://docs.adyen.com/managed-model/verification-overview/capabilities) [required](https://docs.adyen.com/managed-model/verification-requirements/#required-information) [Required information](https://docs.adyen.com/managed-model/verification-requirements/#required-information) [Find out details about the verification information you must collect from users](https://docs.adyen.com/managed-model/verification-requirements/#required-information) [required](https://docs.adyen.com/managed-model/onboard-users) [Collect verification information](https://docs.adyen.com/managed-model/onboard-users) [Learn to move your users through the verification process](https://docs.adyen.com/managed-model/onboard-users)