DEV Community

Munisekhar Udavalapati
Munisekhar Udavalapati

Posted on

BBPS Bill Fetch API: A Complete Guide

Sample Request and Response Structures:

Bill Fetch Request: Describes XML-based structures sent by the customer (BBPOU) or intermediary (BBPCU) to fetch bill details.
Bill Fetch Response: Contains the bill details fetched from the biller or returned to the customer.
Key XML Tags and Attributes:

: Metadata such as API version, timestamp (ts), and unique identifiers (refId).
: Transaction information like timestamp (ts), message ID (msgId), and risk scores.
: Customer-related information such as mobile number, Aadhaar, PAN, and tags for additional attributes.
: Data about the agent initiating the transaction, including device information (e.g., IMEI, IP, MAC).
: Biller identification and customer reference parameters to uniquely identify a bill.
Tag Details:

Explanation of each XML element and attribute with their occurrence constraints, e.g., mandatory (1..1) or optional (0..n).
Sample XSD (XML Schema Definition):

Defines the structure and constraints of the BillFetchRequest message.
Analytics Tags:

Metadata for monitoring or logging purposes (e.g., FETCHREQUESTSTART, FETCHREQUESTEND).
Risk Scores:

Evaluates risk levels (TXNRISK) for the transaction from different providers.
Biller Response:

Includes bill details like customer name, due amount, due date, bill date, and breakdown of charges.

Sentry image

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →

Top comments (0)

Image of Docusign

🛠️ Bring your solution into Docusign. Reach over 1.6M customers.

Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.

Learn more