---
title: "Changes to verification requirements"
description: "Learn about the updates in the verification requirements starting from August 1, 2022."
url: "https://docs.adyen.com/classic-platforms/verification-process/requirements-update"
source_url: "https://docs.adyen.com/classic-platforms/verification-process/requirements-update.md"
canonical: "https://docs.adyen.com/classic-platforms/verification-process/requirements-update"
last_modified: "2022-11-11T11:00:00+01:00"
language: "en"
---

# Changes to verification requirements

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

[View source](/classic-platforms/verification-process/requirements-update.md)

This page is for classic Adyen for Platforms integrations. If you are just starting your implementation, refer to our [new integration guide](/adyen-for-platforms-model) 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, or when an account holder's information or processing tier is updated.

## New requirements

* [Distinguish between types of shareholders](#types-of-shareholders)
* [Identify signatories](#signatories)
* [Identify nationality of natural persons residing in Hong Kong or Singapore](#nationality-hk-singapore)
* [Collect principal place of business address](#principal-place-of-business)
* [Collect information about parent company](#parent-company-info)
* [Collect company Tax Identification Number depending on customer risk classification](#company-tin)
* [Stop collecting information about gender](#gender-info)

### Types of shareholders

Shareholders can be of two types:

* **Owner**: Individuals who directly or indirectly own 25% or more of the total shares, voting rights or other equity in the organization.
* **Controller**: Any individuals who exercise ultimate effective control in making decisions for the whole company. If such an individual cannot be identified, then members of senior management must be identified as controllers. 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 operating in non-EEA countries, we require that you provide at least one controller.
* **Signatory**: Officers or representatives who legally represent the organization towards Adyen and are authorised to enter a binding agreement with Adyen on behalf of their organization. All signatories must be identified.

### Tab: API version v6 and v5

**Owner shareholder**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"shareholderType": "Owner",
				"name": {
					...
				}
			}]
		}
	}
}
```

**Controller shareholder**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"shareholderType": "Controller",
				"name": {
					...
				},
				"jobTitle": "Chief Executive Officer"
			}]
		}
	}
}
```

### Tab: API version v4 and earlier

**Owner shareholder**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"ShareholderContact": {
					"shareholderType": "Owner",
					"name": {
						...
					}
				}
			}]
		}
	}
}
```

**Controller shareholder**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"ShareholderContact": {
					"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. Depending on their country of residence, the signatory's ID information may also be required. We do not limit the number of signatories you can add but we require that you provide at least one.

### Tab: API version v6 and v5

**Signatory**

```json
{
	"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"
			}]
		}
	}
}
```

### Tab: API version v4 and earlier

**Signatory**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"signatories": [{
				"SignatoryContact": {
					"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**

```json
{
	"accountHolderDetails": {
		"individualDetails": {
			"personalData": {
				...
				"nationality": "SG"
			}
		}
	}
}
```

### Tab: API version v6 and v5

**Nationality Shareholder**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"personalData": {
					"nationality": "SG",
				}
			}]
		}
	}
}
```

### Tab: API version v4 and earlier

**Nationality Shareholder**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"ShareholderContact": {
					"personalData": {
						"nationality": "SG",
					}
				}
			}]
		}
	}
}
```

### Tab: API version v6 and v5

**Nationality Signatory**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"personalData": {
					"nationality": "SG"
				}
			}]
		}
	}
}
```

### Tab: API version v4 and earlier

