Solution Architecture

How Crossmint handles stablecoin compliance on your behalf and how to architect your integration

Crossmint’s infrastructure is designed so that you do not need to build or run compliance systems yourself. Instead, Crossmint acts as the regulated party and handles all compliance on your behalf — you orchestrate your flows by calling APIs.

This page explains the architecture behind this approach and the three steps involved in setting up a compliant stablecoin integration.

Every production customer gets access to a forward-deployed solutions architecture team. Before go-live, the team reviews the full flow of funds, identifies edge cases, and ensures the integration is structured correctly from a compliance standpoint. Contact the team to get started.

How Crossmint Handles Compliance

Rather than providing compliance tooling for customers to operate themselves, Crossmint structures the flow of funds so that Crossmint is the regulated party — the entity that holds the licenses, runs the AML program, and assumes the legal liability. You call APIs; Crossmint handles the rest.

Your Responsibilities	Crossmint Responsibilities
Design an appropriate flow of funds for your use case	Review your flow of funds
Call Crossmint APIs to create wallets, register identities, and trigger transfers, on-ramps, and off-ramps	KYC/KYB identity verification
	Sanctions screening
	AML program (SARs, transaction monitoring, ongoing due diligence)
	Obtain and maintain licenses and licensed vendor relationships
	Travel Rule compliance
	Safeguarding and fund protection

Building Your Integration

Using Crossmint’s stablecoin APIs generally follows three steps.

1. Create Wallets for Relevant Entities

Use the Wallets API to create wallets for every entity in your system:

• Company wallets for your own holdings and operations
• User wallets for your customers (or they can connect their own external wallets)
• Agent wallets for AI agents that need to hold or move stablecoins autonomously

Wallets are the foundation — they represent the accounts that send and receive stablecoins.

2. Register Identities for Every External Party

Every external third party that interacts with your system — whether it is a customer using your platform, a contractor receiving a payout, or any other counterparty — must be registered using Crossmint’s Identity APIs.

When you register an identity, Crossmint’s APIs automatically determine what level of verification is needed based on:

• The type of entity (individual vs. business)
• The activity they will perform (receiving a payout vs. on-ramping fiat)
• The jurisdictions involved

You do not need to decide the KYC/KYB level yourself. The API tells you what is required and guides the verification flow.

3. Call Money Movement APIs — Crossmint Handles the Checks

Use the money movement APIs to execute your stablecoin flows:

• Payouts for wallet-to-wallet stablecoin transfers
• On-ramp to convert fiat to stablecoins
• Off-ramp to convert stablecoins back to fiat

Crossmint performs all the compliance checks necessary on your behalf on every call.

See Also

Regulatory Landscape

Why stablecoin transfers are regulated and what compliance requirements apply

Treasury Wallet Guide

Create a wallet and check balances in minutes