RBI tightens rules for payment aggregators to safeguard digital lending collections

India’s Reserve Bank introduces stricter guidelines for payment aggregators, emphasising clear operational boundaries to improve loan repayment processes and mitigate risks in digital lending.

Payment aggregators have become a standard part of India’s digital lending machinery, but their limits are increasingly important for lenders to understand. The Reserve Bank of India has drawn a clear regulatory line: payment aggregators may support loan repayment, but if they also act as loan service providers they cannot handle funds between lender and borrower. That distinction matters because it defines what these platforms are built to do, and what they are not. The latest master directions on payment aggregators, issued in September 2025, also tightened the wider framework around authorisation, governance, escrow accounts and reporting. According to legal and industry summaries of those rules, the regulatory environment is now more explicit, but not more forgiving of blurred operational roles.

For many non-banking financial companies and fintech lenders, the issue is not whether a payment aggregator can process a transaction. It usually can. The more difficult question is what happens when a scheduled debit fails, a borrower misses an EMI or a mandate needs to be repaired before the account slips further into arrears. The aggregation layer is designed to move money efficiently at the point of payment. It is not, by itself, a collections engine. That gap is where lenders can lose recovery momentum, particularly in the early days of delinquency, when fast intervention is often the difference between a brief miss and a harder-to-recover overdue account.

Industry commentary around the RBI’s digital lending rules has repeatedly highlighted this boundary. Payment aggregators are allowed to facilitate repayments, but they are not meant to become a substitute for a lender’s own collections workflow. The Economic Times reported in 2023 that the central bank had clarified that aggregators acting as loan service providers cannot intermediate funds between lenders and borrowers, while Moneycontrol noted that repayment support is permitted only within the Digital Lending Guidelines. In other words, the rail can exist, but it does not remove the lender’s responsibility to manage mandates, notifications and escalation processes.

That operational layer is where recurring collections either hold together or start to fray. A lender collecting through UPI Autopay or eNACH needs more than registration and settlement. It needs ongoing monitoring of mandate health, a way to distinguish a temporary failure from a structural one, and a workflow that routes each missed debit into the right response. Without that, a retriable rejection can be treated like a permanent breakdown, or an expiring mandate can be missed until after the payment has already failed. For portfolios with scale, those small distinctions have financial consequences and compliance implications.

The larger lesson is that payment aggregation and collections orchestration are different jobs. As the RBI has made clear, regulated entities must keep the money flow direct and transparent, while the surrounding process must still be designed well enough to support compliant lending operations. For lenders, that means the real question is not whether their payment aggregator is functioning, but whether the rest of their collections stack is built to do the work the aggregator was never meant to cover. The firms that understand that division are better placed to recover more, reduce avoidable follow-up and maintain the documentation their auditors and partners expect.