**Nationality Signatory**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"shareholders": [{
				"SignatoryContact": {
					"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)**

```json
{
	"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](/classic-platforms/verification-process/requirements-update/Approved_List_ISO10383_MIC_v2.xlsx). 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](https://www.iso20022.org/market-identifier-codes).
  * `stockTicker` is free format.

### Tab: API version v6 and v5

**Public companies**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"listedUltimateParentCompany": [{
				"businessDetails": {
					"legalBusinessName": "Adyen",
					"registrationNumber": "123456",
					"legalEntity": "publicCompany",
					"stockExchange": "XAMS",
					"stockTicker": "ADYEN",
					"stockNumber": "NL0012969182"
				},
				"address": {
					"country": "NL"
				}
			}]
		}
	}
}
```

### Tab: API version v4 and earlier

**Public companies**

```json
{
	"accountHolderDetails": {
		"businessDetails": {
			"listedUltimateParentCompany": [{
				"UltimateParentCompany": {
					"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 USD 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)**

```json
{
	"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](https://docs.adyen.com/api-explorer/Notification/latest/post/ACCOUNT_HOLDER_VERIFICATION) notifications.

Here are the examples of identity verification notifications:

### Tab: AWAITING\_DATA

**IDENTITY\_VERIFICATION**

```json
{
	"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"]
		}
	}
}
```

### Tab: DATA\_PROVIDED

**IDENTITY\_VERIFICATION**

```json
{
	"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": "IDENTITY_VERIFICATION",
			"status": "DATA_PROVIDED"
		},
		"signatoryCode": "d0d93667-89ac-45be-9b9c-c6236049995f"
	}
}
```

Here are the examples of passport verification notifications:

### Tab: AWAITING\_DATA

**PASSPORT\_VERIFICATION**

```json
{
	"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"
	}
}
```

### Tab: INVALID\_DATA

**PASSPORT\_VERIFICATION**

```json
{
	"eventDate": "2021-07-14T12:03:22+02:00",
	"eventType": "ACCOUNT_HOLDER_VERIFICATION",
	"executingUserKey": "Account Holder Verification",
	"live": false,
	"pspReference": "8515748691833060",
	"content": {
		"accountHolderCode": "AH1",
		"kycCheckStatusData": {
			"type": "PASSPORT_VERIFICATION",
			"status": "INVALID_DATA",
			"summary": {
				"kycCheckCode": 1101,
				"kycCheckDescription": "The ID document does not belong to the configured account holder. Please upload a document that does belong to the account holder or change the details of the account. If the document is the correct one, please double check there are no typing errors in the name or date of birth of the account holder."
			}
		},
		"signatoryCode": "f42c2593-341c-44af-b4f7-af502e567849"
	}
}
```

## 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](#hosted-onboarding-page) (HOP)
* [Build your own implementation](#build-own-implementation)

### 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](/classic-platforms/onboard-users/hosted-onboarding-page#get-hosted-onboarding-page-url) process when requested by Adyen.

To check which information has been already provided, use the [/getAccountHolder](https://docs.adyen.com/api-explorer/#/Account/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](/classic-platforms/onboard-users/hosted-onboarding-page#get-hosted-onboarding-page-url) 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](https://docs.adyen.com/api-explorer/#/Account/createAccountHolder) endpoint.

### Build your own implementation

#### Existing sub-merchants

For existing sub-merchants, use the [/updateAccountHolder](https://docs.adyen.com/api-explorer/#/Account/updateAccountHolder) endpoint to provide the above-mentioned required information when requested by Adyen.

To check which information has been already provided, use the [/getAccountHolder](https://docs.adyen.com/api-explorer/#/Account/getAccountHolder) endpoint.

#### New sub-merchants

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

1. Create an [account holder](/classic-platforms/account-holders-and-accounts#create-an-account-holder).
2. Collect the above-mentioned [required information](#new-requirements).
3. Use the [/updateAccountHolder](https://docs.adyen.com/api-explorer/#/Account/updateAccountHolder) endpoint to send this information to Adyen as described in [Step 2](/classic-platforms/onboard-users/custom-onboarding#update-account-holder).
4. Follow the rest of the steps from the [Custom onboarding](/classic-platforms/onboard-users/custom-onboarding) page.

Alternatively, you can collect all the required information in advance and provide it when creating an account using the [/createAccountHolder](https://docs.adyen.com/api-explorer/#/Account/createAccountHolder) endpoint. Then, skip steps 2 and 3.

## See also

* [Onboard and verify users](/classic-platforms/onboard-users)
* [Hosted Onboarding Page](/classic-platforms/onboard-users/hosted-onboarding-page)
* [Build a custom onboarding application](/classic-platforms/onboard-users/custom-onboarding)
