Name Mismatch Blocking Your Withdrawal? The Source Fix

The 30-second answer

A name mismatch blocks a gaming withdrawal because the payout runs a penny-drop name-match: it compares your KYC name against the account-holder name your bank holds, and a fuzzy score below roughly 80% parks or rejects the payout. “RAHUL K” versus “Rahul Kumar Sharma” is enough. Fix it at source, in order — bank to match PAN first, then Aadhaar (capped at two name changes for life) — and use the same account to deposit and withdraw.

This page is a spoke of the KYC & account-recovery hub — start there for the full account-block map, then return here for the name-specific fix.

Editor’s verdict, up front. Of all the silent reasons a real-money gaming withdrawal stalls, a name mismatch is the most common and the most misdiagnosed. Players read “pending” or “verification failed” and assume the app is stalling them, or worse, that it’s a scam. Most of the time it’s a string-comparison failure happening invisibly inside a bank-verification API the app calls before it pays. The app’s KYC name, your PAN, your Aadhaar, and your bank passbook are four separate records that drifted apart over years of forms filled slightly differently — and the payout rail needs at least two of them to line up before money moves. The good news: every one of those records has a defined, government-run correction path. The catch: you have to fix them in the right order, because correcting Aadhaar first when the real problem is the bank wastes one of your two lifetime Aadhaar name changes. This page maps the mismatch types, the verification that catches them, and the source-fix for each — with timelines, costs, and the official portals, all cited.

2026 reality you must read first. Two rule changes tighten the screws this year. From 1 April 2026, the CBDT requires PAN identity details to align exactly with Aadhaar records during verification, and individual PAN-modification requests now use the newly notified Form PAN CR-01 (ClearTax on the 2026 PAN-correction rules). Separately, the free-Aadhaar-update window on the myAadhaar portal ended 14 June 2025, after which document updates online carry a ₹25 fee and demographic changes like name still cost ₹50 at an enrolment centre (UIDAI update charges). So the cost of a name fix is small, but the PAN-Aadhaar alignment is now enforced, which means a mismatch you ignored last year can block both your tax record and your payout this year. Fix it once, properly, and it stays fixed.

What a “name mismatch” actually is — the four records that must agree

When a withdrawal is blocked “for name mismatch,” people picture a single wrong name. The reality is messier: there are four separate name records in play, and a withdrawal can fail if any two of them disagree. Naming them precisely is the whole game, because the fix depends on which two don’t match.

• Your gaming-app KYC name — the name you typed (or that was OCR-read from your uploaded PAN) when you completed in-app verification. This is what the app thinks your name is.
• Your PAN name — the name printed on your PAN card and held in the income-tax database. This is the anchor record, because the app must report 30% TDS against your PAN under Section 194BA, so the app’s KYC name is supposed to equal your PAN name exactly.
• Your Aadhaar name — the name in the UIDAI database. This matters because most app KYC and most bank KYC ultimately verify against Aadhaar, and because PAN and Aadhaar must now align under the 2026 rule.
• Your bank-account holder name — the name your bank holds for the account (or UPI handle) you’re withdrawing to. This is the one the payout actually pays, and the one most people never check, because they never see it written out.

A withdrawal pays money from the app to your bank. Before it does, it runs a check that compares the name it has on file for you against the name the bank has on file for that account. If those two strings don’t match closely enough, the payout stops. That’s it. Every “name mismatch” stall is one of six specific disagreements among those four records — and the next section names all six.

Why this is the single most common hard block

A name mismatch is not a rare edge case. It’s structural, for a reason that has nothing to do with you being careless. Your name was entered into four different systems, at four different times, by four different people, under four different formatting conventions. Your bank may have expanded your initials; your PAN may have abbreviated your middle name; your Aadhaar may carry your maiden name; the gaming app’s OCR may have dropped a space. None of those is “wrong” in isolation. The mismatch is an artefact of records drifting apart over a decade of forms — and it only surfaces the moment money tries to cross from one system to another. The deposit never triggered it (you were sending money in, no name-match needed). The withdrawal is the first time the systems are forced to agree.

For the broader picture of how a name mismatch fits alongside other KYC blocks — frozen accounts, rejected documents, duplicate-device flags — start at the KYC & account-recovery hub. This page goes deep on the name layer alone.

The six mismatch types — find yours before you fix anything

Diagnosing the type is 80% of the fix, because each type corrects in a different system. Read these six, identify which two records disagree, then jump to the matching source-fix later on the page. Do not start correcting anything until you know which type you have — fixing the wrong record is how players burn one of their two lifetime Aadhaar changes for nothing.

Type 1 — Initials vs full name (the most common by far)

What it looks like: your bank or UPI handle reads “R K SHARMA” or “RAHUL K”, but your PAN reads “Rahul Kumar Sharma.” South-Indian names are especially prone to this, where a father’s name or village name is carried as an expanded surname on one document and a single initial on another — “S. Karthik” on the bank account versus “Karthik Subramaniam” on PAN.

Why it blocks: the name-match algorithm compares character strings. “R K SHARMA” against “Rahul Kumar Sharma” can score well below the threshold because two-thirds of the full name is missing, even though a human reads them as the same person. The algorithm can’t safely expand “R” to “Rahul.”

Where to fix: usually the bank (expand the initials to match PAN), because changing your bank record is faster and has no lifetime cap, whereas your PAN is the anchor you want to keep stable.

Type 2 — Spelling variation

What it looks like: “Mohammed” vs “Mohammad” vs “Mohd”; “Lakshmi” vs “Laxmi”; “Saurabh” vs “Sourav”; a doubled letter, a dropped vowel, an anglicised transliteration of a regional-script name.

Why it blocks: even a single transposed or dropped letter drags the fuzzy-match score down. Transliteration variants are the worst, because the “correct” spelling genuinely differs across documents issued in different decades.

Where to fix: the document whose spelling is the outlier. If three records say “Mohammad” and the bank says “Mohammed,” fix the bank. If the app’s KYC OCR misread your PAN, re-submit KYC with a cleaner scan — that may be the only fix needed.

Type 3 — Married name vs maiden name

What it looks like: the account holder married, updated the bank account to the married surname, but the PAN or Aadhaar still carries the maiden name — or the reverse. “Priya Sharma” (maiden, on PAN) vs “Priya Verma” (married, on bank).

