Broker Program overview
The Broker Program offers a revenue-sharing model where brokers receive up to 40% of trading fees generated by referred users. Fee share model: The base fee share is 40% of the trading fee generated by each referred user. Worked example:| WBT Holdings | Fee Share |
|---|---|
| 200 WBT | 40% |
| Up to 2,000,000 WBT | 50% |
- Sub-account architecture for per-customer isolation
- Per-customer API keys
- Fee-free internal transfers between master and sub-accounts
- Cross-marketing support
Customer onboarding flow
Each end customer is onboarded as a sub-account under the broker’s master account.Create a sub-account
Call the sub-account creation endpoint to create a new sub-account for the customer. Each sub-account receives an independent balance and can have dedicated API keys.Endpoint:
POST /api/v4/sub-account/create — API ReferenceGenerate a KYC verification URL
Generate a KYC URL for the sub-account holder. The end customer completes KYC verification through the WhiteBIT interface (WhiteBIT-branded, not white-label).Endpoint:
POST /api/v4/sub-account/kyc-url — API ReferenceCustomer completes KYC
The end customer opens the KYC URL and completes identity verification. The broker monitors KYC status via the sub-account details endpoint.
The KYC verification flow is WhiteBIT-branded. The broker cannot white-label the KYC interface.
- curl
- Python
Sub-account management
Sub-accounts provide complete isolation — each customer has independent balances, order history, and API credentials. CRUD operations:| Operation | Endpoint | Description |
|---|---|---|
| Create | POST /api/v4/sub-account/create | Create a new sub-account |
| List | POST /api/v4/sub-account/list | List all sub-accounts |
| Block | POST /api/v4/sub-account/block | Suspend trading for a customer |
| Unblock | POST /api/v4/sub-account/unblock | Re-enable trading for a customer |
POST /api/v4/sub-account/transfer — see the API Reference.
- Master to sub-account: funding a customer account
- Sub-account to master: revenue collection
Per-customer API keys
Each sub-account can have dedicated API keys with independent IP whitelists and permissions.- Create API keys per sub-account for customers who need direct API access
- IP whitelisting: up to 50 IP addresses per API key
- Permissions: configure per-key permissions (
Info + Tradingvs.Info + Trading + Deposit + Withdraw)
clientOrderId naming
conventions — see Client Order ID: Broker Implementation.
Revenue monitoring
Track fee share revenue across all referred users to monitor Broker Program earnings. Fee share tracking: Monitor trading activity across sub-accounts to estimate fee share earnings. The worked fee share calculation from the Overview section applies to each trade executed by a referred user. Reporting recommendations:- Track trading volume per sub-account over 30-day rolling windows
- Monitor fee tier progression — higher volume improves the base fee rate, which increases the absolute fee share
- Export trade history per sub-account for reconciliation
Fiat for broker end users
European broker end users frequently expect EUR deposit and withdrawal capabilities. Fiat operations (EUR/SEPA) require institutional onboarding with fiat access approval. The broker’s master account must complete the two-phase onboarding process (crypto access via KYB, then fiat access via fiat processing partner review). Once fiat access is approved on the master account, sub-accounts can process fiat deposits and withdrawals. See Institutional Onboarding for the two-phase process. See Payment Integration for fiat endpoint details.Fiat deposit and withdrawal access requires completion of institutional onboarding including the fiat provider approval phase. Contact institutional@whitebit.com to begin the process.
Integration checklist
Complete the following checklist before going live with the Broker Program integration.- Program enrollment — Application submitted to institutional@whitebit.com and approved.
- Master account KYB — KYB verification completed for the broker entity.
- API key generated — Master account API key created with appropriate permissions.
- Sub-account creation — Successfully created at least one test sub-account.
- KYC URL generation — KYC URL generated and tested for a sub-account.
- Fund transfer — Fee-free transfer between master and sub-account verified.
- Per-customer API key — API key created for a sub-account with IP whitelist configured.
- Balance monitoring — Sub-account balance query working.
- Fee share tracking — Revenue monitoring process established.
- Fiat access (if applicable) — Institutional onboarding Phase 2 completed for SEPA access.
- Security review — IP whitelists, API key permissions, and secret storage reviewed per Security Best Practices.
- Go-live review — All items on the Go-Live Checklist verified.
What’s Next
Sub-Accounts
Full product overview for the sub-account system.
Institutional Onboarding
Step-by-step KYB and fiat onboarding process.
Go-Live Checklist
Pre-production readiness verification.