KYC rejection reasons, and the fixes

Updated 16 August 2026 · 12 min read · Written and reviewed by the DematOpen team

The plain answer

KYC rejections are mismatches, not verdicts. The verification compares your application against your PAN, Aadhaar and bank records, and every rejection traces to a difference between them: a name spelled two ways, a signature that does not match, an address that changed, or a mobile number not linked to Aadhaar. Each has a specific fix, and after the fix the same application passes.

The frame matters because most people treat a rejection as a relationship problem with the broker and respond by trying another one. The checks run the same everywhere, because the rules run the same everywhere. The correct response is always: identify the mismatch, fix the record, reapply.

What the KYC check actually compares

To fix a rejection you need to know what the verifier sees. When you submit, the application runs a chain of comparisons:

  • PAN against Income Tax records. Returns your name as recorded for tax purposes.
  • Aadhaar against UIDAI or DigiLocker. Returns your name, date of birth and address as seeded to the number.
  • Bank account through penny drop. Returns the account holder name.
  • KRA records. Your KYC file with the KYC Registration Agency, such as CVL KRA, CAMS KRA or NDML, carries a status: KYC Validated, KYC Registered or KYC On-Hold.
  • CKYC records. The Central KYC registry has kept a 14-digit CKYC number for every investor since 2016, keyed to your PAN and identity documents.

A rejection means one of those comparisons returned a difference. Nothing in the chain evaluates whether you are a good customer or a credit risk; it only asks whether the records agree about who you are. That is why the fixes in the sections below are all record corrections, not apologies or explanations.

Name mismatches

The most common rejection by far. The name on PAN, the name on Aadhaar and the name typed on the form must read the same, letter for letter. Initials, expanded initials, a married surname, or a spelling difference between documents all fail the automated comparison.

The comparison is literal, which trips people in predictable ways. A PAN that says “R. Kumar” against an Aadhaar that says “Ramesh Kumar” fails. A middle name present in one record and absent in the other fails. Even an extra space or a swapped “S/O” field can fail, though the common cases are the visible ones.

  • The fix: pick one canonical name and correct the documents to it. Updating Aadhaar is the usual route, since PAN details can also be corrected through the Income Tax department’s PAN service channels. Correct both, not one, so the next comparison reads identically everywhere.
  • The check: download your KYC status from the KRA and compare every name field against your PAN and Aadhaar before reapplying. The KRA record shows the exact string on file, which is the string the comparison will use.

A name change after marriage is the same problem with a paperwork step: update Aadhaar first with the new name and the marriage certificate, then correct the PAN to match, then apply. Half-updated records are the classic cause of the second rejection.

Signature problems

The signature you photograph during the flow becomes the reference signature for the account. Rejections happen when the signature is cropped, illegible, or so different from the bank’s record signature that the comparison fails.

The fix is behavioural, not documentary. Sign on a plain white sheet with a dark pen, in the same style as your bank records, and frame the full signature in the camera with no shadow across it. Do not abbreviate it on the day of application: the signature you give is the one every future instruction will be compared against, so give your usual one, not a rushed squiggle.

The bank comparison is the one people forget. Your bank holds the signature from its own account opening, and a radically different signature now looks like a different person signing. If your bank signature is ancient, update it at the bank first, then match it during the application.

Address differences

The address on the form should match the address on one of the submitted documents, usually Aadhaar. A recent move that is not yet reflected in Aadhaar is the classic cause. The e-KYC pulls your address from the Aadhaar record, so what you type and what the database returns must agree.

Update Aadhaar first; the address update is digital and takes days, not weeks. Then apply with the new address everywhere. A mismatch between the current address and every document is not a small detail; it is a verification failure, and typing the new address into the form does not help when the Aadhaar record still carries the old one.

Two nuances worth knowing. First, spellings of the same address, such as “Street” versus “St.” or different pin code groupings, can fail the comparison even when the location is obvious to a human. Second, the intermediary may send a KYC completion intimation letter by post when your stated address differs from the OVD, which is a paper trail to respond to, not a fresh rejection.

