Guides

BBPS bill payment in India: the complete guide for 2026

Updated 2026-05-17 · 14 min read

What BBPS is, why it now handles every credit card bill payment in India, who the bill aggregators are, and how to use the system without losing reward points or risking late payments.

"BBPS used to be a backwater for utility bill payments. The RBI's July 2024 mandate made it the regulated rail for every credit card bill in India. That changed the architecture of consumer payments overnight - most users still don't notice it."

Quick answer

  • BBPS = Bharat Bill Payment System. Centralised bill payment rail run by NPCI Bharat BillPay Limited (NBBL) under RBI regulation.
  • Since 1 July 2024, all credit card bill payments from third-party apps are mandated to route through BBPS.
  • The system has three roles: COU (customer-facing app), BOU (biller aggregator), NBBL (the switch).
  • Bill categories: credit cards, utilities (electricity, gas, water), telecom, broadband, DTH, education, insurance, loan EMIs, FASTag, municipal taxes, society maintenance.
  • Auto-debit is supported via NPCI's e-mandate framework with mandatory pre-debit notification 24 hours before debit.

Who this guide is for

This is the deep guide for:

  • Young earners and retail users who want to understand exactly what happened on 1 July 2024 and why some apps temporarily stopped offering credit card bill payment.
  • Founders or product teams building a fintech that touches bill payments.
  • Anyone paying ₹50K+ a month in credit card bills who wants the auto-debit + reward points + GST + standing instruction stack figured out.

What is BBPS, really

BBPS is infrastructure - not an app. It's the same shape of thing as UPI, NACH, or IMPS: a centralised rail that aggregates payments and clears them between parties.

NPCI Bharat BillPay Limited (NBBL) was set up in 2018 as a wholly-owned subsidiary of NPCI to operate BBPS as a separate entity. It is regulated under RBI's payment system licensing framework.

Before BBPS, paying an electricity bill on PhonePe and on Paytm went through totally different backend arrangements - both involved direct integrations with each electricity utility, leading to fragmented data, settlement delays, and weak consumer protection. BBPS standardises this:

`` User → COU app → NBBL switch → BOU → Biller ↑ Settlement, reconciliation, audit trail ``

The three-layer architecture: COU, BOU, NBBL

RoleWhat it doesExamples
COU (Customer Operating Unit)The customer-facing surface where the user initiates the bill payment.CRED, PhonePe, Paytm, Google Pay, BHIM, individual bank apps
BOU (Biller Operating Unit)The biller-side aggregator that connects billers (utilities, banks, telcos) into BBPS.Setu, Cashfree, BillDesk, Eko, AGS Transact, RazorPay
NBBL (Switch)NPCI's central system that routes the transaction, settles funds, and provides the audit trail.One entity - NPCI Bharat BillPay Limited

A single COU can connect to many BOUs implicitly through NBBL - the COU doesn't pick the BOU, the biller-COU pairing is resolved by NBBL via the biller registry.

Why the credit card bill mandate matters

Until mid-2024, credit card bills on third-party apps were handled via direct bank tie-ups. The largest of these was the CRED-HDFC arrangement which gave CRED disproportionate scale (CRED handles ~40% of premium credit card bill payments by value in India by some estimates).

The RBI's concern was twofold:

  1. Fragmentation: dozens of bilateral arrangements meant no consistent settlement, no consistent customer protection, no centralised view.
  2. Concentration: a small number of third-party apps were aggregating significant payment volume on the rails of a few banks.

The mandate forces all third-party CC payments into BBPS. Issuing banks' own apps (HDFC Bank, ICICI Bank, etc.) are exempt - those remain intra-bank and don't need to route through BBPS.

The effective date was originally 30 June 2024. PhonePe, CRED, and others briefly pulled CC bill payment after the deadline. Most re-launched within weeks after onboarding to BBPS via BOUs like Setu and Cashfree.

How a BBPS credit card bill payment flows, step by step

  1. User opens COU app (CRED), navigates to credit card bill.
  2. App fetches outstanding bill from BBPS biller registry - biller-side data is owned by the BOU partner of the issuing bank.
  3. User enters payment amount, picks funding source (UPI, debit card, net banking, or another credit card if allowed).
  4. COU initiates transaction to NBBL with the biller ID, amount, and customer reference.
  5. NBBL routes to the appropriate BOU.
  6. BOU debits the funding source (via UPI/IMPS rail) and credits the biller (the issuing bank).
  7. NBBL writes the transaction to its audit log; both COU and BOU get acknowledgement.
  8. User sees instant confirmation; settlement is T+0 or T+1 depending on funding instrument.

