From Mandate to Market Leadership: How Early BBPS Adopters Are Positioning Themselves as Digital-First Banks

Most cooperative and state banks are treating Bharat Connect, the platform formerly known as BBPS, as a compliance requirement. A regulatory directive from RBI arrived, a team was assigned, a certification was pursued. The banks pulling ahead have taken a different view - treating Bharat Connect as a daily engagement engine, a recurring fee income line, and a data asset that compounds in value with every transaction. The gap between those two positions is already showing up in transaction volumes, customer retention rates, and the pace at which fintech competitors are building habits on bank customers that banks are not yet capturing.

The platform's scale leaves no room to treat this as a future priority. Bharat Connect now has 22,641 live billers, 72 Customer Operating Units, 54 Biller Operating Units, and 1,269 agent institutions as of May 2026.¹ Transaction volume has grown at a 73% compound annual growth rate over five years and is projected to surpass 3 billion transactions annually by 2026.² These are not projections from a nascent platform - they are the numbers of a mature, compounding ecosystem that banks which have not yet deployed are already behind on.

The competitive pressure from non-bank platforms is not theoretical. CRED, operating as an Agent Institution on Bharat Connect, processed over ₹15,000 crore in bill payments in a single month - July 2024 - before it even received COU certification.³ CRED's activities contributed approximately 40% of the growth in Bharat Connect payment value between June and July 2024.³ The fintech platforms building bill payment habits on bank customers are not slowing down, and the habits they build are sticky. A customer who has established a routine of paying electricity, telecom, and insurance through a fintech app does not switch to the bank's app without a meaningful reason to do so.

What Being a COU or BOU Actually Means for Revenue

Banks on Bharat Connect operate as a Customer Operating Unit, a Biller Operating Unit, or both. The distinction matters because each role generates a different revenue stream, and dual registration means both run independently without one cannibalising the other.

COU (Customer Operating Unit)

• What it does: Offers bill payment to customers via the bank's own mobile or internet banking channel
• Revenue driver: Monthly active users × transaction frequency
• Fee range: ₹2.25 (electricity/gas) to ₹2.50–₹5 (water/telecom) interchange received per transaction
• Scales with: User activation - linear, no extra capital needed

BOU (Biller Operating Unit)

• What it does: Onboards billers so they can collect payments via any Bharat Connect channel
• Revenue driver: Number of billers onboarded × ecosystem-wide transaction volume across all 72 COUs
• Fee range: Per-transaction settlement fee from every COU's customers using your onboarded billers
• Scales with: Biller network depth - compounds across the whole ecosystem daily

Beyond fee income, the bill payment data a bank accumulates through its COU and BOU positions is a credit underwriting asset. A customer who consistently pays school fees, insurance premiums, and a home loan EMI through the bank's Bharat Connect-enabled app is providing a real-time, verified picture of their financial obligations and payment reliability. This profile feeds pre-approved working capital products, personal credit offers, and savings product targeting with a conversion advantage that cold outreach cannot replicate.

The engagement mechanics are equally significant. A customer who pays electricity, telecom, insurance, loan EMI, and school fees through the bank's app logs in multiple times per week - not once a month at salary credit or statement time. This is the daily engagement model that fintech aggregators have built on Bharat Connect's rails for years. Banks that deploy Bharat Connect as a COU and BOU can reclaim this engagement on their own platform, under their own brand, with their own data.

The Revenue Architecture: COU and BOU Fee Income at Scale

The revenue case for Bharat Connect is concrete, not directional. Consider a cooperative bank with 500,000 active mobile banking users. If each user averages three bill payments per month across electricity, telecom, and at least one recurring financial obligation, the bank is generating 1.5 million COU transactions monthly from infrastructure it already owns. At the ₹2.25–₹5 interchange rate per transaction, this is a meaningful recurring income line that did not previously exist - and that scales linearly with user activation, not with additional capital deployment.[^10]

The BOU revenue model scales differently. A bank with 500 billers onboarded generates BOU income from every transaction any Bharat Connect user makes with those billers, across all 72 COUs currently active on the platform.¹ A bank with 5,000 billers onboarded earns proportionally more from the same ecosystem. The revenue gap between a thin biller network and a deep one is not marginal - it compounds across every COU's user base, every day, without any additional cost to the BOU.

