Mobile money API with a real sandbox

Prompt to pay, hosted checkout, payment links, payouts, bills and refunds. Each call takes an idempotency key, so a retry never pays twice. Webhooks are signed, with a time window, and repeats are harmless.

Single-file libraries for Node.js, Python and PHP handle token renewal, safe retries and webhook checks. They have no dependencies, so there is nothing to audit or keep patched, and you can copy one to a shared host.

The developer portal shows traffic by day, top endpoints, webhook health and your road to live. Plugins cover common shops, and the docs have a working example per task.

Collection: your system asks the customer to approve a payment, usually by a prompt on their phone, and you wait for the result. Disbursement: your system pays a phone number or bank account from your balance. Both finish later than the request, so you never treat the first reply as the final answer. You treat the signed webhook, or a status query, as the truth.

Retries must be safe: send the same idempotency key twice and the money moves once. Webhooks must be signed, so nobody can fake a success message and take your goods. A sandbox must be able to produce failures on request, such as a timeout or a refused payment, because those are the cases that lose money in production. Errors must say what to do next, not only that something failed.

Run the failures on purpose in the sandbox: a customer who declines, a timeout, a duplicate request and a late webhook. Check that your own books stay correct in each case. Then go live with a small amount and one payment type, and reconcile by hand once before you trust it. Our docs cover going live, with libraries that add no dependencies to your project.