Skip to main content
Every business on Cloudpay has two twins. The test twin is Development and the live twin is Production. Both use https://api.cloudpay.africa/cloudpay. The key prefix decides which twin answers:
Development isn’t a simulator. A test prompt really charges the phone that approves it. That money is kept, and it moves to your live twin when Cloudpay approves the business.

Check which environment answered

Going live

1

Sign up and get approved

Create an account at the dashboard’s Create an account link: your phone number, a code by SMS, a PIN and your business name. Cloudpay approves new businesses, usually within one working day, and lets you know by SMS. Until then only the business itself and its KYB answer; every other call returns 403 merchant_pending.
2

Submit KYB

You can start while you wait for approval. In the dashboard, pick who is getting paid (that decides the documents), fill in the details as they appear on your papers and upload each document, then submit. GET /v1/merchants/{id}/kyb lists what is still missing. You can also do this through the API with PUT /v1/merchants/{id}/kyb, PUT …/kyb/documents/{kind} and POST …/kyb/submit.
3

Cloudpay reviews

Each document is accepted or rejected with a note. If anything needs changing, KYB returns to you with notes.
4

Cloudpay approves the live merchant

Until then, live requests and issuing an sk_live_ key return 403 production_not_approved. Approval comes by SMS; after it you can issue sk_live_ keys, and your Development balance moves across.

Ready-made test data

With an sk_test_ key, the Sandbox endpoints create test data you can use straight away:
  • GET /sandbox/v1/tenant: your test tenant and the magic values.
  • POST /sandbox/v1/customers: a test customer, ready to use.
  • POST /sandbox/v1/merchants: a QR merchant.
A live key gets 403 live_mode_required from these endpoints.