Start here
Test and live
Build and test against test mode, then switch to live by changing keys. The URL and the requests stay the same.
One base URL, two modes
Test and live traffic go to the same base URL. The mode of a request comes from the API key it is signed with: a test key runs in test mode and a live key in live mode.
Every object the API returns carries a mode field, so you can always tell which mode it belongs to.
Keys and webhooks per mode
Your dashboard has a test/live switch. API keys and webhooks are created in the mode the dashboard is in at that moment, and only work in that mode.
- A
webhook_idfrom the other mode is rejected withinvalid_webhook_id. - Requests that take an ID, such as
pin_idorstore_id, only find objects created in the same mode. - Signing, headers and error codes are identical in both modes.
invalid_api_key (401), the same as an unknown key. If your live key is rejected, check that your KYC is approved and that live access has been granted.Issuing in test mode
In test mode you issue and top up real test PINs, paid for from your test wallet. Everything you can do in live mode works the same way, and webhooks fire as they would in live mode.
- Test PINs are paid for from your test wallet and only work with a test key; live PINs only work with a live key. A PIN code from the other mode is rejected as
pin_code_unknown.
Going live
-
Pass the Go-live checklist
Run every case in Go-live checklist with your test key and keep the requests and responses.
-
Get your business verified
Live keys only work once your KYC is approved.
-
Ask for live access
Send your UAT results to support. Once live API access is switched on, switch your dashboard to live mode and create a live API key and live webhook.
-
Swap the keys
Replace the test key ID, secret and webhook IDs in your configuration. No other change is needed.