Verification results

Keep track of the results of the verification and know when to retry.

This page is for classic Adyen for Platforms integrations. If you are just starting your implementation, refer to our new integration guide instead.

You can find out about the verification results by:

Listening to the ACCOUNT_HOLDER_VERIFICATION notification webhook.
Making a /getAccountHolder request.
Checking in your Customer Area.

Adyen sends an ACCOUNT_HOLDER_VERIFICATION notification webhook to inform your server of the results of the check. This notification contains:

content.kycCheckStatusData.type: The type of verification.
content.kycCheckStatusData.status: The status of the check. The status determines if you have further actions to take.
summary: Contains a verification code and a description that provides more information about the results.
requiredFields: An array of fields that are required for the checks.

Here is an example notification when the data that the account holder has provided is invalid.

You can also make a POST /getAccountHolder request to get updates about the verification. Specify the accountHolderCode in your request.

The response returns a verification object. In this object you'll find the resource being verified, along with the following:

type: The type of verification.
status: The status of the check. The status determines if you have further actions to take.
summary: Contains a verification code and a description that provides more information about the results.
requiredFields: An array of fields that are required for the checks.

In addition to getting the results through notifications and API responses, you can also view verification statuses in your Customer Area. Your Customer Area user must have the Merchant MarketPlace role user role.

Log in to your Customer Area.
Go to Platform > Sub-merchants.
Find the account holder and select the KYC tab.

Here you can find more information about the verification process, such status of the checks and the tiers for your platform.

Verification types

The verification is categorized into the following checks.

Type	Description
COMPANY_VERIFICATION	Checks for a business legal entity.
IDENTITY_VERIFICATION	Checks for an individual account holder.
LEGAL_ARRANGEMENT_VERIFICATION	Checks for an account holder with a legal arrangement.
NONPROFIT_VERIFICATION	Checks for a nonprofit organization.
PASSPORT_VERIFICATION	Checks for an identification documents such as a passport or driver's license.
PAYOUT_METHOD_VERIFICATION	Checks for the payout methods that an account holder adds. This type is sent starting from notification webhook version 6. This replaces BANK_ACCOUNT_VERIFICATION and CARD_VERIFICATION from earlier versions.
PCI_VERIFICATION	Checks for PCI SAQ A questionnaire.

Verification statuses

Below are the different check statuses and the action that you can take.

Verification status	Description	Action to take
AWAITING_DATA	There is still missing data required for the verification to start.	Get the required information from the account holder.
DATA_PROVIDED	All the required data has been provided.	None.
PENDING	Verification is in progress.	None. The status will change once the validation is completed.
INVALID_DATA	There are errors in the data provided.	Retry the verification.
RETRY_LIMIT_REACHED	The data has been updated too many times.	For some of the checks, you may retry the verification.
PASSED	The verification has been completed and the data has passed the checks	None. The account holder can continue processing payments and payouts are enabled.
FAILED	Adyen has verified the information, but has found reasons to refuse working with this entity.	None. This is a final state. When a check fails, the account holder status is set to suspended.

Retrying the verification

Adyen uses the data from the account holder to automatically run the verification. However, in some cases, automatic verification might fail. This could be due to incorrect data or the data can't be verified.

In general, the following statuses mean that you can retry the verification.

INVALID_DATA: You should ask the account holder to review their data and update when needed.
RETRY_LIMIT_REACHED: This means that Adyen has tried to verify the account holder more than three times. After the third attempt, Adyen may require additional documents.

The following sections are specific for the verification type.

For individuals

When the IDENTITY_VERIFICATION type has the following statuses, you can ask the account holder to retry.

Status	Action to take
INVALID_DATA	Ask the account holder to review and update their information.
RETRY_LIMIT_REACHED	Upload a photo ID.

For bank accounts

When the PAYOUT_METHOD_VERIFICATION type has the following statuses, you can ask the account holder to retry.

Status	Action to take
INVALID_DATA	Ask the account holder to review and update their information.
RETRY_LIMIT_REACHED	Upload a bank statement.

For organizations

When the COMPANY_VERIFICATION or NONPROFIT_VERIFICATION types has an INVALID_DATA status, check the kycCheckCode to know if you can retry the verification by uploading documents.

For API version 5 and later, refer to Company check verification codes for a full list of codes.
For API version 4 and earlier, check if the kycCheckCode is "1604: The submitted Taxpayer Identification Number and legal business name do not match. Correct any errors."

If you receive any of the codes described above, you should:

Ask the account holder to review if their company name and business registration number are correct, and update if needed.
In case the account holder is certain that their company name and business registration number are correct, give them the option to upload a company registration document.
If after three attempts you still receive any of kycCheckCode described above, require the account holder to upload a company registration document in addition to reviewing and updating their company name and registration number.

Adyen will use the company registration document to manually verify the company.