Background

Breeze uses a tiered KYC model where different levels of verification may be required over time. Each tier represents a progressively more detailed level of identity verification.

This approach allows most users to start with a lightweight verification experience while enabling additional checks when needed to maintain security, compliance, and trust across the ecosystem. By scaling verification requirements progressively, Breeze reduces unnecessary friction during onboarding while ensuring appropriate safeguards are applied as accounts evolve.

⚠️
If a user’s KYC is rejected at any tier, they will be blocked from completing payouts. See KYC Rejection for more details.

When Is Each Tier Required?

Breeze uses a risk-based model to determine the required KYC tier at the point of a payout. The primary factors include the payout method being used and certain risk and compliance indicators associated with the customer’s activity.

Payout method minimums:

Payout Method	Minimum Tier
Card (FIAT)	Tier 1
Bank Transfer (FIAT)	Tier 1
Crypto	Tier 2

Beyond the payout method, Breeze may require a higher tier as a customer’s activity evolves. When this happens, the user will be prompted at the point of their next payout attempt.

Information that is collected for each tier

Fields	Type	Description
email	`string`	Email of the user
firstName	`string`	Max length 100
middleName	`string`	Max length 100
lastName	`string`	Max length 100
dateOfBirth	`string`	In `YYYY-MM-DD` format. Must be a past date, no more than 150 years ago.
phoneNumber	`string`	Max length 20. For United States, use either `XXXXXXXXXX`, `1XXXXXXXXXX` or `+1XXXXXXXXXX` format.
taxId	`string`	Government-issued tax identifier. For United States, provide the Social Security Number (SSN). For other countries, provide the equivalent national tax identification number.
address	`Object`	See details on the nested fields in the rows below with prefix `address.`
address.line1	`string`	Sub-field of `address` object. Max length 255.
address.line2	`string`	Sub-field of `address` object. Max length 255.
address.city	`string`	Sub-field of `address` object. Max length 100.
address.state	`string`	Sub-field of `address` object. For United States, use either the Two-Letter State Abbreviations format or the ISO-3166-2 format.
address.postalCode	`string`	Sub-field of `address` object. For United States, use either the 5-digit format (`XXXXX`) or the ZIP+4 format (`XXXXX-YYYY`).
address.country	`string`	Sub-field of `address` object. In ISO 3166-1 alpha-2 format.

⚠️
API submission limitation: Most Tier 1 fields can be pre-supplied via the Customer Onboarding API. However, taxId(SSN) is the exception — it cannot be passed via API and must always be collected from the user via the hosted KYC form. Supplying all other Tier 1 fields will pre-fill the form but will not skip it.