Why it blocks: the surnames are entirely different strings, so the match score collapses. This is one of the few cases where the names genuinely should differ until updated, which is why it needs a document-backed correction (a marriage certificate), not just a re-type.

Where to fix: align all four records to one surname. Most people move everything to the married name post-marriage; whichever you choose, the marriage certificate is the supporting document the bank and UIDAI require.

Type 4 — PAN vs Aadhaar divergence (now a hard 2026 block)

What it looks like: your PAN and Aadhaar names differ at all — initials, spelling, or order. Until recently this was tolerated for some flows; from 1 April 2026 the CBDT requires PAN to align with Aadhaar (ClearTax), and PAN-Aadhaar linking already fails on anything beyond a minor variation.

Why it blocks: if PAN and Aadhaar don’t agree, two things break at once — your PAN-Aadhaar link (which can render the PAN inoperative, and an inoperative PAN can block TDS reporting and therefore the payout) and the app’s verification against whichever record it uses. This is the type that, left unfixed, cascades into other problems.

Where to fix: the income-tax e-filing portal offers an Aadhaar-OTP-based correction to update the PAN name to match Aadhaar without physical documents, when the mismatch is minor (UIDAI PAN-Aadhaar FAQ). A complete divergence needs a full correction in one database.

Type 5 — Joint account / second-holder name

What it looks like: you’re withdrawing to a joint account where you’re the second holder, and the bank returns the primary holder’s name on the name-match check. Your KYC says “Rahul,” the bank returns “Suresh” (your father, the primary holder).

Why it blocks: the payout rail’s name-match typically resolves to the primary account holder’s name, not yours. If you’re not the primary holder, the names will never match no matter how clean your own records are.

Where to fix: this is not a name-correction problem — it’s an account-choice problem. Withdraw to an account where you are the sole or primary holder. No amount of editing your PAN fixes a joint-account second-holder mismatch.

Type 6 — App-KYC name vs everything (OCR / typo at signup)

What it looks like: all your official documents agree, but the gaming app’s stored KYC name is wrong — a typo you made at signup, or its OCR misread your uploaded PAN (“RAJ” read as “RAI”).

Why it blocks: the app compares its own (wrong) stored name against your correct bank name and fails. Your official records are fine; the app’s copy is corrupt.

Where to fix: inside the app — re-submit KYC with a clean, well-lit scan of your PAN, or raise a support ticket to correct the stored name. This is the only type fixed entirely without touching a government portal.

The six types in one line: Types 1, 2, 3 are real divergences across your official records (fix at the bank/UIDAI/PAN source). Type 4 is a PAN-Aadhaar problem that cascades (fix the link first). Type 5 is a wrong-account choice, not a name error (switch accounts). Type 6 is the app’s copy being wrong (re-submit KYC). Sort your case into one of these before spending a rupee on a correction, because three of the six don’t require a government correction at all.

How the check actually works: penny-drop name-match, step by step

Here’s the part most explainers skip — the mechanism that’s silently deciding your payout. When you request a withdrawal, the app doesn’t just blast money at your account number. It first verifies that the account is real, active, and held by you. It does that with a penny-drop name-match, and understanding the steps tells you exactly why your specific name is failing.

Step 1 — The penny drop

The verification system sends a tiny amount, typically ₹1, to your account number and IFSC, over NPCI’s IMPS rail (Noble Web Studio on bank-verification APIs). A successful ₹1 transfer proves two things at once: the account exists and is active, and — crucially — the bank returns the registered account-holder name in the transaction response. That returned name is the “ground truth” the system now has to reconcile against your KYC.

Step 2 — The name-match score

The system takes the bank-returned name and compares it against the name it holds for you (your KYC/PAN name), producing a fuzzy-match confidence score — an algorithmic percentage, not a yes/no (Karza/Perfios on name-match scoring). “Rahul Kumar” against “Rahul Kumar” scores ~100%. “Rahul Kumar” against “R K” scores far lower. The algorithm tolerates trivial differences (case, extra spaces, the odd punctuation mark) but penalises missing words, different surnames, and spelling drift.

Step 3 — The threshold decision

The score is bucketed against thresholds. Industry-standard tiers, drawn from how payee-name-matching systems are configured, run roughly like this (Optimus on fuzzy-match thresholds):

• High confidence (~95–100%): auto-approved, money moves.
• Medium (~85–94%): usually auto-approved, sometimes sampled for review.
• Low (~70–84%): routed to a human reviewer — this is your “pending for verification.”
• Below ~70%: typically rejected outright — this is your “name mismatch, withdrawal failed.”

An 80% similarity threshold is a commonly described regulatory-defensible setting for payment name-matching (Unit21 on ACH fuzzy-matching). So the practical takeaway: your payout doesn’t need a perfect name match, it needs to clear roughly 80%. A single dropped initial often still clears; a missing surname or a different surname usually doesn’t. That’s why “R K Sharma” vs “Rahul Kumar Sharma” sometimes passes and sometimes parks — it’s hovering near the threshold.

Step 4 — Penniless verification (the newer variant)

Some platforms now use penniless / penny-less verification, which retrieves the account-holder name without sending the ₹1, by querying the account directly (Bulkpe penniless-verification docs). The name-match logic in Step 2–3 is identical; only the “is the account live” probe changes. For you, the outcome is the same: a name-match score still decides whether your withdrawal flows.

The one number to remember: ~80%. Your name doesn’t have to be identical across systems — it has to be similar enough that the fuzzy-match score clears the platform’s threshold, which is commonly around 80%. That’s why the fix is rarely “make everything perfect” and usually “close the one gap dragging your score under the line” — most often a missing surname (Type 1) or a different surname (Type 3).

Why the algorithm can’t just “see” they’re the same person

A reasonable objection: a human glancing at “R K Sharma” and “Rahul Kumar Sharma” instantly reads them as one person, so why can’t the software? The answer matters, because it tells you what the algorithm can and cannot forgive — and therefore which mismatches you can safely ignore and which you must fix.

