How to Verify an IFSC Code Before Transferring Money

Entering the wrong IFSC is one of the most common reasons NEFT, RTGS or IMPS transfers fail — or, in worse cases, land at the wrong branch. Salary credits, vendor payments and property deposits are too important to trust to an old WhatsApp forward. This guide is a verification workflow: how to confirm a code is valid, matches the intended branch, survived bank mergers, and what to do if money still goes astray.

If you need the basics of what an IFSC is, start with What is an IFSC Code?. This page focuses on verification before you hit Pay.

When verification matters most

• First-time payee (new vendor, landlord, builder, freelancers)
• High-value transfers (property token, business invoice, large personal remittance)
• Codes copied from email signatures, PDFs or chat — easy to mistype
• Accounts that moved after a bank merger or branch shift
• Salary account setup — wrong IFSC can delay the first payroll credit

For everyday UPI to a trusted UPI ID you already use, you usually do not enter IFSC. The risk rises whenever you type account number + IFSC manually.

30-second format check

Every valid IFSC in India follows one rigid pattern:

• Exactly 11 characters — no spaces, no dashes
• Characters 1–4: Letters only (bank code, e.g. SBIN, HDFC, ICIC)
• Character 5: Always the digit 0 (zero — not the letter O)
• Characters 6–11: Alphanumeric branch identifier

Example shape: HDFC0001234 (illustrative). If a code fails this pattern — 10 characters, a letter in position 5, or symbols — your bank’s payment system should reject it before the transfer starts. Fix format first, then verify branch identity.

Reliable sources ranked

Three verification methods

Method A — IFSCNOW lookup

1. Open the IFSCNOW homepage search.
2. Paste the full 11-character IFSC (or search by bank → state → city → branch).
3. Confirm bank name, branch name, city and address match what the recipient told you.
4. Copy the code carefully — watch zero vs letter O.

Method B — Cheque, passbook or net banking

1. Ask the recipient to open their passbook / cheque leaf / account summary screen.
2. Have them read the IFSC aloud character by character, or send a clear photo of the printed code (not a blurry screenshot of an old chat).
3. Match the branch name on that document to the branch name returned by your lookup.

Method C — Bank site / RBI list

1. Use the recipient bank’s official branch locator (URL from the bank’s homepage — not a random search ad).
2. Optionally cross-check against RBI’s published IFSC / branch reference files when you need an official audit trail.
3. If the bank site and the recipient’s passbook disagree, trust the passbook/net-banking entry and ask the recipient to clarify with their branch.

End-to-end workflow

1. Collect — IFSC from recipient’s latest official source.
2. Format-check — 11 characters, zero in position 5, uppercase.
3. Look up — IFSCNOW / bank locator / RBI list; match bank + branch + city.
4. Account↔branch — IFSC must belong to the branch holding the account, not “any” branch of that bank.
5. Test — for new payees, send ₹1 via IMPS (or a small NEFT). After successful credit, send the full amount.
6. Save safely — store the verified beneficiary inside your banking app; avoid retyping from chat next time.

0 vs O and other typing traps

• 0 (zero) vs O (letter): Position 5 must be zero. A letter O there is invalid.
• 1 vs I vs l: Read characters aloud; prefer copy-paste from a trusted source.
• Extra spaces: Trim spaces before and after the code.
• Old merger prefixes: VIJB, BKDN, ORBC and similar legacy codes may no longer be active — see below.
• Wrong bank, right city: A valid IFSC for “HDFC Andheri” does not help an ICICI account in Andheri.

Post-merger IFSC changes

Public-sector bank consolidations retired or remapped thousands of IFSC codes. Older cheque books may still show prefixes such as Vijaya Bank (VIJB), Dena Bank (BKDN) or Oriental Bank of Commerce (ORBC) that now belong under successor banks (for example, Bank of Baroda / Punjab National Bank mappings depending on the merger).

When verifying after a merger:

• Ask the recipient for an IFSC from a post-merger passbook or app screen
• Use the new bank’s branch locator, not the old bank’s retired site
• During transition windows both codes may briefly work — switch permanently to the new code
• If a lookup shows “branch closed / merged,” stop and get a fresh code before sending money

What happens if you use the wrong code

If money left your account but did not reach the intended person:

1. Call your bank immediately with the UTR / reference number, amount, date, wrong IFSC used, and the correct IFSC + account details.
2. Ask them to raise a recall / reverse request with the beneficiary bank.
3. Keep written ticket numbers. Speed matters — mule accounts empty quickly.
4. For suspected fraud (not a typo), also follow the steps in our digital banking fraud guide.

Pre-transfer checklist

• ☐ IFSC is 11 characters with 0 in position 5
• ☐ Bank name matches the recipient’s bank
• ☐ Branch name/city matches passbook or net banking
• ☐ Account number re-checked digit by digit
• ☐ Not relying only on an old chat/invoice
• ☐ ₹1 test done for first-time high-value payees
• ☐ Chosen the right rail (NEFT vs RTGS vs IMPS) for amount and urgency

Where IFSC usually appears (by document)

Layouts differ by bank. If you cannot find the code, search the bank’s help article for “IFSC on cheque” or visit the branch — do not guess from a similar nearby branch.

Case: first salary credit

New joiners often paste an IFSC from an old savings account or a friend’s tip. If payroll uses NEFT/RTGS with the wrong IFSC, the first salary can bounce or delay.

1. Open your salary account in the bank app and copy IFSC from the official account details screen
2. Confirm the account number (including leading zeros)
3. Submit the same pair to HR and keep a screenshot
4. Ask HR which rail they use (NEFT is common for payroll)
5. After the first credit, save the beneficiary details inside your own banking app for reimbursements

IFSC vs UPI — when you still need the code

UPI payments to a UPI ID skip IFSC entry. You still need a verified IFSC when:

• Adding a beneficiary with account number + IFSC in net banking
• Sending NEFT / RTGS / IMPS from branch or net banking forms
• Receiving wires that your bank maps via IFSC for the credit leg
• Sharing bank details on invoices, rent agreements or marketplace seller forms

If someone only sends a UPI ID for a large property payment, you can still ask for account + IFSC as a parallel confirmation — then verify the IFSC independently before sending via NEFT/RTGS.

Frequently Asked Questions

Can I verify an IFSC using just the account number?

No. You need the IFSC from the account holder or a branch lookup.

Does UPI require IFSC verification?

Not for normal UPI ID payments. Account-number + IFSC payee setup still needs a correct IFSC.

Is IFSC case-sensitive?

Use uppercase. Apps may accept lowercase, but capitals avoid 0/O confusion.

What if my transfer failed because of a wrong IFSC?

Invalid codes usually return funds in a few days. Wrong-account credits need an urgent bank-led reversal request with your UTR.

Are old Vijaya Bank or Dena Bank codes still valid?

Often not. Confirm the successor bank’s current IFSC from a fresh official source.

Should I trust an IFSC from a WhatsApp invoice?

Only after cross-checking passbook, net banking or an official lookup.