Configuration
Set environments, API keys, SDKs, idempotency, and webhook signing before building a 0Gate integration.
Use configuration pages before writing production code. They keep credentials server-side, route test keys to sandbox, route live keys to production, and keep webhook signing verifiable.
Configuration map
| Page | Use it for |
|---|---|
| Environments | Sandbox, production, local hosts, widget origins, and key modes. |
| API keys | Secret key, publishable key, and webhook secret placement. |
| SDK setup | Package names, imports, and base URL shape. |
| Webhook signing | Raw-body signature verification and event intake. |
| Idempotency | Retry-safe writes and duplicate handling. |
Configuration is environment-specific
Do not mix test keys with production hosts or live keys with sandbox hosts. Do not expose sk_* or whsec_* values
in browser code, mobile apps, logs, screenshots, or support tickets.