A name-match algorithm works on string similarity and phonetics, not on identity. It uses techniques like edit-distance (how many character changes turn one string into the other), token matching (treating each word as a unit), and phonetic encoding (so “Mohammed” and “Mohammad” sound alike) (Signzy on beneficiary name matching). What it deliberately cannot do is invent missing information. It cannot know that “R” stands for “Rahul” rather than “Rajesh” or “Ramesh” — expanding an initial is a guess, and a payment system that guesses is a payment system that misdirects money. So the algorithm penalises missing tokens hard, because a missing word is missing evidence, not a forgivable typo.

This produces a clear, usable rule of thumb for which mismatches clear and which don’t:

• Forgiven (small score hit, usually still clears): case differences, extra spaces, a single dropped or doubled letter on a long name, a missing period after an initial, a swapped first/last token order in some implementations.
• Penalised hard (usually drops below threshold): a missing full word (initial vs full name), a different surname (married/maiden), a transliteration variant that changes several letters, a name that’s substantially shorter on one side.
• Fatal (near-zero match): an entirely different name (joint-account second holder), or a name in a different script that wasn’t transliterated consistently.

The practical consequence: a single-letter spelling slip on “Subramaniam” might still clear, because one wrong letter in eleven is a 90%-ish match — but dropping “Kumar” entirely from “Rahul Kumar Sharma” removes a whole token and can crater the score. That’s why Type 1 (missing word) is both the most common block and one of the easier ones to predict: if a whole name-part is absent on one record, expect a failure and fix it before you even test.

The reason in one line: the algorithm matches strings, not identities, and it refuses to guess missing words — so a dropped letter is often forgiven, but a dropped name-part or a different surname is not. Knowing that lets you predict which of your records will fail before the payout ever runs.

The mismatch-source map: which record is wrong, and where to fix it

Before any correction, you need to know which of the four records is the outlier — because you fix the outlier, not the majority. Run this two-minute check.

1. Write out all four names exactly as they appear, character for character: your PAN card, your Aadhaar, your bank passbook/cheque, and (from the app’s KYC screen) your stored app name.
2. Find the majority. If three agree and one differs, the differing one is your outlier — fix that. If they split two-and-two, the PAN is your anchor: keep PAN as the target and bring the others to match it, because PAN is what the app reports TDS against.
3. Check PAN vs Aadhaar first. If those two disagree at all, that’s Type 4, and you fix that before anything else — it’s the cascade risk.

Here’s the source-of-truth and correction table. Treat the bank as the easiest and least risky to change (no lifetime cap, no tax consequence), Aadhaar as the most constrained (twice in a lifetime), and PAN as the anchor you change only to align with Aadhaar.

Sources for the table: bank name change is free and branch-based (HDFC change-of-name, SBI name-correction process); PAN fees and timelines (ClearTax PAN update guide); Aadhaar name change is centre-only and capped at two (UIDAI: how many times name can be updated, UIDAI update charges).

The correct order to fix your name — and why order matters

This is the part that saves you weeks and saves you a wasted Aadhaar change. Do not fix names in a random order. There’s a dependency chain, and getting it wrong means re-doing work.

The golden rule: bank first, Aadhaar last

Fix the bank before the government records, and fix Aadhaar only if you must. The reasoning:

• The bank is the record being paid, so if the bank name is the outlier, correcting just the bank to match your PAN can unblock the withdrawal with zero government paperwork. Always check whether the bank is the problem first, because it’s the cheapest, fastest fix with no lifetime cap.
• Aadhaar name changes are capped at two for life (UIDAI). Spend one carelessly and you may not have one left for a genuine future need (marriage, legal name change). So Aadhaar is the last lever you pull, only when Aadhaar itself is genuinely the outlier.
• PAN is the anchor. Because TDS reports against PAN, you generally keep PAN stable and bring other records to match it — unless PAN disagrees with Aadhaar, in which case the 2026 rule forces you to align PAN to Aadhaar.

The decision sequence, step by step

Follow this in order. Stop as soon as the withdrawal clears — you may not need every step.

1. Re-write all four names and find the outlier (the two-minute check above). This tells you which record to touch.
2. If the app’s KYC name is the outlier (Type 6) → re-submit KYC inside the app with a clean PAN scan, or raise a support ticket. Don’t touch any government record. Re-test the withdrawal.
3. If you’re withdrawing to a joint account where you’re the second holder (Type 5) → switch the withdrawal to an account where you’re the sole/primary holder. No correction needed. Re-test.
4. If the bank name is the outlier (Types 1, 2) → correct the bank record to match your PAN. Free, no cap. Re-test once it reflects.
5. If PAN and Aadhaar disagree (Type 4) → fix this before step 6. For a minor mismatch, use the free Aadhaar-OTP PAN-name update on the e-filing portal so PAN matches Aadhaar. For a major divergence, decide which is correct and correct the other.
6. If Aadhaar is genuinely the outlier (and you’ve confirmed it) → visit an enrolment centre with proof and update the Aadhaar name (₹50, one of your two lifetime changes). This is the last resort.
7. For a married/maiden surname (Type 3) → align everything to one surname using your marriage certificate as proof, working bank → PAN → Aadhaar in that order.

The order in one line: app-KYC → joint-account → bank → PAN/Aadhaar alignment → Aadhaar last. Most stuck withdrawals are solved by step 2, 3, or 4 — re-submitting KYC, switching accounts, or a free bank correction — without ever touching Aadhaar. Reach for the Aadhaar change only when you’ve proven Aadhaar is the wrong one, because you only get two for life.

Source-fix 1 — correcting your name on your bank account

The bank is the record the payout actually pays, and it’s the easiest to change: there’s no charge for a name correction and no lifetime limit (HDFC). Two routes exist.

Route A — branch (works at every bank)

This is the universal path, used when the name spelling is wrong, when initials need expanding, or after marriage.

1. Visit your home branch and ask the customer-service desk for the name correction / change form (at SBI this is a specific name-correction form; at most banks it’s part of the KYC-details-change form).
2. Fill in your current (wrong) name, the corrected name, and your account number.
3. Attach proof that supports the new name: your PAN card is the natural proof when the goal is “make the bank match my PAN,” plus Aadhaar; for a married-name change, attach the marriage certificate; for a legal name change, the gazette notification.
4. Submit and collect the acknowledgement slip. Processing typically takes a few working days (SBI process).

Route B — online (some banks, e.g. HDFC InstaServices)

A few banks let you do a minor correction online via Aadhaar e-KYC and Video KYC. HDFC’s InstaServices “Change of Name” flow asks for your Customer ID and DOB/PAN, sends an OTP to your registered mobile, and processes the change without a branch visit (HDFC InstaServices). Availability varies by bank, so check your bank’s app first; if it’s not there, use the branch route.

The faster sub-fix: just expand the initials

For Type 1 (initials vs full name), the cleanest fix is often not a “name change” at all but asking the bank to expand your initials to the full name on PAN, since that’s a correction to match your existing ID, not a new identity. “R K SHARMA” becomes “RAHUL KUMAR SHARMA” — and your name-match score jumps from sub-threshold to ~100%. Bring your PAN; the bank is correcting to a government ID, which they readily accept.

Bank-fix bottom line: it’s free, uncapped, and usually done in a few working days, and it’s the fix that resolves the largest share of name-mismatch withdrawals because the bank is so often the outlier that carries clipped initials or an old spelling. Always check the bank first — fixing it there avoids spending a scarce Aadhaar change.

Source-fix 2 — correcting your name on PAN (NSDL / UTIITSL)

PAN is your anchor record because the gaming app reports 30% TDS against it under Section 194BA, and from 1 April 2026 it must align with Aadhaar. You change PAN in one of two ways depending on how big the mismatch is.

The free route — Aadhaar-OTP update on the e-filing portal (minor mismatch)

If your PAN name only differs slightly from your Aadhaar name, the income-tax e-filing portal can update the PAN to match Aadhaar for free, with no physical documents, using an Aadhaar OTP (UIDAI PAN-Aadhaar FAQ). This is the path to use when the goal is Type 4 alignment and the difference is minor — it’s free and fast. The OTP goes to your Aadhaar-registered mobile, so that number must be live.

The paid route — full correction via Protean (NSDL) or UTIITSL

For a real name change (married name, a substantial spelling correction, or when you don’t want to match Aadhaar’s version), use one of the two government-authorised entities — Protean eGov (formerly NSDL e-Gov) or UTIITSL (ClearTax). From 1 April 2026, individual modification requests use the new Form PAN CR-01.

• Fees: ₹72 for an e-PAN delivered to email (no physical card), or about ₹107 for a physical card dispatched within India (ClearTax fee structure).
• Timeline: an e-PAN via Aadhaar e-KYC arrives in 2–3 working days; a physical card via online application with name correction takes about 15–20 working days.
• Proof: with Aadhaar e-KYC the process is largely documentless; otherwise you attach name proof and a supporting document for the change (marriage certificate, gazette, etc.).

The trap to avoid

Don’t correct your PAN to something that then disagrees with Aadhaar — under the 2026 rule that breaks your PAN-Aadhaar link and can render the PAN inoperative, which can in turn block TDS and your payout. Decide your single canonical name first, then move every record to it, with PAN and Aadhaar landing on identical text.

PAN-fix bottom line: if the mismatch is minor and you just need PAN to match Aadhaar, use the free e-filing OTP update. If it’s a genuine name change, budget ₹72–₹107 and 2–3 days for e-PAN (or 15–20 for a physical card), file the new Form PAN CR-01, and make sure the result is identical to your Aadhaar, not just close.

Source-fix 3 — correcting your name on Aadhaar (UIDAI)

Aadhaar is the most constrained record, so treat a name change here as a last resort. Two hard constraints govern it.

Constraint 1 — name is NOT editable online

You can update your address online on the myAadhaar portal, but name (like DOB and gender) must be updated in person at an Aadhaar enrolment centre / Seva Kendra — it cannot be changed through the online portal (Razorpay on Aadhaar update). So a name fix means a physical visit, supporting proof, biometric capture, and a ₹50 fee (UIDAI charges).

Constraint 2 — only twice in a lifetime

UIDAI allows a name update only twice in your entire lifetime (UIDAI FAQ). This covers both full name changes and significant spelling corrections. Once you’ve used both, further requests are normally rejected; the only recourse is an exception process through a UIDAI regional office — call 1947 or email UIDAI with your EID — and even that is not guaranteed (UIDAI on limit-exceeded). For comparison, DOB and gender are each editable once in a lifetime, while address has no limit.

How to do it (when you’ve confirmed Aadhaar is the outlier)

1. Book or walk in to an Aadhaar enrolment centre / Seva Kendra.
2. Carry proof of name — typically your PAN (if aligning Aadhaar to PAN), passport, or a gazette/marriage certificate for a legal change.
3. Pay ₹50 and give the biometric capture.
4. Track the update with the URN you’re given; the change reflects in a few working days, after which re-link PAN-Aadhaar if needed.

Aadhaar-fix bottom line: it’s ₹50, in-person only, and limited to two name changes for life — which is exactly why it’s the last step in the order. If you can solve the mismatch at the bank or with a free PAN-OTP alignment, do that and save your Aadhaar change for a future you can’t predict.

Source-fix 4 — correcting your name inside the gaming app

Sometimes every official record is fine and the only wrong copy is the app’s stored KYC name (Type 6). No government portal touches this. Two paths.

Re-submit KYC with a clean scan

Most apps store the KYC name from an OCR read of the PAN you uploaded. A blurry, angled, or low-light photo causes OCR errors — “RAJ” read as “RAI,” a dropped letter, a merged word. Re-submitting a flat, well-lit, full-frame scan of your PAN often lets the OCR re-read it correctly and overwrites the bad stored name with no further action.

Raise a support ticket to correct the stored name

If re-submission doesn’t fix it (some apps lock the name after first verification), raise an in-app ticket stating: “My KYC name is stored incorrectly as [WRONG]; my PAN reads [CORRECT]; please update so my withdrawal name-match passes.” Attach the PAN scan. Keep the ticket ID. For the full document-level KYC-rejection playbook — what counts as an acceptable document, why a re-upload gets rejected, how long review takes — see Teen Patti KYC rejected.

App-fix bottom line: if your PAN, Aadhaar, and bank all agree and only the app disagrees, the fix is inside the app, free, and needs no government paperwork — re-upload a clean PAN scan first, and escalate to a support ticket only if the name is locked.

