Scope and delivery
Delivery model
WaaS gives each end user a sub-account under the partner’s main account, with deposits, withdrawals, conversion, and trading. See the WaaS overview.Verification variants
Managed sub-accounts, KYC reliance, or shared KYC
Three variants share the sub-account architecture: managed sub-accounts (WhiteBIT verifies each end user), sub-accounts with KYC reliance (the partner verifies; gated), and shared-KYC sub-accounts (each sub-account carries the main account’s verification; WhiteBIT verifies only the partner). For end users with personal WhiteBIT accounts, the partner integrates through App Builders instead. See Choose a verification variant.KYC reliance eligibility
KYC reliance is gated: it requires a supervised, AML-obligated entity and an individual WhiteBIT Compliance assessment. See the eligibility conditions.Shared-KYC sub-accounts
A shared-KYC sub-account is created withshareKyc: true and carries the main account’s verification. WhiteBIT verifies the partner during Institutional Onboarding (KYB) and does not verify the end users; the partner verifies its own end users. The partner still gets a separate balance, deposit address, and API keys per end user, fee-free transfers, and the main account’s approval of each sub-account withdrawal. See Build path per variant.
Pooled account
A single account that holds all end users’ funds, with a deposit address per end user and the partner’s own ledger, is the Crypto-as-a-Service model. See Integration models.Onboarding and access
Onboarding phases
Institutional onboarding has two phases: Phase 1 grants crypto operations access after KYB; optional Phase 2 adds EUR/SEPA fiat access. See Institutional Onboarding.Deposit address per end user
Each sub-account has a separate crypto deposit address, requested with a call signed by the sub-account’s API key. Crypto deposits to sub-accounts are disabled by default; the account manager enables these deposits for the account. See Sub-Accounts and the Developer guide.Integration
Reconciliation approach
A sub-account counts as a separate account and can have its own webhook. Webhook delivery is retried but not replayed, so poll the deposit history of each sub-account on a schedule as well, even when a webhook is configured. Sign the history call with the sub-account’s API key. Deduplicate byuniqueId. See Payment and payout flows.
Fiat operations scope
Fiat deposits and withdrawals operate on the partner’s main account, from and to the partner’s own bank account only, not per end user. End users’ fiat stays in the partner’s own system. See the Developer guide.Test environment availability
WhiteBIT does not offer a public testnet or sandbox. Test on the live API with minimum amounts and check per-asset minimums via Asset Status; the WhiteBIT Codes flow in WaaS Recipes is a low-risk way to try a real signed call.Compliance
MiCA and Travel Rule for EEA end users
For EEA users, MiCA restricts some stablecoin operations, 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.Support
Support contacts
The assigned account manager is the primary contact. Programs and onboarding go toinstitutional@whitebit.com. Platform questions are answered at help.whitebit.com, and API documentation is on docs.whitebit.com.
What’s next
Overview
What WaaS provides, the verification variants, and how to apply.
Developer guide
The technical integration: verification variants, deposit and payout flows, compliance, and testing.
WaaS Recipes
Runnable examples with a starter repo.
Partner FAQ
Cross-cutting answers shared across programs — KYB, sandbox, fees, and rate limits.