Are you looking for test card numbers?

Would you like to contact support?

Atenção, esta página não se encontra disponível em Português
Marketpay icon

Verification checks

Learn about the KYC process and verification checks.

Each account holder will need to pass KYC (Know Your Customer) in order to payout. The required information for KYC is determined by the account holder's legal entity type and the country they are operating in.

We categorize the required information for KYC into these check types:

Each check has a required set of fields, with the required fields different per country. You can choose whether you want to collect all the required information using the staggered approach or upfront.

To know the data you need to collect from your account holder, refer to the KYC requirements list.

Verification statuses

Each verification check has a status that represents the current state 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. Get the required information from the account holder.
RETRY_LIMIT_REACHED The data has been updated too many times. Get the required information from the account holder.
PASSED The verification has been completed and the data has passed the checks None.
FAILED Adyen has verified the information, but has found reasons to refuse working with this entity. If you think this state was reached in error, reach out to our Support Team.

Refer to the documentation for the specific check to know more about the possible reasons and required actions.


Whenever a verification check has its status updated, a corresponding ACCOUNT_HOLDER_VERIFICATION notification will be sent. This notification contains the content.verificationType, which specifies which verification check was updated, and the check's new status, content.verificationStatus.

Each notification has a KYC verification code representing why the given status was reached. Refer to the Verification codes page for each code and what they represent.

Here is an example notification for a Photo ID check that was updated to the state of INVALID_DATA.

Webhook for check with INVALID_DATA
   "error": {
      "errorCode": "1104",
      "message": "test error message"
   "eventDate": "1970-01-01T01:00:00+01:00",
   "executingUserKey": "executing-user-key",
   "live": true,
   "pspReference": "TSTPSPR0001",
   "content": {
      "accountHolderCode": "AH0000001",
      "bankAccountUUID": "00000000-0000-0000-0000-000000000000",
      "kycCheckStatusData": {
         "type": "PASSPORT_VERIFICATION",
         "status": "INVALID_DATA",
         "summary": {
            "kycCheckCode": 1104,
            "kycCheckDescription": "Document has expired"
         "requiredFields": [
      "shareholderCode": "SH00000001"

Staggered or front-loaded KYC

You have the choice to collect all KYC information in a staggered approach, collecting information only when needed, or front-load your information collection, collecting all KYC information up front.

Collecting all KYC information upfront is generally a larger burden for the account holder and can negatively affect conversion but immediately unlocks payment processing and payout. This also means you will not need to go back to the account holder to collect information later.

Collecting the KYC in a staggered approach enables a faster initial sign-up and generally a higher conversion. Though this means you will need to go back to the account holder to request information at later stages.

If you want to front-load your KYC information collection, reach out to our Support Team for assistance.

See also