This is significantly more controlled than the pre-BBPS bilateral world.

Bill categories supported on BBPS in 2026

CategoryExamples
Credit card billsAll major issuers (HDFC, ICICI, SBI, Axis, AmEx, IDFC FIRST, RBL, etc.)
ElectricityAll state DISCOMs, private discoms (Tata Power, Adani Electricity, BSES, etc.)
GasIndraprastha Gas, Mahanagar Gas, Gujarat Gas, LPG (Indane, HP, BPCL)
WaterMunicipal water utilities
Mobile postpaidAirtel, Jio, Vi, BSNL
Broadband / LandlineAll major ISPs (ACT, Hathway, Jio Fiber, Airtel Xstream, BSNL)
DTH and cableTata Play, Dish TV, Airtel DTH, d2h, Sun Direct
Insurance premiumsLIC, HDFC Life, ICICI Pru, SBI Life, Bajaj Allianz, Star Health, etc.
Loan EMIsPersonal loans, home loans, auto loans, education loans (most NBFCs and banks)
FASTagAll toll plazas via FASTag
Municipal taxesProperty tax, water tax (in supported municipalities)
Society maintenanceApartment associations using NoBroker, MyGate, ApnaComplex
SubscriptionsStreaming, education, fitness (growing category)
Education feesSchools and colleges integrated via SCROL, Eduvanz, etc.

The biller count crossed 21,000 in 2024 and continues to grow. NPCI publishes the biller list at bbps.org.in and through NPCI public data dashboards.

Auto-debit on BBPS: how recurring payments work

BBPS supports two flows:

Push mode: user initiates each payment. Default for one-off or manual users.

Pull mode (auto-debit / standing instruction): user authorises a recurring debit. Built on NPCI's e-mandate framework. Key rules:

  • Pre-debit notification: 24 hours before each debit, the COU must send a notification to the user.
  • User must be able to cancel the mandate from the same COU at any time.
  • Mandate amount can be fixed or variable (variable = "as per actual bill").
  • Maximum mandate value per debit is set during mandate creation.

For credit card bills specifically, auto-debit is the recommended flow because credit card due dates are sensitive - missing a due date triggers ₹500-1000 late fee + interest from statement date on the entire outstanding.

How BBPS interacts with credit card reward points

A common misconception: paying a utility bill via BBPS earns different reward points than paying outside.

It doesn't. BBPS is the payment rail. Reward points are determined entirely by:

  1. The card used to fund the payment (HDFC Diners Club, ICICI Amazon Pay, etc.).
  2. The merchant category code (MCC) the BBPS transaction is mapped to.

Most banks now classify BBPS transactions under specific MCCs (4900 for utilities, 6012 for financial services, etc.). What changed materially in 2023-24 is that many premium cards (Axis Magnus, HDFC Infinia, ICICI Emeralde) excluded utility, rent, insurance, education, government, and tax categories from reward earning. This is a card-level policy change, not a BBPS issue.

To check whether a specific BBPS category earns rewards on your card:

  1. Find the card's MITC (Most Important Terms and Conditions) document on the bank website.
  2. Look for the "categories excluded from reward earning" section.
  3. Cross-reference with the MCC for BBPS category you'll pay.

If the category is excluded, paying that bill via the card earns nothing - neither on BBPS nor on direct payment.

When BBPS is the wrong choice

Cases where you should bypass BBPS:

  1. Paying your own bank's credit card from your own bank's account: faster and no MCC ambiguity if you pay direct.
  2. Government bill payments where the government portal offers a discount: e.g., some property tax portals give 5% rebate on direct portal payment, lost if routed via BBPS.
  3. Cash payments at agent locations: BBPS supports cash-mode in some BCs (Business Correspondents) but the convenience fee usually exceeds the benefit.

Pitfalls in using BBPS

  1. Phishing apps: fake COU lookalikes that intercept bill payments. Always use a known app from official app stores.
  2. Wrong biller mapping: some billers have multiple variants in the BBPS registry (e.g., MSEB has 7 different entries by region). Picking the wrong one means the payment doesn't reach the correct account.
  3. Auto-debit on cards with utility exclusions: you're paying convenience but earning nothing on reward points.
  4. Late settlement on non-CC bills: rare, but some BBPS transactions for utilities have shown T+2 to T+3 settlement, occasionally causing utility-side late fees. Pay 2-3 days before due date.
  5. Mandate not cancelled after account close: if you close a credit card but the auto-debit mandate is still active, you get ₹100 mandate failure debits. Always cancel mandates first.

