Go-live checklist

Before you switch your integration to live keys.

Your business is verified (KYC approved) and the methods you sell with are switched on for your market.

You created a live API app in the developer console, keep its secret key in your server’s secret store (never in an app, a page or a repository), and gave every other system a restricted key with only the scopes it needs.

Your webhook endpoint uses HTTPS, verifies Watenga-Signature with the live signing secret, answers 2xx quickly and does the work afterwards, and handles the same event twice (deliveries can repeat).

You fulfil orders from the webhook or by reading the payment on your server, never from a browser callback or the address alone.

Writes carry an Idempotency-Key (the SDKs do it), and you pass your own when you retry a refund or a charge yourself.

Your app is pinned to API version 2026-10-29 in the developer console, or you send Watenga-Version.

You tested declines, cancelled mobile-money prompts, refunds and a webhook outage (deliveries are retried for about three days; replay failed ones from the console).

Refund limits are set for the live app if your systems refund, and your team’s roles in the dashboard match who may do what.

You know where to look when something fails: the developer console’s request logs and webhook deliveries, the request_id of every error, and the status page.

Related: Testing · Webhooks · Authentication