Skip to main content
Register the transfer recipient as a user in your Crossmint project, then attach the recipient data required for payouts. Crossmint uses this data to screen recipients against Office of Foreign Assets Control (OFAC) sanctions lists.

Requirements

  • An API key
  • A stable user identifier in your system (used as userLocator)
  • A Crossmint wallet address for the recipient (or the ability to create one)

Step 1: Accept Crossmint’s Privacy Policy

Before sharing any user KYC data with Crossmint, you must ensure your users have accepted Crossmint’s Privacy Policy. This is a prerequisite for any company sharing their customers’ KYC data with Crossmint. Requirements for collecting consent Consent must be obtained following the guidelines below:
  1. The user must have the ability to see the terms they must accept
  2. The user must grant consent with a checkbox, unchecked by default
  3. The user does not need to open the hyperlink to the privacy policy to view the terms
  4. The user needs to see Crossmint’s logo in the flow
  5. The specific text that you must present to your end user is: “I consent to my KYC data being processed by Crossmint in accordance with its Privacy Policy
  6. The text can be localized but must link to the same privacy policy link provided above
  7. If the privacy policy is updated, you must ask the user to agree to the above terms again
Meeting these requirements is mandatory for sharing user KYC data with Crossmint. Only record acceptance through the API below after the user has granted consent this way. Crossmint audits data-sharing integrations for compliance with these requirements.
Once the user has accepted the privacy policy, record their acceptance using the Accept Legal Document endpoint:
This call also creates a user with the specified userLocator if one does not already exist.

Step 2: Create a User

Register the transfer recipient as a user in your Crossmint project and associate the user with a Crossmint wallet address. There are two ways to create a user:

Choose a Method

  • Use Method 1 if you create the wallet and user in one API call
  • Use Method 2 if you register the user first and create the wallet later
Create a wallet for a user and associate it to a userLocator by setting the owner property. This method creates in a single API call both the wallet, and the user associated with it.The owner property accepts a userLocator. This associates the wallet with the user identifier in your system.
  • If you have your own user IDs, set the wallet's "owner" property using the userId format (userId:<userId>, e.g., userId:johnd-123).
  • If you bring your own auth, Crossmint automatically extracts the user ID from your JWT and assigns it to the wallet's "owner" property.
Register a user with Crossmint without creating a wallet yet. Later, when you create a wallet for that registered user, you can link the wallet’s owner property to that user’s registered userLocator value. This will associate the wallet with the user identifier in your system.
  • If you have your own user IDs, set the wallet's "owner" property using the userId format (userId:<userId>, e.g., userId:johnd-123).
  • If you bring your own auth, Crossmint automatically extracts the user ID from your JWT and assigns it to the wallet's "owner" property.
Step 1: Register the user
Step 2: Create wallet and link to registered userWhen you are ready to create a wallet for the registered user, use the same userLocator in the owner field:

Step 3: Register User Data

Use the Create User API to attach userDetails to the user. To see data requirements by activity and region, see Data Requirements. For payouts, the only information needed is userDetails.

Guides

Data Requirements

Quickstart