PAN Verification for Gaming: Why It Blocks Your Withdrawal & the Fix

The 30-second answer

Before any legal Indian real-money gaming app pays you a single rupee, your PAN has to pass verification. The reason is tax: the app must deduct 30% TDS on net winnings and report it against your PAN under Section 194BA, so an unverified or mismatched PAN means it legally cannot release your money. A withdrawal blocks at this gate for one of a few boring, fixable reasons — your PAN is inoperative because it isn’t linked to Aadhaar, the name or date of birth on your PAN doesn’t match your bank account or Aadhaar, or the system flags a duplicate PAN. Each has a specific repair. Fix the right one, re-submit, and the payout clears. This page maps every PAN failure mode and the exact fix, with the primary rules behind each number. For the broader KYC picture, start at the KYC and account-recovery hub.

Editor’s verdict, up front. “PAN not verified” is the single most under-explained reason a first gaming withdrawal stalls, and players almost always misread it as the app stealing their money. It usually isn’t. It’s a data-matching failure between three records that were never required to agree before — your PAN, your Aadhaar, and your bank account. The app’s verification engine checks all three against the Income Tax Department’s database, and any one mismatch parks the payout. The trap most people fall into is the inoperative PAN: a PAN that looks perfectly valid in your wallet but is switched off in the tax system because you never linked it to Aadhaar. That state triggers both a KYC failure and a 20% higher TDS rate. This guide tells you which of your three records is broken, and the exact, dated procedure to fix each.

2026 context you must read first. The legal ground under Indian real-money gaming shifted hard in 2025. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) received Presidential assent on 22 August 2025 and the operating Rules came into force on 1 May 2026. Many of India’s biggest cash operators suspended their real-money formats. If you’re reading this in mid-2026, your task is often no longer “verify my PAN on a live app” but “get my stranded balance out of a wind-down” — and PAN verification still gates that recovery, because the operator must still attribute any 194BA TDS to your PAN before it releases the balance. Never deposit again “to unlock” a withdrawal; a new deposit into a money game is now illegal. The PAN fixes below apply identically whether your app is still live or winding down.

Why PAN is mandatory before any gaming payout

Players treat PAN as a formality — a card you upload once and forget. In gaming KYC it is the opposite of a formality. It is the legal hinge the entire payout depends on, and there are two separate laws forcing it.

Reason 1 — Tax attribution under Section 194BA

Since 1 April 2023, every legal online real-money gaming app in India must deduct TDS at 30% on a player’s net winnings, with no minimum threshold — the old ₹10,000 floor is gone. This is Section 194BA of the Income-tax Act, introduced by the Finance Act 2023. The tax doesn’t vanish into the operator’s pocket: the operator files quarterly TDS returns linked to your PAN and issues you a Form 16A TDS certificate, and the deducted amount appears against your PAN in Form 26AS / the Annual Information Statement (AIS) so you can claim credit when you file your return (Section 194BA mechanics confirmed here).

Read that chain backwards and the necessity of PAN becomes obvious. The operator has to report a number against a specific PAN. If your PAN is missing, wrong, or fails verification, there is no valid identity to attribute the tax to — so the operator legally cannot complete the payout-with-deduction. That is why the app enforces PAN at the cash-out, not at the deposit: the deposit creates no tax event, but the withdrawal does. A blocked “PAN not verified” withdrawal is, underneath, a blocked tax report.

Reason 2 — Anti-money-laundering obligations (PMLA)

The second force is the Prevention of Money Laundering Act (PMLA) and the broader KYC/AML framework that financial-adjacent businesses operate under. A platform paying real cash to users has to know who it is paying — a verified, government-issued identity tied to a real bank account — to satisfy AML and customer-due-diligence expectations and to keep its payment-aggregator relationships intact (PMLA’s role in legal gaming KYC noted here). PAN is the spine of that identity check in India because it’s the one document that ties directly into the tax and financial system. So even setting tax aside, a real-money operator cannot responsibly pay an unverified person without breaching its own AML posture.

Money laundering through gaming works by cycling cash in as deposits and out as “winnings” to launder its origin, so the AML regime leans hard on knowing the real, verified identity behind every payout. PAN is what makes that identity traceable end to end — it links the player to the tax system, the bank account, and the reported TDS. An operator that pays an unverified or mismatched PAN effectively creates an untraceable payout, which is precisely the gap AML rules exist to close. That’s why the verification is strict and why “close enough” on a name or DOB isn’t accepted: a fuzzy identity defeats the entire purpose of the check. From your side it feels like bureaucratic friction; from the regulator’s side it’s the difference between a clean payment and an unattributable one.

What that means for you, practically

You can’t argue your way around PAN verification, because the operator isn’t being difficult — it’s discharging two legal duties at once. So the productive move is never “demand they skip PAN.” It’s “find out which part of my PAN verification failed and fix exactly that.” The rest of this page is that diagnosis. For the document-by-document KYC view across PAN, Aadhaar, and bank proof, the KYC and account-recovery hub is the parent page; this spoke goes deep on the PAN layer specifically.

The one-line reason PAN is non-negotiable: the app must report 30% net-winnings TDS against your PAN under Section 194BA and satisfy PMLA identity checks. No verified PAN means no valid tax report and no AML-clean payee — so the payout cannot legally complete. This is enforcement of law, not the app withholding your cash.

How PAN verification actually works inside gaming KYC

Most players never see what happens after they upload a PAN image. Understanding it tells you exactly why a verification fails, because the failure is almost always at one specific checkpoint.

