Skip to main content
Common questions about the WhiteBIT Payments & Fiat program.

Access and enablement

Access to fiat operations

Fiat deposits and withdrawals require completed institutional onboarding with approved fiat access — a separate second phase that is not automatic after KYB. See the On/Off-Ramp overview.

Per-account activations

Four capabilities are enabled per account rather than by default — the fiat deposit invoice endpoint, dedicated per-user deposit addresses, Express Withdraw, and Travel Rule API access. Request all four through the account manager, with the API key for the invoice endpoint; see Unique address per user for per-user deposit addresses. See the enablement gates.

Account limits

The account’s deposit and withdrawal limit is a rolling monthly limit counted in USD equivalent. For bank transfers, WhiteBIT sets the account’s limit from the source-of-funds and source-of-wealth information provided during onboarding; the account manager confirms the values. See Program terms.

Crypto flows

Persistent versus per-user deposit addresses

A persistent address suits single-wallet and treasury setups; a fresh address per end customer suits payment providers that reconcile by address (plus memo on memo networks). See Choosing between the two endpoints.

Charging a WhiteBIT user off-chain

Express Withdraw charges a specific amount from a WhiteBIT user’s balance in one confirmation, settling as an instant off-chain transfer into the partner’s Main balance. See Express Withdraw payments.

Fiat and SEPA

SEPA payment reference

The uniqueId submitted with the fiat deposit request must appear in the SEPA payment-reference field so the incoming settlement matches the original request. See SEPA payment reference.

SEPA deposit provider

The account manager confirms the deposit-side SEPA provider for EUR fiat deposits on each account during onboarding. See the On/Off-Ramp guide for the fiat deposit flow.

Compliance

Travel Rule for EEA and Turkey

Inbound crypto deposits for EEA and Turkey accounts are held until Travel Rule verification completes, and crypto withdrawals from EEA accounts carry a Travel Rule payload. See Travel Rule.

Reconciliation

Matching deposits and withdrawals

Reconciliation is webhook-driven with history polling as a fallback, deduplicated on the uniqueId carried in both paths. See Webhook reconciliation.

What’s next

Overview

What the Payments & Fiat program provides and who it is for.

Integration

Deposits, withdrawals, conversion, WhiteBIT Codes, and Express Withdraw.

Partner FAQ

Cross-cutting answers shared across programs — KYB, sandbox, fees, and rate limits.