BBPS Integration: Build a Bill Payment App in India
Updated: 2 days ago
AI Summary: BBPS integration connects an Indian bill-payment app to Bharat Connect through an appropriate operating or agent-institution route. The build needs bill fetch and payment flows, status handling, reconciliation, complaints and partner controls. Choosing the responsible licensed entity before designing the app helps separate the fintech's technology role from regulated operations. |
Electricity, gas, broadband, DTH, FASTag recharge, loan EMIs, insurance premiums, school fees: a huge share of India's recurring payments now runs through the Bharat Bill Payment System (BBPS), which NPCI Bharat BillPay Ltd (NBBL) operates under the Bharat Connect brand. If you are adding bill payments to a wallet, a banking app, a lending app or a retail agent network, BBPS is the rail you will plug into.
The rules changed in 2024. The RBI (Bharat Bill Payment System) Directions, 2024, in force from 1 April 2024, replaced the 2014 framework. They set out who can participate, how funds must be held and how complaints must be handled. That changes the build question from "how do we call a bill-fetch API?" to "which role do we play in BBPS, and what must our software do because of that role?"
This guide covers the roles, the route choice, onboarding, the flows your app must support, a reference architecture, the compliance features to build, and the factors that drive cost and timeline. If you are mapping licences across products and markets first, start with our Fintech Licensing Requirements 2026 guide.
BBPS integration: How BBPS is structured under the 2024 RBI Directions
The Directions describe a tiered system. Every design decision you make depends on where you sit in it.
Role | What it does | Who can play it |
BBPCU (Bharat Bill Pay Central Unit) | Operates BBPS, sets operational and technical standards, runs clearing and settlement, provides guaranteed settlement | NBBL, the authorised payment system provider |
COU (Customer Operating Unit) | Gives customers a physical or digital interface to pay bills, directly or through Agent Institutions | Banks, authorised non-bank Payment Aggregators, existing authorised BBPOUs |
BOU (Biller Operating Unit) | Onboards billers (directly or via biller aggregators) so their bills can be collected on BBPS | Same as COU |
Agent Institution (AI) | Provides the customer interface (app, website, counter) for bill payments | Entities certified by NBBL and onboarded by a COU |
TSP (Technology Service Provider) | Provides technology to billers, BBPOUs or AIs to integrate with BBPS | Entities certified by NBBL; no funds may flow through a TSP |
Sponsor bank | Facilitates settlement of non-bank BBPOUs with NBBL | Scheduled commercial banks |
COUs and BOUs together are called Bharat Bill Payment Operating Units (BBPOUs). Three points in the Directions matter most for product teams:
Banks and non-bank Payment Aggregators do not need a separate BBPS authorisation. They must inform RBI's Department of Payment and Settlement Systems (DPSS) before they start operating as a BBPOU.
Running your own bill payment system outside BBPS is a regulated activity. Any entity other than a biller that operates a system for paying bills outside BBPS is a "payment system" under the PSS Act and needs RBI authorisation.
The COU is responsible for its Agent Institutions. It must give customers access to all billers on BBPS, provide a way to raise disputes, and answer for the AIs it has signed.
Which route should you take?
This is the most important decision in the project. It sets your capital needs, your integration depth and your launch date.
Route | What you build | Regulatory status | Who holds funds | Best for |
Agent Institution via a COU | Customer app or agent app on top of a COU's BBPS APIs | Certified by NBBL, onboarded by a COU; no RBI authorisation of your own | The COU (and its settlement arrangements) | Fintech apps, lenders, retail agent networks, super-apps starting out |
Participating Agent Institution | Direct technical integration with the BBPCU, with a COU for fund settlement | Certified by NBBL; owns its tech integration, security and infrastructure | Settled through the COU | AIs with high volumes that want more control over uptime and features |
Own COU / BOU | Full BBPOU stack: customer or biller onboarding, escrow, settlement, disputes | Bank, or non-bank authorised as a Payment Aggregator, then intimation to RBI DPSS | You, in a BBPS-only escrow account (non-banks) | Payment companies whose core business is bill collection |
TSP | Integration software for billers, BBPOUs or AIs | Certified by NBBL; never touches funds | Not you | Tech vendors and biller-side integrators |
Agent Institution through a COU
This is how most apps launch. You sign with a COU (a bank or authorised non-bank PA running BBPS), submit an Agent Institution consent form, complete the COU's due diligence and certification, then integrate its BBPS APIs. NBBL's Procedural Guidelines for BBPS (V6, November 2025) say Agent Institutions are certified by the BBPCU and onboarded by the COU. They also say AIs cannot onboard other AIs or extend BBPS services to more digital interfaces. If you plan to white-label your bill pay for partners, design for that limit from day one.
Participating Agent Institution
The same guidelines describe "participating AIs" that integrate directly with the BBPCU. They own the technical integration, transaction security and infrastructure, but a COU still onboards them for fund settlement. This route gives you more control over latency, retries and feature rollout. It also gives you more operational responsibility.
Becoming a BBPOU yourself
Under the 2024 Directions, the practical route to becoming a non-bank COU or BOU is to be an authorised Payment Aggregator. Under the RBI Payment Aggregator Directions, 2025 that means ₹15 crore of net worth when you apply and ₹25 crore by the end of the third financial year after authorisation, plus all the PA duties on escrow, merchant due diligence and security. Our payment aggregator build guide explains those duties. Older articles quote a separate ₹25 crore net-worth rule for BBPOU applicants. That came from the 2014 guidelines, which the 2024 Directions replaced.
Technology service provider
If you build biller integration software, BBPS middleware or reconciliation tools for others, you can seek NBBL certification as a TSP. The Directions require NBBL to ensure no funds flow through a TSP, so your architecture must keep you out of the money path.
Onboarding steps and timelines
For an Agent Institution, the usual sequence is:
Choose a COU. Compare biller coverage, API quality, uptime, settlement terms, commercials and support. Ask which payment modes they support in BBPS (UPI, cards, net banking, wallets, cash at agents).
Submit the Agent Institution consent form with company KYC, financials and promoter details. Axis Bank, a COU, lists items such as business address proof, KYC documents, a banker's opinion, two years of ITRs and financial statements, and background checks on promoters and directors. It also notes that an entity that has applied for, or received in-principle approval as, a BBPOU is not eligible to be an AI. Your COU's list may differ.
COU due diligence. Under NBBL's guidelines the COU must visit every AI during onboarding to check its infrastructure and business model, and must verify the AI's grievance contact details.
Integration and UAT against the COU's sandbox, including NBBL's screen and flow requirements for biller categories, receipts and complaints.
Activation. An NBBL circular requires the COU to forward the AI consent letter within 7 days and to complete activation within 60 calendar days of receiving it.
For your own BBPOU, NBBL's guidelines add steps: intimate RBI DPSS, sign an agreement with NBBL (a tripartite agreement with a sponsor bank for non-banks), get connectivity, complete UAT certification, intimate RBI again before going live, and start operations within six months of UAT certification.
Core BBPS flows your app must support
BBPS is built around fetching the bill before payment. The Directions say transactions need the bill to be fetched before payment starts. For prepaid services, the customer's relationship with the biller is validated through the platform instead. In practice your app handles these flows:
Biller master sync. Pull the list of categories, billers and each biller's input parameters (consumer number, account ID, mobile number and so on). Billers change often, so sync on a schedule and cache.
Bill fetch, then pay. The customer enters identifiers, you fetch the bill (amount, due date, bill number), show it, take payment, and send the payment request with the fetched bill reference.
Validate, then pay. For prepaid recharges and some billers, you validate the customer with the biller, then pay.
Direct or ad-hoc payment for billers that allow it.
Transaction status. Fetch and payment responses can be asynchronous. Poll status APIs or consume callbacks, and never mark a payment final on the client's word alone.
Complaints. Register complaints against the BBPS reference number and track their status.
Reminders and auto-pay. Store consented billers and due dates for reminders. Auto-debit needs a mandate on the payment instrument (for example UPI AutoPay or card e-mandate), with its own rules.
Vendor docs such as Setu's BBPS API list show how one COU exposes these flows. NBBL publishes the underlying BBPS Technical Standards.
Reference architecture
Module | Responsibilities |
Biller catalogue service | Category and biller master sync, input-parameter schemas, logos, search, caching |
Customer and biller registry | Saved billers, consented reminders, nicknames, linked payment methods |
Bill fetch / validate orchestrator | Builds requests from biller schemas, handles timeouts, retries and biller downtime |
Payment orchestration | Collects payment via UPI, cards, net banking, wallet or cash (agent apps); idempotency keys per BBPS request |
BBPS connector | COU API client (or direct BBPCU client for participating AIs), request signing, encryption, certificate rotation |
Transaction state machine | Initiated, pending, success, failed, reversed, refunded; links your order ID, payment ID and BBPS reference |
Receipts and notifications | Instant confirmation by screen, SMS or printed receipt, with the BBPS reference number |
Complaints module | Raise and track BBPS complaints, map them to internal tickets, show status to users |
Reconciliation and settlement | Daily match of your payments, COU settlement files and BBPS transaction reports; break handling |
Agent network module (if physical) | Agent onboarding, float or wallet limits, commissions, device binding, printed receipts |
Admin and reporting | Biller performance, failure rates, complaint ageing, finance reports |
Treat the BBPS connector as replaceable. Many teams start on one COU and later add a second for redundancy or better biller coverage. A clean adapter layer makes that a configuration change, not a rewrite. Our list of must-have API integrations for Indian fintech startups covers the KYC and payment APIs that usually sit next to it.
Compliance features to build
Instant confirmation and receipts
Customers must get immediate confirmation of a bill payment. Show the BBPS reference number on the success screen, in the SMS and on any printed receipt. That reference is what the complaint system uses.
Disputes and complaint integration
The Directions require NBBL to run a centralised, end-to-end complaint system in line with RBI's Online Dispute Resolution guidelines, and all COUs and BOUs must be integrated with it. As an AI, you need an in-app way to raise complaints that flows into your COU's integration. Track ageing so nothing breaches the timelines.
Failed transaction TAT and refunds
The Directions point COUs and BOUs to RBI's circular on harmonisation of turnaround time and customer compensation for failed transactions (20 September 2019). Build automated reversal tracking for cases where the customer was debited but the bill was not paid, and alert operations before deadlines.
Escrow and funds flow (non-bank COU or BOU)
A non-bank BBPOU must open an escrow account with a scheduled commercial bank only for BBPS transactions. The Directions list the allowed credits and debits: funds collected from customers, settlement of BBPS transactions, failed or disputed transactions, and recovery of charges or commissions. Your ledger must tag every movement to one of those buckets. If you are an AI, confirm in your COU contract exactly when and how funds move, so your own books match.
Security and data
Encrypt traffic and payloads as your COU and NBBL's technical standards require, protect API credentials in a secrets vault, and log every request with its BBPS reference for audit. Apply the same controls you would for any Indian payments product: role-based admin access, VAPT before launch, and secure storage of customer identifiers. Our guide to API security for Indian fintechs goes deeper.
Channel rules
Axis Bank's AI FAQ notes that an Agent Institution must offer BBPS bill payment on all its current channels where bill payment is offered. If you have a website, an app and an agent network, plan the rollout across all of them.
Cost and timeline drivers
We do not publish fixed prices because the range is wide. These are the factors that move cost and time the most:
Driver | Why it matters |
Route | AI on a COU is an app-plus-integration project; your own BBPOU adds PA authorisation, escrow, settlement and NBBL certification |
Number of biller categories | Each category has its own inputs, validation and edge cases (prepaid vs postpaid, partial payment, overdue) |
Payment modes | UPI-only is simplest; adding cards, wallets and cash-at-agent adds flows and reconciliation |
Physical agent network | Agent onboarding, float management, commissions and receipt printing are a product of their own |
Auto-pay and reminders | Mandates, scheduling and notification consent add scope |
Redundancy | A second COU or failover logic improves success rates but adds integration and reconciliation work |
COU onboarding speed | Document review, field visit and UAT slots often set the launch date more than your code does |
Commercials (customer convenience fees, commissions and COU charges) vary by COU, biller category and payment mode. Get them in writing during COU selection.
Build plan in phases
Pick the route and the COU. Confirm biller coverage for your target categories and the commercials.
Design the transaction state machine and ledger around the BBPS reference number.
Build the biller catalogue and fetch-pay flows for two or three high-volume categories first, such as electricity, mobile prepaid and broadband.
Add complaints, receipts and reconciliation before go-live, not after.
Complete UAT and activation with your COU.
Expand to more categories, auto-pay, an agent network or a second COU.
For a comparison of BBPS with private bill pay options, see our earlier post on Bharat Bill Pay vs PayU. For how NPCI's systems fit together, read our analysis of the NPCI technology stack.
FAQs
Do I need an RBI licence to offer BBPS bill payments in my app?
Not if you join as an Agent Institution through a Customer Operating Unit. You need NBBL certification and onboarding by the COU, and the COU takes responsibility for you. You need RBI authorisation (as a Payment Aggregator) only if you want to be a non-bank COU or BOU yourself.
What is the difference between a BBPOU and an Agent Institution?
A BBPOU is a system participant in BBPS: a Customer Operating Unit, a Biller Operating Unit, or both. An Agent Institution provides the customer interface and works under a COU. BBPOUs settle with NBBL; AIs settle through their COU.
Is there still a ₹25 crore net-worth rule for BBPOUs?
That rule came from the 2014 BBPS guidelines, which the RBI BBPS Directions, 2024 replaced. Under the 2024 Directions, banks, authorised non-bank Payment Aggregators and existing authorised BBPOUs can participate. A non-bank therefore needs PA authorisation, which carries its own net-worth requirement.
How long does BBPS onboarding take for an Agent Institution?
NBBL requires the COU to complete activation within 60 calendar days of receiving your consent letter. Your own build time depends on how many biller categories and payment modes you launch with.
Can I build my own bill payment system outside BBPS?
Only with RBI authorisation. The 2024 Directions say any entity other than a biller that runs a bill payment system outside BBPS is operating a payment system under the PSS Act and needs authorisation.
Can an Agent Institution white-label BBPS to other apps?
NBBL's procedural guidelines say AIs cannot onboard other AIs or extend BBPS services to additional digital interfaces. Check with your COU before you plan any partner distribution.
Build your BBPS bill payment app with Fintegration
Fintegration builds payment, lending and banking platforms for fintechs in India and the US. We can help you choose a COU, design the biller catalogue, transaction state machine and reconciliation layer, and integrate BBPS alongside UPI, KYC and your existing ledger. Talk to our team to scope your build.
