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

ModelBest forHow it works
Import KYC dataPlatforms that already verify usersYou pass user data to Crossmint via API (Sumsub token-sharing coming soon)
Crossmint-hostedTeams that want the fastest integrationThe user completes KYC inside secure embedded components

​
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. These endpoints use a userId: locator, a unique identifier you choose for the user.

​
KYC Tiers

Crossmint has different KYC tiers based on transaction volume and risk profile:
TierApplies whenRequirements
Tier 1Not available for offramps
Tier 2All offramp usersAs specified in the data requirements page

​
Guides

Import KYC Data

Data Requirements