Going live
Swap the key. Everything else should already work.
Nothing about the request or response shapes changes between modes, which means the only thing you can newly get wrong is the credential and what surrounds it.
Before you issue a live key
-
GET /reseller/mewith your test key returnsmode: "test", and your application refuses to start if the mode is not what that deployment expects. - A verify step runs before every electricity order, and you show the customer the name and address before taking their money.
- Your reference is generated and stored before the request is sent, and a retry re-sends the same one.
- A timeout is treated as unknown, not as a failure. You either retry with the same reference or poll it.
- You handle the inline failure:
success: falsewith the order indata. Tested against22222222222. - You handle a terminal
refundedand a terminalfaileddifferently. - You do not give value on
acceptedorprocessing. Tested against44444444444. - Your webhook endpoint verifies the signature in constant time, and the
dashboard's test callback returns
200. - Your webhook handler is idempotent on
reference, and answers before doing its work. - You keep your own mapping from reference to product, because a VAS callback does not carry the target.
- You have a reconciliation pass that polls anything non-terminal, so a missed callback cannot leave an order unresolved.
- Your own concurrency is capped under your in-flight limit.
- The empty-balance
422is handled. Tested by spending the sandbox down. - Nothing logs an API key, and no key is in your repository.
Then
- Get KYB approved. Live keys require it; test keys never did. Check
kyb_statusonGET /reseller/me. - Fund your partner balance. Live orders spend it, and an order it will not cover is refused.
- Set your live webhook URL and signing secret, on the Webhooks page. They are separate from your test ones, and a live order will not call your test endpoint.
- Send the dashboard's test callback to the live endpoint and confirm
200. - Set your address allowlist.
calling_fromonGET /reseller/mefrom your production server tells you what to add. Do this from the server, not your laptop. - Issue the live key, put it where your secrets live, and deploy.
- Confirm the mode.
GET /reseller/meshould now saymode: "live".
Your first live order
Make it small and make it yours. A 100 naira top-up to a phone you hold, or the smallest electricity amount your disco accepts on a meter you own. Then check, with your own eyes:
- the order reached
delivered - the token works, if it was electricity
- your webhook fired and your handler recorded it
- the amount that left your balance is the amount you expected
- it appears on the Transactions page in your dashboard
Warning
Do not make your first live order a customer's. And do not test the failure paths in live mode: a real refused vend costs real money and takes real time to unwind. That is what the reserved sandbox numbers are for.
Keep the test key
Point your staging deployment at test mode permanently. The two modes are separate credentials on the same base URL, so you do not need a separate environment to keep a safe place to try things.
Important
Our staging environment is not a sandbox. It carries live provider credentials, so a live key used there spends real money against a real meter. Safety comes from the key being a test key, never from which hostname you called.
After you are live
- Watch the API calls page for the shape of your traffic and the statuses you are getting.
- Watch Webhooks for deliveries that needed retries. A pattern there usually means your handler is too slow.
- Earnings shows what you have accrued.
If something looks wrong with money, stop and ask us rather than issuing your customer a credit from your own pocket. Support says what to send.