Skip to main content
Answers to common questions about WhiteBIT Yield-as-a-Service (YaaS).

Scope and delivery

What Yield-as-a-Service delivers

YaaS lets a partner offer WhiteBIT Crypto Lending yield to end users through the API, under the partner’s own brand. See the overview.

Difference from the self-service quickstart

The Crypto Lending quickstart shows the self-service flow for a single account; YaaS adds the B2B layer — a sub-account per end user, funding, and per-user reconciliation. See the Integration guide.

Integration model

How end-user funds are segregated

Each end user earns in a dedicated sub-account with independent balances and history; the master account is the funding hub. See How it works.

Whether end users need separate WhiteBIT accounts

End users do not open separate accounts — each is provisioned as a sub-account under the partner’s master account (Model A). See Sub-Accounts.

Pooled account

A single pooled (omnibus) account for end-user funds is not offered, because pooled custody conflicts with client-fund segregation and Travel Rule requirements. See why not a pooled account.

Onboarding and access

How lending access is granted

Crypto Lending is available on the master account with B2B access; on sub-accounts it is not enabled by default and must be enabled per sub-account on request. See How to get started.

API key type for a sub-account

Running lending on a sub-account requires a type:2 key (info, trading, deposits, withdraws). See Prerequisites.

Operations

Tracking each end user’s earnings

Each sub-account’s investments and payment history are that end user’s earnings; there is no aggregated cross-sub report, so reconciliation is per sub-account. See Reconcile earnings per user.

Fixed versus flexible plans

Fixed plans lock funds for a term with interest paid at maturity; flexible plans allow withdrawal anytime with interest credited daily. See Crypto Lending.

Test environment availability

WhiteBIT does not offer a public testnet or sandbox. Test on the live API with minimum amounts. See the Integration guide.

Compliance

Regulatory review

Eligibility to offer yield to end users is assessed during KYB and handled as part of onboarding rather than in the API. See Regulatory Compliance.

Support

Support contacts

The assigned account manager is the primary contact; programs and onboarding go to institutional@whitebit.com. See Institutional Onboarding.

What’s next

Overview

What Yield-as-a-Service provides, the model, and how to apply.

Integration

Provision sub-accounts, invest, and reconcile earnings.