Developer Docs
BBPSBill Payments API
Bill payment flow
A bill payment is five calls, in this order. The first three happen before any money moves; the last is only needed when a webhook has not arrived.
Sample reference
The order of calls is how the integration works. Exact paths and fields are confirmed with your sandbox credentials.
- 01GET
Biller catalogue
/v1/bbps/billersShow the customer the billers they can pay, and which fields each one needs.
- 02POST
Validate customer
/v1/bbps/customers/validateCheck the consumer number before any money is involved.
- 03POST
Fetch bill
/v1/bbps/bills/fetchGet the live amount due. Skip this if the biller's fetchSupported is false.
- 04POST
Submit payment
/v1/bbps/paymentsPay, with your own clientReference. Store the referenceId that comes back.
- 05GET
Transaction status
/v1/bbps/payments/{referenceId}If the payment came back PENDING and no webhook has arrived, ask for its status.
📘 Where webhooks fit
A payment can come back PENDING. Its final result arrives by webhook; the status call is the backstop. Webhooks & Transaction Status
