Skip to main content
Delivery receipts provide a mechanism to track the final status of data bundle disbursement requests. When you submit a request with a receiptRequest object, the system will send a delivery receipt to your specified callback URL once the provisioning attempt reaches its final state. This enables real-time monitoring of data disbursement success, failure, or pending conditions.
Delivery receipts are only sent when a receiptRequest object is included in the original data disbursement request.
Ensure that the callback URL is publicly accessible and can accept incoming HTTP POST requests without requiring authentication.
If you enabled optional SMS notifications (messaging), the callback URL may also receive SMS delivery receipts. SMS receipts use the same format as the Message API delivery receipts; see Message Delivery Receipts.
Receipts may be delivered asynchronously and out of order.

​
Delivery Receipt Format

A delivery receipt is sent as an HTTP POST request to the specified callback URL containing the following JSON payload: 
{
  "correlator": "8f24c8c6-7e7c-4b6f-a622-d4a25f91d3c1",
  "phone": "+254123456789",
  "denomination": "2GB",
  "timestamp": "2025-06-02T14:30:00Z",
  "status": "Delivered",
  "reason": "ok",
  "reasonCode": "200"
}

​
Fields Explanation

FieldTypeDescription
correlatorStringThe same correlator supplied in your initial disbursement request. Used for tracing and matching.
phoneStringThe recipient MSISDN in international format.
denominationStringThe specific mobile data bundle attempted for provisioning.
timestampStringISO-8601 timestamp indicating when the final delivery outcome was recorded.
statusStringThe final delivery result of the data disbursement.
reasonStringOptional. Human-readable explanation describing the delivery status.
reasonCodeStringOptional. Provider or system code explaining the cause of a failure or delivery state.

​
Possible Delivery Status Values

StatusDescription
WaitingThe disbursement is awaiting processing.
DeliveredSignifies successful provisioning of the data bundle to the recipient.
UncertainThe delivery status is uncertain, possibly due to a lack of information from the gateway.
FailedTermination failed while attempting to handover to gateway
InvalidMsisdnThe recipient’s MSISDN (phone number) is invalid.
InvalidDenominationThe disbursement was discarded as it is not allowed per campaign rules allowed denominations.
InsufficientUnitsThere are not enough units (e.g., credits or balance) to complete the disbursement.
DuplicatedThe disbursement request is duplicated based on campaign rules frequency validation.
Callback endpoints must return HTTP 200 OK to acknowledge receipt. Failure to do so may trigger retry behavior depending on delivery policies.