Go to production

Going to production with Core means taking responsibility for real money. Before you flip the switch, every item on this checklist should be true: you have rotated keys, signed agreements, validated reconciliation, configured monitoring, and rehearsed an incident.

This page is meant to be opened the day before launch and walked through item by item. If anything is unchecked, do not launch.

Engineering checklist

• Production API keys generated, stored in a secrets manager, and rotated.
• Idempotency keys sent on every write request.
• Webhook endpoint deployed, signature verification in place, retry-tolerant.
• Reconciliation job runs at least daily and alerts on drift.
• Logging includes Mono request ID on every API call.
• Monitoring and alerting on 5xx responses, webhook failures, and reconciliation drift.
• Incident runbook documented and rehearsed.

Operational checklist

• Customer support has access to the Mono Dashboard with appropriate scopes.
• Finance has documented the reconciliation procedure and owns the ledger close.
• Compliance has reviewed the data model and the retention policy.

Mono certification

Mono performs a certification review before activating production credentials. Details will be documented here.

Next steps

• Best practices
• Sandbox
• Webhooks