What CaaS provides
- A deposit address per end user — issued from the partner’s account for each currency and network. See Address issuance and end-user mapping.
- Conversion — between supported assets at a quoted rate with Convert.
- Crypto payouts — withdrawals from the partner’s account to the addresses end users choose. See Payouts.
- Fiat — added in optional Phase 2 onboarding and run through the partner’s WhiteBIT account. See the On/Off-Ramp guide.
- Custody and security — custody and the security certifications of the WhiteBIT platform. See Security and compliance.
Who CaaS is for
How CaaS works
CaaS runs on the partner’s own WhiteBIT account: the partner issues a deposit address per end user and keeps the end-user ledger, and WhiteBIT processes deposits and payouts on the blockchain networks. See Integration models for how this compares with sub-accounts and with customers’ own accounts.Responsibilities
In the European Union, a separate onboarding process and separate rules apply.
What end customers can do
- Create crypto wallets — a unique deposit address per end user. See the Integration guide.
- Store crypto in institutional custody — see Security and compliance.
- Buy and sell with fiat — fiat access is added in optional Phase 2 onboarding and runs through the partner’s WhiteBIT account; Convert accepts the supported fiat currencies as either leg of a conversion. See Convert and the On/Off-Ramp guide.
- Send and receive crypto — on-chain transfers to and from external addresses.
Program terms
Commercial terms are agreed per contract during onboarding.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; timing depends on integration
scope.
Security and compliance
- 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% of digital assets are stored in cold wallets (CaaS product page).
- 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.
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
Issue deposit addresses, credit deposits, pay out, and reconcile.
FAQ
Common questions on scope, deposit addresses, payouts, onboarding, and support.
Integration models
How the partner’s own account compares with sub-accounts and customers’ own accounts.