Skip to main content
The data required for each user varies depending on the type of regulated activity they want to perform and their residency.

Progressive KYC Tiers for On/Offramp

On/offramp verification is progressive with KYC tiers based on transaction behavior and risk. A user typically does not have to provide their full data up front for low volume activity. See Onramp user onboarding and Offramp KYC & compliance for how and when each tier applies to each product, including regional differences.
The occasional user KYC tier is available for both Crossmint hosted and API based flows. Availability can vary by region.

Additional Document Requests

At any time, Crossmint’s compliance team may request a specific additional document from a user such as a proof of address, a source of wealth document, or an identity document. These requests are independent of a user’s KYC tier and may happen even after a prior successful verification. Document collection is handled automatically in Crossmint hosted KYC flows. If you are using the KYC data sharing API, this is surfaced through the missingDocuments verification status.

Field Requirements

The tables below show what identity information each product needs, by tier and region. For more technical details see the Create User API.
Payouts do not need kycData or dueDiligence.
The recipient of a regulated payout is not required to directly accept Crossmint’s legal documents.

Acceptable Identity Documents

  • United States: Social Security Number (SSN) in kycData.identityDocument. If Crossmint asks for a photo ID, a driver’s license or a passport.
  • EU/EEA: Passport, or a national ID card issued by an EU/EEA country or Switzerland. Residents of Spain can also use a Spanish residency permit, but cannot use a Spanish passport.
  • Mexico, Colombia, Argentina, Canada: Passport, or a national ID card issued by the country of residence, an EU/EEA country, or Switzerland.
  • Rest of World: Passport, or a national ID card issued by an EU/EEA country or Switzerland.
The document number must be valid for the issuing country.

Projects Using the KYC Data Sharing API

  • Projects set up for KYC data sharing must send the verificationHistory object which holds the timestamps of when your platform completed its own ID check and liveness check with every dueDiligence submission. See Import User KYC Data. Other projects must not send verificationHistory, or the request is rejected.
  • The end user’s IP address is required whenever kycData is sent.
  • Users must accept Crossmint’s Terms of Service before on/offramp activity. Crossmint hosted flows collect acceptance automatically. API based integrations record it through the Accept Legal Document endpoint with type: crossmint-terms-of-service and region (us, eu, or worldwide). Terms of Service acceptance is not required for payouts.

Next Steps

Quickstart

Register your first user and upload documents in minutes.

Talk to an expert

Contact the Crossmint sales team for support.