Embedded Trading FAQ

Answers to common questions about WhiteBIT Embedded Trading.

​

Eligibility and approval

​

Embedded Trading eligibility

Embedded Trading is open to partners that operate trading for end customers, and enrollment is approval-gated — every application is individually reviewed before provisioning is enabled. Apply by emailing institutional@whitebit.com; see Eligibility and approval.

​

KYC reliance for account operators

KYC reliance — WhiteBIT relying on the partner’s own customer verification — may be available to eligible licensed partners under a written agreement, assessed case by case and never enabled by default. The eligibility criteria are on the Integration guide.

​

End-customer KYC branding

The end-customer KYC verification flow is WhiteBIT-branded and cannot be white-labeled. See Eligibility and approval.

​

Program terms

​

Revenue share

The revenue share is up to 40% of the trading fees generated by referred customers; the applicable rate and any additional commercial terms are agreed individually at enrollment. The canonical terms are on the Embedded Trading program page; see also Program terms.

​

Revenue reporting

Earnings are reported through the WhiteBIT Analytical Dashboard; the program does not expose a dedicated fee-share endpoint. Programmatic reconciliation combines the sub-account list with per-sub-account trade history — see Revenue monitoring.

​

Integration models

​

Sub-account or Fast API Key

Partner-operated sub-accounts (this program) and customers’ own accounts via Fast API Key are two separate architectures for two different personas. The Embedded Trading overview compares both; the Fast API Key path — copy trading, trading bots, and portfolio apps — is documented under App Builders.

​

Sub-account API key limits

Each sub-account supports up to 50 API keys, independent from the main account and from other sub-accounts, each with its own IP whitelist and permission scope. See Account architecture.

​

What’s next