Documents you’ll need for each correction — gather these first

Nothing slows a name fix more than reaching the counter without the right proof and being turned away. Here’s exactly what each record requires, so you walk in once and finish.

For a bank name correction

• The bank’s name-change / KYC-details-change form (collected at the branch, or downloaded).
• PAN card — the natural proof when your goal is “make the bank match my PAN,” since the bank is correcting to a government ID.
• Aadhaar as a secondary ID.
• For a married-name change: the marriage certificate.
• For a legal name change: the gazette notification of the change.
• A cancelled cheque or passbook to identify the account.

For a PAN name correction (paid route)

• The new Form PAN CR-01 (mandatory for individual modifications from 1 April 2026).
• Proof of identity, address, and DOB — Aadhaar covers all three and enables the largely documentless e-KYC route.
• A document supporting the name change if it’s a genuine change (marriage certificate, gazette).
• Your existing PAN number.
• For the free e-filing OTP route: just your Aadhaar number and access to your Aadhaar-registered mobile for the OTP — no documents at all.

For an Aadhaar name correction

• Proof of name in the new spelling — PAN, passport, or for a legal/married change the gazette or marriage certificate (UIDAI’s accepted-document list governs exactly what qualifies).
• In-person attendance for biometric re-capture (name can’t be done online).
• The ₹50 fee.
• Your existing Aadhaar / EID number.

For an app KYC re-submission

• A flat, well-lit, full-frame scan of your PAN (the source of the OCR read).
• Sometimes a selfie / liveness check the app prompts for.
• Your registered mobile number for the OTP.

Document bottom line: the marriage certificate unlocks every married-name change, PAN is the universal “match-to-this” proof for a bank or Aadhaar correction, and the free PAN-Aadhaar OTP route needs no documents at all — just a live Aadhaar-linked phone. Gather the one proof your specific correction needs before you go, and each fix is a single visit.

The realistic timeline: how long until the payout actually flows

Players want one number: “when will my money come?” There isn’t one — it depends on which record you fixed and how it’s verified. Here’s the honest end-to-end clock for each path, from “correction submitted” to “withdrawal clears.”

Two timing truths fall out of that table. First, the fastest fixes touch no government record — re-submitting app KYC, switching accounts, or routing the payout back to the deposit account can clear it the same day, which is why those are the first things to try. Second, the slowest path is a physical PAN card at 15–20 working days, so if you must correct PAN, choose the e-PAN (2–3 days) unless you specifically need the plastic. Don’t put your payout on the 3-week track when the 3-day track exists.

Timeline bottom line: a name-mismatch payout clears in anywhere from the same day (account switch / app re-KYC) to 2–3 weeks (physical PAN card) — and the difference is entirely which record you have to touch. Always try the same-day, no-government-record fixes first, and if you must correct PAN, take the e-PAN route, not the physical card.

What to do when a withdrawal is stuck purely on name mismatch

You’ve identified the type and you’re correcting at source — but you have money sitting in a stuck payout right now. Here’s the action sequence for the live withdrawal, run in parallel with the source-fix.

Step 1 — Confirm it’s actually a name mismatch (not something else)

A withdrawal can stall for limits, bonus-wagering, or a rail failure too. Confirm it’s name-specific:

• The failure/pending message references “verification,” “account verification,” “name,” or “beneficiary.”
• A small test withdrawal also fails the same way (rules out an amount/limit problem).
• Your deposit from the same account worked but the withdrawal won’t (deposits don’t run name-match; withdrawals do — a classic name-mismatch signature).

If the stall is about pending status generally rather than name specifically, the withdrawal-stuck fix maps every pending state and its wait-limit. If money was debited-but-not-credited on the rail, that’s a different problem with its own protections — see the withdrawal hub for the T+1 auto-reversal and ₹100/day rules.

Step 2 — Use the same account for deposit and withdrawal

The single most reliable unblock: withdraw to the exact account/UPI handle you deposited from. Many apps soft-trust an account that successfully funded the wallet, and forcing the payout back to that same instrument sidesteps a borderline name-match. If you deposited from a UPI handle whose name matches your KYC, withdraw there, not to a different bank account.

Step 3 — Switch to a clean-matching account

If your primary account carries the mismatch and you have a second account where your name matches your PAN cleanly (sole holder, full name, correct spelling), add it as the withdrawal method and re-test. This is faster than a correction and often instantly clears the payout while the source-fix processes in the background.

Step 4 — Raise the right ticket with the right words

When you contact support, name the mechanism — it routes you to the team that can actually act:

Subject: Withdrawal blocked on name-match — please advise required name

My withdrawal of ₹[AMOUNT] requested [DATE] is failing the
account name-match / verification check.
- KYC name (PAN): [EXACT PAN NAME]
- Bank account holder name: [EXACT BANK NAME]
- UPI ID / account used: [HANDLE / A/C]
Please confirm: (1) which name the payout is matching against,
(2) the exact name format you need on the receiving account,
and (3) whether I should switch to a sole-holder account that
matches my PAN. Ticket/reference ID please.

Asking the app which name it’s matching against is the highest-leverage question — it tells you whether to fix the bank, switch accounts, or re-submit KYC, instead of guessing.

Step 5 — Don’t make it worse

• Never open a second account to “get around” the block — duplicate-account flags freeze balances and are harder to clear than a name fix.
• Never deposit more “to verify” or “to unlock” — no legal app requires a deposit to release a withdrawal, and post-PROGA a fresh deposit into a money game is illegal anyway.
• Never share an OTP or UPI PIN with anyone who “calls to fix your KYC.” Legitimate verification never needs your PIN. For the broader account-block escalation map — frozen accounts, risk-review holds, written-reason demands — go to the KYC & account-recovery hub.

Live-payout bottom line: while your source-fix processes, the fastest practical unblock is route the withdrawal back to the same account you deposited from, or to a sole-holder account whose name matches your PAN — and ask support the one question that matters: which name are you matching against?

Worked examples — three real mismatch shapes, fixed end to end

Abstract rules are easy to nod at and hard to apply. Here are three concrete shapes with the exact fix path. None of these is a personal account — they’re constructed from the common patterns above to show the decision in motion.

Example 1 — the South-Indian initials case (Type 1)

