“Check whether it is on the RBI list” is the advice everyone gives and almost nobody completes, for a reason that is not laziness. There are two lists. They are built from different material, and they answer questions a borrower tends to run together into one.
One is a directory of apps. The other is a register of companies. Getting a straight answer out of either requires knowing which question you asked.
What each list is made of
The app-side directory exists because a rule requires it. The Reserve Bank of India (Digital Lending) Directions, 2025, issued on 8 May 2025, obliges regulated entities to report every digital lending app they deploy — their own and their lending service providers’ — to the Bank’s Centralised Information Management System, each app as a separate line item carrying its link, ownership details and grievance officer contact. The Directions state that the reported data is to be published on the Bank’s website in an automated manner, and, in the same breath, that the Bank does not verify or validate what is submitted. That is the whole character of the thing: a publication pipeline running off filings, not a vetting process. The resulting listing sits on the Bank’s data portal, linked from the RBI home page as “DLA’s deployed by Regulated Entities”.
The company-side list is older and duller. The Bank’s list of NBFCs and ARCs registered with the RBI is a downloadable file — Excel or PDF — carried alongside a second file of entities whose Certificate of Registration has been cancelled. As of this writing the registered list is stated as on 30 June 2026; the cancelled file is offered without any date at all. The page invites anyone who spots a discrepancy to write in by email.
The question each one actually answers
The directory answers: has any regulated lender admitted, on the record, that this app belongs to its lending chain? Narrow, but useful. The loan-app market’s central deception is a front with no lender behind it, and no regulated entity will have filed one.
The register answers a different question: does the company named in the fine print hold a Certificate of Registration, and has that certificate survived? The cancelled file matters more than borrowers realise. A company that once held registration and no longer does will still have an app store listing, a website and a well-drilled sales script.
Neither answers the question borrowers most want answered — whether this lender will behave — and no register anywhere does.
Where the pair breaks down
The failure mode is the join between them. An app in the directory is tied to the entity that reported it, but the name on the screen during onboarding is frequently a service provider’s brand, and the name on the sanction letter is the lender’s. A borrower who confirms the app and never reads the entity name has verified the packaging.
Names are the other friction. Trade names on app stores frequently differ from corporate names in a registration file, so the check often ends in an inconclusive search, not a finding. And absence proves less than it feels like it proves: an app missing from the directory is a strong reason to stop, but the honest reading is that no regulated entity has filed it, not that it was examined and rejected.
Verdict
The sequence, in the order that saves time: find the entity name in the app’s terms or its Key Fact Statement rather than on the marketing screens; search that name in the registered-NBFC file; then open the cancelled file and search it again. Only then look for the app in the directory. That order starts from the company that will hold the debt, the fact everything else hangs off.
None of this is financial advice, and this desk asserts nothing about any named app’s standing. The lists are the Bank’s, the reading of them is yours, and a registration claim made inside an app is no substitute for finding that entity in the regulator’s own records.