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.
Who CaaS is for
What end customers can do
- Create crypto wallets — a unique deposit address per end user across 80+ networks. See Wallet-as-a-Service 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 and spot markets for the crypto side. See the On/Off-Ramp guide.
- Send and receive crypto — on-chain transfers, plus fee-free internal transfers with WhiteBIT Codes.
Onboarding and launch path
The path from first conversation to a live offering has four stages.1
Approval
Review and agree the business case with the WhiteBIT team.
2
Onboarding
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.
3
Integration
Connect the partner platform to WhiteBIT through the API. See the
Integration guide.
4
Launch
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; enablement is not
available via API. Request it through the assigned account manager or 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.
- 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 and 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.
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
for the full list.
How to get started
- Contact institutional@whitebit.com with the business case, target segment, and target regions.
- Prepare for Institutional Onboarding — KYB, plus optional fiat access (Phase 2).
- Build against the Integration guide and clear the Go-Live Checklist before real volume.
What’s next
Integration guide
Route each capability to its guide, align the dedicated-instance architecture, and operate in production.
FAQ
Common questions on scope, onboarding, regions, and support.
Institutional Onboarding
KYB and the two-phase onboarding process.
CaaS product page
Program overview, segments, and figures on institutional.whitebit.com.