Together, COU and BOU income represent a revenue model that is more durable than one-time merchant acquisition fees and more defensible than transaction-processing arrangements that can be repriced. The data that accumulates - structured, verified, purpose-tagged payment behaviour - becomes the underwriting foundation for credit products offered at the right moment, to the right customer. No cold-outreach campaign can match that confidence. The ceiling on that BOU revenue, however, is set not by the bank's own ambition but by its biller network depth - which is why the choice of technology partner determines the revenue outcome more directly than any other deployment decision.

The addressable scope of Bharat Connect continues to expand. The platform now covers 25 or more biller categories - MF/SIP, insurance, education, municipal taxes, FASTag, National Common Mobility Card (NCMC), loan repayment, credit card, and NRI cross-border utility payments. RBI has further proposed linking the FX-Retail platform to Bharat Connect to facilitate NRI forex bill payments, expanding the addressable transaction pool well beyond domestic utility payments.⁴ NBBL has set a target of 1 billion monthly transactions on the platform within the next three to four years, up from the current base of 260 million.² Each new category is an additional daily engagement touchpoint for a bank already live. Each one is a missed opportunity for a bank still in deployment.

How State and Cooperative Banks Can Generate Revenue Through Digital Rupee Merchant Networks

Why Biller Network Depth Is the Competitive Moat

A bank live on Bharat Connect with thin biller coverage is technically compliant but commercially limited. If the electricity provider, telecom operator, insurance company, or municipal corporation that a customer actually uses is not available on the bank's platform, the customer pays through a competitor app. Once that habit forms, it is expensive to recapture. Biller depth is what determines whether a bank's Bharat Connect deployment becomes the customer's primary bill payment destination or a secondary option they use for the narrow subset of billers the bank happens to cover.

Bharat Connect has 22,641 live billers as of May 2026.¹ A bank starting biller onboarding from scratch today faces a significant gap. Each biller requires individual due diligence, technical integration, and NBBL compliance sign-off. This is operationally intensive at any scale and does not compress below a certain time threshold regardless of how much resource is applied to it.

What constitutes adequate biller coverage is not ambiguous. There is no prescribed minimum, but the logic is straightforward: a platform that covers eight of the twelve categories below sends the customer to a competitor app for the remaining four - and that competitor captures the daily habit, not the bank. These twelve categories represent the recurring payment obligations most Indian households carry simultaneously.

• Electricity
• Insurance premiums
• Gas
• Loan EMI
• Water
• Credit card
• Municipal taxes
• School and college fees
• Postpaid telecom
• NPS contributions
• DTH
• FASTag

The practical implication is that the bank's choice of Bharat Connect technology partner determines its day-one biller coverage more than its own onboarding effort does. A partner with a pre-integrated biller network converts months of individual onboarding work into a configuration exercise. The difference between going live with 500 billers and going live with thousands is the difference between a platform that covers a narrow subset of a customer's payment needs and one that positions the bank as their single bill payment destination from the first day of deployment.

Compliance and Certification: What Banks Must Have in Place

NBBL's Bharat Bill Payment System Procedural Guidelines, updated November 2025, define certification requirements for each participant role - COU, BOU, Agent Institution, and TSP.⁵ Banks must be certified at each role they intend to operate. Operating without certification creates regulatory exposure, not just operational risk, and the bank is liable for the compliance standing of any TSP it engages. For banks evaluating vendors, NBBL certification is the baseline requirement that distinguishes a legitimate RBI approved bill payment vendor from a platform provider that has not completed the certification cycle. The regulatory baseline for bank participants covers four non-negotiable requirements:

1. Maintain BBPS settlement infrastructure correctly so that it’s structured and segregated per NBBL specifications.
2. Hold escrow accounts with scheduled commercial banks per RBI Master Direction (required for non-bank BBPOUs).⁶
3. Verify independently that the TSP is NBBL-certified - never accept the vendor's self-description.
4. Ensure settlement funds never flow through the TSP under any circumstances - this is a hard regulatory rule, not a guideline.

Beyond Baseline: The Certification Timing Advantage

