Use approved product surfaces
Keep product availability, KYC/KYB, regional support, liquidity, and settlement behavior inside the surfaces enabled for your account.
0Gate is the default public path. 0Pools is for approved liquidity partners. 0Base and 0Link are account-gated product surfaces. Availability, regions, webhook payloads, production limits, and support commitments depend on the product contract, capability checks, and account enablement.
Availability is account-specific
A product appearing in docs does not mean every partner can use it in every region, currency, asset, or environment. Confirm access from your 0Bit account configuration, documented capability checks, and support path before showing a flow to users.
Integration routing
Product boundaries
| Surface | Use it for | Do not claim |
| --- | --- |
| 0Gate | Default public integration path for hosted checkout, on-ramp, off-ramp, swap, embeds, redirects, WebViews, and signed webhook flows. | Permanent regional, asset, payment-method, payout-method, or completion guarantees. |
| Capabilities | Dynamic country, currency, asset, method, and eligibility checks where documented. | That a supported value is legal approval, final settlement, or permanent availability. |
| 0Pools | Approved partner liquidity workflows for entitled partners that need headless quote and trade paths. | General access, liquidity source, reserve, venue, routing, market-maker, or treasury internals. |
| 0Base | Account-enabled checkout object, payment-intent, payment-link, reporting, and webhook planning surfaces. | Live merchant checkout or money-movement behavior unless 0Bit has enabled it for your account. |
| 0Link | Account-gated routing boundary where 0Bit has explicitly enabled a 0Link path. | Internal routing APIs, venue details, best-price claims, fallback behavior, or execution strategy. |
| Webhooks | 0Gate signed webhooks and other product webhook contracts documented for enabled product surfaces. | Exactly-once delivery, undocumented payload fields, raw payload exposure, or copying 0Gate payloads to another product. |
| Compliance and KYC/KYB | Capability-led user-facing states such as verification required, unavailable, processing, failed, or complete. | Detailed policy thresholds, exemptions, provider names, legal conclusions, or unsupported country/region promises. |
| Rate limits and support | Bounded retries on 429, Retry-After when present, and support through support@0bit.io. | Exact throughput, SLA, uptime, response-time, or support-tier promises unless they are in the partner agreement. |
Implementation checklist
- Confirm the product surface is enabled for your partner account and environment.
- Run capability, entitlement, or eligibility checks before showing the flow.
- Keep unavailable states neutral and support-safe.
- Use documented API objects and hosted surfaces only.
- Close business state from verified backend events, not browser-only callbacks.
- Keep provider, treasury, routing, reserve, and internal settlement details out of your UI and support artifacts.
- Contact support@0bit.io when a product surface, region, method, or asset is not enabled.