---
title: "Verification types"
description: "Collect verification information from your users upfront or in a staggered process."
url: "https://docs.adyen.com/platforms/verification-overview/verification-types"
source_url: "https://docs.adyen.com/platforms/verification-overview/verification-types.md"
canonical: "https://docs.adyen.com/platforms/verification-overview/verification-types"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# Verification types

Collect verification information from your users upfront or in a staggered process.

[View source](/platforms/verification-overview/verification-types.md)

Adyen provides two ways for collecting verification information from your users:

* Upfront: users must complete full verification before they can process payments and receive payouts through your platform.
* Staggered: only the minimum required verification data is collected from users before they start using your platform, based on processing volume, country/region of operation, and other relevant factors.

As a platform, you should collect verification data from your users upfront because the capability to receive payments is automatically requested for them. If you are a [payment facilitator](/platforms/account-structure-resources/platform-structure#payment-facilitator), you can request to use a staggered verification process.

## Upfront verification

In an upfront verification process, you collect all of the [required verification information](/platforms/verification-requirements/required-kyc-information/) when you onboard your user. The information is verified after you create an account holder. You will not need to ask them for additional information if they reach a higher verification tier.

## Staggered verification

Only [payment facilitators](/platforms/account-structure-resources/platform-structure#payment-facilitator) can use staggered verification. To request it, reach out to your Adyen contact.

In a staggered verification process, you collect additional required information from users only when needed. Verification [tiers](#tiers) determine what additional information needs to be collected and verified by Adyen to enable or continue payouts for account holders. When a user processes a higher amount of funds than the limit of their current tier, they are moved to a higher tier.

This approach is faster because not all users need to complete the full verification process. For example, users who only process smaller amounts are required to complete fewer verification checks, so they can be paid out quickly.

When a user is [moved to a higher tier](/platforms/verification-overview?tab=users_move_to_a_higher_tier_3#when-users-move-to-a-higher-tier-staggered-verification), their payouts are temporarily disallowed until they complete additional verification checks. [Adyen informs you](/platforms/verification-overview?tab=users_move_to_a_higher_tier_3) of these changes and what data needs to be provided through webhooks. After your user provides the data and Adyen verifies it, their payouts are allowed again.

### Tiers

Tiers are determined by the user's [country](/platforms/verification-requirements#country-of-operation), [legal entity](/platforms/verification-requirements#legal-entity-type), and processed amount. There are four tiers.

Processing volume is not the only factor in a user being moved to a higher tier. Triggered [verification checks](/platforms/verification-overview#when-the-verification-process-happens) and requesting high-risk [capabilities](/platforms/verification-overview/capabilities) may result in account holders being moved to a higher tier.

For the following countries and regions, tiers for processed amounts are calculated based on their local currencies.

| User country/region | Currency |
| ------------------- | -------- |
| Australia           | AUD      |
| United States       | USD      |
| Canada              | CAD      |
| New Zealand         | NZD      |
| Singapore           | SGD      |
| Hong Kong           | HKD      |
| Other               | EUR      |

## See also

* [Required information](/platforms/verification-requirements/required-kyc-information)
* [User capabilities](/platforms/verification-overview/capabilities)