The Aadhaar-mobile linkage

The OTP for verification goes to the mobile number registered with Aadhaar, not to your current SIM unless they are the same. An unlinked or stale mobile stalls the application at the first OTP, which reads as a rejection even though no document failed.

The fix is the Aadhaar mobile update, done at an enrolment centre or online where the UIDAI portal allows it, before the application, not during. The update takes time to propagate, so budget for it: the pattern of applying, failing at OTP, updating Aadhaar, and reapplying is a week lost that a five-minute check would have saved.

The rest of the list

ReasonWhat happensThe fix
Poor document photosDetails unreadable in the uploadRetake in daylight, flat, full frame
Expired or damaged documentsVerification cannot completeRenew the document first
Bank account name mismatchFunds verification failsUse an account in the same name as PAN
Duplicate applicationA pending or active application existsResume or close the old application first
Video KYC session droppedThe recording is incompleteRedo the call with a stable connection

The duplicate application row deserves attention, because it is the one rejection that has nothing to do with documents. Starting a new application while an old one still sits pending at the same broker creates two records for one person, and the system rejects the second as a duplicate. Resume or formally close the first attempt before starting again.

Before you reapply: the sequence that works

A reapplication with unchanged records produces the same rejection, because the comparison runs identically. The sequence that actually converts a rejection into an approval:

  • Get the exact reason. Ask support for the rejection code or the specific mismatch. Guesswork sends you to the wrong fix.
  • Pull your KRA record. Check your KYC status and the name and address fields on file at CVL KRA, CAMS KRA or NDML with your PAN.
  • Correct the source document. Aadhaar for name, address and mobile; PAN for the tax-side name; the bank for the signature and holder name.
  • Verify the fix propagated. Wait for the updated document to reflect the change, and for Aadhaar updates to settle, before spending the application.
  • Reapply with the same broker. The check runs the same way everywhere, so the broker that rejected you will approve you once the records align, and your half-built file there is reusable.

The whole loop takes days, mostly waiting for record updates to propagate. The people who loop it multiple times are the ones who reapply without waiting for the propagation, so the old record answers the new application.

What people usually get wrong

A rejection means the broker does not want me

Rejections are automated comparisons failing, not business decisions. The same application passes once the documents align.

I should try a different broker after a rejection

The KYC checks are the same at every broker, because the rules are the same. A mismatch that failed one verification fails them all.

Reapplying quickly fixes it

Speed changes nothing; the comparison runs identically. Only fixing the underlying document mismatch changes the outcome.

A rejection is recorded against my name permanently

Nothing is recorded. A rejection does not touch your KRA record, your CKYC record or your credit report, and other intermediaries cannot see it.

Questions people ask

The broker communicates the specific reason, by email or in the app. If the message is vague, support can pull the exact rejection code for your application. KYC rejections are not mysterious: every one maps to a document mismatch, and this page lists the common ones with fixes.

There is no mandated waiting period. Fix the underlying mismatch first, then reapply immediately. Reapplying without fixing the mismatch produces the same rejection, because the check is the same.

No. Name mismatches are fixed by correcting the document itself, typically Aadhaar, so that all records read the same name. The fix is administrative, not a black mark. Your KYC record stays usable once the records align.

No. A KYC rejection is a failed verification, not a penalty. It does not appear in credit reports, and other intermediaries cannot see it. Fix and reapply.

Enter your PAN on any KRA website, such as CVL KRA, CAMS KRA or NDML, and download your KYC status. The record shows a KYC Validated, KYC Registered or KYC On-Hold status, plus the name and address fields on file. Comparing those fields against your PAN and Aadhaar tells you exactly which mismatch remains before you spend another application.

The name mismatch, then the Aadhaar mobile linkage, then the address. The name fails the most comparisons because it appears in PAN, Aadhaar, bank and KRA records at once. The mobile blocks the very first OTP. Everything else, signatures and photo quality included, is lower cost to fix afterwards.

Sources