Crypto-As-A-Service (CAAS)
Crypto-As-A-Service (CAAS) is a backend API solution that lets a platform offer crypto functionality to its users without building a full exchange, custody, wallet, trading, or settlement infrastructure from scratch.
Instead of operating the full crypto stack yourself, your application connects to Binance through APIs. Your team only needs to build and manage the front end user experience, while the CAAS backend handles the core crypto operations such as account creation, wallet management, balances, transfers, trading, deposits, withdrawals, and reporting.
Account Structure
CAAS works on a modular level with the sub-account system as the central core infrastructure. Each account is held by a master account and every user under it is created as a sub-account. Each sub-account functions as a wallet with its own unique deposit address.
See Getting Started for how to create sub-accounts and issue their API keys.
What the API covers
Once that foundation is in place, available products such as institutional buy/sell crypto (on/off-ramp), spot trading, futures trading, and KYC SaaS can be layered on top as modular services.
API Integration generally covers:
| Area | What it does |
|---|---|
| CAAS Account | Create and manage Binance sub-accounts for the partner's end users, and manage their API keys and permissions. |
| CAAS Asset | Query sub-account balances and deposit history, and move funds between the master account and its sub-accounts. |
| CAAS Fee | Query and configure the commission the partner earns on its end users' activity. |
| Wallet | External movement of funds: fetch a sub-account's deposit address, submit withdrawals, and query deposit and withdrawal history and per-coin network config, through /sapi/v1/capital/*. |
| Travel Rule | Required where your sub-accounts sit under a Binance local entity. Submit originator/beneficiary information for deposits and withdrawals and look up VASPs and per-country questionnaires. |
| Spot Trading | Place and manage spot orders for your end users' sub-accounts, and query their trades and order history, through the main /api/* endpoints. |
| Futures Trading | Trade USD-M futures from your end users' sub-accounts through the main /fapi/* endpoints. COIN-M is covered by /dapi/*. |
| KYC SaaS | Verify your end users' identity: submit KYC information for a sub-account, query its verification status, and respond to requests for additional information. |
| Markup | Set the commission your end users pay above Binance's own fee, using fee groups. See the Markup Overview. |
| Institutional Buy/Sell | Embed a fiat on/off-ramp in your own application: quote, execute, and track end-user fiat-to-crypto purchases and sales. |
KYC SaaS, Markup and the Institutional Crypto Buy/Sell Solution are modules enabled per partner, on top of the core CAAS integration. Travel Rule applies only to sub-accounts held under a Binance local entity — see the deposit and withdrawal questionnaires. Everything else is part of the base integration.
Where to go next
Next, read Getting Started for prerequisites and the integration order, then the Integration Guide for the step-by-step account creation flow. The API basics are base URLs, rate limits and endpoint security. Release history is in the Binance Link Change Log.
Before you integrate
CAAS is a gated service. Availability is subject to institutional onboarding, jurisdiction, Binance entity, and the approved commercial model. For more information, please contact link@binance.com or your account manager.