0Bit Documentation

Guides

Task-based 0Bit implementation guides organized by workflow, product boundary, and launch stage.

Use these guides when you already know the job you need to complete. The default public partner path is 0Gate: create the session server-side, embed or redirect the hosted experience, and treat signed webhooks as the durable source of truth.

Guide routing

Choose the task, then stay inside its product boundary.

0Gate is the default public path for hosted checkout, ramp, swap, embeds, redirects, and signed webhooks. 0Pools is for approved liquidity partners. 0Base and 0Link are account-gated boundaries, not shortcuts around product approval.

0Gatepublic hosted path
0Poolsapproved headless path
0Base / 0Linkaccount-gated boundaries
Controlskeys, events, compliance

Start here

Match the guide to the job

You need a public checkout, on-ramp, off-ramp, or swap flow.
You need to embed the hosted surface inside a web or mobile app.
You need to constrain, theme, or route the hosted experience.
You need production controls before a flow can safely go live.

Guide library

Embeds & widgets

Browser, redirect, WebView, theme, callback, and session-shaping guides.

Webhooks & events

Signed event intake, verification, lifecycle handling, replay, and durable event logs.

Compliance & security

Keys, browser-safe values, origins, idempotency, retries, data handling, and review gates.

Operations

Sandbox testing, launch readiness, monitoring, debugging, pagination, versioning, and support.

Common baseline

Server creates the session.Amounts, flow constraints, return URLs, references, and idempotency keys are bound before the browser loads.
Browser receives browser-safe values.Send only the publishable key and a session-scoped client secret to the frontend.
Webhooks close durable state.Client callbacks can update UX, but signed backend events drive fulfillment and reconciliation.
Retries are idempotent.Duplicate requests, duplicate events, and delayed delivery should not create duplicate fulfillment.
Sandbox first.Test raw-body webhook verification, duplicate event handling, retry behavior, and reconciliation before using live credentials.

See also

On this page