> ## Documentation Index
> Fetch the complete documentation index at: https://crossmint-devin-1787949784-wallet-docs-two-concept-model.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Data Requirements
> Required data fields by activity type and region
The data required for each user depends on the type of regulated activity they want to perform, the KYC tier that applies, and the user's residency.
## KYC Tiers for On/Offramp
On/offramp verification is progressive. Crossmint applies a KYC tier based on cumulative transaction volume, transaction frequency, and risk profile, so a user does not have to provide the full data set up front for low-value activity.
| Tier | Applies when | What is required |
| :-------------------------- | :------------------------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------- |
| **Progressive (light) KYC** | Up to \$1,000 in total volume in the last 12 months and a low transaction count | `userDetails` and `kycData` only |
| **Full KYC** | Transacting over the progressive (light) KYC limits | Progressive KYC data plus `dueDiligence`, `verificationHistory`, an identity document, and a selfie |
Verification status is reported per tier: `onramp-light` / `offramp-light` for the progressive tier and `onramp` / `offramp` for the full tier. See [Onramp user onboarding](/onramp/introduction/user-onboarding) and [Offramp KYC & compliance](/offramp/concepts/kyc-and-compliance) for how and when each tier applies to each product, including regional differences.
Progressive (light) KYC is available for both the embedded (client-side) flow and the import-KYC-data (server-side) API flow. Availability can vary by region.
### Additional Document Requests
Independently of the tier, Crossmint's compliance team may request a specific document from a user at any time — a proof of address, a source of wealth document, or an identity document. Each is requested on its own, only for the users that need it, and surfaces through the verification status API as `requires-data` with the document listed in `missingDocuments`. Upload the document and re-trigger verification to resolve it — see [the quickstart](/identity/quickstart#additional-document-requests) for the full flow.
## Requirements for non-US residents
The following tables show what information is required for each activity type and tier for users residing outside the United States. To see the specific fields required for each object follow the [Create User API](/api-reference/users/upsert-user) documentation.
### Data Requirements
| Object | Payouts | On/offramp (progressive) | On/offramp (full) |
| ------------------- | :-----: | :----------------------: | :---------------: |
| userDetails | ✅ | ✅ | ✅ |
| kycData | | ✅ | ✅ |
| dueDiligence | | | ✅ |
| verificationHistory | | | ✅ |
### Document Requirements
No documents are required for progressive (light) KYC. Documents are only requested once a user reaches the Full KYC tier. Use the [Upload Document API](/api-reference/users/upload-document) to upload the necessary materials.
| Document Type | Payouts | On/offramp (progressive) | On/offramp (full) |
| ----------------- | :-----: | :----------------------: | :---------------: |
| Identity document | | | ✅ |
| Selfie | | | ✅ |
Proof of address (`proof-of-address`) and source of wealth (`source-of-wealth`) are never part of a standard tier — upload them only when Crossmint's compliance team requests them from a specific user (see [Additional Document Requests](#additional-document-requests)).
Under progressive (light) KYC an identity **number** may still be required inside `kycData.identityDocument` — an ID number for EU/EEA residents (optional for the rest of the world). This is a data field, not a document upload; passport, ID card, selfie, and other document uploads are only requested at the Full KYC tier.
**Identity document types for non-US residents:**
* For residents of countries outside of EU/EEA, only passport (`id-passport`) is accepted. Driving licenses or local ID cards are not accepted.
* For residents of EU/EEA countries, passport (`id-passport`), ID cards (`id-idcard-front`, `id-idcard-back`), or residency permit (`id-residency-permit`, Spain residents only) are accepted.
## Requirements for US residents
There are no KYC tiers for US residents: the required data does not change with transaction volume. What is required depends on the user's state of residence.
### Data Requirements
| Object | Most states | NY, NC, TN, TX, VA |
| ------------------- | :---------: | :----------------: |
| userDetails | ✅ | ✅ |
| kycData | ✅ | ✅ |
| dueDiligence | | ✅ |
| verificationHistory | ✅ | ✅ |
US-specific field rules:
* `kycData.phoneNumber` is **required** (it is optional for non-US residents)
* Identity is provided via SSN in the `kycData.identityDocument` field (type `"ssn"`)
* When the `dueDiligence` object is included, its `estimatedYearlyIncome` field is **required** (it is optional for non-US residents). In states that do not require due diligence, omit the `dueDiligence` object entirely.
### Document Requirements
No identity document upload or selfie is required for standard on/offramp — identity is verified through the SSN provided in `kycData`.
Crossmint's compliance team may still request documents from specific US users (see [Additional Document Requests](#additional-document-requests)). For US residents, an identity document request is satisfied with a passport (`id-passport`) or driver's license (`id-idcard-front`, `id-idcard-back`); a proof of address may also be requested. Source of wealth is generally not requested from US residents.
## Next Steps
Register your first user and upload documents in minutes.
Contact the Crossmint sales team for support.