BBPS — Prepaid Mobile / DTH Recharge

Detect the operator and circle from the customer's mobile number, read the operator's input fields, list the available plans, then submit the chosen plan as a payment.

Product & pricing: Bharat Bill Payment System (BBPS)

1. 1
   GETGet Operator Code and Circle

   Detect the telecom operator and circle from the customer's mobile number. Both come back as name/value pairs under `dependent_params` at the top level of the response, not under `data`.

2. 2
   GETGet Operator Parameters

   Read the recharge fields this operator requires, using the `phone_operator_code` from the previous step as `operator_id`. Prepaid operators typically expose `utility_acc_no` labelled "Mobile Number" plus a "Recharge Type" list — send every returned `param_name` to the payment step.

3. 3
   GETGet Recharge Plans

   List the plans for this operator and circle, and let the customer choose one. Mind the rename: pass the previous `circle_area` value as `circleid` here. Plans arrive under `dependent_params` → the `req_list` entry's `value` array.

   If response_type_id is 1805 — skip to step 4, Pay BBPS Bill. Plans unavailable (status is still 0) — take the amount from the customer and continue.

4. 4
   POSTPay BBPS Bill

   Submit the recharge. Map the fields: `phone_operator_code` from step 1, `utility_acc_no` = the customer's mobile number, `category` = the Mobile Prepaid / DTH id from Get Categories, and `amount` = the chosen plan's `amount` (or the agent-entered amount when plans were unavailable). `confirmation_mobile_no` and `sender_name` come from agent-entered customer detail. Omit `utilitycustomername` — it is optional, and only applies to bill payments where Bill Fetch supplied it. Persist `tid` and `client_ref_id`.

   If status is 0 — the flow is complete.

Flow at a glance