Banks that completed NBBL certification before RBI's July 2024 credit card bill payment mandate had a distinct operational advantage when that mandate triggered a surge in Bharat Connect transaction volumes. They had tested stable infrastructure before the volume hit. Late certifiers are now onboarding into a high-volume, mature system without the benefit of a low-volume testing period to identify and resolve integration issues. TSPs with prior multi-bank NBBL certification experience move new clients through the testing and certification process faster than newer TSPs completing their first cycle - a compounding advantage for the bank that prioritises speed in its partner selection.

TSP certification status should be verified independently before engagement, not accepted on the vendor's representation. NBBL maintains a list of certified participants. Using an uncertified TSP or a TSP through which funds flow improperly - creates the bank's own regulatory exposure, not the TSP's.

Speed to Market: The Cost of Every Month of Delay

The Bharat Connect deployment sequence has five stages, each with dependencies that cannot be done in isolation:

1. NBBL certification as COU and/or BOU
2. Biller network onboarding
3. COU/BOU API integration to the Bharat Connect switch
4. Channel embedding in mobile and internet banking
5. Staff training and merchant education

The cumulative gap between a bank that starts this process in Q3 2025 and one that starts in Q1 2026 is not measured in weeks. It is measured in quarters of transaction volume that either accrued to the bank or accrued to a competitor.

CRED's trajectory illustrates the stakes clearly. As an Agent Institution - without COU certification - it processed ₹15,000 crore in bill payments in a single month and contributed approximately 40% of Bharat Connect's value growth between June and July 2024.³ It then received COU certification, gaining direct biller access and the ability to settle independently. The fintech platforms building these volumes on bank customers are not constrained by the same internal approval cycles and legacy system dependencies that slow bank deployments. They are moving faster, and the habits they build compound.

NBBL regularly launches new biller categories and features. A technology partner that adopts these at launch - not six to twelve months later - means the bank's customers access new payment capabilities while they are still new, before the market moves on. The first bank in a geography to offer FASTag recharge, NRI cross-border bill payment, or MF/SIP through a Bharat Connect-integrated banking app captures the habit formation that every later entrant has to compete against.

The regulatory expansion trajectory reinforces the urgency. RBI's December 2024 proposal to link the FX-Retail platform to Bharat Connect - enabling NRI forex bill payments - is a new transaction category that banks already live as COUs and BOUs will capture from day one of its rollout.[4] Banks still in deployment at that point will miss the early volume and, more importantly, will miss the habit formation that early volume creates.

Why Digiledge Bill Payments Is Built for This Deployment

Banks that deploy Bharat Connect as a strategic asset - not a compliance checkbox - become their customers' daily financial operating system. Every bill paid through the bank's app is simultaneously a retention event, a behavioural data point, and a cross-sell signal. COU fee income on 1.5 million monthly transactions, BOU fee income from a deep biller network, and reduced customer acquisition costs from daily app engagement are all live within the first year of a well-executed deployment. The bank that treats Bharat Connect as infrastructure treats it as cost. The bank that treats it as a revenue platform treats it as investment with a defined return.

Digiledge Bill Payments is an NBBL-certified, Bharat Connect-compliant platform where banks operate as COU or BOU while fully controlling their UI/UX through a white-labelled platform.⁹ It delivers three things that in-house builds and thin TSPs do not:

• Full coverage of 25+ biller categories - including MF/SIP, NRI cross-border payments, and insurance - embedded within the existing banking or merchant app without a separate integration build.
• COU and BOU roles under one integration, with the bank retaining full UI/UX control through a white-labelled platform.
• A pre-integrated biller network - inherited, not built - since day-one it positions the bank as the customer's primary bill payment destination, not a partial alternative.

Digiledge has been a first-mover on every major Bharat Connect feature launch for four consecutive years and has received NPCI recognition for this track record. It built BOAT - Biller Onboarding and Automated Testing - for NPCI directly, a tool that now underpins automated biller certification across the ecosystem. It operates one of the largest pre-integrated biller networks in the market, meaning banks that deploy with Digiledge inherit that network rather than build it biller by biller. And it has delivered a bank-enablement model - staff training and merchant education included, not just technology delivery - across Federal Bank, Karnataka Bank, Canara Bank, Indian Bank, and CSB Bank.⁷

The difference between deploying with a partner that has this infrastructure in place and deploying with one that does not is the difference between day-one biller coverage that positions the bank as the customer's primary payment destination and a deployment that works technically but delivers thin value until the biller network catches up months later.

Frequently Asked Questions

