Santosh Rathore
I built and maintain ifscdesk.com. I am not a bank, a banker, or an adviser, and this site is not affiliated with the Reserve Bank of India, NPCI, Razorpay or any bank. What I do here is narrow: take the RBI's public branch list, publish it without guessing, and keep every release so a code that disappears can still be answered for.
What the site is built from
Every branch page comes from the RBI's consolidated branch list as published in Razorpay's open dataset. We have archived 135 releases of that file going back to February 2016 — 132 of them distinct once byte-identical rebuilds are removed — which is what makes it possible to say when a code was last valid instead of guessing that it still is. The method, including what we found wrong inside the source data, is set out on Data and method.
The rule everything else follows
If a field is empty in the source record, the page says it is empty. We never fill it in. That is why 31,400 retired codes carry no replacement here: we could derive one arithmetically for most of them, we tested that, and roughly one in ten of the derived codes pointed at a branch whose name did not match. So we require a second, independent signal before naming any successor, and every page that names one shows which signal was used.
Corrections this site publishes
The guides exist because the common answer to several of these questions is wrong or unsourced. Each of the following is argued from a primary source on the page that makes it:
- The fifth character of an IFSC is not documented anywhere by the RBI as "reserved for future use" — IFSC vs MICR vs SWIFT.
- MICR is not unique per branch: 522 codes in the current file are shared by more than one branch.
- A bank's merger date and the date its IFSC codes stopped working are not the same date, and the gap runs to more than a year — Old IFSC to new IFSC.
- Under the RBI's rules a NEFT or RTGS credit is released on the account number, not the name — what happens when you get one wrong.
Contact
If something on this site is wrong, tell me and I will fix it or say why I cannot: contact@ifscdesk.com. Corrections that come with a source get handled fastest. Site policies are on About, Privacy and Terms.