Wallet and funding history
See available and reserved funds separately, with wallet movements recorded for review.
Manage wallet funding, recipients and schedules in one organisation workspace. Send a single top-up or a recipient list through the dashboard or REST API, then track each transaction through its final outcome.
Dashboard and API submissions
Choose one number or a saved contact list.
The requested amount is reserved before fulfilment starts.
Airtime is routed to the recipient’s mobile network for delivery.
Transaction status and wallet history reflect the result.
Airtime operations
Bring wallet funding, recipient management, scheduling and transaction history into one organisation workspace.
See available and reserved funds separately, with wallet movements recorded for review.
Add contacts, import recipient files and reuse lists for future airtime distributions.
Send a distribution now or choose a future date and time for it to be processed.
Review each recipient’s delivery status and see how the outcome affects reserved funds.
How it works
Airtime requests move through a shared workflow whether they start in the web workspace or through the API.
Payments matched to your organisation’s funding reference are credited and shown in payment history.
Enter one recipient, choose a saved contact list or import contacts before you submit.
Submit from the web workspace or API. The requested wallet amount is reserved for processing.
Successful transactions settle the reservation; final failures release the reserved amount.
Airtime API
Submit a single recipient or a batch with an idempotency key. Statum records the request and reserves the funds before returning 202 Accepted; that response means processing has been accepted, not that delivery is complete.
When a final delivery outcome is received, Statum sends the transaction status to your configured, signed HTTPS callback. The balance endpoint remains available for balance checks.
Read the API documentationAccess and accountability
Contacts, users and transactions belong to the organisation workspace.
Grant balance access and airtime sending as separate permissions.
Funding, reservations, settlement and release have an auditable history.
Common questions
No. A 202 Accepted response confirms that the request was recorded for asynchronous processing and its funds were reserved. Delivery is determined by the final delivery status, which is sent to your callback.
Yes. Submit one recipient or many recipients from the web workspace or API. A single recipient follows the same reservation and fulfilment workflow as a batch.
Yes. Web and API submissions can be scheduled for a future date and time as well as submitted for immediate processing.
No. Configure a completion callback on the API credential to receive final transaction outcomes. The balance endpoint can be queried when you need an updated wallet balance.
Airtime is routed to the recipient’s mobile network for processing. Statum tracks the final delivery outcome, settles or releases the reserved amount, and notifies the API caller through its configured completion callback.
Manage distributions in the dashboard or connect your systems through the Airtime API.