> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Crypto-as-a-Service
> Put WhiteBIT behind a partner's product as the exchange, custody, and compliance backend for a white-label crypto offering.
Crypto-as-a-Service (CaaS) lets a partner offer digital-asset functionality under its own brand
while WhiteBIT operates the exchange, custody, and compliance infrastructure behind it. For how
the integration is assembled, see the [Integration guide](/guides/caas-integration).
Launching a full branded exchange fits CaaS. Adding wallets or payouts to an existing product
instead fits [Wallet-as-a-Service](/guides/waas-overview), the building block CaaS uses for
end-customer wallets.
CaaS orchestrates existing WhiteBIT building blocks rather than adding new API surface. The
[Integration guide](/guides/caas-integration) routes each capability — wallets, payments,
accounts, and compliance — to the guide that documents it.
## What CaaS provides
* A dedicated, custom-branded instance, integrated into the partner's platform through the API.
* End-customer crypto capabilities — wallets, custody, fiat buy and sell, and cross-border
transfers — delivered under the partner's brand.
* The security and compliance posture of the underlying exchange: institutional custody,
certifications, and regulated operation.
* Coverage across 80+ blockchain networks and hundreds of digital assets. Asset and market
coverage and program terms are confirmed during onboarding — see the
[CaaS product page](https://institutional.whitebit.com/crypto-as-a-service).
## Who CaaS is for
| Segment | Typical use |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Banks and EMIs (electronic money institutions) | Embed digital-asset functionality — wallets, custody, buy and sell, transfers — into an existing regulated product. |
| Fintechs and neobanks | Let end customers accept, store, and move digital assets across borders inside the partner app. |
| Telecom operators | Offer crypto buy and sell to subscribers. One implemented pattern is access through a USSD code (a carrier menu dialed as a short code). |
| Core banking and Banking-as-a-Service (BaaS) providers | Integrate CaaS into the product suite and resell it as a white-label option to corporate customers. |
## What end customers can do
* **Create crypto wallets** — a unique deposit address per end user across 80+ networks. See
[Wallet-as-a-Service](/guides/waas-overview) for the wallet-level integration.
* **Store crypto in institutional custody** — 96% of platform digital assets are held in cold
storage, with Fireblocks on the custody side.
* **Buy and sell with fiat** — fiat access over EUR/SEPA rails, added in optional Phase 2
onboarding, with [Convert](/platform/convert) and spot markets for the crypto side. See the
[On/Off-Ramp guide](/guides/on-off-ramp-integration).
* **Send and receive crypto** — on-chain transfers, plus fee-free internal transfers with
[WhiteBIT Codes](/platform/whitebit-codes).
## Onboarding and launch path
The path from first conversation to a live offering has four stages.
Review and agree the business case with the WhiteBIT team.
Complete institutional onboarding — KYC for the director or responsible person and KYB for the
company (Phase 1, crypto operations), with an optional Phase 2 for fiat operations via SEPA. See
[Institutional Onboarding](/institutional/onboarding).
Connect the partner platform to WhiteBIT through the API. See the
[Integration guide](/guides/caas-integration).
Go live with the crypto functionality embedded in the partner product — typically around four
weeks from approval, depending on integration scope.
Crypto deposits are disabled by default on institutional accounts. Once enabled, the capability
applies to the account and its [sub-accounts](/products/sub-accounts/overview); enablement is not
available via API. Request it through the assigned account manager or [institutional@whitebit.com](mailto:institutional@whitebit.com).
## Security and compliance
End customers inherit the security and compliance posture of the underlying platform.
* **Certifications:** ISO 27001, CCSS Level 3, and PCI DSS Level 1; the CCSS Level 3 assessment
is conducted by Hacken. See [Regulatory Compliance](/institutional/compliance).
* **Custody:** 96% cold wallet storage, with Fireblocks integration on the custody side.
* **Regional compliance (EEA):** MiCA restricts some stablecoin operations for EEA users, and the
Travel Rule governs EEA and Turkey transfers. Both affect the assets and flows available to those
end users. See [Regulatory Compliance](/institutional/compliance) and
[Travel Rule](/concepts/travel-rule).
* **Data and licensing:** WhiteBIT processes data in the European Union and provides a Data
Processing Agreement (DPA) on request. VASP registrations and DPA requests are handled by
[compliance@whitebit.com](mailto:compliance@whitebit.com).
The instance model, end-user account mapping, the KYC/KYB split, and commercial terms are agreed
and documented with WhiteBIT during onboarding, before development starts. See
[Architecture alignment during onboarding](/guides/caas-integration#architecture-alignment-during-onboarding)
for the full list.
## How to get started
1. Contact [institutional@whitebit.com](mailto:institutional@whitebit.com) with the business case, target segment, and target regions.
2. Prepare for [Institutional Onboarding](/institutional/onboarding) — KYB, plus optional fiat
access (Phase 2).
3. Build against the [Integration guide](/guides/caas-integration) and clear the
[Go-Live Checklist](/best-practices/go-live-checklist) before real volume.
For compliance, VASP, and DPA matters, contact [compliance@whitebit.com](mailto:compliance@whitebit.com).
## What's next
Route each capability to its guide, align the dedicated-instance architecture, and operate in production.
Common questions on scope, onboarding, regions, and support.
KYB and the two-phase onboarding process.
Program overview, segments, and figures on institutional.whitebit.com.