How BBPS fits into the Indian payments stack

RailUse caseSettlementOperator
UPIP2P + P2M paymentsT+0NPCI
BBPSBill paymentsT+0 / T+1NBBL (NPCI subsidiary)
NACHBulk batch debits (salary, EMI)T+1NPCI
IMPSImmediate fund transferT+0NPCI
RTGSLarge-value real-timeReal-timeRBI
AePSAadhaar-based via BCT+0 / T+1NPCI
NETCTolls via FASTagT+0NPCI
AAConsented financial data sharingN/A (data, not money)RBI ReBIT

For the Account Aggregator framework explainer, see Account Aggregator India consumer guide.

How Qubera works with BBPS

Qubera reads your credit card statements via email extraction and surfaces:

  1. Total outstanding across all your cards (consolidated view).
  2. Due dates per card (so you don't miss any).
  3. Optimal payment date - usually 2-3 days before due, after grace period analysis.
  4. Funding source recommendation - which account or which auto-debit gives the best net cost.

Qubera doesn't move money - your bill payment still flows through your COU (CRED, PhonePe, your bank app) into BBPS. We sit on top as the intelligence layer that tells you what to pay, when, and from where.

For the full credit card optimisation deep-dive, see optimize credit card spending India.

Further reading

Frequently asked questions

What is BBPS?

BBPS (Bharat Bill Payment System) is the centralised RBI-mandated platform for bill payments in India. Run by NPCI Bharat BillPay Limited (NBBL), it standardises how Customer Operating Units (COUs, like apps and banks) pay billers (utilities, credit cards, insurance, loans, etc.) through Biller Operating Units (BOUs) such as Setu, Cashfree, and BillDesk.

Why are all credit card bill payments now routed through BBPS?

From 1 July 2024, the RBI mandated that all credit card bill payments in India must flow through BBPS. The reason: NPCI wanted a single, auditable, regulated rail for credit card bill settlement instead of fragmented bank-by-bank arrangements. After enforcement (and a brief postponement), most third-party apps now route CC bills through BBPS exclusively.

Can I still pay credit card bills outside BBPS?

From the issuing bank's own app or website, yes - that's not a third-party route, it's intra-bank. From third-party apps (CRED, PhonePe, Paytm, Google Pay, etc.), no - these now go through BBPS as the regulated rail. Some apps initially pulled credit card bill features when the mandate hit, then re-launched after onboarding to BBPS.

What is the difference between COU and BOU in BBPS?

COU (Customer Operating Unit) is the customer-facing app or bank channel where you initiate the payment - CRED, PhonePe, Paytm, your bank app. BOU (Biller Operating Unit) is the biller-side aggregator that connects the biller (utility, credit card issuer) to BBPS - Setu, Cashfree, BillDesk, NPCI BillPay itself. NBBL sits in the middle as the switch.

Do I lose credit card reward points by paying via BBPS?

No, BBPS is just the payment rail. Reward points are determined by the card you use to fund the payment - if you pay an electricity bill via BBPS using a credit card that gives 2% on utility, you still get the 2%. The exception: many premium cards have started excluding utility, rent, insurance, and government from reward earning entirely - that's a card-level change, not a BBPS issue.

Which bill categories are supported on BBPS?

After the 2024 expansion, BBPS supports: credit card bills, electricity, gas (pipeline and LPG), water, broadband and landline, mobile postpaid, DTH and cable, education fees, insurance premiums, EMIs and loan repayments, FASTag recharges, municipal taxes, society maintenance, subscriptions, and several housing finance billers. Categories continue to be added quarterly.

How do BBPS auto-debit and recurring payments work?

BBPS supports both push (user-initiated each cycle) and pull (auto-debit / standing instruction) modes. Auto-debit is the most common for utility and credit card bills - once a user sets it up via the COU app, NPCI's e-mandate framework triggers the payment on each due date, with pre-debit notification 24 hours before. Cancellation is mandatory via the same COU.

Is BBPS safe?

BBPS is centrally regulated by RBI with NBBL as the implementing entity. All transactions are auditable. The settlement risk is borne by NPCI rather than individual COUs. The main consumer risk is not BBPS itself but app-level vulnerabilities - phishing apps mimicking COUs, fake biller listings. Always use a known COU (issuing bank, CRED, PhonePe, Paytm, Google Pay).

Related guides

Qubera is the AI personal finance companion for India. Loading the interactive version…