Skip to main content
Institutional onboarding involves two distinct phases: crypto operations access (required for all partners) and fiat operations access (optional, for EUR/SEPA). Each phase has a separate compliance review cycle.

​
Overview

The onboarding process involves KYC, KYB, compliance review cycles, and (for fiat) additional documentation through a fiat processing partner. Listing the requirements upfront helps partners prepare documentation before starting, reducing back-and-forth delays. Timeline: Timeline varies depending on corporate structure, document availability, and compliance feedback cycles. Allow 2-4 weeks for Phase 1 and an additional 2-4 weeks for Phase 2. Contact institutional@whitebit.com for current processing estimates.

​
Phase 1: Crypto Operations Access

Phase 1 grants access to crypto trading, sub-accounts, lending, and all API endpoints.
1

Create a WhiteBIT account

Register at whitebit.com/auth/register. Use the corporate email address that will serve as the primary account contact.
2

Complete KYC for the director or responsible person

Navigate to account verification settings. Complete individual identity verification for the person with signing authority.
3

Initiate KYB (Know Your Business)

Navigate to whitebit.com/verification-business. Click “Get link” to generate the KYB verification form. Complete and submit the form with corporate documentation.
4

Compliance review

The WhiteBIT compliance team reviews the submission. Expect clarification requests and additional documentation requirements. Respond to compliance feedback promptly — the review cycle involves back-and-forth until all requirements are met.
5

Approval and access

Upon approval, full crypto operations become available. Generate API keys at whitebit.com/settings/api. Begin API integration using the First API Call guide.

​
Phase 2: Fiat Operations Access (EUR/SEPA)

Phase 2 adds EUR deposit and withdrawal capabilities via SEPA. Phase 2 requires additional onboarding through WhiteBIT and a fiat processing partner.
WhiteBIT manages the fiat processing partner onboarding on behalf of the partner. Partners do not contact the fiat processing partner directly.

​
Required Documents

The fiat processing partner typically requests the following. All documents must be in English (translated if necessary), apostilled, and less than 3 months old. Corporate documents:
  • Memorandum and Articles of Association
  • Extract from Register of Legal Entities
Beneficial owner source of funds/wealth:
  • Annual tax declaration
  • Salary payslips (most recent 6 months)
  • Bank statements (most recent 6 months)
  • Relevant agreements and invoices
Company source of funds:
  • Annual tax declaration
  • Financial statement or audit report
  • Bank statements (most recent 6 months)
  • Relevant agreements and invoices
Document requirements may vary based on jurisdiction and corporate structure. Contact institutional@whitebit.com for current requirements before preparing documents.

​
Process

After WhiteBIT submits the documentation to the fiat processing partner, the fiat processing partner’s compliance team reviews the submission. Expect an iterative review cycle similar to Phase 1. Upon final approval, EUR/SEPA operations become available on the account.

​
Contact

For institutional onboarding inquiries, partnership discussions, or to check the status of an in-progress application, contact institutional@whitebit.com.

​
What’s Next

Institutional Overview

Explore the full catalog of institutional products and services.

Compliance

MiCA, Travel Rule, and regional regulatory requirements affecting API behavior.