Records: PAN reads “Karthik Subramaniam.” Bank reads “S KARTHIK.” Aadhaar reads “Karthik Subramaniam.” App KYC reads “Karthik Subramaniam” (matches PAN).

Diagnosis: the bank is the lone outlier — it carries the father-initial-prefix format “S KARTHIK” while three records agree on “Karthik Subramaniam.” Name-match score of “Karthik Subramaniam” vs “S KARTHIK” lands well under 80%, so the payout parks.

Fix: bank only. Visit the branch, ask to expand the name to match PAN → “KARTHIK SUBRAMANIAM,” attach PAN as proof. Free, ~a few working days. No Aadhaar change, no PAN change. Withdrawal clears once the bank record reflects.

Example 2 — the post-marriage surname case (Type 3)

Records: PAN reads “Priya Sharma” (maiden). Aadhaar reads “Priya Sharma” (maiden). Bank reads “Priya Verma” (updated to married name after opening a new account). App KYC reads “Priya Sharma.”

Diagnosis: the bank is the outlier for now, but the player wants to live under the married name “Verma” long-term. Different surnames = score collapse.

Fix (player’s choice to move everything to “Verma”):

1. Bank already says “Verma” — leave it.
2. PAN → correct to “Priya Verma” using the marriage certificate (₹72 e-PAN, 2–3 days), so TDS reports against the married name.
3. Aadhaar → update to “Priya Verma” at a centre with the marriage certificate (₹50, uses one lifetime change).
4. App KYC → re-submit with the new PAN so the app’s stored name becomes “Priya Verma.”

End state: all four read “Priya Verma,” PAN and Aadhaar identical (2026-compliant), withdrawal clears. The shortcut — if she only needed this one payout out fast — would be step 1’s reverse: temporarily withdraw to an account still in “Priya Sharma” matching her current PAN. But the durable fix aligns everything.

Example 3 — the OCR typo case (Type 6)

Records: PAN reads “Rajesh Nair.” Aadhaar reads “Rajesh Nair.” Bank reads “Rajesh Nair.” App KYC reads “Rajeshh Nair” (an extra “h” the OCR added from a blurry upload).

Diagnosis: every official record agrees; only the app’s stored copy is wrong. The app is matching its corrupt “Rajeshh Nair” against the bank’s correct “Rajesh Nair” and failing by one character — which is often enough to drop below threshold on a short name.

Fix: app only. Re-submit KYC with a sharp, flat PAN scan; the OCR re-reads “Rajesh Nair” and overwrites the typo. If the name is locked, a support ticket with the PAN attached corrects it. Zero government paperwork, zero cost. This is the case players most often over-fix — racing to “correct” their PAN when the PAN was never wrong.

The pattern across all three: find the outlier, fix only the outlier, and reach for Aadhaar only when it’s genuinely the wrong one. Two of these three cases needed no Aadhaar change at all, and the third used exactly one — by design.

Why the deposit worked but the withdrawal won’t — the asymmetry explained

A question that confuses almost everyone: “I funded my wallet from this exact account, so why won’t it pay back to the same account?” The answer is a structural asymmetry in how money moves, and understanding it kills the “the app is scamming me” suspicion.

When you deposit, you push money from your account into the app’s account. Your bank authenticates you (PIN/OTP), and the app simply receives funds — it does not run a name-match on the sender, because it doesn’t need to; the money arrived, that’s all that matters. Deposits are name-blind.

When you withdraw, the app pushes money to a beneficiary account, and now it’s legally and operationally on the hook to confirm that beneficiary is you — anti-money-laundering rules require that payouts go to the verified account holder, not a random third party. So the withdrawal runs the penny-drop name-match that the deposit never did. That’s the entire asymmetry: deposits don’t check the name; withdrawals must. The same account can therefore deposit flawlessly and fail to receive, purely because only one direction triggers the check.

This also explains why “withdraw to the same account you deposited from” helps but isn’t a guarantee — the deposit trust lowers the suspicion, but the withdrawal still runs its own name-match, and if your bank’s stored name is genuinely sub-threshold against your KYC, even the deposit-funded account can park the payout. The name-match is on the bank-held name, not on “did this account send us money before.”

The asymmetry in one line: a deposit authenticates you to your bank and is name-blind; a withdrawal must prove the beneficiary is you and so runs a name-match. Same account, two different checks — which is why depositing successfully never guarantees the payout flows.

The UPI-handle trap: the name behind your @upi is not the one you see

A subtle source of name mismatch lives inside your UPI handle, and most players never realise it’s there. When you pay to a UPI ID like rahul@oksbi, the name displayed in your app might be a nickname or an old label — but the name the rail matches against is the bank-held account name behind that handle, which can be different.

Three handle-specific traps recur:

• The handle resolves to a different account than you think. If you created the UPI ID on one bank and later made another your default, the payout may match against whichever account the handle currently points to — and its name may not be your clean PAN name.
• A third-party-app handle (PhonePe/GPay/Paytm wallet vs bank UPI). Some handles route to a wallet or a linked account whose registered name differs from your primary bank. The displayed sender name can be a profile nickname, while the legal account name behind it is what the match uses.
• A handle on a joint or family account. The same joint-account problem (Type 5) hides inside a UPI handle: if family@okhdfc sits on an account where you’re the second holder, the match resolves to the primary holder’s name, and your payout fails even though “the UPI worked for deposits.”

The fix is to withdraw to a handle whose underlying bank account is in your own name, matching your PAN — and if you’re unsure what name sits behind a handle, do a tiny test: have someone send you ₹1 and check the account-holder name their app displays on confirmation, because that displayed name is the bank-held name the payout will match. If it isn’t your full PAN name, that handle will block the payout no matter how clean your documents are. When a UPI withdrawal specifically is failing, the withdrawal-stuck fix covers the rail-side states; the name behind the handle is the piece to check here.

UPI-handle bottom line: the name your app shows for a handle is not necessarily the bank-held account name the payout matches against. Confirm the real account-holder name behind your handle (a ₹1 test reveals it), and only pay out to a handle whose underlying account is in your own PAN-matching name.

Why the name-match is mandatory — the AML reason you can’t argue around

