Skip to main content
Every end user must pass KYC before they can withdraw funds through the Offramp. You can collect this verification with a Crossmint-hosted flow, or pass data you have already verified yourself. This page covers the onboarding models, the KYC tiers, and where to find the exact data requirements.
The user KYC API must be enabled for your project. If calls return "project not configured to support the users KYC endpoints", contact sales to enable it.

Choose Your Onboarding Model

How Verification Works

Verification runs asynchronously. You register the user, trigger verification, then poll until their offramp eligibility reads verified. Only verified users can save a payment method or create an order. The Identity quickstart walks through the full sequence (accept the privacy policy, register the user, trigger verification, upload any required documents, and poll status), and its response reports eligibility per product, including offramp (full KYC) and offramp-light (progressive KYC). These endpoints use a userId: locator, a unique identifier you choose for the user.

KYC Tiers

Crossmint applies KYC tiers based on cumulative transaction volume, transaction frequency, and risk profile — the same model used for Onramp:
Light KYC is available to non-US residents; US residents always complete Full KYC. Identity verification eligibility reports both tiers per user: offramp-light (progressive) and offramp (full).

Guides

Import KYC Data

Data Requirements