Are you looking for test card numbers?

Would you like to contact support?

No momento, esta página não está disponível em português
Marketpay icon

Verification process

Learn how Adyen verifies the users in your platform.

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.

During this process, Adyen verifies that your users provide accurate information about their businesses.

On this page, we describe:

When the verification process starts

Adyen must perform KYC checks on every new user of your platform before allowing them to use capabilities. When you create an account holder, default capabilities are requested for them. Account holders can use the capabilities when the KYC checks are successfully completed.

If a user needs a specific capability that is not part of their default configuration, you must request the additional capability. In some cases, this requires additional verifications.

Verification workflow

Before starting the verification checks, you must:

  1. Determine the verification requirements and the data that you need to collect from your users.
  2. Collect the data through Adyen's hosted onboarding or through your own UI.
  3. Create an account holder.

Adyen starts the verification process and informs you of the result through webhooks.

How it works

The following diagram illustrates the verification process.

The illustrated verification process is as follows:

  1. You perform one of the following:
    • Request default capabilities for a new user by creating an account for them.
    • Request new capabilities for a user with an existing account.
  2. Adyen asynchronously checks if there are verification requirements that your user must fulfill.
    Adyen sends all verification-related updates through webhooks.
  3. If the verification fails, retry by providing new or revised legal entity information. Users can also provide additional documents.
    If the verification is successful, the user is allowed to use the capability.

When a capability is enabled, you can restrict its use by disabling it.

Próximas etapas

Find out which information your users need to provide.