Prepare production launch
Confirm credentials, domains, webhooks, idempotency, monitoring, support, and account enablement before live traffic.
Production launch is an integration readiness gate. Treat it as evidence collection: you should be able to show that the same flow works in sandbox and that live credentials, origins, webhooks, monitoring, and support are configured correctly.
Do not launch on browser success alone
A production-ready flow has verified backend events, idempotent fulfillment, reconciliation, monitoring, and support procedures. A successful widget callback is not enough.
Production access is account-gated
Live regions, assets, methods, KYC/KYB behavior, webhook contracts, and non-0Gate products depend on your 0Bit account, environment, and agreements. Confirm they are enabled before launching a user-facing flow.
Launch gate
Checklist
| Area | Required before launch |
|---|---|
| Product boundary | Flow belongs to a product surface enabled for your account. |
| Credentials | Live secret keys are server-side only. |
| Browser values | Only publishable key and session-scoped client secret reach the client. |
| Origins | Production origins and return URLs are explicitly allowed. |
| Webhooks | Signature verification and event logging pass. |
| Idempotency | Write retries and event retries are duplicate-safe. |
| Monitoring | Alerts exist for session failures, webhook dead letters, and reconciliation backlog. |
| Support | Runbook uses ids and redacted artifacts, not secrets or raw PII. |
| Availability | Region, KYC/KYB, asset, method, and product access are enabled for the environment. |
Launch confirmations
| Area | Confirm before launch | Avoid |
|---|---|---|
| Product surface | 0Gate, approved 0Pools, enabled 0Base, or another documented surface is available to your account. | Using review-only or internal-boundary products in production. |
| Supported regions | Capability response, account configuration, or 0Bit support confirms the flow can be shown. | Hardcoding permanent country or region availability claims. |
| KYC/KYB | Hosted verification and partner configuration behave as expected in sandbox and live. | Promising exact verification outcomes in customer-facing copy. |
| Webhook contract | Event names, payload fields, signature header, replay behavior, and delivery logs match the reference you use. | Processing undocumented payload fields as durable business logic. |
| API reference | Your integration uses the current documented product API and OpenAPI-backed reference. | Copying internal or unsupported endpoint paths. |
| Support path | Production runbooks point to support@0bit.io with redacted identifiers. | Sending secrets, raw payloads, or customer PII in tickets. |
Launch record
type LaunchReadiness = {
productSurface: '0gate' | '0pools_approved' | '0base_review' | '0link_review';
sandboxEvidenceId: string;
webhookVerified: boolean;
idempotencyVerified: boolean;
monitoringVerified: boolean;
complianceApproved: boolean;
};