Skip to main content
The Payments & Fiat program covers programmatic movement of funds into and out of WhiteBIT: crypto deposits and payouts, fiat rails over EUR/SEPA and card providers, instant off-chain merchant charges, and corporate on/off-ramp between fiat and crypto. It suits payment providers crediting end customers, merchants collecting payments, and businesses settling revenue over EUR rails.

What Payments & Fiat provides

  • Crypto deposits — a persistent or per-end-user deposit address, with incoming funds reconciled by webhook (Payment Integration).
  • Crypto and fiat payouts — withdrawals with optional on-the-fly currency conversion (Payment Integration).
  • Fiat rails — EUR/SEPA bank transfers and card-provider checkout, added through institutional onboarding (On/Off-Ramp guide).
  • Merchant charges — one-tap, off-chain settlement from a WhiteBIT user’s balance with Express Withdraw, and fee-free transfers with WhiteBIT Codes.
  • Reconciliation — signed webhooks plus history polling keyed on client-side identifiers.

Who Payments & Fiat is for

  • Payment providers — assign a deposit address per end customer and credit accounts on confirmation.
  • Merchants and platforms — collect crypto payments from WhiteBIT users instantly and off-chain.
  • Corporate on/off-ramp clients — move company funds between fiat and crypto over EUR rails.

How it works

Every flow authenticates with an HMAC-signed API key and reconciles against signed webhooks and history polling. Most crypto flows are available after standard account setup; some — Express Withdraw and dedicated per-user deposit addresses — require a separate per-account enablement, and fiat flows require completed institutional onboarding with approved fiat access (a separate second phase). The Payment Integration guide documents each flow — deposits, withdrawals, conversion, WhiteBIT Codes, and Express Withdraw — and the On/Off-Ramp guide covers the corporate fiat ↔ crypto journey end to end.

Program terms

Fee schedules and limits for fiat deposits and withdrawals are set per individual agreement and confirmed by the account manager during onboarding; the enabled currency and provider matrix is reported at runtime and reviewed at onboarding (see program terms). Compliance obligations apply to cross-border transfers: For transfers in scope of the Travel Rule, originator and beneficiary information is required. See Travel Rule for the field requirements and the transfer flow. The deposit-side SEPA provider for EUR fiat deposits is confirmed per account at onboarding and is not documented in the public reference; the On/Off-Ramp guide documents the deposit and withdrawal flows and the per-account values confirmed at onboarding.

How to get started

Build crypto flows against the Payment Integration guide. For fiat rails, email institutional@whitebit.com with the registered legal entity, the licenses held, whether the scope is crypto-only or fiat as well, and the countries served, then complete institutional onboarding. Clear the Go-Live Checklist before real volume.

What’s next

Integration

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

FAQ

Access and enablement, SEPA, Travel Rule, and reconciliation.

On/Off-Ramp guide

The corporate fiat ↔ crypto journey over EUR/SEPA rails.