API Reseller
BBPS API
Biller discovery, bill fetch and payment across the Bharat Connect network. Bill fetch returns the live amount due from the biller, so your product never asks a customer to type an amount they might get wrong.
What you get
- Full biller directory with per-biller input parameters
- Live bill fetch returning the actual amount due
- Payment with instant confirmation where the biller supports it
- Complaint registration and status for a disputed payment
- Category coverage across electricity, water, gas, broadband and more
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Discovery
- Biller directory endpoint returns per-biller input parameters.
- Bill fetch
- Returns the live amount due from the biller, so no customer types an amount.
- Payment
- Instant confirmation where the biller supports it, otherwise pending.
- Disputes
- Complaint registration and status endpoints against a prior payment.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About bbps api
Why fetch the bill instead of letting the customer type the amount?
Because a typed amount is frequently wrong, and a wrong amount is a failed or partial payment that then needs a complaint raised. Bill fetch returns the live amount due from the biller, which removes the error entirely for billers that support it.
A payment succeeded but the biller has not credited the customer. What now?
Register a complaint against the original payment through the complaint endpoint and track it by its status. The payment is confirmed on our side, so this is a biller-side posting delay rather than a payment failure, and it is resolved through the dispute path rather than by re-paying.