> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Embedded Trading FAQ

> Common questions about WhiteBIT Embedded Trading: eligibility and approval, revenue share, the two integration models, sub-account limits, and copy-trading availability.

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](/guides/sub-account-integration#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](/guides/sub-account-integration#eligibility-and-approval).

### End-customer KYC branding

The end-customer KYC verification flow is WhiteBIT-branded and cannot be white-labeled. See [Eligibility and approval](/guides/sub-account-integration#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](https://institutional.whitebit.com/broker-program); see also [Program terms](/guides/sub-account-integration#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](/guides/sub-account-integration#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](/guides/embedded-trading-overview) compares both; the Fast API Key path — copy trading, trading bots, and portfolio apps — is documented under [App Builders](/guides/app-builders-overview).

### 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](/guides/sub-account-integration#account-architecture).

## What's next

<CardGroup cols={2}>
  <Card title="Overview" icon="circle-info" href="/guides/embedded-trading-overview">
    What Embedded Trading provides and the two integration architectures.
  </Card>

  <Card title="Sub-account integration" icon="sitemap" href="/guides/sub-account-integration">
    Per-customer sub-accounts, API keys, and revenue reconciliation.
  </Card>

  <Card title="Partner FAQ" icon="circle-question" href="/guides/partner-faq">
    Cross-cutting answers shared across programs — KYB, sandbox, fees, and rate limits.
  </Card>
</CardGroup>