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.

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`	For United States, use social security 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.