On/Off-Ramp

The WhiteBIT on/off-ramp integration moves corporate funds between fiat and digital assets, in both directions — fiat in to crypto out, and crypto back to EUR — with all fiat operations at the partner’s main account. For the flows, code, and reconciliation, see the Integration guide. Adjacent scenarios route to separate guides:

• The integration collects payments from end users or processes merchant flows — see Payment Integration.
• End customers hold dedicated accounts under a partner main account — see the Embedded Trading integration guide.
• For the full partner-type map, see Partner Solutions.

​

What On/Off-Ramp provides

• Fiat deposits via API — a hosted payment URL for card checkout or for a SEPA bank transfer, per the providers enabled for the account. A bank transfer comes only from the partner’s own KYB’d bank account and can also use the bank details that Create fiat deposit returns.
• Fiat withdrawals via API — EUR payouts over IBAN (SEPA) to the partner’s own KYB’d bank account, plus card rails where enabled, each carrying a beneficiary record.
• Quoted-rate conversion — Convert on the Trade balance: a confirmed quote executes in full at the quoted amounts or not at all, so the rate is known up front.
• The crypto leg — deposit addresses, withdrawals, and the refund flow.
• Reconciliation — signed webhooks plus history polling with client-side identifiers.

The Integration guide documents each endpoint, the request bodies, and both directions.

​

Who On/Off-Ramp is for

• Corporate crypto investors — convert company treasury funds between EUR and digital assets on the main account.
• Businesses settling revenue over EUR rails — move payouts or revenue between fiat and crypto without operating end-user accounts.
• Crypto-native companies with fiat obligations — off-ramp digital assets to EUR to pay suppliers, payroll, or tax from the company bank account.
• Fiat-first companies funding on-chain operations — on-ramp EUR to USDC or other digital assets for on-chain payouts, vendor settlement, or protocol operations on the main account.

​

How it works

Requests authenticate with an HMAC-signed API key on the partner’s main account. The one exception is the card payout step: Issue card token takes a JWT from the HMAC-signed Issue JWT token endpoint. Crypto operations are available after standard account setup; fiat operations require completed Institutional Onboarding with approved fiat access — a separate, non-automatic phase after KYB. The Integration guide covers both directions end to end: the fiat leg, the conversion step, and the crypto leg. The diagram shows where funds move between the partner, an end user’s card, the partner’s main account, and the blockchain.

​

Program terms

Fee and limit figures are set per individual agreement, so no numbers appear in these pages. During onboarding, the account manager confirms:

• The fee schedule for fiat deposits and withdrawals applicable to the account.
• Deposit and withdrawal limits, for both fiat and crypto.
• The enabled currency and provider matrix. At runtime, Asset Status reports the per-currency can_deposit / can_withdraw flags and the request provider values; the Fee endpoint reports the public fee schedule and limits per fiat asset, the same for every caller.
• Settlement windows and cutoff behavior for the fiat rails in use, including weekends and holidays.

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.

​

Compliance essentials

Compliance shapes which assets and flows are available to the account. The Integration guide shows how each constraint affects requests; Regulatory Compliance holds the full reference.

• MiCA (EEA): EEA accounts cannot deposit, withdraw, or create WhiteBIT Codes in USDT since December 30, 2024. Use USDC or EURI for the crypto leg. See Regulatory Compliance.
• Travel Rule (EEA and Turkey): inbound crypto deposits are held until Travel Rule verification completes; crypto withdrawals from EEA accounts carry a Travel Rule payload. See Travel Rule.
• Fiat KYC: fiat withdrawals require KYC verification. In exceptional, documented cases the institutional team can arrange a per-account override.

​

How to get started

Fiat access is the second phase of Institutional Onboarding and is not automatic after KYB approval. Phase 1 (corporate account, KYB, API keys) enables crypto operations; Phase 2 adds EUR/SEPA capabilities after review by a fiat processing partner, with source-of-funds documentation. WhiteBIT manages the fiat-partner onboarding on the applicant’s behalf. How to apply: email institutional@whitebit.com with a description of the service. Include the registered legal entity (name, registration number, jurisdiction), licenses or registrations held, whether the scope is crypto-only or fiat as well, and the countries where the service operates. The full application question list is on the Partner Solutions page. Six capabilities in the ramp integration carry a dedicated enablement gate:

​

Support and contacts

• Onboarding status, limits, and institutional matters: institutional@whitebit.com, or the assigned account manager once onboarded.
• Fiat endpoint enablement and access questions: the account manager, with the API key included in the request.
• Dedicated deposit addresses: the account manager.
• OTC block trading for large conversions is part of the institutional catalog — see the Institutional Overview.
• Self-service: help.whitebit.com for platform questions; this portal for API documentation.

​

What’s next