Use support checklist

Collect the identifiers and redacted evidence needed to investigate 0Bit integration issues.

Support works best when every issue can be tied to one local attempt, one 0Bit product object, relevant request ids, webhook event ids, delivery ids, and a redacted timeline. For 0Gate flows, the product object is usually the session.

Support evidence must be redacted

Do not send secret keys, webhook secrets, authorization headers, client secrets, raw webhook payloads, raw KYC data, or provider responses in tickets.

For production partner support, email support@0bit.io.

Checklist

Include	Why
Local attempt id	Anchors the issue in your system.
Product object id	Lets 0Bit trace the hosted session, checkout, quote, trade, or other approved product record.
API request id	Lets 0Bit trace a specific API call.
Webhook event id	Links delivery to your event log.
Webhook delivery id	Supports replay or delivery investigation.
Timestamp and environment	Separates sandbox from live and narrows logs.
Redacted request shape	Shows intent without leaking secrets.
Current and expected status	Clarifies the requested outcome.

Include by severity

Severity	Include
Production stopped	Environment, partner account, affected product surface, first-seen time, request ids, product object ids, event ids, and current user impact.
Production degraded	Same identifiers plus affected count, timestamp window, retry behavior, and current partner-side state.
Integration blocked	Endpoint, SDK package/version, sanitized error code/message, request id, environment, and the docs page followed.
Documentation/product question	Page URL, exact question, product surface, and whether the partner is approved for 0Pools, 0Base, or 0Link review.

Support timeline

Ticket template

Environment: sandbox or live
Local attempt id:
Product object id:
Request ids:
Webhook event ids:
Webhook delivery ids:
Observed status:
Expected status:
Timestamp range:
Redacted notes: