BBPS Biller Onboarding for Lenders: EMIs From Any App
Last reviewed: November 2026
BBPS biller onboarding for lenders is the process of registering a lender as a biller in the Loan Repayment category of the Bharat Bill Payment System (BBPS), now branded Bharat Connect, so borrowers can fetch and pay equated monthly instalments (EMIs) from any participating app, bank or agent outlet. Without it, borrowers who miss a mandate debit pay by bank transfer or a stray QR code, and the lender spends days working out which loan each payment belongs to.
This guide is for chief technology officers (CTOs) and heads of collections at non-banking financial companies (NBFCs), banks, housing finance companies (HFCs) and microfinance institutions (MFIs). It covers how BBPS works for loans, a seven-step onboarding workflow, the bill fetch fields that matter, go-live checks and the metrics to track.
Key Takeaways
- Lenders join BBPS through a Biller Operating Unit (BOU), which onboards billers and carries out due diligence under the RBI Bharat Bill Payment System Directions, 2024.
- The bill fetch response is the heart of the integration; it decides whether borrowers can pay part, pay ahead or clear overdue amounts.
- Every BBPS payment carries a BBPS reference number, which makes automatic posting and reconciliation far easier than for bank transfers.
- Since 1 April 2026, only regulated lenders can stay in the Loan Repayment category, after NPCI Bharat BillPay Ltd directed the removal of unregulated billers.
What Is BBPS Biller Onboarding for Lenders?
BBPS biller onboarding for lenders connects the lender's loan system to the Bharat Connect network as a biller. After onboarding, a borrower can open a participating payment app, choose Loan Repayment, select the lender, enter a loan account number and pay the amount the lender returns.
BBPS is one of several digital repayment channels. Lender-generated links are covered in our guide to digital payment links for loan collections; BBPS differs because the borrower starts the payment from an app of their choice.
Who Does What in BBPS?
Four roles do the work in BBPS: the central unit, the Biller Operating Unit, the Customer Operating Unit (COU) and the biller. The RBI Bharat Bill Payment System Directions, 2024 (RBI/DPSS/2023-24/111, 29 February 2024, applicable from 1 April 2024) define them.
| Role | Who It Is | What It Does for a Lender |
|---|---|---|
| Central unit (BBPCU) | NPCI Bharat BillPay Ltd (NBBL) | Sets standards, routes transactions, clears and settles |
| Biller Operating Unit | A bank or authorised non-bank payment aggregator | Onboards the lender, carries out due diligence, settles funds |
| Customer Operating Unit | Apps, banks and agent networks | Gives borrowers the interface to fetch and pay |
| Biller | The lender | Returns bill details and posts payments to loans |
Why Does BBPS Biller Onboarding for Lenders Go Wrong?
BBPS biller onboarding for lenders goes wrong for five reasons: a fetch built on stale data, confusing customer parameters, unclear payment rules, posting only from the settlement file and complaints left outside the grievance process. Each is a design choice made early.
| Cause | Effect | Prevention Check |
|---|---|---|
| Fetch reads a nightly file, not the live loan | Borrower pays an EMI already debited by mandate | Real-time fetch from the loan system |
| Customer parameter borrowers do not know | Fetch failures and abandoned payments | Loan account number, with registered mobile as backup |
| No clear rule on part or advance payments | Payments rejected or wrongly allocated | Product-wise payment rules in the fetch response |
| Posting only after settlement | Borrower shown as overdue after paying | Post on payment confirmation, reconcile later |
| BBPS complaints handled outside the grievance system | Duplicate or missed complaints | Map BBPS complaints into one grievance queue |
What Is the Right Workflow for BBPS Biller Onboarding for Lenders?
The right workflow for BBPS biller onboarding for lenders has seven steps: choose the operating unit, complete due diligence, define customer parameters, build the bill fetch, set payment rules, build posting and reconciliation, and test complaints before go-live.
- Choose a Biller Operating Unit.
- Complete due diligence and the biller agreement.
- Define customer parameters, usually the loan account number.
- Build a real-time bill fetch service from the loan system.
- Set payment rules for part, advance, overdue and foreclosure payments.
- Build posting on confirmation and reconciliation on settlement.
- Test complaints, reversals and edge cases, then go live.
Steps 1 and 2: How Do You Choose a Biller Operating Unit?
Choose a Biller Operating Unit on four points: integration effort, settlement timing, fees and complaint support. Under the 2024 Directions, banks and authorised non-bank payment aggregators can act as operating units, and a BOU onboards billers either directly or through biller aggregators.
The BOU must apply merchant due diligence to the lender, so keep registration certificates and board approvals ready. Since March 2026, NBBL requires Loan Repayment billers to be regulated entities, so expect proof of regulatory status to be checked.
Step 3: Which Customer Parameters Should Borrowers Enter?
Use the loan account number as the main customer parameter, because it identifies exactly one loan. A registered mobile number can be a secondary option, but it creates a choice problem for borrowers with several loans.
Old account number formats cause many fetch failures. If your loan system changed numbering after a migration, accept both formats in the fetch, and our guide to customer master data cleanup in the LMS shows how to fix the underlying data.
Steps 4 and 5: What Should the Bill Fetch Response Contain?
The bill fetch response should contain six items: the amount due, due date, overdue amount, penal charges if any, payment rules and the borrower's masked name. Bharat Connect's loan repayment rules say partial payments, advance EMIs, overdue and penal amounts and foreclosure work only if the biller enables them.
| Fetch Field | Source in Loan System | Rule to Apply |
|---|---|---|
| Current EMI due | Repayment schedule | Exclude EMIs already presented by mandate |
| Due date | Repayment schedule | Show the next unpaid instalment |
| Overdue amount | Arrears ledger | Real-time, not from last night's file |
| Penal charges | Charges ledger | Show only if collected through BBPS |
| Part or advance payment allowed | Product rules | Set per product, not per borrower |
| Masked borrower name | Customer master | Enough for the borrower to confirm the loan |
The most common trap is the mandate overlap. If an EMI is already in a NACH presentation file, the fetch should not invite the borrower to pay the same amount again, and our guide to eNACH vs UPI AutoPay covers how mandates sit alongside other channels.
Step 6: How Should BBPS Payments Be Posted and Reconciled?
Post BBPS payments on the operating unit's payment confirmation, using the payment date as the value date, and reconcile against the settlement credit later. The 2024 Directions require every BBPS transaction to carry a BBPS reference number from initiation, which is the key that ties confirmation, settlement and complaints together.
Unmatched settlement lines should go to an exception queue, not a general suspense account. Our guide to unidentified receipts in lending explains why suspense balances grow when this step is skipped.
Step 7: How Are BBPS Complaints Handled?
BBPS complaints are handled through NBBL's centralised end-to-end complaint management system, with the BBPS reference number as the identifier. Operating units must integrate with it, so the lender's job is to receive these complaints and answer them inside its own grievance process.
Our guide to a loan grievance redressal system shows how to keep one record per complaint, whichever channel it came from.
Which Checks Should Run Before a BBPS Biller Goes Live?
Eight checks should run before a BBPS biller goes live: live fetch, mandate overlap, format tolerance, payment rules, posting, reversal handling, settlement match and complaint routing.
| Go-Live Check | What It Prevents |
|---|---|
| Fetch returns live balances for test loans | Borrowers paying stale amounts |
| EMIs in open mandate files are excluded | Double payment of one instalment |
| Old and new account formats both fetch | Fetch failures after migrations |
| Part and advance rules match product policy | Rejected or misallocated payments |
| Payment posts on confirmation with correct value date | Borrower wrongly shown overdue |
| Reversals unwind the posting | Loans closed on failed payments |
| Settlement credits match confirmations by reference | Hidden suspense balances |
| BBPS complaints reach the grievance queue | Missed complaint timelines |
How many EMI payments last month arrived without a loan reference you could use?
Talk to Our Software Development Specialists
Visit Digiqt to see how custom software can connect your loan system to BBPS cleanly.
How Much Can BBPS Biller Onboarding for Lenders Save?
BBPS biller onboarding mainly saves the time spent identifying payments made outside mandates. In this illustrative scenario, a lender receives 20,000 non-mandate EMI payments a month, 8% arrive without a usable loan reference, and each takes 20 minutes to trace and post.
Assume half of these payments move to BBPS, where the loan account number travels with the payment. These figures are assumptions, not benchmarks.
| Measure | Without BBPS | With BBPS for Half of Payments |
|---|---|---|
| Non-mandate payments a month | 20,000 | 20,000 |
| Payments needing manual tracing | 1,600 | 800 |
| Staff hours spent tracing | 533 | 267 |
| Borrowers wrongly shown overdue while tracing | Up to 1,600 | Up to 800 |
The lesson for leadership: the real gain is not staff hours but borrower trust. A borrower who paid on time and still gets a reminder call becomes a complaint, and sometimes a lost customer.
Where Does Custom Software Development Fit in BBPS Biller Onboarding for Lenders?
Digiqt's custom software development service covers user interface and user experience (UI/UX) design with wireframing and prototyping, web development, scalable and secure app development and quality assurance. Its technology categories include backend, frontend, database, DevOps and data engineering, delivered by a dedicated development team that starts with problem statement analysis.
For BBPS, that maps to three builds:
- A bill fetch service that reads live balances and payment rules from the loan system.
- A posting service that applies payments on confirmation and unwinds reversals.
- A reconciliation view that matches settlement credits to confirmations by BBPS reference number.
Quality assurance matters most during operating unit certification, where test cases cover fetch failures, timeouts and reversals. Test the build on your own loan data and product rules before go-live.
Digiqt's recurring payment intelligence AI agent shows how bill payment data can be analysed for recurring patterns.
Which Repayment Channel Fits Each Situation?
The right channel depends on how the borrower pays and why the mandate did not work.
| Borrower Situation | Recommended Approach |
|---|---|
| Mandate working normally | Keep the mandate; BBPS only for ad hoc payments |
| EMI bounced, borrower wants to pay now | BBPS fetch or a payment link |
| Cash-preferring rural borrower | Bharat Connect agent outlet, where available |
| Borrower wants to prepay or foreclose | BBPS only if foreclosure is enabled; else branch |
| Payment by unknown bank transfer | Exception queue and outreach to move to BBPS |
Which Metrics Show BBPS Biller Onboarding for Lenders Is Working?
Five metrics show whether BBPS biller onboarding is working: BBPS share, fetch success, fetch-to-pay conversion, auto-posting rate and complaint rate. Review them monthly by app and product.
| Metric | Formula | What a Weak Number Signals |
|---|---|---|
| BBPS share of non-mandate collections | BBPS payments ÷ non-mandate payments | Borrowers not told about BBPS |
| Fetch success rate | Successful fetches ÷ fetch requests | Wrong formats or service downtime |
| Fetch-to-pay conversion | Payments ÷ successful fetches | Confusing amounts or rules |
| Auto-posting rate | Payments posted without manual touch ÷ BBPS payments | Posting or matching gaps |
| Complaint rate | BBPS complaints per 10,000 transactions | Reversal or posting delays |
Fetch failures are often an uptime problem. Our guide to API monitoring for lending integrations shows how to watch them.
Which Mistakes Weaken BBPS Loan Repayments?
Four mistakes weaken BBPS loan repayments, and each is avoidable.
- Building fetch on a batch file. Borrowers pay amounts that are already wrong.
- Ignoring mandate overlap. One EMI is collected twice and refunds follow.
- Posting only on settlement. On-time borrowers look overdue for a day or more.
- Not telling borrowers BBPS exists. The channel stays live but unused.
What Is Changing Next?
UPI merchant pricing has changed. According to the Department of Financial Services and NPCI FAQs of 15 September 2026, person-to-merchant UPI payments above ₹2,000 carry a merchant discount rate (MDR) of 0.4%, capped at ₹300, from 15 October 2026, and merchants cannot pass it on to customers.
Many borrowers pay BBPS bills through UPI, and EMIs are usually above ₹2,000. Ask your operating unit how the new pricing flows into your BBPS charges before you plan channel economics for 2027.
Want borrowers to pay EMIs from any app without a reconciliation backlog?
Talk to Our Software Development Specialists
Visit Digiqt to see how custom software development can make BBPS loan repayments post and reconcile automatically.
Sources
- RBI: Master Direction – Bharat Bill Payment System Directions, 2024 (RBI/DPSS/2023-24/111, 29 February 2024)
- Bharat Connect: Loan Repayment
- TeamLease RegTech: NPCI Discontinues Unregulated Billers in BBPS Loan Repayment Category (March 2026)
- Department of Financial Services and NPCI: FAQs on MDR on Select UPI (P2M) Transactions (15 September 2026)
- Digiqt: Custom Software Development



