Launch readiness is the point where the integration, operators, and compliance posture all agree on the same evidence trail. Use this page before live traffic. Use Going Live for the longer production handoff guide.Documentation Index
Fetch the complete documentation index at: https://docs.usezentra.com/llms.txt
Use this file to discover all available pages before exploring further.
Required Before Live Traffic
Prove the first reviewed flow
Run at least one sandbox transfer or payment flow end to end with idempotency, API state inspection, and webhook handling.
Verify event consumers
Confirm signature verification, duplicate event handling, retry behavior, and alerting for failed webhook deliveries.
Confirm tenant controls
Check enabled products, limits, key environment, webhook endpoints, and internal access rules for the tenant.
Prepare operational review
Make sure support, finance, and compliance teams know where to inspect request state, delivery history, and audit evidence.
Production Acceptance Criteria
- Live API keys are stored outside client-side code and source control.
- All money-affecting writes use deterministic request identity where documented.
- Webhook consumers verify signatures and deduplicate events.
- Draft/reference namespaces are not used in default production flows.
- Operational owners know how to investigate a failed provider callback, retry, or reconciliation mismatch.
- The integration team has a rollback or pause path for launch issues.