Are you looking for test card numbers?

Would you like to contact support?

Marketpay icon

Changes to verification requirements

Learn about the updates in the verification requirements starting from August 1, 2022.

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

As part of Adyen's ongoing efforts to maintain high verification standards and to comply with local regulations, we started requiring additional information as part of our sub-merchant onboarding procedures since July 15, 2021. The new requirements will be enforced for all platforms as of August 1, 2022. The new information allows us to verify data from sub-merchants better and to ensure compliance with regulations specific to each country of business.

On this page, you will learn about these updates and what you need to do to prepare for these changes.

To give more time to update integrations, we've postponed enforcing these changes from July 15, 2021 to August 1, 2022.

The following requirements apply to all new sub-merchants starting August 1, 2022. For existing sub-merchants, we might request additional information from them during our periodic risk assessments.

New requirements

Types of shareholders

Shareholders can be of two types:

  • Owner: A shareholder that owns more than 25% of the business.
  • Controller: A shareholder that is able to make decisions on behalf of the business, but is not necessarily an owner. Such shareholders must be identified with their job titles. We do not limit the number of controllers you can add but we require that you provide at least one shareholder (owner or controller) for sub-merchants operating in the European Economic Area (EEA). For sub-merchants in the U.S. and BR, we require that you provide at least one controller.
Owner shareholder
{
    "accountHolderDetails": {
        "businessDetails": {
            "shareholders": [{
                "shareholderType": "Owner",
                "name": {
                    ...
                }
            }]
        }
    }
}
Controller shareholder
{
    "accountHolderDetails": {
        "businessDetails": {
            "shareholders": [{
                "shareholderType": "Controller",
                "name": {
                    ...
                },
                "jobTitle": "Chief Executive Officer"
            }]
        }
    }
}

Acceptable jobTitle values include:

  • Chief Executive Officer
  • Chief Financial Officer
  • Chief Operating Officer
  • Chief Information Officer
  • Chief Strategy Officer
  • President
  • Vice President
  • Executive President
  • Managing Member
  • General Partner
  • Managing Partner
  • Partner
  • Treasurer
  • Director

If you need to use a different value, you can specify that value in the jobTitle field.

Signatories

We introduce signatories — natural persons that are authorized to act on behalf of or represent the sub-merchant in their relation towards Adyen. We require that such individuals are identified by providing their name, job title, residence address, date of birth, email address, and phone number. We do not limit the number of signatories you can add but we require that you provide at least one.

Signatory
{
    "accountHolderDetails": {
        "businessDetails": {
            "signatories": [{
                "name": {
                    "firstName": "John",
                    "lastName": "Carpenter"
                },
                "jobTitle": "Chief Executive Officer",
                "personalData": {
                    "dateOfBirth": "1990-09-09"
                },
                "address": {
                    "city": "San Francisco",
                    "country": "US",
                    "houseNumberOrName": "1",
                    "postalCode": "12345",
                    "street": "Awesome St",
                    "stateOrProvince": "CA"
                },
                "email": "testshareholder@email.com",
                "fullPhoneNumber": "+31612345678"
            }]
        }
    }
}

Nationality of persons residing in Hong Kong or Singapore

For individual account holders, shareholders, and signatories that have an address in Hong Kong or Singapore, Adyen requires information about the nationality of the account holder.

Nationality Account Holder
Nationality Shareholder
{
    "accountHolderDetails": {
        "businessDetails": {
            "shareholders": [{
                "personalData": {
                    "nationality": "SG",
                }
            }]
        }
    }
}
Nationality Signatory
{
    "accountHolderDetails": {
        "businessDetails": {
            "shareholders": [{
                "personalData": {
                    "nationality": "SG"
                }
            }]
        }
    }
}

Principal place of business address

If a business’s principal place of business is different from its registered address accountHolder.address, Adyen requires this to be identified through the principalBusinessAddress field. The country of the principal place of business and registered address must be the same. The principal place of business address cannot be a PO Box.

Principal business address (all API versions)
{
    "accountHolderDetails": {
        "principalBusinessAddress": {
            "country": "US",
            "houseNumberOrName": "5",
            "postalCode": "94123",
            "street": "Short Street",
            "stateOrProvince": "CA",
            "city": "SF"
        }
    }
}

Parent company information

For sub-merchants that are 100% subsidiaries of companies listed on public stock exchanges or other regulated markets, we require the following:

  • stockExchange: The 4-character market identifier code, following the ISO Standard format. Here's a complete list of supported stock exchanges. For parent companies in the US, this means the companies are listed in the New York Stock Exchange, NYSE American, or NASDAQ.
  • One of either stockNumber or stockTicker:
    • stockNumber is the ISIN, a 12-character alphanumeric code, and is defined in ISO 10383.
    • stockTicker is free format.