When you submit your PAN to a gaming app, the app (or its KYC vendor) doesn’t just eyeball the photo. It runs your PAN number, name, and date of birth against the Income Tax Department’s authoritative database through a PAN verification API. The two official rails for this are Protean eGov Technologies (formerly NSDL) and UTIITSL — the same two entities that issue and service PAN cards. To use the API, a business registers with Protean, signs its JSON requests with a Class 2/3 digital signature certificate, and posts to the production endpoint (Protean’s documented Online PAN Verification endpoint is https://opvapi.egov-nsdl.com/TIN/PanInquiryAPIBackEnd), at a published cost of ₹12,000 + 18% GST per year for up to 750 verifications/day (Protean OPV integration details).

What the API returns — the four signals that decide your fate

The verification response is not a simple yes/no. Protean’s PAN Lite response returns four distinct fields, and each one can independently block you:

1. PAN status — is the PAN valid and operative, or inoperative (the Aadhaar-linking trap, covered in depth below)?
2. Name match — does the name you entered match the name on the PAN record? Returned as Y (match), N (no match), or null (unavailable).
3. DOB match — does your date of birth match the PAN record? Same Y / N / null values.
4. Aadhaar seeding status — is this PAN linked to an Aadhaar?

The match values matter because the app’s logic reads them. A response of name-match N or DOB-match N, or a PAN-status of inoperative, is exactly what flips your withdrawal from “approved” to “verification pending / failed.” The verification “cross-references in real time to confirm validity,” which is why a single wrong character is enough to fail it (PAN Lite Y/N/null behaviour described here).

Why this design produces “silent” failures

Here’s the practical consequence that traps players. The API gives the operator a precise reason code — name N, DOB N, inoperative, etc. But the operator’s app often shows you only a generic “PAN verification failed” or “KYC pending.” You’re left guessing which of the four signals broke. So the skill is reverse-engineering the precise failure from your own records, which is exactly what the diagnostic below does. If your app instead returned a flat “KYC rejected” with no PAN detail, the Teen Patti KYC-rejected fix walks the broader rejection tree; come back here once you’ve narrowed it to PAN.

The mechanism in one line: the app pushes your PAN + name + DOB to Protean/UTIITSL, which returns PAN status, name-match (Y/N/null), DOB-match (Y/N/null), and Aadhaar-seeding status. Any one of those four going the wrong way blocks the payout — but the app usually hides which one from you. Diagnosing the specific field is the whole game.

The numbers: what a verified vs inoperative PAN does to your payout

Abstract rules don’t land until you see them in rupees, so here are three worked examples. They use round figures to show exactly how PAN status changes what reaches your bank. The 30% TDS comes from Section 194BA; the 20% floor comes from Section 206AA when a PAN is inoperative.

Example A — verified, operative PAN (the clean case)

You deposit ₹10,000, play, and your withdrawable winnings reach ₹25,000. You withdraw ₹25,000 with net winnings of ₹15,000 for the year.

• TDS at 30% on ₹15,000 = ₹4,500.
• The app pays ₹25,000 − ₹4,500 = ₹20,500 to your bank.
• The ₹4,500 is reported against your PAN in Form 26AS/AIS and is creditable when you file.

Your bank shows ₹20,500 arriving; the “missing” ₹4,500 isn’t lost, it’s parked as tax you can reclaim. This is the outcome you want — and it only happens when your PAN verifies cleanly.

Example B — inoperative PAN (the punitive case)

Same numbers, but your PAN is inoperative because you never linked Aadhaar. Two things go wrong at once:

• The withdrawal may not release at all, because the verification fails (you can’t even get to the payout).
• Where a deduction does happen against an inoperative PAN, Section 206AA treats it as “no valid PAN” and forces the higher of the normal rate or 20%. The normal gaming rate is already 30%, but the broader effect of 206AA is that an inoperative PAN is the worst possible state to deduct against — and any lower-rate situations get bumped to the 20% floor.

The honest summary: an inoperative PAN is “lose-lose.” Best case, the payout is blocked until you fix it. Worst case, money that does move is taxed at the no-PAN rate, and you’re chasing a refund through your ITR instead of having it credited cleanly.

Example C — the year-end deduction nobody expects

Suppose you withdrew nothing all year but ended 31 March with ₹15,000 of net winnings still in the wallet. Under the 194BA mechanism, the app must deduct ₹4,500 TDS on that year-end balance even though you never cashed out — and it must report it against your PAN. If your PAN went inoperative in the meantime, that year-end deduction also runs into the 206AA problem. This is why keeping your PAN operative matters even when you’re not actively withdrawing: the tax event can fire at year-end on its own.

The numbers in one line: a verified, operative PAN gets you taxed cleanly at 30% with the cut reclaimable. An inoperative PAN either blocks the payout or forces deduction at the punitive 20% 206AA floor — and the year-end 194BA deduction can fire even if you never withdraw. Verified PAN isn’t just about getting paid; it’s about being taxed the right amount.

Run the diagnostic first: which PAN signal is failing?

Before you fix anything, narrow your failure to one of the four signals. Work through these in order; the first “yes” is very likely your culprit.

If none of these is wrong and the payout is still stuck, your problem is probably downstream of PAN — at the bank or the payment rail — and the 3 Patti withdrawal hub covers the rail-side escalation. But in practice, the overwhelming majority of “PAN not verified” gaming blocks are #1 or #2 above.

The single most useful first action: check whether your PAN is operative, because the inoperative-PAN state is both the most common cause and the one with the nastiest side effect (a 20% higher TDS rate). That’s the next section, and it’s the heart of this page.

The inoperative-PAN trap (the one that catches everyone)

This is the failure mode that almost nobody understands until it bites them, so read it carefully. Your PAN can be 100% valid, correctly spelled, and still completely block your gaming withdrawal — because it has gone inoperative.

What “inoperative” means

An inoperative PAN is a PAN that is technically still allotted to you but has been switched off in the tax system because it was not linked to your Aadhaar by the deadline. The PAN number still exists; it just stops functioning for tax and KYC purposes. When the gaming app’s verification API queries it, the PAN status comes back as inoperative, and that is a hard fail at the verification gate (inoperative-PAN definition).

The reason this catches people is that nothing visibly changes on the card. You can hold a physical PAN card, read every digit perfectly, and have it be inoperative without any outward sign. The only way to know is to check the status (procedure below). Players who don’t know this concept exists will resubmit the same correct PAN ten times and watch it fail ten times, because the problem isn’t the image — it’s the back-end status.

The two specific consequences that hit a gamer

An inoperative PAN does two distinct bad things to your payout, and you need to understand both:

Consequence 1 — KYC / verification fails outright. An inoperative PAN cannot pass the gaming app’s verification, full stop. Beyond gaming, an inoperative PAN means you “will not be able to file income tax returns, receive tax refunds, or carry out any transaction where quoting of PAN is mandatory,” and it specifically causes “difficulties in completing KYC processes” (consequences listed here). A gaming withdrawal is exactly such a PAN-mandatory transaction.

Consequence 2 — 20% higher TDS under Section 206AA. This is the one that costs you real money even after you fix the KYC. Under Section 206AA of the Income-tax Act, if the deductee’s PAN is inoperative, the deductor must deduct TDS at the higher of the normal rate or 20% (Section 206AA higher-rate rule). For gaming the normal 194BA rate is already 30%, so the practical bite shows up across the financial system: an inoperative PAN is treated as “no valid PAN,” and the 20% floor under 206AA applies to TDS that would otherwise be lower. The CBDT itself frames an inoperative PAN as triggering “higher tax deductions at source (TDS)” among other penalties. So an inoperative PAN doesn’t just block you — where it does pay, it can pay you less, because tax is grabbed at the punitive no-PAN rate.

A real relief window worth knowing (don’t over-pay)

There is genuine, documented relief that protects you from being penalised for the operator’s deduction. The CBDT Circular No. 9/2025, dated 21 July 2025 grants relief where a PAN was inoperative at the time of a payment but is subsequently made operative by linking Aadhaar. For payments made between 1 April 2024 and 31 July 2025, the deductor isn’t held liable for the higher 206AA/206CC rate if the PAN is made operative on or before 30 September 2025. An earlier Circular No. 6/2024 gave a similar grace for earlier periods. The lesson for you: linking your Aadhaar promptly doesn’t only unblock the KYC — within the relief windows it can also undo the punitive higher-rate exposure. So the fix below is doubly worth doing fast.

A second inoperative deadline that traps a newer group

There’s a quieter version of this trap that hit a specific group of PAN holders. The CBDT directed that individuals who obtained their PAN using an Aadhaar enrolment ID (rather than the actual Aadhaar number) — for PANs issued before 1 October 2024 — must complete Aadhaar-PAN linking by 31 December 2025, or their PAN goes inoperative from 1 January 2026 (enrolment-ID deadline). If you got your PAN this way and didn’t act, your card could be freshly inoperative in 2026 even if you “linked Aadhaar” once before. The tell is the same — the Verify PAN Status check — and the fix is the same linking flow. The point: inoperative status isn’t a one-time event from years ago; new waves of it keep arriving as deadlines pass, so check status now rather than assuming a past link still holds.

How to check whether your PAN is operative (free, 3 minutes)

Don’t guess. Confirm. The Income Tax Department gives you a free status check:

1. Go to the Income Tax e-filing portal homepage.
2. In Quick Links, click “Verify PAN Status” (some builds label it “Link Aadhaar Status”).
3. Enter your PAN, full name, date of birth, and mobile number, then Continue.
4. Enter the 6-digit OTP sent to your mobile (valid 15 minutes, 3 attempts) and Validate.
5. The result tells you whether your PAN is operative or inoperative — and whether it’s linked to Aadhaar (official Verify-PAN process).

If it says operative and Aadhaar-linked, this isn’t your problem — go back to the diagnostic and check name/DOB matching. If it says inoperative, you’ve found your block, and the fix is the next section.

The inoperative-PAN trap in one line: a perfectly valid PAN that isn’t Aadhaar-linked goes inoperative, which fails gaming KYC and exposes you to the 20% TDS floor under Section 206AA. Nothing on the card shows it — you must check the status on the e-filing portal. Linking Aadhaar fixes both, and within the CBDT 9/2025 relief window it can also reverse the higher-rate hit.

Fix: link your PAN to Aadhaar (the ₹1,000 fee, the steps, the timeline)

If your PAN is inoperative, the only fix is to link it to your Aadhaar, which now costs a ₹1,000 fee because the free deadline has long passed. Here is the precise, current procedure.

Step 0 — Make sure your PAN and Aadhaar agree first

Linking will fail if the name, gender, and date of birth on your PAN and Aadhaar don’t match — even a single-letter difference or a changed name order can stop it (demographic-match requirement). So before you pay the fee, confirm your two records match. If they don’t, fix the mismatch first (see the name/DOB section below), or you’ll pay ₹1,000 and still fail.

Step 1 — Pay the ₹1,000 fee (Challan ITNS 280, the exact heads)

The fee to make an inoperative PAN operative is ₹1,000, paid as Challan No. ITNS 280 with Major head 0021 (Income Tax Other than Companies) and Minor head 500 (Other Receipts), through the e-Pay Tax flow (official fee/challan details):

1. On the e-filing portal, go to e-Pay Tax.
2. Enter your PAN, confirm it, and a mobile number for OTP.
3. After OTP, proceed on the Income Tax tile.
4. Select the relevant Assessment Year and Type of Payment = Other Receipts (500).
5. Pay ₹1,000 via your bank. A challan is generated.

Getting the Minor head 500 right matters — pay it under the wrong head and the system won’t recognise the payment when you try to link.

Step 2 — Wait, then submit the linking request

Payments made at NSDL/Protean take a few days to reflect on the e-filing site, so you’re advised to submit the actual PAN–Aadhaar linkage request 4–5 days after paying (timing note). Then, on the e-filing portal’s Link Aadhaar page, enter your PAN and Aadhaar and submit. If there’s only a minor name mismatch in your Aadhaar data, an Aadhaar OTP to your Aadhaar-registered mobile can confirm it; your date of birth must be identical on both for the link to finalise.

Step 3 — Reactivation timeline

After a successful linking request, your PAN moves from inoperative to operative in roughly 7 to 30 days — the commonly cited window is “operative after 30 days of applying,” and many cases clear in about a week (reactivation timeline). Re-run the Verify PAN Status check until it reads operative, then re-submit your gaming KYC. Submitting the gaming verification before the status actually flips will just fail again.

The one-page version of this fix

• Cost: ₹1,000 (ITNS 280, Major head 0021, Minor head 500).
• Pre-requisite: PAN and Aadhaar name/DOB must match — fix that first if not.
• Wait: ~4–5 days after paying before submitting the link request.
• Reactivation: ~7–30 days; verify status before re-doing gaming KYC.
• Bonus: within the CBDT 9/2025 relief window, linking can also undo the 206AA 20% higher-rate exposure.

Reality check on timelines: this is not a same-day fix. Between the ₹1,000 payment settling, the link request, and reactivation, budget one to four weeks before your gaming withdrawal can clear. That’s frustrating mid-withdrawal, but it’s also why checking PAN status before you ever try to cash out is the smartest move you can make. Do it the day you complete KYC, not the day you want your money.

PAN name and DOB mismatch (the second most common block)

If your PAN is operative but verification still fails, the culprit is almost always a mismatch — and there are two different mismatches that look identical from the outside but have different fixes. Diagnosing which one you have is half the battle.

Mismatch type A — PAN name vs bank account name

The gaming app needs three records to agree: your PAN, the name on your bank account / UPI handle that will receive the money, and (often) your Aadhaar. The most common single stall on a first gaming withdrawal is the name on your bank/UPI not matching the name on your PAN. Your PAN reads “Rahul Kumar Sharma,” your bank reads “Rahul K Sharma,” and the risk engine can’t auto-reconcile them, so it parks the payout for manual review.

Fix: make your bank account holder name match your PAN exactly, and use the same account for the withdrawal that you used for any deposit. If the difference is in the bank’s record (an abbreviation, a dropped middle name), you correct it with the bank, not the app — the app can’t override your bank’s name field. This is the most common silent stall and the cheapest to fix, because a bank name update is usually free and fast. The dedicated walkthrough for the name-on-account problem is the Aadhaar name-mismatch withdrawal fix, which covers the bank/Aadhaar/PAN three-way reconciliation step by step.

Mismatch type B — PAN vs Aadhaar demographic mismatch

The second mismatch is between your PAN and your Aadhaar themselves. This one is more serious, because it doesn’t just fail the gaming check — it blocks the Aadhaar linking you may need to make your PAN operative in the first place. To link (and to pass most KYC), your name, gender, and date of birth must match across both documents, and the system is strict: “even small differences like a single letter, an extra initial or a change in name order can cause the linking to fail” (demographic-match rule).

There are two tiers of this:

• Minor mismatch (a spelling nuance, an initial): often resolvable via an Aadhaar OTP to your registered mobile during linking, with no document change needed.
• Major mismatch (the names are substantively different): the linking fails outright, and you’re prompted to change the name in either Aadhaar or PAN so the two agree.

How to correct each record

You fix the mismatch at the source record that’s wrong:

• To correct your Aadhaar (name/DOB): use the UIDAI Self-Service Update Portal or visit an Aadhaar Seva Kendra. A minor spelling correction can go through on OTP; a major change may need a Gazette notification or affidavit. UIDAI allows a name update only twice in a lifetime, so don’t waste it. Turnaround is roughly 5–7 working days (Aadhaar correction process).
• To correct your PAN (name/DOB): apply on the Protean (NSDL) or UTIITSL website using the “Request for New PAN Card Or/And Changes or Correction in PAN Data” form, attach your updated ID proof, and pay a small fee (around ₹110–₹200). A reissued PAN typically arrives in 10–15 working days (PAN correction process).

Which one do you change? Change the record that’s actually wrong. If your PAN has a typo, fix the PAN. If your Aadhaar has the old spelling, fix the Aadhaar. If neither is “wrong” but they simply differ in format (full name vs initials), the path of least resistance is usually the one that’s easier to update and that also matches your bank — because ultimately all three need to line up for the gaming payout to clear.

The DOB trap specifically

Date of birth is the quiet killer here. The DOB must be identical across PAN and Aadhaar for linking to finalise, and a DOB-match N from the PAN verification API is a flat fail with no OTP workaround. A surprisingly common cause: an Aadhaar that records only a year of birth (no day/month) where the PAN has a full date, or a transposed day/month. If your name matches but verification still fails, check the DOB on all three records digit by digit before anything else.

The mismatch rule in one line: gaming verification needs your PAN, bank account, and Aadhaar names + DOB to agree exactly. A bank-vs-PAN name gap is fixed at your bank; a PAN-vs-Aadhaar gap is fixed by correcting whichever source record is wrong (Aadhaar via UIDAI, PAN via Protean/UTIITSL). DOB must be identical everywhere — it has no OTP shortcut.

Duplicate PAN (the flag that freezes everything)

A rarer but more alarming PAN block is the duplicate-PAN flag. If the gaming app’s verification or your bank’s systems detect that more than one PAN is associated with your identity, the payout can freeze pending review — and unlike a name typo, this one carries a legal penalty you need to clear properly.

Why people end up with two PANs

Almost nobody applies for a second PAN on purpose. It happens by accident: an online application gets rejected, the person re-applies offline, and both eventually get issued. Or someone applies fresh after marriage (name change) instead of updating the existing card. The result is the same — two valid PANs tied to one person, which the law expressly forbids.

The law: one person, one PAN

Under Section 139A of the Income-tax Act, an individual may hold only one PAN, and the section “expressly prohibits anyone who has already been assigned a PAN from making a fresh application, acquiring, or holding an additional permanent account number.” Holding more than one can attract a penalty of up to ₹10,000 under Section 272B, levied at the Assessing Officer’s discretion based on intent (multiple-PAN penalty rule).

Why it specifically breaks a gaming payout

A duplicate-PAN situation is poison for a 194BA payout because it breaks tax attribution. The operator has to report your TDS against one PAN, but the system sees two identities for one person — so the verification can’t cleanly resolve “who” is being paid, and the anti-fraud layer treats two PANs on one account (or one PAN across two accounts) as a multi-accounting / identity-anomaly signal. The honest read: a duplicate PAN looks, to an automated risk engine, a lot like fraud, even when it’s an innocent paperwork accident.

The fix: surrender the extra PAN

You keep one PAN — ideally the one already linked to your Aadhaar, bank, and the gaming account — and surrender the duplicate:

1. File the “Request for New PAN Card Or/And Changes or Correction in PAN Data” form (Form 49A) on the Protean/UTIITSL portal, or do it offline at a PAN Service Centre.
2. In that form, mention the duplicate PAN you wish to surrender in the dedicated field.
3. Submit; the duplicate is cancelled while your retained PAN stays active (surrender procedure).

Be ready for scrutiny: the Assessing Officer may examine the incomes and taxes filed against the surrendered PAN and ask you to explain the duplication. Keep it clean — surrender, don’t just ignore the extra card, because an un-surrendered duplicate keeps tripping the same flag every time you cash out.

Duplicate PAN in one line: the law allows one PAN per person (Section 139A), with a ₹10,000 penalty under Section 272B for holding more. Two PANs break 194BA tax attribution and look like fraud to a risk engine, so payouts freeze. The fix is to surrender the duplicate via the Protean/UTIITSL correction form and keep the Aadhaar-linked one.

Special situations that break PAN verification differently

The standard fixes above cover most players, but four specific life situations create PAN-verification problems with their own twists. If one of these is you, read the matching note before you waste time on the general diagnostic.

Name change after marriage

A very common cause of PAN trouble for women: the name on PAN, Aadhaar, and the bank account drift apart after marriage because they were updated at different times (or not at all). Your bank account might carry your married name, your PAN your maiden name, and your Aadhaar something in between. The gaming verification then fails on a name-match N, and Aadhaar linking can fail too. The fix is to pick one canonical name and update all three records to it — PAN via Protean/UTIITSL, Aadhaar via UIDAI (remembering the twice-in-a-lifetime name-change cap), and the bank account at your branch. Use the same name everywhere, and the three-way match clears.

Minors and the “first PAN” question

A real-money gaming account must belong to an adult with a PAN — this isn’t a verification quirk, it’s a hard eligibility rule, since the tax and AML framework assumes a legally responsible adult. If an account was opened in a minor’s name or with a parent’s PAN against a child’s identity, the verification and the 194BA tax attribution can’t reconcile, and the payout will stall on an identity that “doesn’t fit.” There’s no clever fix here: the account holder, the PAN, and the bank account must all be the same adult. Trying to route a minor’s winnings through a parent’s PAN is exactly the kind of mismatch that freezes a payout and can flag the account.

NRIs and PAN

A Non-Resident Indian can hold a PAN, but NRI status adds wrinkles: the Aadhaar-linking requirement is structured differently for those not eligible for Aadhaar, and the bank account used (NRO/NRE) must still match the PAN name. If you’re an NRI hitting a PAN-verification wall on a gaming withdrawal, the likely issues are an Aadhaar-seeding gap or an NRO/NRE account name that doesn’t reconcile with the PAN. Confirm your PAN’s operative status first (the same e-filing check works), then check the receiving-account name against the PAN. The deeper legality question — whether you can even play from abroad post-PROGA — sits outside this page; this section only addresses the PAN-verification mechanics.

A reissued or recently-corrected PAN

If you just corrected your PAN (a name or DOB fix) or it was recently reissued, give the change time to propagate before re-attempting gaming KYC. A PAN correction takes roughly 10–15 working days to reflect in the issuing database, and the verification API reads that database — so a correction you made yesterday won’t pass a check today. Re-run the Verify PAN Status check, confirm your new details show, and only then re-submit. The same lag applies after Aadhaar linking: the status flip isn’t instant. Acting on a “fixed” record before the back-end actually updates is one of the most common reasons people think a fix “didn’t work.”

Special-cases rule of thumb: marriage name-drift, a minor/parent identity mismatch, NRI Aadhaar-seeding gaps, and a freshly corrected PAN that hasn’t propagated each break verification in their own way. The common thread is still the same — the account holder, PAN, Aadhaar, and bank name must all describe one adult identity, and back-end changes take days to weeks to take effect. Don’t re-test a fix before the database has actually updated.

PAN-verification myths that cost players money

A handful of wrong beliefs send players down expensive dead ends. Clear these out before you act.

Myth: “If my PAN card is physically valid, it must pass verification.” False. A perfectly printed PAN can be inoperative in the tax system. The card is just paper; the verification reads the back-end status, which can be switched off without any visible change. Always check status, not the card.

Myth: “The app is keeping my money — PAN is just an excuse.” Almost always false. The app is legally barred from paying out against an unverifiable PAN because it can’t report the 194BA TDS or satisfy PMLA. A regulated operator that wanted to steal wouldn’t politely queue your payout behind a PAN check; it would just deny it. A PAN block is enforcement, not theft.

Myth: “I can use a friend’s or family member’s PAN/account to get paid faster.” Dangerous and false. The PAN, the gaming account, and the receiving bank account must all be the same person. Using someone else’s PAN guarantees a tax-attribution mismatch, looks like fraud to the risk engine, and can get both accounts flagged. This is the single worst self-inflicted move.

Myth: “Paying an online ‘PAN agent’ will make it operative instantly.” False and usually a scam. The ₹1,000 linking fee is paid only on the government e-filing portal, and reactivation takes 7–30 days regardless of who you pay. Anyone promising “instant operative PAN for a fee” is phishing your details or your money.

Myth: “Once I fix my PAN, my older inoperative-period TDS is gone forever.” Not necessarily. Within the CBDT 9/2025 relief window, making your PAN operative can undo the deductor’s higher-rate liability, and any excess 20% 206AA TDS already taken is adjusted in your ITR against your AIS. Keep every TDS certificate; don’t write the money off.

Myth: “A bigger withdrawal verifies faster if I split it small.” Splitting doesn’t change PAN verification at all — PAN is checked once per account, not per transaction. Splitting can help with daily limits, but it does nothing for a PAN block. If PAN is the problem, the amount is irrelevant; fix the PAN.

The myth-busting bottom line: a valid-looking card can be inoperative; a PAN block is the app obeying tax/AML law, not stealing; using someone else’s PAN/account is the worst thing you can do; no online “agent” can shortcut the official 7–30 day reactivation; and the ₹1,000 fee exists only on the government portal. Believe these five things and you’ll never waste money on a fake fix.

Document quality (the trivial failure everyone forgets)

Before you go chasing inoperative-PAN status or name mismatches, rule out the dumbest cause: a bad image. A meaningful share of “PAN not verified” results are simply the app’s OCR or a human reviewer being unable to read the card you uploaded.

The common image sins:

• A blurry or low-resolution photo where the 10-character PAN can’t be read cleanly.
• Glare or shadow across the PAN number or name.
• A cropped image that cuts off a corner or the name line.
• A screenshot of a screenshot, or a heavily compressed WhatsApp-forwarded image that’s degraded.
• The wrong side or a coloured-photocopy that washes out the print.

The fix costs five minutes: re-shoot the physical PAN card in good, even light, flat and fully in frame, with all four corners visible and the PAN number and name sharp. Upload that fresh capture. If the app accepts a PDF e-PAN, the official e-PAN download from the e-filing or Protean portal is even cleaner than a phone photo because it’s a generated document, not a picture.

This matters because document-quality rejections are indistinguishable from real verification failures in the app’s generic “PAN failed” message. Players burn days assuming their PAN is inoperative when the API never even got a clean number to check. Re-upload a crisp image once before you assume the worse problems — it’s the cheapest test in this whole guide. If a clean re-upload still fails, then the failure is real data (status or match), and you move to the diagnostic.

The trivial-failure reminder: a chunk of “PAN not verified” results are just an unreadable image — blur, glare, crop, or a re-compressed screenshot. Re-shoot the physical card in even light with all four corners visible, or upload the official e-PAN PDF, before assuming an inoperative-PAN or mismatch problem. It’s the five-minute test that saves you days.

The PAN-to-withdrawal dependency chain (why fixing PAN unblocks the money)

It helps to see the whole dependency as a chain, because it explains why a PAN fix — which feels unrelated to “getting my money” — is the thing that actually releases the payout.

Here is the chain, in order, for a legal Indian gaming withdrawal:

1. You request a withdrawal of winnings to your bank/UPI.
2. The app must deduct 30% TDS on net winnings under Section 194BA and report it against your PAN.
3. To report against your PAN, the PAN must verify — operative status, name match, DOB match, no duplicate.
4. If PAN verification fails, the tax report can’t be filed, so the app cannot release the payout (releasing untaxed/unattributed winnings would breach 194BA and AML).
5. Fix the failing PAN signal → PAN verifies → tax can be attributed → the payout clears.

That’s why “PAN not verified” is not a side issue you can route around — it sits directly on the critical path between your winnings and your bank account. Every other escalation in the withdrawal world (NPCI disputes, RBI timelines, bank traces) lives downstream of this gate and only becomes relevant after PAN passes. If your money is stuck at PAN, no amount of bank escalation helps, because the app hasn’t yet handed anything to the rail.

Where PAN sits versus the rest of the KYC gate

Within KYC, PAN is the tax-and-identity check; Aadhaar is the identity/address check; the bank/UPI is the destination check. They’re separate validations, and a payout needs all three to pass. This page is the PAN layer. Once PAN is clean, if your withdrawal still won’t move, the bottleneck has shifted — to a name-on-account problem (Aadhaar name-mismatch fix), to a broader KYC rejection (KYC-rejected fix), or to the payment rail itself (3 Patti withdrawal hub). Diagnose in that order and you never waste effort on the wrong gate.

A note on TDS and the “less money arrived” confusion

One more thing the PAN chain explains: if your payout does arrive but is smaller than expected, that’s usually 194BA TDS, not a PAN failure. On net winnings the cut is 30%, reported against your PAN, and creditable in your ITR via Form 26AS/AIS. But if your PAN was inoperative at deduction, you may have been hit at the punitive 20% floor under 206AA on top — which is another reason to fix inoperative status fast and to keep your TDS certificates. A correct, verified PAN both unblocks the payout and ensures the tax taken is the right amount you can actually reclaim.

The dependency in one line: winnings → 30% TDS must be reported against your PAN → PAN must verify → only then does the payout release. PAN verification sits on the critical path, so fixing the failing PAN signal is literally what frees the money. Bank and rail escalations only matter after this gate passes.

Per-failure fix table: match your symptom to the exact repair

Pull everything together. Find your symptom on the left; the right columns give the cause, the fix, and how long it takes.

Read this as a decision tree, not a menu. Start at the top (inoperative PAN is statistically your most likely block), confirm it with the free status check, and only move down if you’ve ruled out each row above. Fixing the wrong row wastes the most precious thing in a stuck withdrawal — time inside the rule-clocks that protect you downstream.

Step-by-step: the clean PAN-verification path from scratch

If you want the proactive version — set PAN up correctly before you ever try to withdraw, so this never bites — here’s the sequence. Doing this the day you finish KYC, not the day you want your cash, is the single best habit in this whole guide.

Step 1 — Confirm your PAN is operative

Run the free Verify PAN Status check on the e-filing portal (PAN + name + DOB + mobile + OTP). If operative and Aadhaar-linked, proceed. If inoperative, stop and link Aadhaar first (₹1,000 path above) — don’t even attempt gaming KYC until status flips, because it will only fail.

Step 2 — Align your three names and DOBs

Lay your PAN, Aadhaar, and bank account side by side and confirm the name and DOB are identical across all three. Fix any odd one out at its source before uploading anything to the gaming app. This is the step that prevents the name-match N / DOB-match N API failures.

Step 3 — Upload a clean PAN image

Use a sharp, well-lit photo of the physical card with all four corners visible, or the official e-PAN PDF. Don’t upload a forwarded, compressed, or cropped image.

Step 4 — Use one bank account, in your own name

Register a bank account / UPI handle in your own name that matches your PAN, and use the same one for deposits and withdrawals. Mixing accounts, or using a family member’s account, is a classic self-inflicted block.

Step 5 — Expect a stricter first-withdrawal review

Even with everything correct, many apps run a stricter manual review on your first-ever payout. A first withdrawal taking longer than later ones is normal, not a red flag — give it the app’s stated window before escalating.

Step 6 — Keep your TDS certificates

After payouts, keep the Form 16A TDS certificates and check the deductions in your Form 26AS / AIS. This is how you reclaim the 30% at filing — and how you’d spot a wrong 206AA 20% hit from a period when your PAN was inoperative.

If you follow this path, “PAN not verified” simply never happens to you, because you’ve pre-cleared all four signals the API checks. The whole point of doing it early is that the fixes (especially Aadhaar linking) take days to weeks — and you don’t want to discover that mid-withdrawal with money you need.

When PAN is fine and the payout is still stuck

Sometimes you do everything above, your PAN reads operative, every name and DOB matches, there’s no duplicate, the image is crisp — and the withdrawal still won’t move. At that point the bottleneck has moved past PAN, and chasing PAN further is wasted effort. Here’s where to look next.

• The account-name destination layer. PAN can be perfect while the name on the receiving bank account still doesn’t reconcile at the bank’s end. That’s a distinct fix from PAN, covered in the Aadhaar name-mismatch withdrawal page.
• A broader KYC rejection. If the app is rejecting the whole KYC (not just PAN) — Aadhaar issues, address proof, a flagged account — the Teen Patti KYC-rejected fix walks the full rejection tree and tells you what document is actually failing.
• The payment rail. If KYC fully passed and the money was handed to UPI/IMPS but never landed, that’s a rail problem — debited-but-not-credited, a stale handle, a batch delay — with its own RBI/NPCI protections. The 3 Patti withdrawal hub maps the rail-side escalation, the T+1 auto-reversal, and the ₹100/day compensation.
• A risk hold unrelated to PAN. A sudden large win, a new account, or a duplicate-device flag can park a payout in manual review even with clean PAN. Ask support in writing for the specific reason and a timeline, and keep the ticket ID.

The general rule: PAN is the first KYC gate, not the only one. Clear it, confirm it’s clear, then move methodically to the next gate. The worst outcome is shouting at the app about PAN when your actual block is two gates downstream.

Honest limit of this page: it fixes the PAN layer of gaming KYC, which is the most common and most misunderstood block. It does not fix a name-on-account problem at your bank, a broader Aadhaar/address KYC rejection, or a payment-rail failure — those have their own pages, linked above. Diagnose in order (PAN → bank name → full KYC → rail) and you’ll always be fixing the gate that’s actually closed.

What to do while a PAN fix is in progress (and what not to do)

A PAN repair — especially Aadhaar linking — takes days to weeks, and that waiting period is where players make their costliest mistakes. Here’s how to handle the gap without making things worse.

Do document everything on Day 0. The moment your withdrawal blocks on PAN, screenshot the exact error message, the withdrawal amount, the timestamp, and your KYC status screen. Raise an in-app support ticket stating the specific issue (“PAN verification failed / KYC pending on withdrawal of ₹[amount]”) and get a ticket ID in writing. This timestamps your complaint, which matters if the block later turns out to be on the app’s side rather than your PAN.

Do fix the PAN at its source, in parallel. While support is responding, run the Verify PAN Status check and start the relevant repair (link Aadhaar, correct a name, surrender a duplicate). Don’t wait for support to “fix” your PAN — they can’t; only you can correct your own tax records. Support’s job is to re-trigger verification once your PAN is clean.

Do re-submit only after the status actually changes. The most common wasted week: re-uploading the same PAN before the back-end status has flipped. Linking and corrections take 7–30 days to reflect. Re-run the status check, confirm operative/corrected, then tell the app to re-verify.

Don’t deposit more “to unlock” the withdrawal. No legal app requires a deposit to release a withdrawal, and post-PROGA a new deposit into a money game is illegal. Any prompt to “add ₹X to verify your account” is a theft pattern — stop and report it.

Don’t call “PAN verification helpline” numbers from Google or YouTube. Most legal apps route support in-app and have no public phone line. Numbers posted online are overwhelmingly scams that exist to phish your OTP, PAN image, and UPI PIN. Never share those with a caller.

Don’t open a second gaming account or use a different PAN. Spinning up a “fresh” account with a friend’s PAN to dodge the block deepens the flag and can freeze both accounts. The only path is fixing the one PAN tied to the one account.

The mindset that wins: treat the wait as a process with a clock, not a fight. You’re not arguing with the app; you’re repairing a government record so the app’s legal check can pass. Once it passes, the money releases on its own.

While waiting, in one line: document Day 0, fix the PAN at its source in parallel, re-submit only after the status truly changes, and never deposit more, never call a Google “helpline,” never use another PAN. The wait is a record-repair clock, not a negotiation — when the record is clean, the payout clears itself.

A printable PAN-verification readiness checklist

Run this list before your first withdrawal and you’ll clear every one of the four signals the verification API checks. Tick all six and “PAN not verified” simply won’t happen to you.

1. PAN is operative. Confirmed on the e-filing portal’s Verify PAN Status page — reads operative and Aadhaar-linked.
2. Name matches across all three records. PAN, Aadhaar, and your receiving bank account / UPI handle all carry the identical name (same spelling, same order, same initials).
3. DOB matches across PAN and Aadhaar. Identical day, month, and year — no year-only Aadhaar against a full-date PAN, no transposed day/month.
4. Exactly one PAN. You’ve never held a second PAN; if you did, the duplicate is surrendered and only the Aadhaar-linked one remains.
5. Receiving account is yours. The bank account / UPI handle that will receive the money is in your own name, matching your PAN, and is the same account you use to deposit.
6. Clean PAN image ready. A sharp, well-lit photo of the physical card (all four corners visible) or the official e-PAN PDF — not a forwarded, cropped, or compressed screenshot.

If any item is unticked, fix that one before you attempt a withdrawal, because every fix here (Aadhaar linking, name correction, duplicate surrender) takes days to weeks. The entire reason to run this checklist early is that the repairs are slow — discovering an unticked box mid-withdrawal, with money you need, is exactly the trap this page exists to prevent. For the full cross-document KYC checklist beyond PAN, the KYC and account-recovery hub covers Aadhaar and bank-proof readiness alongside it.

Where to verify and get official help

Every fact on this page traces to a primary source. Use these official doors directly rather than third-party “PAN helper” sites, which are often scams:

• Check PAN status / link Aadhaar: the Income Tax e-filing portal — Verify PAN Status, Link Aadhaar, and e-Pay Tax all live here, free.
• PAN corrections / new card / surrender duplicate: Protean (NSDL) TIN-PAN or UTIITSL — the two authorised PAN service agencies.
• Aadhaar corrections: UIDAI Self-Service Update Portal or an Aadhaar Seva Kendra.
• The tax rules themselves: Section 194BA, Section 206AA, and CBDT circulars at incometaxindia.gov.in.

Two safety rules that apply to PAN specifically. First, never pay a “PAN agent” who DMs or calls you offering to “verify your PAN for gaming” or “make it operative fast” — the official ₹1,000 fee is paid only on the government e-filing portal, and anyone collecting it elsewhere is phishing. Second, never share your Aadhaar OTP, PAN image, or bank OTP with a “support” caller — legitimate verification happens inside the app and on government portals, never over a phone call from a number you found online. If someone pressures you this way, it’s a scam; for the broader fraud-vs-delay picture see the KYC and account-recovery hub.

FAQ

1. Why do gaming apps need my PAN before I can withdraw? Because legal Indian apps must deduct 30% TDS on net winnings under Section 194BA and report it against your PAN, and they must satisfy PMLA identity checks. With no verified PAN there’s no valid tax report and no AML-clean payee, so the payout legally can’t complete. PAN is enforced at the cash-out, not the deposit, because the withdrawal is the taxable event.

2. What does “PAN not verified” actually mean? The app pushed your PAN, name, and DOB to the Protean/UTIITSL verification API, and one of four signals came back wrong: an inoperative PAN status, a name-match of N, a DOB-match of N, or a duplicate/Aadhaar-seeding issue. The app usually hides which one, so you diagnose by checking your own records — starting with PAN status.

3. What is an “inoperative” PAN and why does it block my withdrawal? An inoperative PAN is a valid PAN that’s been switched off in the tax system because it isn’t linked to Aadhaar. Nothing on the card shows it. It fails gaming KYC and, under Section 206AA, exposes you to a 20% TDS floor. Check status free on the e-filing portal’s Verify PAN Status page; fixing it means linking Aadhaar.

4. How do I check whether my PAN is operative? Go to the Income Tax e-filing portal, click Verify PAN Status under Quick Links, enter PAN + name + DOB + mobile, and validate the 6-digit OTP (valid 15 minutes, 3 attempts). It tells you operative-or-inoperative and Aadhaar-linked-or-not, for free, in about 3 minutes.

5. How much does it cost to link PAN with Aadhaar now, and how? A ₹1,000 fee, paid as Challan ITNS 280 with Major head 0021 and Minor head 500 (Other Receipts) on the e-Pay Tax flow. Wait 4–5 days for the payment to reflect, then submit the Link Aadhaar request. The free deadline is long gone, so this fee is unavoidable for an inoperative PAN.

6. How long until my PAN becomes operative after I link Aadhaar? Roughly 7 to 30 days — the commonly stated figure is “operative after 30 days of applying,” though many clear in about a week. Re-run Verify PAN Status until it reads operative before you re-submit gaming KYC, or the verification will just fail again.

7. My name is spelled differently on my PAN and bank account — is that the problem? Very likely. A PAN-vs-bank name mismatch is the most common silent stall on a first gaming withdrawal. Make your bank account name match your PAN exactly, use the same account for deposit and withdrawal, and correct any error with the bank (the app can’t override it). See the Aadhaar name-mismatch fix for the full three-way reconciliation.

8. My PAN and Aadhaar names don’t match — how do I fix it? For a minor mismatch, an Aadhaar OTP during linking may resolve it. For a major one, correct the wrong record: Aadhaar via the UIDAI Self-Service portal (≈5–7 working days; name change allowed only twice in a lifetime), or PAN via Protean/UTIITSL (≈10–15 working days, ₹110–₹200). The DOB must be identical on both.

9. Why did less money arrive than I withdrew — is my PAN broken? Usually not — that’s 194BA TDS: 30% of net winnings, deducted and reported against your PAN, and reclaimable at filing via Form 26AS / AIS. But if your PAN was inoperative at deduction, you may have been hit at the higher 20% 206AA floor too, which is one more reason to fix inoperative status fast and keep your TDS certificates.

10. Can I get the 20% higher TDS back if my PAN was inoperative? Partly, via relief. CBDT Circular No. 9/2025 protects deductors (and effectively you) for payments between 1 Apr 2024 and 31 Jul 2025 if the PAN was made operative by 30 Sep 2025. Any excess TDS already deducted is adjusted when you file your ITR against your AIS — so keep every TDS certificate.

11. What happens if I have two PAN cards? Holding more than one PAN is illegal under Section 139A and can draw a ₹10,000 penalty under Section 272B. Two PANs break 194BA tax attribution and look like fraud to a risk engine, freezing payouts. Surrender the duplicate using the Form 49A correction on Protean/UTIITSL, keep the Aadhaar-linked one, and the flag clears.

12. The app keeps rejecting my PAN even though it’s correct — why? First rule out a bad image: blur, glare, a cropped frame, or a re-compressed screenshot the OCR can’t read. Re-shoot the physical card in even light with all four corners visible, or upload the official e-PAN PDF. If a clean re-upload still fails, the problem is real data — check status, name, and DOB next.

13. Do I need PAN to withdraw from a now-discontinued app under PROGA? Yes. Even in a wind-down balance recovery, the operator must still attribute any 194BA TDS to your PAN before releasing the balance, so PAN verification still gates the recovery. Complete KYC, expect 30% TDS on net winnings, and never deposit again — a new deposit into a money game is now illegal post-PROGA.

14. Is it safe to pay someone who offers to “verify my PAN for gaming”? No — it’s a scam. The official ₹1,000 linking fee is paid only on the government e-filing portal, and PAN verification happens inside the app and on official portals. Never pay a DM/caller “agent,” and never share your Aadhaar OTP, PAN image, or bank OTP with anyone who calls. Real support never needs those.

15. PAN is fine and verified but my withdrawal is still stuck — what now? The block has moved past PAN. Check, in order: a name-on-account problem at your bank (fix here), a broader KYC rejection (fix here), or a payment-rail failure with RBI/NPCI protections (hub here). PAN is the first KYC gate, not the only one — clear it, confirm it, then move to the next gate methodically.

Sources & method. PAN verification mechanics, the inoperative-PAN consequences, linking procedure, mismatch fixes, and tax rules on this page are built from primary government and authoritative sources — not personal tests. Key references: Section 194BA TDS-on-gaming and PAN-attribution; Section 206AA 20% higher-rate-on-inoperative-PAN and CBDT Circular No. 9/2025 (21 Jul 2025) relief; the Income Tax e-filing portal Verify-PAN, Link-Aadhaar and ₹1,000 fee (ITNS 280, head 0021/500) procedures; Protean OPV / PAN Lite verification fields (status, name-match Y/N/null, DOB-match, Aadhaar seeding); UIDAI and Protean / UTIITSL name/DOB-correction processes; Section 139A / 272B duplicate-PAN rules and surrender; inoperative-PAN consequences via CBDT/Outlook and ClearTax. This page is information, not legal or financial advice — verify each step against the current e-filing portal and your operator’s Terms.