India's banking sector went through a major consolidation wave in recent years, with the government merging several public sector banks into larger entities. For customers, the visible effect was often a straightforward name change on their passbook — but behind the scenes, IFSC codes for merged branches frequently changed too, and that detail catches a lot of people off guard during transfers.
Why mergers affect IFSC codes at all
An IFSC code's first four characters identify the bank itself. When Bank A merges into Bank B, branches that previously operated under Bank A's IFSC prefix are typically migrated to Bank B's prefix over time, since Bank A ceases to exist as an independent institution. The branch itself doesn't move — only its code and reporting bank identity change.
Major mergers and what changed
The State Bank of India merger absorbed several associate banks (State Bank of Bikaner & Jaipur, State Bank of Mysore, State Bank of Travancore, and others) into SBI directly, consolidating their separate IFSC prefixes under SBIN. Punjab National Bank absorbed Oriental Bank of Commerce and United Bank of India, with those banks' branches gradually transitioning to PUNB-prefixed codes. Canara Bank absorbed Syndicate Bank, moving Syndicate's branches to CNRB-prefixed codes over the transition period.
Why old IFSC codes sometimes still work
To avoid disrupting standing instructions, ECS mandates, and recurring transfers set up under old codes, RBI and the merged banks often maintained backward-compatible routing for a transition window, letting old codes continue working temporarily even after the official code changed. This transition period isn't indefinite, though, and relying on an outdated code becomes riskier the further out from the merger date you are.
How to find your branch's current, correct IFSC code
Rather than trusting an old passbook or a saved payee's stored details, search your bank and branch name directly on an IFSC finder to confirm the currently valid code. If your bank went through a merger and you're not sure which post-merger name applies, searching by your original branch's city and name usually surfaces the updated record under the new parent bank.
What to do if a transfer fails due to an old IFSC code
If a transfer bounces because of an outdated IFSC code, the fix is simply updating the payee's saved bank details with the current code — no need to open a new account or re-verify KYC, since the underlying account itself hasn't changed, only its routing identifier.
Should you update saved payees proactively?
If you regularly send money to accounts held at banks that went through a merger, proactively updating those saved payee details with current IFSC codes avoids a failed-transfer surprise at an inconvenient moment, particularly for time-sensitive payments like rent or EMIs.