It helps to know that the name-match isn’t the app being difficult; it’s the app obeying a rule it can’t waive. Indian real-money platforms operate under anti-money-laundering (AML) and KYC obligations that require payouts to go to a verified account belonging to the same person who holds the gaming account. A name-match is the operational proof of that “same person” requirement — it’s how the platform demonstrates, to its banking partners and regulators, that it didn’t pay winnings into a stranger’s account.

That’s why three “reasonable” requests will always be refused, and knowing this saves you from wasting days asking:

• “Just pay me anyway, I promise it’s my account.” The platform can’t override the match without breaking its own AML controls and risking its banking relationship. A verbal assurance isn’t verification.
• “Pay it to my friend’s / family member’s account instead.” A payout to a different person’s account is exactly what the rule exists to prevent — even if the money is genuinely yours, the beneficiary name won’t be you, so it can’t pass.
• “My deposit came from this account, so trust it for withdrawal.” Deposits don’t establish beneficiary identity (they’re name-blind), so a successful deposit isn’t the verification the withdrawal needs.

The flip side is the reassurance: because the match is a compliance control, not a discretionary hold, a clean name-match almost always releases the payout automatically. There’s no human deciding to keep your money — there’s a string comparison deciding whether the rule is satisfied. Fix the strings so they agree, and the control clears itself. For everything beyond the name layer — frozen accounts, written-reason demands, the full grievance escalation — the KYC & account-recovery hub maps the rest of the AML-driven verification chain.

AML bottom line: the name-match exists so winnings reach the verified player and no one else — which is why “pay me anyway” and “pay my relative” can never work. The upside: it’s an automatic compliance control, not a human holding your money, so aligning your names releases the payout without anyone’s discretion.

Common mistakes that turn a one-day fix into a one-month ordeal

The name-mismatch fix is genuinely simple when done in order. These are the avoidable detours that stretch it into weeks.

1. Fixing the anchor instead of the outlier. Players change their PAN when the bank was the lone wrong record. Now PAN is being re-issued for 2–3 days (or 15–20 for a physical card) and the bank still doesn’t match. Fix the outlier, found by the four-name comparison — usually the bank.
2. Burning an Aadhaar change you didn’t need. Updating Aadhaar to fix a bank-side mismatch wastes one of your two lifetime name changes. Once both are gone, future changes need a regional-office exception that may be refused. Aadhaar is the last lever.
3. Correcting PAN to something that breaks the Aadhaar link. Post-2026, PAN must match Aadhaar; “fixing” PAN to a third spelling makes the PAN inoperative, which can block TDS and the payout. PAN and Aadhaar must end identical.
4. Opening a second account to dodge the block. This triggers a duplicate-account / multi-device flag that freezes balances and is far harder to clear than a name correction. For what to do if you’re already flagged, see the KYC & account-recovery hub.
5. Depositing more “to unlock” the withdrawal. No legal app needs a deposit to release a payout, and post-PROGA a fresh money-game deposit is illegal. It’s the clearest scam-pattern tell.
6. Withdrawing to a joint account as the second holder. The match resolves to the primary holder’s name, so your records will never match. Use a sole/primary-holder account.
7. Re-submitting the same blurry PAN scan. If OCR mis-read your PAN once, the same bad photo re-reads the same way. Use a flat, well-lit, full-frame scan.
8. Not asking support which name it’s matching against. Guessing wastes days. The one question — which name are you matching to? — tells you exactly which record to fix.

The meta-mistake behind all eight: acting before diagnosing. Spend the two minutes to write out all four names and find the outlier, fix that one at source, keep PAN and Aadhaar identical, and the whole thing is a few-working-days job, not a month.

How to prevent name mismatches from ever blocking you again

Once you’ve cleared this, lock it shut so it never recurs across apps, banks, or future accounts.

• Pick one canonical name and standardise everything to it — same spelling, same expansion of initials, same surname across PAN, Aadhaar, bank, and every app KYC. The cheapest time to align records is before money is stuck in them.
• Keep PAN and Aadhaar character-for-character identical. The 2026 rule makes this mandatory anyway, and it removes the single most cascading mismatch type (Type 4).
• Always deposit and withdraw from a sole-holder account whose name matches your PAN. Never route a payout to a joint account where you’re the second holder.
• Use the same account for everything on a given app. One verified, name-matched account per app, used for both deposit and withdrawal, gives the cleanest trust signal.
• When you open any new bank account, give your full name exactly as on PAN — don’t let the form clip it to initials, which is how Type 1 mismatches are born.
• Re-check after any life event. Marriage, a legal name change, or a corrected document means re-aligning all four records before your next withdrawal, not after it stalls.

Prevention in one line: choose one canonical name, make PAN and Aadhaar identical, and only ever pay out to a sole-holder account that matches your PAN — do that once and the name-match check becomes a formality you’ll never notice again.

Is the correction worth it? A quick cost-benefit for small balances

One honest caveat before you spend time and money: not every stuck payout justifies every fix. If your blocked balance is ₹150 and the only path is a paid PAN correction plus a ₹50 Aadhaar change plus three branch visits, the effort can exceed the recovery — and that math should inform your choice.

Work the decision like this. First, exhaust the free, same-day moves regardless of balance size — re-submitting app KYC, switching to a sole-holder account, or routing the payout back to your deposit account cost nothing and often clear it. Reach for a paid government correction only when the stuck amount, plus the value of future payouts that the same mismatch would keep blocking, clearly beats the ₹50–₹107 in fees and the time. For most players the answer is “yes, fix it” — because the correction is a one-time cost that unblocks every future withdrawal across every app, not just this one payout. A ₹107 PAN fix that permanently clears your name-match is cheap if you’ll ever withdraw again. The only case where it isn’t worth it: a tiny one-off balance on an app you’ll never use again, where a free account-switch can’t reach it either.

Cost-benefit bottom line: always try the free, same-day fixes first, then weigh a ₹50–₹107 correction against all future blocked payouts, not just today’s — because a name fix is a one-time cost that unblocks every withdrawal you’ll ever make, which makes it worth it for almost everyone except a tiny, one-off, throwaway-app balance.

Related fixes (go deeper on your exact case)

This page is the name-mismatch spoke of the KYC cluster. For the adjacent problems:

