PAN Aadhaar name mismatch? Fix KYC rejections without running office to office

PAN Aadhaar name mismatch and KYC rejection repair desk

Quick answer. Do not randomly change Aadhaar, PAN, passport and bank records one by one. First decide which record is the “source of truth” for the transaction that failed. Then correct only the record that is blocking the workflow, save proof, and escalate with a written grievance. Use RTI only when a public authority is holding the record or refusing to tell you the reason.

  • 1. Identify the failed gate: PAN-Aadhaar link, bank KYC, mutual fund KYC, DigiLocker, passport, voter ID or job background verification.
  • 2. Match exact fields: name, date of birth, gender, father's name, initials, spacing, expanded surname and mobile-linked Aadhaar.
  • 3. Fix the right database: PAN, Aadhaar, issuer database, bank/KRA, passport file or state certificate record.
  • 4. Keep proof: screenshots, acknowledgement numbers, rejected email, old and corrected document.

Why this article exists

The same citizen problem appears in many forms:

  • PAN-Aadhaar linking fails because one record has initials and the other has the expanded name.
  • Mutual fund KYC is rejected even after PAN and Aadhaar look correct.
  • DigiLocker says “name mismatch” or “no record found” for PAN, marksheet, driving licence or certificate.
  • Passport police verification or RPO processing gets held because father's name, surname or address proof differs.
  • Bank, broker, wallet, insurer or employer background verification rejects a perfectly genuine person because their databases compare fields too strictly.

RTI Wiki already has separate guides for these situations. This page is the bridge between them: one repair map, with links to the deeper article when your case needs detail.

First decide: spelling problem or database problem?

What failed Usually means Start here
PAN-Aadhaar link failed PAN and Aadhaar demographics do not match exactly, or fee/link status is pending PAN-Aadhaar linking guide · PAN inoperative fix
Mutual fund KYC rejected KRA has old address/name/PAN-Aadhaar status or needs fresh OVD/video KYC Mutual fund KYC rejected guide
DigiLocker cannot fetch PAN, marksheet or certificate Source issuer database does not match Aadhaar, or issuer API is failing DigiLocker issuer reality · DigiLocker documents not showing
Passport file on hold RPO/police verification needs address, name, father's name or adverse-report clarification Passport police verification delayed
Bank/broker/wallet KYC failed Private platform is comparing PAN, Aadhaar XML, CKYC or KRA data Use grievance first; RTI only if a public authority record is involved
Government certificate rejected State issuer record is old, misspelled, not digitised or not pushed to DigiLocker RTI the issuing department after portal grievance

The 20-minute repair flow

  • Minute 0-5: take screenshots. Save the exact rejection message. Do not close the page before capturing the error code, application number and timestamp.
  • Minute 5-10: compare documents line by line. PAN, Aadhaar, passport, marksheet and bank KYC should be compared for name order, initials, father's name, DOB and gender.
  • Minute 10-15: choose the correction target. If PAN-Aadhaar linking failed, fix PAN or Aadhaar. If DigiLocker failed, fix the issuer database. If mutual fund KYC failed, fix KRA/AMC records.
  • Minute 15-20: file a written grievance. Use the portal first. If the portal gives no reason or no movement, escalate with RTI only where the holder is a public authority.

Which record should you correct first?

Do not assume Aadhaar is always the record to change. In many cases, Aadhaar is only the authentication key. The failed system may be comparing against PAN, school board records, passport file, KRA data, EPFO, state revenue records or an old bank profile.

  • For tax, PAN-Aadhaar and broker onboarding: make PAN and Aadhaar match first.
  • For DigiLocker: correct the issuing department's record. DigiLocker cannot repair a wrong issuer database.
  • For passport: preserve legal-name continuity. If school certificate, Aadhaar and PAN differ, prepare a short explanation and supporting proof before the RPO asks.
  • For mutual funds: update KRA status through CAMS, KFintech, CVL KRA or the AMC route.
  • For banks: ask for the exact rejection reason in writing. “KYC failed” is not enough.