Public companies
{
    "accountHolderDetails": {
        "businessDetails": {
            "listedUltimateParentCompany": [{
                "businessDetails": {
                    "legalBusinessName": "Adyen",
                    "registrationNumber": "123456",
                    "legalEntity": "publicCompany",
                    "stockExchange": "XAMS",
                    "stockTicker": "ADYEN",
                    "stockNumber": "NL0012969182"
                },
                "address": {
                    "country": "NL"
                }
            }]
        }
    }
}

Company Tax Identification Number

Adyen requires the merchant to provide a Tax Identification Number (TIN) for all business sub-merchants that have processed more than $1,000. The following list contains TINs for each country.

For countries that have two TINs available, provide either one. For countries that are not listed, the Tax Identification Number and Business Registration Number are the same.

Country TIN Example value
Austria Umsatzsteuer-Identifikationsnummer ATU51507409
Tax number 079/8331
Czech Republic Daňové identifikační číslo CZ00177041
Estonia VAT/Tax number EE100254507
Germany Umsatzsteuer-Identifikationsnummer DE 115235681
Steuernummer 143/102/60208
Greece AFM 94049864
Ireland Value added tax identification number IE99999999XX
Latvia VAT/Tax number LV43603021620
Lithuania VAT/Tax number LT664517219
Luxembourg VAT/Tax number LU18928066
Tax Identification Number 2001/2214/155
Netherlands RSIN 811786523
Poland Numer identyfikacji podatkowej (NIP) number 7740001454
Slovakia VAT/Tax number 2020382111
Slovenia VAT/Tax number 80267432
Tax Identification Number (all API versions)
{
    "accountHolderDetails": {
        "businessDetails": [{
            "taxId": "811786523"
        }]
    }
}

Gender information

Adyen will no longer require the gender field for individuals and shareholders.

Verification notifications

Signatories also go through the verification process similar to shareholders. We will keep you informed about the status through our ACCOUNT_HOLDER_VERIFICATION notifications.

Here are the examples of identity verification notifications:

IDENTITY_VERIFICATION
{
    "eventDate": "2021-07-14T11:17:36+02:00",
    "eventType": "ACCOUNT_HOLDER_VERIFICATION",
    "executingUserKey": "Account Holder Update",
    "live": false,
    "pspReference": "8515748691833060",
    "content": {
        "accountHolderCode": "AH1",
        "kycCheckStatusData": {
            "type": "IDENTITY_VERIFICATION",
            "status": "AWAITING_DATA",
            "requiredFields": ["AccountHolderDetails.BusinessDetails.shareholder", "AccountHolderDetails.BusinessDetails.signatory"]
        }
    }
}

Here are the examples of passport verification notifications:

PASSPORT_VERIFICATION
{
    "eventDate": "2021-07-14T11:39:23+02:00",
    "eventType": "ACCOUNT_HOLDER_VERIFICATION",
    "executingUserKey": "Account Holder Update",
    "live": false,
    "pspReference": "8515748691833060",
    "content": {
        "accountHolderCode": "AH1",
        "kycCheckStatusData": {
            "type": "PASSPORT_VERIFICATION",
            "status": "AWAITING_DATA",
            "requiredFields": ["AccountHolderDetails.BusinessDetails.Signatories.Document.document"]
        },
        "signatoryCode": "d0d93667-89ac-45be-9b9c-c6236049995f"
    }
}

What do I need to do

Here are the necessary steps to ensure compliance with the new verification requirements. Choose your implementation option and proceed with the corresponding instructions:

Hosted Onboarding Page

Existing sub-merchants

For existing sub-merchants, we might request additional information from them during our periodic risk assessments. Notify your existing sub-merchants about the upcoming changes and start the verification process when requested by Adyen.

To check which information has been already provided, use the /getAccountHolder endpoint.

New sub-merchants

If you are onboarding a new sub-merchant using HOP, Adyen will take care of requesting the necessary information as described in Step 2 of the HOP integration page.

Alternatively, you can collect all the required information in advance and provide it when creating an account using the /createAccountHolder endpoint.

Build your own implementation

Existing sub-merchants

For existing sub-merchants, use the /updateAccountHolder endpoint to provide the above-mentioned required information when requested by Adyen.

To check which information has been already provided, use the /getAccountHolder endpoint.

New sub-merchants

If you are onboarding a new sub-merchant, proceed with the provided instructions:

  1. Create an account holder.
  2. Collect the above-mentioned required information.
  3. Use the /updateAccountHolder endpoint to send this information to Adyen as described in Step 2.
  4. Follow the rest of the steps from the Custom onboarding page.

Alternatively, you can collect all the required information in advance and provide it when creating an account using the /createAccountHolder endpoint. Then, skip steps 2 and 3.

See also