Skip to main content
Anchor use cases for Wallet-as-a-Service partners, on the sub-account model (managed sub-accounts, KYC reliance, or shared-KYC sub-accounts). Each recipe links to the guide and API reference that document its endpoints. This is a curated selection of common use cases, not the full API surface; for every endpoint and parameter, see the Developer guide and the Payment Integration guide.
These are private (signed) endpoints, so each call needs an API key. Enablement prerequisites vary by flow:
  • Sub-account and payout flows require institutional onboarding (KYB).
  • Sub-account crypto deposits are disabled by default — request enablement through the assigned account manager.
  • WhiteBIT Codes work on a regular account without KYB (see the live demo below).
A runnable Python starter that packages these flows is planned.

Per-user deposit address

Create a sub-account per end user; once crypto deposits are enabled for the account, get each sub-account’s deposit address with its own API key.
Endpoints: sub-account/create, main-account/address

Reconcile deposits

Credit users from deposit webhooks, with history polling as the required fallback. Deduplicate by uniqueId.
Endpoints: main-account/history + webhooks

Payout / withdraw

Send a crypto payout to a user’s address, with a conversion before the payout where needed; the main account approves each sub-account withdrawal.
Endpoints: main-account/withdraw, sub-account/withdraw/confirm

WhiteBIT Codes settlement

Move balance fee-free between accounts by creating and applying a WhiteBIT Code.
Endpoints: main-account/codes, main-account/codes/apply

Payout with conversion

Hold one currency, pay out another: move the source currency to the Trade balance, quote, confirm, move the converted asset back to Main, then withdraw.
Endpoints: main-account/transfer, convert/estimate, convert/confirm, main-account/withdraw

Refund a canceled deposit

Return funds from a canceled deposit (status 4/9) to an address.
Endpoints: main-account/refund-deposit

Exact-amount payout

The receiver gets the exact amount; the fee is charged on top of the account balance.
Endpoints: main-account/withdraw-pay

Multichain payout

Pay out an asset on any supported network via the network parameter.
Endpoints: main-account/withdraw

​
Run the recipes

Each use case above maps to signed REST calls documented in the Payment Integration guide, which carries copy-pasteable cURL and Python examples per endpoint. Before running any flow, create an API key with the required permissions and confirm the enablement prerequisites above apply to the account. A fuller Python starter that packages every recipe into one clone-and-run project is planned; the WhiteBIT Codes flow below is runnable today.

​
Demo

Run it (needs a key with Codes permission and USDT on the main account):
Live WhiteBIT Codes on a real balance: create a code for 1 USDT with POST /api/v4/main-account/codes and apply it with POST /api/v4/main-account/codes/apply, then watch the main-account balance move. Real API calls, no mock. To reproduce: use an API key with WhiteBIT Codes permission on an account that holds the USDT on its main balance, then call the create and apply endpoints — see WhiteBIT Codes and the create and apply references.

​
What’s next

WaaS integration guide

Verification variants, deposit and payout flows, and compliance.

WaaS overview

What WaaS is and how to get started.