• The full account-block map → KYC & account-recovery hub — frozen accounts, risk holds, the whole verification escalation in one place. Start here.
• KYC document rejected / re-upload failing → Teen Patti KYC rejected — the document-level fixes when a scan won’t pass.
• Withdrawal stuck / pending generally → withdrawal stuck fix — every pending state and its wait-limit, when it’s not specifically a name problem.
• The whole withdrawal picture → 3 Patti withdrawal hub — payout times, rails, TDS, the Day-0-to-30 escalation ladder, and the rail-failure protections.

FAQ

1. Why does a name mismatch block my withdrawal but not my deposit? Because a deposit is name-blind — your bank authenticates you and the app just receives funds — while a withdrawal must run a name-match to prove the beneficiary is you, under anti-money-laundering rules. The withdrawal runs a penny-drop check comparing your KYC name to the bank-held account name, and a fuzzy-match score below roughly 80% parks or rejects it. Same account, two different checks.

2. How does the name-match check actually work? The payout sends a ₹1 penny drop over NPCI’s IMPS rail (or uses penniless verification), and the bank returns your registered account-holder name. The system then scores that name against your KYC name as a fuzzy-match percentage: ~95–100% auto-approves, ~85–94% usually passes, ~70–84% goes to a human reviewer, and below ~70% is typically rejected. An 80% threshold is a commonly used setting.

3. My bank says “R K SHARMA” but my PAN says “Rahul Kumar Sharma” — is that the problem? Almost certainly, yes — this is the Type 1 initials mismatch, the single most common cause. “R K SHARMA” scores well under 80% against the full name. The fix is to ask your bank to expand the initials to your full PAN name (free, no lifetime cap, a few working days), not to change your PAN.

4. In what order should I fix my name across PAN, Aadhaar, and bank? App-KYC → joint-account check → bank → PAN/Aadhaar alignment → Aadhaar last. Fix the cheap, uncapped records first (the bank is free with no limit), keep PAN as your anchor, and only change Aadhaar as a last resort because it’s limited to two name changes for life.

5. How many times can I change my name on Aadhaar? Twice in your entire lifetime, per UIDAI — covering full changes and significant spelling corrections. After two, requests are normally rejected, and the only recourse is a regional-office exception (call 1947 with your EID), which isn’t guaranteed. DOB and gender are each changeable once; address has no limit.

6. Can I change my Aadhaar name online? No. Name, DOB, and gender must be updated in person at an Aadhaar enrolment centre / Seva Kendra for a ₹50 fee — only address is editable online on the myAadhaar portal. Carry name proof (PAN, passport, or a marriage certificate/gazette for a legal change).

7. What does it cost and how long does a PAN name correction take? About ₹72 for an e-PAN (emailed) or ₹107 for a physical card within India. An e-PAN via Aadhaar e-KYC arrives in 2–3 working days; a physical card takes ~15–20 working days. From 1 April 2026, individual corrections use the new Form PAN CR-01, and PAN must align exactly with Aadhaar.

8. My PAN and Aadhaar names are different — does that block my payout? It can, and from 1 April 2026 the CBDT requires them to match. A PAN-Aadhaar mismatch can break the link and render the PAN inoperative, which can block TDS reporting and therefore the withdrawal. For a minor mismatch, use the free Aadhaar-OTP PAN-name update on the income-tax e-filing portal; for a major one, correct one record so both end identical.

9. Does correcting my name on a bank account cost anything? No — banks do not charge for a name correction. The branch route works everywhere (form + PAN/marriage-certificate proof, a few working days), and some banks (e.g. HDFC InstaServices) offer an online change via Aadhaar e-KYC and Video KYC.

10. I’m withdrawing to a joint account and it keeps failing — why? Because the name-match usually resolves to the primary account holder’s name. If you’re the second holder, the names will never match no matter how clean your records are. The fix isn’t a name correction — withdraw to an account where you are the sole or primary holder.

11. All my documents are correct but the app still shows my name wrong — what now? That’s a Type 6 mismatch: only the app’s stored KYC name is wrong, usually from an OCR misread of a blurry PAN upload. Re-submit KYC with a flat, well-lit, full-frame PAN scan; if the name is locked, raise a support ticket with the PAN attached. No government correction needed.

12. What’s the fastest way to unblock a payout that’s stuck right now on name mismatch? Route the withdrawal back to the exact account you deposited from, or to a sole-holder account whose name matches your PAN, and ask support the one question that matters: which name are you matching against? Run this in parallel with the source-fix so you’re not idle while a correction processes.

13. Should I open a new account to get around the name mismatch? No. A second account commonly triggers a duplicate-account / multi-device flag that freezes balances and is much harder to clear than a name correction. Fix the existing record at source instead; if you’re already flagged, see the KYC & account-recovery hub.

14. The app says “deposit ₹X to verify your account and release the withdrawal” — is that real? No — it’s a scam pattern. No legal app requires a deposit to release a withdrawal, and post-PROGA a fresh deposit into a money game is illegal. Never deposit to unlock a payout, and never share an OTP or UPI PIN with anyone “calling to fix your KYC.”

15. After I fix my name, how do I make sure this never happens again? Standardise to one canonical name across PAN, Aadhaar, bank, and every app; keep PAN and Aadhaar character-for-character identical (2026-mandatory anyway); and only ever pay out to a sole-holder account that matches your PAN. When opening any new account, give your full name exactly as on PAN so the form doesn’t clip it to initials.

Sources & method. The mechanics, costs, timelines and legal rules on this page are built from primary and authoritative sources — not personal payout tests. Key references: NPCI penny-drop / name-match and penniless verification (Noble Web Studio, Karza/Perfios, Bulkpe); fuzzy-match thresholds (Optimus, Unit21); PAN correction fees, timelines and the 1 Apr 2026 Form PAN CR-01 / Aadhaar-alignment rule (ClearTax); PAN-Aadhaar name-mismatch resolution (UIDAI PAN-Aadhaar FAQ); Aadhaar name-update limit of two-in-a-lifetime, in-person requirement, and ₹50 / ₹25 fees (UIDAI update limits, UIDAI charges, Razorpay); bank name-correction process and zero charge (HDFC, SBI). This page is information, not legal or financial advice — verify each step against your operator’s current Terms, your bank’s policy, and the latest UIDAI/CBDT rules.