Exchanges and trading apps
Use 0Gate hosted flows for approved exchange funding, withdrawal, and swap entry points without exposing headless liquidity internals.
Exchanges and trading apps may use 0Gate when they want a hosted buy, sell, or swap surface that keeps the user-facing ramp path inside 0Gate. If an exchange needs a fully headless liquidity integration, that belongs outside 0Gate product docs and requires separate approval.
Good 0Gate fit
| Exchange task | 0Gate pattern |
|---|---|
| Fund account with fiat | Hosted on-ramp session with account/order reference. |
| Withdraw to fiat | Hosted off-ramp session where enabled. |
| Start from a trading app asset page | Flow-locked hosted widget or redirect. |
| Support reconciliation | Store session id, transaction ref, event id, and request id. |
Boundary
Do not document headless liquidity internals here
0Gate product docs should keep exchanges on the hosted path unless the partner is explicitly approved for another product surface. Do not publish pool inventory, venue routing, treasury, reserve, or provider details on 0Gate pages.
Integration model
- Decide whether the user is funding, withdrawing, or swapping.
- Check product and capability support for the market.
- Create a hosted 0Gate session from the exchange backend.
- Use the hosted widget, kit block, or redirect.
- Keep account balance pending until verified backend events.
- Reconcile with session, transaction, webhook, and exchange account records.