South Indian initials, expanded surnames and father's name mismatch

Many automated KYC systems are weak at Indian naming patterns. They treat “R Ravi”, “Ravi R”, “Ravi Raman” and “Raman Ravi” as different people even when the documents clearly refer to the same person.

Use this practical rule:

  • If the mismatch blocks PAN-Aadhaar, make the names match exactly in PAN and Aadhaar.
  • If the mismatch blocks passport, follow Passport Seva/RPO requirements and carry supporting documents.
  • If the mismatch blocks job or private KYC, ask for manual verification and submit a self-declaration with both documents.
  • If the mismatch is in a government certificate, correct the certificate at source or RTI the issuing department for the record basis.

When RTI helps, and when it does not

RTI is powerful when the record is with a public authority. It is weak when the dispute is only with a private bank, broker, wallet, AMC, employer or app.

Use RTI for:

  • UIDAI, Income Tax/PAN public records, passport/RPO file movement, state certificate issuer, school board, municipal certificate, EPFO or government department.
  • Asking for file status, correction-request status, reasons for rejection, copy of internal note, pending officer name, and timeline under citizen charter/SOP.

Do not start with RTI for:

  • A private app's internal KYC rule, private employer BGV, private AMC back-office delay, or wallet onboarding failure.

For private entities, use written grievance first, then regulator/ombudsman route where available. For mutual funds, start with the KRA/AMC correction flow and SEBI SCORES if ignored.

RTI questions you can ask a public authority

Subject: Request for information regarding rejection / mismatch in [PAN / Aadhaar / DigiLocker / passport / certificate] record

Under Section 6(1) of the Right to Information Act, 2005, I request the following information:

1. The present status of my correction / verification / application request bearing acknowledgement number [number].
2. The exact reason recorded for rejection, mismatch, hold or non-fetch of my record.
3. The name/designation of the office or database from which the mismatch was detected.
4. The list of documents required to correct the mismatch.
5. The maximum time prescribed by rule, SOP, citizen charter or office instruction for deciding such correction requests.
6. A copy of the relevant rule, SOP, circular or office instruction used to process such correction requests.
7. The date on which my request was received by the concerned section and the date on which it was last acted upon.

Use the AI RTI Drafter if you want the above converted into a cleaner authority-specific draft. If the PIO rejects or ignores the request, move to the First Appeal Builder.

Common mistakes

  • Changing Aadhaar just because one app failed. Sometimes PAN, KRA or issuer data is the real problem.
  • Retrying DigiLocker for weeks when the issuer database itself is wrong.
  • Creating a new bank/broker/mutual-fund account instead of fixing KRA status.
  • Sending original documents by courier without acknowledgement.
  • Relying on phone calls. Written grievance numbers matter.
  • Filing RTI to a private company instead of the public authority that holds the source record.

FAQ

Should I change PAN or Aadhaar first?

Change the record that is wrong for the failed workflow. If PAN-Aadhaar linking is the failed workflow, both records must match exactly. If DigiLocker cannot fetch a marksheet, the school board database is usually the correction point.

Can RTI force DigiLocker to show my document?

Usually no. DigiLocker fetches from the issuer. RTI the issuer for why your record is missing, not DigiLocker alone.

My private bank says KYC failed. Can I file RTI?

Not to a private bank under RTI. Ask the bank for the exact reason in writing, then use its grievance channel and regulator route. Use RTI only if the bank is a public authority or the mismatch is in a government record.

Is a small spelling difference serious?

For human review, often no. For automated KYC, yes. A missing middle name, expanded initial, swapped first/last name or DOB format issue can block onboarding.

What is the safest first step?

Save the rejection screenshot and compare the exact fields across PAN, Aadhaar, passport, bank/KRA and issuer records. Do not make blind corrections.

Reader signal

Was this article useful?

Tap once if it helped you. These counters show other citizens which pages are worth reading.

- views