Payonclick Developer Docs
v1

Fetch Bill

POST https://payonclick.in/ext/v1/bbps/bill/fetch
Requires bills or transfer Signed request Counts toward your 60 req/min

Fetch the live bill and open a payment context


Body Params

NameTypeDescription
biller_id required string From /billers
customer_params required array [{ paramName, paramValue }] matching /biller/{id}
mobile_number required string Customer 10-digit mobile

Responses

StatusDescription
200 OK Fetch the live bill and open a payment context — see the example on the right.
200 OK · ad-hoc biller Alternate outcome for the same call — the second Response tab.
4xx / 5xx { "success": false, "error": { "code": "…", "message": "…" } } — every code is listed under Error Codes.
🔏
This call must be signed

POST carries an X-Signature header over POST\n/ext/v1/bbps/bill/fetch\n{TIMESTAMP}\n{BODY_SHA256}. The samples on the right compute it for you; the rules are in Request Signing.

📘
Good to know

An ad-hoc biller still issues a bill_token with allow_manual_amount: true — supply your own amount at payment. A mandatory-fetch biller with no bill returns 422 BILL_FETCH_FAILED and no token, so it can never be paid blind.