BBPS Bill Fetch vs Payment Flow: Technical Overview

By Anvesh Tiwari

2 Apr 2026 · Updated 15 Apr 2026 · 2 min read

BBPS flows split into bill fetch (get amount and due date) and payment (debit customer and settle to biller). Getting both right is essential for customer trust. Learn more on Bill Connect.

Bill fetch

Customers enter account or consumer numbers; system retrieves validated bill details.

Payment

After confirmation, initiate pay and track status until success or failure with user-visible messaging.

Related: Best payout API · BBPS API · AEPS API · Mobile recharge API · Request demo

Understanding BBPS: Bill Fetch vs Payment Flow

The BBPS (Bharat Bill Payment System) API consists of two core flows: Bill Fetch and Bill Payment. Understanding the difference is critical for building a reliable bill payment integration.

What is the Bill Fetch Flow?

The Bill Fetch flow retrieves the outstanding bill amount from the biller’s system before the customer makes a payment. This step ensures accuracy and prevents overpayment or underpayment.

• Step 1: Customer enters their Consumer Number / Account ID
• Step 2: Your system calls the BBPS Bill Fetch API with biller ID + consumer details
• Step 3: BBPS retrieves the exact due amount from the biller in real time
• Step 4: Customer sees the bill amount and due date

Not all billers support bill fetch — some only support direct payment. NxtBanking’s API automatically handles both scenarios.

What is the Bill Payment Flow?

Once the bill is fetched (or in direct-pay scenarios), the payment flow transfers money from the customer’s account to the biller via the BBPS network.

• Step 1: Customer confirms the bill amount and initiates payment
• Step 2: Your system calls BBPS Pay API with transaction details + payment mode
• Step 3: BBPS processes the payment and returns a Transaction Reference Number (TRN)
• Step 4: Biller receives confirmation; customer gets receipt
• Step 5: Webhook fires to your server confirming success/failure

Bill Fetch vs Direct Payment — When to Use Each?

Error Handling in Both Flows

• Bill Fetch Errors: Consumer not found, biller system down, invalid account number
• Payment Errors: Timeout, duplicate transaction, insufficient balance, biller rejection

NxtBanking’s BBPS API includes built-in retry logic, detailed error codes, and real-time status webhooks — making both flows robust and developer-friendly.