1. What is the difference between a COU and BOU on Bharat Connect, and how do banks earn from each?

A Customer Operating Unit earns a per-transaction fee on every bill paid through its own channel. A Biller Operating Unit earns on every transaction settled for billers it has onboarded, across all COUs on the platform. Dual registration means both revenue streams run simultaneously. The BOU income scales with biller network depth - more billers onboarded means more transactions earning revenue.

2. How does a bank qualify as an RBI approved bill payment vendor on Bharat Connect?

Banks must be certified by NBBL as a Bharat Bill Payment Operating Unit - covering the COU, BOU, or both roles they intend to operate. Certification requires a system audit, NPCI compliance sign-off, and structured testing per NBBL's Procedural Guidelines (November 2025). The TSP a bank engages must also be independently NBBL-certified, with settlement funds never flowing through the TSP.

3. What is the minimum biller coverage a bank needs to be its customers' primary BBPS platform provider?

At minimum: electricity, gas, water, municipal taxes, postpaid telecom, DTH, FASTag, insurance, loan EMI, credit card, education fees, and NPS. A platform missing any major category sends customers to a competitor app for those payments, where the competitor captures the daily engagement habit. Biller depth, not API compliance, determines whether the bank's platform becomes the customer's default.

4. How does Bharat Connect generate value added services for banking apps beyond basic bill payments?

Bill payment data accumulated through a bank's COU and BOU positions creates a structured, verified picture of a customer's recurring financial obligations - insurance, loan EMIs, school fees, utility payments. This becomes a credit underwriting asset and a product targeting signal, enabling pre-approved working capital, personal credit, and savings products with conversion rates that cold outreach cannot approach.

5. What does the Bharat Connect bill payment API integration process involve for a cooperative bank?

Integration involves NBBL certification as a COU and/or BOU, API connection to the Bharat Connect central switch via a certified TSP, biller network onboarding, and channel embedding in mobile and internet banking. A TSP with pre-integrated biller networks and prior NBBL certification experience compresses the longest lead-time stages - biller onboarding and compliance testing - from months into weeks.

References

1. 1.
   Bharat Connect Ecosystem Statistics - 22,641 live billers, 72 COUs, 54 BOUs, 79 Operating Units, 1,269 Agent Institutions (updated 1 May 2026). bharat-connect.com/statistics
2. 2.
   Mindgate Solutions - Bharat Connect 73% CAGR in transaction volume over five years to 2024; 3 billion annual transaction projection by 2026; NBBL target of 1 billion monthly transactions within 3-4 years, December 2025. mindgate.solutions/guides/bharat-connect-bbps
3. 3.
   Business Standard - CRED receives COU certification from BBPS; processed ₹15,000 crore in bill payments in July 2024 as Agent Institution; contributed ~40% of BBPS value growth June–July 2024, 23 August 2024. business-standard.com/companies/news/cred-receives-nod-from-bbps-to-operate-as-a-customer-operating-unit-124082300910_1.html
4. 4.
   RBI Statement on Developmental and Regulatory Policies - Proposal to link FX-Retail platform with Bharat Connect for NRI cross-border bill payments, December 2024. rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=58927
5. 5.
   NBBL - Bharat Bill Payment System Procedural Guidelines, November 2025. teamleaseregtech.com/updates/article/50680/bharat-bill-payment-system-bbps-procedural-guidelines
6. 6.
   RBI Master Direction on Bharat Connect/BBPS - escrow account requirements for non-bank BBPOUs, TSP certification rules, and fund flow prohibitions. rbi.org.in/Scripts/BS_ViewMasDirections.aspx
7. 7.
   Mintoak Blog - RBI's Bharat Connect Mandate: A New Era for Fintechs and Banks - cited for Digiledge bank-enablement model and NPCI recognition context. mintoak.com/blog/rbis-bharatconnect-mandate-a-new-era-for-fintechs-and-banks
8. 8.
   PwC India - Payments Landscape India - cited for broader BBPS transaction value projections and financial services digitisation context. pwc.in/consulting/financial-services/fintech/payments-landscape-india.html
9. 9.
   Digiledge Bill Payments Product Page - Mintoak - NBBL-certified, Bharat Connect-compliant, 25+ biller categories, white-labelled COU/BOU module. mintoak.com/products/digiledge-bill-payments