Skip to content
Airtime Control
Airtime distribution for organisations

Bulk airtime distribution for teams in Kenya.

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.

  • Single or bulk sends
  • Immediate or scheduled
  • Transaction-level results

One clear distribution flow

Dashboard and API submissions

Airtime workflow
  1. 01

    Prepare recipients

    Choose one number or a saved contact list.

  2. 02

    Reserve the airtime amount

    The requested amount is reserved before fulfilment starts.

  3. 03

    Route to the mobile network

    Airtime is routed to the recipient’s mobile network for delivery.

  4. 04

    Record the final outcome

    Transaction status and wallet history reflect the result.

Airtime operations

The tools to send airtime with control.

Bring wallet funding, recipient management, scheduling and transaction history into one organisation workspace.

Wallet and funding history

See available and reserved funds separately, with wallet movements recorded for review.

Reusable recipient lists

Add contacts, import recipient files and reuse lists for future airtime distributions.

Immediate or scheduled sends

Send a distribution now or choose a future date and time for it to be processed.

Transaction-level outcomes

Review each recipient’s delivery status and see how the outcome affects reserved funds.

How it works

From organisation funding to final status.

Airtime requests move through a shared workflow whether they start in the web workspace or through the API.

  1. 01 — FUND

    Add funds to the organisation wallet

    Payments matched to your organisation’s funding reference are credited and shown in payment history.

  2. 02 — PREPARE

    Select recipients and amounts

    Enter one recipient, choose a saved contact list or import contacts before you submit.

  3. 03 — SUBMIT

    Send now or schedule

    Submit from the web workspace or API. The requested wallet amount is reserved for processing.

  4. 04 — REVIEW

    Track the delivery outcome

    Successful transactions settle the reservation; final failures release the reserved amount.

Airtime API

Submit airtime by API. Receive the final result by callback.

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 documentation

Built around asynchronous delivery

  • Idempotency keys let clients safely retry an identical submission.
  • Each transaction has a public UUID; internal database identifiers are not exposed.
  • Signed callbacks carry final transaction results and can be retried for delivery.
  • Poll the balance endpoint when needed; final transaction outcomes arrive by callback.

Access and accountability

Clear access. Traceable wallet activity.

Organisation-scoped data

Contacts, users and transactions belong to the organisation workspace.

Scoped API credentials

Grant balance access and airtime sending as separate permissions.

Recorded wallet movements

Funding, reservations, settlement and release have an auditable history.

Common questions

Airtime distribution, explained.

Does an accepted API request mean airtime has been delivered?

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.

Can I send airtime to one number or a whole list?

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.

Can I schedule an airtime distribution?

Yes. Web and API submissions can be scheduled for a future date and time as well as submitted for immediate processing.

Do I need to poll for transaction status?

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.

How is a transaction outcome confirmed?

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.

Bring your airtime workflow into one workspace.

Manage distributions in the dashboard or connect your systems through the Airtime API.