> ## 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

> What WhiteBIT Embedded Trading is, the two integration architectures (partner-operated sub-accounts and customers' own accounts via Fast API Key), and how enrollment works.

WhiteBIT Embedded Trading lets a partner offer trading to its own customers on WhiteBIT's exchange infrastructure. A partner integrates through one of two architectures depending on who holds the trading account — the partner, or the end customer. Both are approval-gated and share the same enrollment channel.

## Integration architectures

The account-holding question separates the two models: partner-operated accounts use the sub-account architecture; customers' own accounts use the Fast API Key architecture.

<CardGroup cols={2}>
  <Card title="Sub-account integration" icon="sitemap" href="/guides/sub-account-integration">
    The partner operates a dedicated sub-account per end customer under a master account. WhiteBIT provides per-customer isolation, per-customer API keys, and fee-free internal transfers. WhiteBIT performs end-customer KYC, unless KYC reliance is agreed.
  </Card>

  <Card title="Fast API Key integration" icon="key" href="/guides/fast-api-key-integration">
    End customers keep personal WhiteBIT accounts and grant the partner an OAuth-issued API key on the consent screen. WhiteBIT holds custody and performs KYC. Fits copy trading, trading bots, and portfolio apps.
  </Card>
</CardGroup>

The two architectures are WhiteBIT's **Model A** (partner-operated sub-accounts) and **Model B** (customers' own accounts via Fast API Key). The [integration models](/concepts/integration-models) page compares the two models side by side — account holder, KYC responsibility, and best fit — plus the *managed sub-accounts* / *attribution* / *KYC reliance* vocabulary. Model B fits more use cases than embedded trading alone: copy-trading, trading-bot, and portfolio apps built over users' own accounts route to [App Builders](/guides/app-builders-overview).

## Eligibility and approval

Embedded Trading enrollment is approval-gated. Every application is individually reviewed before provisioning is enabled. To apply, email `institutional@whitebit.com` with a description of the service, the registered legal entity, licenses held, the intended account structure, who performs end-customer KYC, and the countries served. The full application question list is on the [Partner Solutions](/guides/partner-solutions#how-to-apply) page.

**KYC reliance eligibility:**

KYC reliance — WhiteBIT relying on the partner's own customer verification — may be available,
but is not enabled by default. It is never automatic, and operates as a delegation:
responsibility for customer verification is never transferred. Eligibility is assessed case by
case. Reliance is available only to partners that are supervised AML-obligated entities (for
example EMI, PI, VASP, or MiCA-CASP license holders) in an adequate jurisdiction, applying
broadly equivalent customer due diligence, under a written agreement and an individual
WhiteBIT Compliance assessment. A confirmed entry on the relevant public register establishes
the licensing basis; a confirmed EU/MiCA entity is additionally required when EU users are in
scope.

Licensing regimes and entity structures vary, and the examples above may not capture every
case. Describe your licence(s), jurisdiction, and customer due-diligence approach in full in
your application so the WhiteBIT Compliance team can review your specific situation and make a
determination.

## Program terms

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 during enrollment; the canonical program terms are published on the [Embedded Trading program page](https://institutional.whitebit.com/broker-program). Commercial terms for the Fast API Key architecture — including attribution — are confirmed with WhiteBIT at enrollment.

## What's next

<CardGroup cols={2}>
  <Card title="Sub-account integration" icon="users" href="/guides/sub-account-integration">
    Eligibility, per-customer sub-account setup, per-customer API keys, and revenue reconciliation.
  </Card>

  <Card title="Fast API Key integration" icon="key" href="/guides/fast-api-key-integration">
    The OAuth API key flow for partners acting on customers' own accounts.
  </Card>

  <Card title="Copy trading" icon="copy" href="/guides/copy-trading">
    A Fast API Key use case: mirror a lead trader's orders into followers' own accounts.
  </Card>

  <Card title="Embedded Trading FAQ" icon="circle-question" href="/guides/embedded-trading-faq">
    Eligibility, revenue share, integration models, and copy-trading gating.
  </Card>
</CardGroup>