ID Verification Failed on a Gaming App? Fix Every KYC Block

The 30-second answer

When a gaming app says “ID verification failed,” it’s almost never your identity that’s wrong — it’s the capture. There are 7 distinct failure types, and most clear on one clean re-submit. The single fastest fix: stop uploading phone photos and pull a digitally signed document straight from DigiLocker, which removes 3 failure types at once.

The seven failures are a blurry selfie, a dropped video-KYC session, an Aadhaar OTP that never arrived, a rejected address proof, an underage block, a document too blurry for OCR, and a name mismatch. India’s KYC rules under the RBI Master Direction on KYC, last amended 4 January 2024, demand a clean, machine-readable match — which is exactly what a DigiLocker fetch delivers. This page maps every ID-verification failure that isn’t a PAN or name-mismatch problem; those have their own pages. Start at the KYC account recovery hub if you’re not sure which block you have.

Editor’s verdict, up front. Ninety percent of “my ID won’t verify” complaints are not the app rejecting you — they’re an automated check that couldn’t read what you sent. A face-match engine that can’t see your face in a dark selfie. A V-CIP agent who lost your video to a 3G dropout. An OCR that read “0” as “O” on a smudged utility bill. Each of these has a different, specific fix, and almost none of them require you to “try a better app” — the same rules apply everywhere because the same RBI direction governs them all. The single highest-leverage move in this entire guide is to replace every phone-camera upload with a DigiLocker-issued, UIDAI-signed file, because that removes the two biggest failure sources at once: bad image quality and unverifiable authenticity. The rest is matching your specific error to the right rung.

2026 reality you must read first. The legal ground shifted hard. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) received Presidential assent on 22 August 2025 and prohibits all online money games where you stake money for a return, with the operating Rules in force from 1 May 2026. If you’re verifying ID on a still-live legal app, this guide is your fix. If you’re trying to verify ID to recover a stranded balance from a now-discontinued cash app, KYC is still the gate you must pass — operators and banks kept the withdrawal flow open for balance recovery, but only to verified accounts. Either way: complete the verification, never deposit again to “unlock” anything, and never share an OTP or PIN with a “support agent.” The verification rules below cover both cases, and we flag which is which.

What “ID verification” actually checks (and why it fails)

When people search “id verification failed gaming app,” “video kyc problem,” “selfie verification not working,” or “aadhaar verification failed,” they’re describing the same gate from different angles. Before any fix makes sense, you have to know what the app is actually testing. A real-money gaming app in India runs Customer Due Diligence (CDD) — the legal process of confirming you are a real, identifiable, of-age person — and it does that by checking five distinct things, each of which can fail independently:

• Are you a real, live human right now? — the liveness / selfie / face-match check. The app captures your face and confirms it’s a live person (not a photo, video, or deepfake) and that the face matches your ID photo.
• Is your identity document genuine and yours? — the document authenticity + OCR check. The app reads the data off your Aadhaar, PAN, or other ID and confirms the document is real and unaltered.
• Do you live where you say? — the address / OVD check. An Officially Valid Document proves your current address.
• Are you old enough? — the age-verification check. Every legal RMG app blocks under-18s (some block under-21s in certain states), computed from your date of birth on the ID.
• Does everything match? — the cross-match check. Your name, date of birth, and photo must reconcile across the selfie, the ID, and your bank/UPI account.

A failure is just one of those five checks returning “no.” The error message you see (“verification failed,” “KYC rejected,” “documents not clear”) is usually too vague to tell you which check failed — so the rest of this page is a map from symptom to the specific failing check, then to its fix. Two of the five — PAN-specific problems and name mismatch — are big enough to have their own pages: see PAN card verification on gaming apps and Teen Patti KYC rejected. This page covers the other layers: selfie/liveness, video-CIP, Aadhaar OTP/XML, address proof, age block, and document-quality/OCR failures, plus the clean-source DigiLocker fix that quietly solves several at once.

Why the app is so strict about this

It isn’t the app being difficult. Under India’s Prevention of Money-Laundering Act and the RBI KYC Master Direction, an entity that pays out cash to an unverified or wrongly verified account is breaking anti-money-laundering law. The same direction is why your bank made you do video KYC to open an account — gaming-app verification is the same legal machinery, applied to the same risk. The strictness is a feature, not a bug: it’s also what gives you leverage when your documents are clean and the app still won’t pay. If you’ve passed a real KYC, you have the RBI rulebook behind you when you escalate a stuck payout — which is the whole logic of the withdrawal escalation ladder.

The seven verification failures, and which one is yours

Diagnosing the type is most of the fix, because each one re-verifies differently. Here’s the fast triage — match your symptom to a type, then jump to that type’s full section below.

The triage in one line: Types 1, 2, 6 are capture-quality failures — fix them by sending a cleaner input. Types 3, 4 are source failures — fix them by going to the authoritative source (UIDAI/DigiLocker). Type 5 is usually final (you can’t fake an age). Type 7 has its own pages. Sort your error into the right bucket before you re-submit anything, because re-uploading the same blurry photo five times just deepens a manual-review flag.

The single thread running through Types 1, 2, 4 and 6: the cleaner and more authoritative your source, the higher your pass rate. A digitally signed Aadhaar XML from DigiLocker beats a phone photo of a laminated card every time. We’ll come back to that fix repeatedly because it’s the one move that lifts four of the seven failure types at once.

Type 1 — Selfie, liveness, and face-match failures

Symptom: “Selfie verification failed,” “face not detected,” “liveness check failed,” “face does not match document,” or the camera screen that just won’t accept your face no matter how many times you tap capture.

What’s really happening: the app is running two checks on one photo or short video clip. First, liveness detection — confirming you’re a live person in front of the camera right now, not a printed photo, a screen, a recorded video, or a deepfake. Second, face match — comparing your live face to the photo on your Aadhaar or PAN. UIDAI itself notes that its face-recognition model was tightened to reduce spoofing, which made it stricter on low-light and tilted images, and gaming-app vendors use the same kind of engine. So the most common reason a real face fails is not fraud detection paranoia — it’s that the engine genuinely can’t see your face clearly enough to be confident.

The eight things that break a liveness check

Run down this list before you blame the app. In rough order of how often they’re the real cause:

1. Poor or uneven lighting. A dark room, or strong backlight from a window behind you, throws your face into shadow. UIDAI’s own guidance is to use a well-lit, clear environment and avoid fans, windows or curtains creating shadows. Face an even light source; don’t sit with a window or lamp behind you.
2. Glare or reflection. Glasses reflecting a ceiling light, a glossy phone screen, sweat or oil shine — all of it confuses the matcher. Take glasses off for the capture.
3. Face partly covered. A mask, scarf, cap, hair across the forehead, or anything that hides the jaw, brows, or eyes. The matcher needs the full face landmark set.
4. Moving too fast or too still. Liveness wants natural micro-movement and a blink. Moving the phone around blurs the frame; holding rigidly like a passport photo can read as a still image. Hold steady but let the app detect natural blinking.
5. Wrong distance or angle. Too close, too far, tilted up or down. Hold the phone at eye level, arm’s length, face square to the lens.
6. A genuinely outdated ID photo. If your Aadhaar photo is ten years old and you’ve aged, grown a beard, or changed dramatically, the face-match score can dip below threshold even with a perfect selfie. This is the case where re-shooting won’t help — you may need V-CIP with a live agent (Type 2) who can use judgment.
7. A low-quality front camera. Budget phones with weak front cameras produce noisy, soft images. UIDAI notes some phones let you switch to the rear camera, which often captures better lighting and focus — try that if the app allows it.
8. You’re trying to use a photo of a photo. Holding up a printed selfie or showing another screen will (correctly) fail liveness. A live selfie cannot be replaced with a photo, video, screenshot, or deepfake — that’s the whole point of liveness.

The fix: a clean re-shoot in under two minutes

The fix for a face-match failure is almost always a better capture, not a different identity:

• Stand or sit facing a window in daytime or an even indoor light in front of you, never behind.
• Remove glasses, mask, cap; pull hair off your face.
• Hold the phone at eye level, about an arm’s length away, face square.
• Wipe the camera lens — a smudged front lens is a silent killer.
• Let the app run its blink/turn prompts naturally; don’t rush.
• If the front camera is weak, switch to the rear camera if the app offers it.

If you re-shoot three times in good conditions and it still fails, stop re-trying — repeated fails can flag your account for manual review. That’s your signal to move to video KYC with a live agent (Type 2), where a human can override an over-cautious automated score, or to raise a support ticket with the KYC recovery hub steps. One genuinely-stuck face-match (old photo, unusual lighting condition, a disability that affects capture) is exactly what the live-agent V-CIP path exists for.

Privacy note worth knowing: a legitimate app captures your selfie inside its own secured flow and stores it encrypted. If an “agent” asks you to send your selfie or a video of your face over WhatsApp or to a personal number, that’s a scam pattern, not KYC. Real verification never happens in a personal chat.

Type 2 — The RBI Video-CIP (V-CIP) process and why it fails

Symptom: the app schedules or launches a video call with an agent to verify you, and it drops, freezes, says “agent unavailable,” “could not capture location,” “session expired,” or restarts you to the back of the queue.

What’s really happening: you’ve hit the Video-based Customer Identification Process (V-CIP) — RBI’s framework for verifying identity over a live video call, treated as equivalent to in-person verification. It’s defined in the RBI Master Direction on KYC, V-CIP provisions amended 4 January 2024. V-CIP is more demanding than a selfie because it’s doing more: a live, consent-based audio-visual interaction with a trained official, plus liveness, face match, document capture, geo-tagging, and an encrypted recording — all in one session. More moving parts means more ways for a session to break.

What RBI actually requires in a V-CIP session

Understanding the requirements tells you exactly why a session fails. The binding norms include:

• A live agent and live interaction. V-CIP must be a live, informed-consent audio-visual interaction — not a pre-recorded clip. If no trained official is available, the session can’t proceed, which is why “agent unavailable” happens during off-hours.
• Geo-tagging. The recording must be geo-tagged with the customer’s live GPS coordinates and a date-time stamp. If your phone’s location is off, denied to the app, or spoofed, the geo-tag fails and the session is rejected.
• Liveness and face match. The V-CIP must detect face liveness, prevent spoofing, and conduct a face match live — so all the lighting and clarity issues from Type 1 apply here too, in real time.
• You must be inside India. RBI requires the system to detect IP addresses from outside India or IP spoofing and block the connection. A VPN that routes your traffic abroad will fail you.
• A stable, encrypted connection. The interaction uses end-to-end encryption and data stored on systems located in India. A flaky connection breaks the encrypted stream and ends the session.
• A clear video and audio feed. The agent has to see your face and your document clearly enough to verify both, the same clarity bar as a selfie but sustained over a whole call.

The seven reasons a V-CIP call breaks — and the fix for each

1. Weak or unstable network. A video KYC needs a steady connection for the whole call; a mobile-data dropout freezes the feed and kills the session. Fix: use stable Wi-Fi or a strong 4G/5G signal, close other apps eating bandwidth, and don’t move around (lifts, basements, moving vehicles drop signal).
2. Location turned off or denied. The geo-tag is mandatory; if the app can’t read your GPS, it can’t complete a compliant V-CIP. Fix: turn device location ON, grant the app precise-location permission, and stay in one spot. Don’t use a fake-GPS app.
3. A VPN or proxy routing you outside India. RBI requires the system to reject foreign or spoofed IPs. Fix: turn off any VPN/proxy before the call. This is a frequent silent failure for users who keep a VPN on by habit.
4. No agent available (off-hours / queue). V-CIP needs a live trained official; many providers run agent hours, and you’ll hit “agent unavailable” outside them. Fix: retry during the app’s stated V-CIP hours (often daytime/business hours), and join the queue early.
5. Poor lighting / camera, same as Type 1. The live face match and document capture need clarity. Fix: sit facing an even light, wipe the lens, hold the phone steady at eye level, and keep your original ID handy to show on camera.
6. A blurry or glare-covered document on camera. The agent must read your physical ID live; a laminated card under a ceiling light glares out. Fix: tilt the card to kill the glare, hold it steady and flat, and have good light on the document as well as your face.
7. Session timeout from fumbling. Long pauses, repeated permission prompts, or app crashes can expire the session. Fix: grant camera, mic, and location permissions before you start, have your documents ready in hand, and follow the agent’s prompts without long gaps.

The V-CIP pre-flight checklist, in one breath: Wi-Fi on, VPN off, location on, good front light, lens wiped, original ID in hand, permissions pre-granted, during agent hours. Hit all eight and a V-CIP that kept failing usually clears on the next try. If it still won’t connect after several attempts in good conditions, that’s a provider-side queue/capacity issue — raise it with support and ask for the next available slot, not a re-loop into a full queue.

The reason V-CIP exists at all is for the hard cases the automated selfie can’t handle — an old ID photo, an unusual face-match condition, a document that needs a human eye. So if your Type 1 selfie keeps failing for a legitimate reason, V-CIP is your escalation, not a punishment. A live official can apply judgment a threshold-based algorithm can’t.

Type 3 — Aadhaar OTP and offline XML failures

Symptom: “OTP not received,” “Aadhaar OTP verification failed,” “could not verify Aadhaar,” “invalid XML,” “share code incorrect,” or an Aadhaar-based eKYC step that just won’t complete.

What’s really happening: the app is trying to verify your Aadhaar through one of two paths, and one of them is broken. The two paths matter because the fix differs:

• Aadhaar OTP eKYC — the app sends a one-time password to the mobile number linked to your Aadhaar, and you enter it. This is the most common Aadhaar verification path.
• Aadhaar Paperless Offline eKYC (XML / ZIP) — you download a digitally signed, machine-readable XML file from UIDAI, protected by a “Share Code,” and hand the file plus its share code to the app. The XML is digitally signed by UIDAI so the app can verify it’s genuine without contacting UIDAI live.

Why Aadhaar OTP verification fails

1. Your mobile isn’t linked to your Aadhaar — or it’s an old number. The OTP is sent only to the registered mobile number. If the number on your Aadhaar is one you no longer use, the OTP goes to a dead SIM and you never see it. Fix: check which number is linked (you can verify on the UIDAI portal/mAadhaar app), and if it’s outdated, update your mobile number at an Aadhaar enrolment centre before retrying. There’s no remote shortcut for this — UIDAI requires in-person mobile updates.
2. Network/SMS delay. The OTP is just an SMS; on a congested network it can be slow. Fix: wait the full delivery window, ensure you have signal, then request a resend — but don’t spam “resend,” which can trigger a temporary lockout.
3. OTP entered after it expired. Aadhaar OTPs are short-lived. Fix: enter it promptly; if it expired, request a fresh one.
4. Aadhaar temporarily locked or biometrics locked. If you’ve locked your Aadhaar/biometrics via UIDAI for security, OTP-based eKYC can be blocked. Fix: unlock it on the UIDAI portal, then retry.

Why the offline Aadhaar XML fails

1. Wrong Share Code. The ZIP is encrypted with a Share Phrase/Share Code you set when generating it; enter the wrong code and the app can’t open it. Fix: re-enter the exact code you set, matching case; if you forgot it, generate a fresh XML with a code you’ll remember.
2. A stale or expired XML. While the underlying Aadhaar XML is valid for a lifetime for verification, some apps require a freshly generated file (often within a few days) so the timestamp is recent. Fix: generate a new XML right before you submit it.
3. A corrupted or wrong file. Uploading the unzipped contents, the wrong ZIP, or a partially downloaded file all fail. Fix: upload the ZIP exactly as downloaded from UIDAI, without unzipping it.
4. Demographic mismatch inside the XML. If your name or DOB on Aadhaar doesn’t match what you entered in the app (or your PAN), the signed XML is authentic but the cross-match still fails — that’s a Type 7 problem, handled on the KYC rejected page.

The cleaner path: skip the loose XML, use DigiLocker

Here’s the move that quietly fixes most Type 3 (and Type 4 and 6) failures at once. Instead of generating a loose XML or photographing your Aadhaar card, fetch your Aadhaar directly from DigiLocker inside the app’s KYC flow. Why it’s better:

• DigiLocker pulls a government-issued, digitally signed copy of your Aadhaar — recognised as an “equivalent e-document” with the same legal validity as the original under the IT Act, 2000.
• Under the RBI KYC Direction, regulated entities are authorised to accept DigiLocker-issued OVDs for customer identification.
• There’s no OCR step to fail — the data comes through clean and machine-readable, so the smudge/glare/blur failure modes vanish.
• It’s authenticated at source, so the app doesn’t have to second-guess whether your document is genuine.

If the app offers a “Verify via DigiLocker” or “Fetch from DigiLocker” option, take it over photographing your card almost every time. We give DigiLocker its own section below because it’s the cleanest fix in this whole guide.

Type 4 — Address proof and OVD rejections

Symptom: “Address proof rejected,” “document not accepted,” “address does not match,” “OVD invalid,” or your utility bill / rent agreement bouncing back.

What’s really happening: the app wants proof of your current address via an Officially Valid Document (OVD) — and either the document you sent isn’t on the accepted list, or its address doesn’t match what’s on file, or it’s too old. The term OVD is precise. Under the RBI KYC framework, the recognised OVDs are a defined set: passport, driving licence, proof of possession of Aadhaar, Voter ID, a NREGA job card, and a National Population Register letter containing your name and address. A random gas bill or a screenshot of a banking app is not an OVD, even though people assume any official-looking paper counts.

The six reasons an address proof fails

1. It isn’t an OVD at all. A mobile-phone bill, a credit-card statement, or a college ID is not on the OVD list. Fix: submit an actual OVD — most easily your Aadhaar (which doubles as address proof) fetched from DigiLocker.
2. The address is outdated. Your Aadhaar still shows your old hometown address but you’ve moved. The app’s address-on-file (or your bank’s) doesn’t match. Fix: update your address on Aadhaar first (online via UIDAI if you have a valid document, or at an enrolment centre), then re-verify — there’s no point submitting a document with a stale address.
3. A “deemed OVD” is too old. For documents the rules allow as address proof only when an OVD lacks the current address (utility bills, bank statements in some flows), there’s typically a recency window of about two months. An old bill is rejected for age. Fix: use a recent document within the window, or better, use Aadhaar itself.
4. Name on the address proof differs from your KYC name. The bill is in a parent’s or spouse’s name, not yours. Fix: use an OVD in your own name; a bill in someone else’s name doesn’t prove your address.
5. A blurry or cropped scan. The address line is cut off, smudged, or unreadable — that’s really a Type 6 OCR failure wearing an address-proof costume. Fix: re-scan the full document, flat and clear, or pull it from DigiLocker.
6. A reduced-KYC “small account” hitting its ceiling. If you onboarded with minimal details, you may be on a limited-KYC tier with caps, and full withdrawal needs a full OVD. Fix: complete full KYC with a proper OVD to lift the limit.

The clean fix: Aadhaar as address proof, via DigiLocker

For the overwhelming majority of users, the simplest valid address proof is your own Aadhaar, because it’s a single OVD that proves identity and address together. Fetched from DigiLocker, it arrives signed, clean, and pre-accepted by regulated entities — which collapses reasons 1, 5, and most of 6 at once. The only address-proof problem DigiLocker can’t fix is reason 2: if your Aadhaar address itself is wrong, you must update Aadhaar at source first. No app can paper over a genuinely outdated address on your government record.

Type 5 — Age-verification (the underage block)

Symptom: “You are not eligible to play,” “must be 18 years or older,” “account restricted,” or a hard block at signup or first withdrawal that mentions age.

What’s really happening: every legal real-money gaming app in India must block minors. The minimum is 18 under contract law (a minor can’t enter a binding wagering contract), and a few states historically set the bar at 21 for staked play. The app computes your age from the date of birth on your verified ID. If that DOB makes you under the threshold, the block is deliberate and final — and trying to bypass it is both against the terms and, post-PROGA, legally fraught.

When the age block is correct (most of the time)

If you are genuinely under 18, there is no fix — and you shouldn’t look for one. Real-money gaming is closed to minors by law, and any “workaround” (using a parent’s ID, faking a DOB) is identity fraud that can freeze the account and any balance permanently, with no recourse. The honest answer here is the boring one: wait until you’re of legal age, and don’t risk a permanent ban and a fraud flag for it.

When the age block is a data error (rare, but fixable)

Occasionally an adult is wrongly blocked because the DOB on a document is wrong — a data-entry error on Aadhaar, a typo at enrolment, a DOB that defaulted to 1 January of a year. In that narrow case:

• Check your actual DOB on every document. If your Aadhaar shows the wrong birth year, the app is correctly reading a wrong source.
• Correct the DOB at the source first. Update it on Aadhaar (UIDAI permits one date-of-birth update with valid proof) or the relevant document, then re-verify on the app. The app can’t override your government record; you fix the record.
• If the DOB is right and you’re an adult but still blocked, raise a support ticket with a clear DOB document — this is the rare manual-review case, and the KYC recovery hub covers how to escalate it.

The age section in one line: if the block is real, respect it — there’s no legitimate fix and the downside of faking it is a permanent ban plus fraud exposure. If it’s a genuine data error on your DOB, the fix is to correct the document at source, not to argue with the app. The app is only reading what your ID says.

Type 6 — Document quality and OCR failures

Symptom: “Document not clear,” “upload a clearer image,” “details could not be read,” “please re-upload,” or the app accepting the file but then failing the data behind it.

What’s really happening: the app runs OCR (Optical Character Recognition) to read the text off your uploaded ID image — name, number, DOB, address. If the image is too blurry, dark, glared, cropped, or skewed for the OCR to read confidently, it either rejects the upload outright or reads the data wrong (turning a stuck “name mismatch” into a Type 7 cross-match failure that’s really an image problem). This is the most self-inflicted failure type, and the easiest to fix, because it’s purely about image quality.

The eight image problems that break OCR — and the fix

1. Blur from a moving hand. Fix: brace your elbows or rest the phone on a stable surface; let autofocus lock before shooting.
2. Glare on a laminated card. A ceiling light or flash bounces off the plastic right across the text. Fix: turn off the flash, tilt the card slightly to move the glare off the data, and use soft, even light.
3. Too dark. Low light makes everything noisy and unreadable. Fix: shoot near a window in daytime or under a bright, even lamp.
4. Cropped edges. Part of the document — often the address line or a corner with the number — is cut off. Fix: capture the entire document with a small margin all around.
5. Skew / angle. A document photographed at a slant distorts the text for OCR. Fix: hold the camera directly above and parallel to a flat document.
6. Low resolution / heavy compression. Screenshots, WhatsApp-forwarded images (which compress hard), and tiny thumbnails lose detail. Fix: use the original full-resolution photo, never a forwarded/compressed copy.
7. A damaged or faded physical document. A worn, torn, or sun-faded card may be genuinely unreadable. Fix: use a different valid document, or pull a fresh digital copy from DigiLocker.
8. Wrong file or wrong side. Uploading the back when the front was asked for, or a different document entirely. Fix: read the prompt and upload the exact document and side requested.

The structural fix that skips OCR entirely

Here’s why DigiLocker keeps winning. When you fetch a document from DigiLocker, there is no OCR step — the data comes through as structured, machine-readable fields straight from the issuer, digitally signed and treated as equivalent to the original. Every single one of the eight OCR problems above evaporates because there’s no photograph to misread. If your document keeps failing the “not clear” check and the app offers DigiLocker, switching to it isn’t a marginal improvement — it removes the entire class of failure. The only documents you’d still have to photograph are ones DigiLocker doesn’t hold; for Aadhaar, PAN, and driving licence (the big three for gaming KYC), DigiLocker has you covered.

DigiLocker: the clean-source fix for four of the seven failures

DigiLocker shows up in four of the seven failure types as the cleanest fix, so it earns its own section. Understanding why it works tells you when to reach for it.

What it is. DigiLocker is a government digital-document wallet run by India’s Ministry of Electronics and IT. It stores issuer-verified copies of your documents and lets you share them in a form that’s recognised as an “equivalent e-document” with the same legal validity as a physical original under the IT Act, 2000. The documents commonly available include Aadhaar (as XML or masked PDF), PAN, driving licence, and vehicle registration — which covers almost everything a gaming app’s KYC asks for.

Why apps accept it. Under the RBI KYC Direction, regulated entities are authorised to accept DigiLocker-issued OVDs as part of customer identification. So it isn’t a workaround or a grey-area trick — it’s a first-class, RBI-blessed verification path.

The four failures it removes:

• Type 6 (OCR / document quality) — no photo, no OCR, no blur/glare/crop to fail. The data is structured and clean.
• Type 3 (Aadhaar XML) — fetching Aadhaar via DigiLocker hands the app a signed copy directly, sidestepping the loose-XML Share Code dance.
• Type 4 (address proof) — your DigiLocker Aadhaar is a valid OVD that proves identity and address together, pre-accepted by regulated entities.
• Type 1 / Type 2 partly — a clean, authenticated ID photo from DigiLocker gives the face-match engine a higher-quality reference image to compare your live selfie against.

How to use it in a KYC flow:

1. In the app’s KYC step, choose “Verify via DigiLocker” or “Fetch from DigiLocker” if offered.
2. You’re redirected to the DigiLocker login (Aadhaar number + OTP, or your DigiLocker credentials).
3. You consent to share the specific documents the app requested.
4. The app pulls the signed documents directly — no upload, no photo, no OCR.

The one thing it can’t fix. DigiLocker delivers your government record cleanly — so if that record itself is wrong (outdated address, wrong DOB, a name that differs from your PAN), DigiLocker faithfully delivers the wrong data and the cross-match still fails. DigiLocker fixes capture and authenticity; it does not fix bad underlying data. For that, you correct the document at source (UIDAI for Aadhaar, the issuer for the rest), which is the recurring theme of this whole guide: clean the source, not the symptom.

The capture environment: a 90-second setup that lifts your pass rate

Most verification failures are decided before you tap “capture,” by the room you’re sitting in. Because Types 1, 2, and 6 are all clarity problems, a single 90-second environment setup raises your pass rate across all three at once. Treat this as a pre-flight you run once, then verify everything in that spot.

• Light source in front, daylight if possible. Sit facing a window in daytime or an even lamp placed in front of you. UIDAI’s own capture guidance is to use a well-lit, clear environment and avoid fans, windows, or curtains creating shadows. The single most common reason a real face or a real document fails is a light source behind you throwing the subject into shadow.
• A plain, dark, matte surface for documents. Photograph an ID on a non-reflective dark background so the edges are detected cleanly and the OCR isn’t fighting a busy table pattern.
• Flash off, glare off. Camera flash bounces straight off laminated cards across the data line. Kill the flash and tilt the card a few degrees so any ceiling-light reflection slides off the text, not across your Aadhaar number.
• A wiped lens. A smudged front camera is a silent killer of liveness checks — a ten-second wipe with a cloth can be the whole fix.
• A stable phone. Brace your elbows or rest the phone on a stack of books. Hand-shake blur defeats both face liveness and document OCR.
• VPN off, location on, signal strong. This is for the V-CIP case specifically, but turning a habitual VPN off and granting precise location before you start saves a dropped session.

Run that setup once and verify your selfie, your document, and (if needed) your V-CIP session from the same chair. Roughly 8 of 10 failures that looked like “the app is broken” turn out to be “the room was wrong,” and this fixes the room.

Document-by-document: what each one is really checked for

Different documents fail for different reasons, because the app checks different things on each. Knowing what’s being read tells you what to get right:

• Aadhaar. Checked for the photo (face match), DOB (age), address (OVD), and the demographic data behind it. It’s the one document that can satisfy identity and address at once, which is why fetching it from DigiLocker solves so much. Its weak point is a stale linked mobile (breaks OTP eKYC) or an outdated address — both fixed only at UIDAI.
• PAN. Checked mainly for the name and number, because the app reports your 30% TDS against it under Section 194BA. A PAN failure is usually a name mismatch or a PAN not linked to Aadhaar — which is exactly why PAN has its own dedicated page.
• Driving licence / Voter ID / passport. Used as alternative OVDs when Aadhaar isn’t used for address. Checked for a current address and a readable photo. Their weak point is an expired document or a superseded address after a move.
• A selfie. Not a document at all — it’s the live liveness + face-match input, checked against the photo on your ID. Its weak point is purely capture quality, which is why the environment setup above matters most here.

The practical upshot: match the document to what it’s checked for, and you stop wasting attempts. Submitting a perfect driving-licence scan won’t fix a face-match failure, and re-shooting a selfie ten times won’t fix a stale Aadhaar address. Read your error, find the document that owns that check, and fix that one.

CKYC: the verification you might already have

Here’s a fact that saves a lot of people a lot of re-verification: you may have already completed KYC in a way the app can reuse, through CKYC.

What CKYC is. The Central KYC Records Registry (CKYCRR) is a centralised KYC system managed by CERSAI (the Central Registry of Securitisation, Asset Reconstruction and Security Interest). It lets you complete KYC once and reuse it across banks, mutual funds, insurers, and other financial institutions. When you finished KYC at a bank, CERSAI issued you a 14-digit CKYC Identifier (KIN) — a single, centralised identity record usable across all RBI-, SEBI-, IRDAI-, and PFRDA-regulated institutions.

Why it matters for a stuck gaming-app KYC. If a payment partner behind the gaming app can pull your existing CKYC record using your CKYC number or PAN, you may not need to re-do the whole selfie/document dance at all — your prior verification is reused. So before you fight a failing fresh KYC, it’s worth checking whether you have a CKYC number (you can look it up via CERSAI or your bank) and whether the app’s flow offers a CKYC/PAN-based lookup.

The catch. Your CKYC record reflects whatever you submitted when you created it. If your address or name has changed since, the reused record can carry the same stale data — and you’re back to a cross-match failure. There are also account tiers: a full “Normal” CKYC built on a core OVD is what unlocks full RMG verification, while a “Small” or “Simplified” account carries limits. So CKYC is a shortcut if your record is current and full-tier; if it’s stale, update it (which also benefits every other institution that reuses it).

CKYC in one line: you may have already done this KYC and just need the app to reuse your 14-digit CKYC record — but only if that record is current and full-tier. Check before you re-verify from scratch; updating a stale CKYC record fixes the problem everywhere at once.

The re-verification path, by failure type

Each failure type re-verifies through a slightly different door. Here’s the consolidated map — find your type, do the source fix, then re-submit clean.

Two patterns jump out of that table. First, DigiLocker is the re-submit door for Types 3, 4, and 6 — three of the seven, plus a quality boost to 1 and 2. Second, the only fixes that happen “at source” are when your government record itself is wrong (a dead Aadhaar mobile, a stale address, a wrong DOB). Everything else is a capture or session problem you fix by sending a cleaner input. If you find yourself re-uploading the same photo over and over, you’re treating a source problem as a capture problem (or vice versa) — re-read your error against this table and switch doors.

The Day-0-to-14 KYC escalation ladder

Most ID-verification failures clear on a clean re-submit within a day. But if you’ve done the right re-submit and the app still won’t verify or release your account, you climb a ladder — and like the withdrawal escalation ladder, it works because each rung matches the problem to the right lever. Don’t skip rungs and don’t jump to a regulator on Day 1.

Day 0 — Diagnose, clean the source, re-submit once

• Identify your failure type from the triage table — don’t re-submit blind.
• Fix the source if it’s a source problem (dead Aadhaar mobile, stale address, wrong DOB). If it’s a capture problem, prepare a clean input.
• Re-submit once, cleanly — DigiLocker fetch where possible, good light and a wiped lens otherwise.
• Screenshot the exact error message and the timestamp. A vague “verification failed” is your evidence later, and the precise wording sometimes hints which check failed.

Do not re-submit the same blurry photo five times — repeated automated fails can route your account to a manual-review hold that’s slower than a single clean attempt.

Day 1–3 — Open an in-app ticket with specifics

• Raise an in-app support ticket stating your failure type, the exact error text, what you’ve already tried, and that your documents are clean and current.
• Ask the specific question: “Which check is failing — liveness, OCR, address, or cross-match?” Forcing a specific answer is far more useful than “please help.”
• Get a ticket / complaint ID in writing. This timestamps your complaint for any later escalation.

Day 4–7 — Request V-CIP / human review

• If automated KYC keeps failing on a legitimate document, ask explicitly for a video-KYC (V-CIP) session with a live agent. A human can override an over-strict automated face-match or read a document an OCR can’t.
• If the app claims your document is invalid when it isn’t, ask for the specific rule — which OVD they accept, which field failed — in writing.
• Re-confirm your CKYC status in parallel: if you have a current full-tier CKYC record, ask whether the app can reuse it.

Day 8–14 — Formal escalation and the source authorities

• Send a final-notice email to the app’s official support, referencing the ticket ID, the failure type, and the days elapsed, stating you’ll escalate.
• For the underlying document, go to the source authority directly: UIDAI for Aadhaar issues (mobile update, DOB/address correction, locked Aadhaar), the Income Tax portal for PAN, your bank for CKYC/account-name reconciliation.
• If the app is holding a verified, KYC-clean account hostage (refusing to verify a clearly valid identity, or refusing to release a recoverable balance), that’s a service-deficiency matter: the National Consumer Helpline 1915 and the consumer-forum route apply, the same escalation logic as the KYC account recovery hub.
• If you suspect fraud — a fake “KYC support agent” asking for your OTP/PIN, a clone app harvesting documents — report to cybercrime 1930 and cybercrime.gov.in immediately, and stop sharing anything.

Honest limit of this ladder: it’s powerful when your documents are clean and the app or your government record is the blocker — UIDAI fixes a wrong Aadhaar, a regulator/consumer forum pressures a deficient app. It’s weaker against a shady or offshore app that simply ignores you, because that operator may sit outside Indian reach. That asymmetry is the strongest argument for only verifying on a clearly legal, licensed platform in the first place.

What passing verification actually unlocks — and the tier trap

A lot of confusion comes from thinking KYC is one binary switch. It isn’t. There are tiers of verification, and an app can let you in at a low tier — enough to deposit and play — while quietly holding back the full verification you need to withdraw. So you “passed KYC,” yet the payout still won’t release. Understanding the tiers stops you from chasing the wrong fix.

The clearest analogy is the CKYC account types, which mirror how RMG apps tier verification. CERSAI itself defines a “Normal” account built on a core OVD, a “Simplified” account, and a “Small” account that needs only personal details and a photo but carries strict transaction limits. RMG apps run the same logic:

• Low-tier / provisional. You signed up with minimal details — maybe just a phone number and basic info. Enough to deposit and play small, but not enough to withdraw cash. Many users hit their first wall here and read it as “verification failed” when it’s really “verification incomplete.”
• Full / cash-out tier. A complete OVD-based identity (PAN + Aadhaar, name matching your bank), which is what unlocks real withdrawals. This is the tier the whole seven-failure map above is about getting you to.

The tier trap looks like this: you deposited and played fine for weeks, so you assume you’re verified — then your first withdrawal triggers the full check, which fails, and it feels like the app suddenly broke. It didn’t. You were on the low tier all along, and the cash-out is the moment the full check runs. This is identical to the pattern on the 3 Patti withdrawal page, where the cash-out — not the deposit — is when KYC is enforced. The fix is to complete the full OVD-based verification proactively, ideally via DigiLocker, before you ever try to withdraw, so the cash-out clears instantly instead of stalling in a sudden manual review.

Why doing full KYC early is the smart play

Completing full verification the day you sign up — not the day you try to cash out — has three concrete payoffs. First, a clean, verified account auto-approves small payouts instead of routing them to manual review, so your money moves in seconds rather than days. Second, you discover any document problem (stale address, wrong DOB, dead Aadhaar mobile) while you have time to fix it at the source, instead of under pressure with a winning balance trapped. Third, a verified account gives you full RBI leverage if a payout later stalls for a payment-rail reason — because the app can’t claim “incomplete KYC” as a stalling excuse. Front-loading the verification turns the single most common cause of a stuck first payout into a non-event.

Scam patterns that ride on “verification problems”

Verification trouble is bait. Scammers know a frustrated user trying to pass KYC will do almost anything, so they impersonate “verification support.” Recognise these patterns — they change your whole strategy from fix to report:

• “Send your Aadhaar/PAN/selfie to this WhatsApp number to verify.” Real KYC happens inside the app’s secured flow, never in a personal chat. Anyone collecting your documents over WhatsApp is harvesting them, not verifying you.
• “Share the OTP to complete verification.” No legitimate verification ever asks you to read an OTP to a human. The OTP goes into the app, never to a person. An OTP request over a call is the single clearest scam tell.
• “Pay a ₹X ‘KYC fee’ / ‘verification charge’ to unlock your account.” KYC is free. No legal app charges you to verify your identity. A “verification fee” is theft.
• “Deposit ₹X to activate verified withdrawals.” No legal app requires a deposit to verify or to withdraw — and post-PROGA, a new deposit into a money game is also illegal. This is the clearest theft pattern there is.
• A “customer care number” from a random website, YouTube comment, or search ad. Most legal apps have no public phone helpline and route support in-app. Numbers posted publicly are overwhelmingly scam lines built to phish your OTP and PIN. Report them to 1930 / cybercrime.gov.in.
• A “mod” or “unlimited chips” APK that asks for KYC. A sideloaded clone can harvest every document you upload. Only verify inside an app from its official source.

If you hit two or more of these, stop verifying, document everything, and report — the problem isn’t your ID, it’s that you’re on or talking to something malicious.

Quick-reference: source authorities for fixing your record

When the fix is “correct the document at source,” here’s exactly which door to use. Bookmark this — it’s the whole source-fix map in one block.

The pattern across that table is the thesis of this whole page: you fix your government record at the government source, and you fix capture problems by sending a cleaner input. The app sits in the middle and just reports what it sees. Once you internalise that split, almost every “verification failed” message tells you which of the two doors to walk through.

Related fixes (go deeper on your exact case)

This page is the identity-and-document spoke. For neighbouring cases, these go step-by-step:

• The KYC hub for any account-recovery block → KYC account recovery — the master flow for a verification or account-access wall.
• A KYC that’s outright rejected → Teen Patti KYC rejected — the rejection-specific reasons and the name/DOB cross-match fixes.
• A PAN-card-specific failure → PAN card verification on gaming apps — the PAN format, linkage, and 194BA-reporting angle.
• Verified but the payout is stuck → 3 Patti withdrawal stuck — the Day-0-to-30 escalation ladder for money that won’t come out once you’re verified.

FAQ

1. Why does my gaming app keep saying “ID verification failed”? Usually it’s a capture problem, not an identity one. The four most common causes, in order, are a dark or glared selfie failing the liveness/face-match check, a blurry document photo failing OCR, an Aadhaar OTP going to a number no longer linked to your Aadhaar, and a name/DOB mismatch across documents. Re-submit a clean input — ideally a DigiLocker-fetched document — in even light, and roughly 7 of 10 of these clear on the first clean attempt.

2. Why does my selfie / liveness check keep failing? Almost always lighting. The face-match engine — tightened by UIDAI to reduce spoofing, which made it stricter on low-light and tilted images — can’t read a face in shadow. Face an even light in front of you (never a window behind you), remove glasses and any face covering, wipe the lens, hold the phone at eye level about an arm’s length away, and let it detect a natural blink. If it still fails after 3 clean tries, switch to a video-KYC session with a live agent.

3. What is V-CIP and why does my video KYC keep dropping? V-CIP (Video-based Customer Identification Process) is RBI’s live video-verification method, defined in the KYC Master Direction amended 4 January 2024. It needs a stable connection, your location turned on (the recording must be geo-tagged with live GPS), no VPN (RBI requires it to block IPs outside India), good light, and a live agent available. The fix is the 8-point pre-flight: Wi-Fi on, VPN off, location on, good front light, lens wiped, original ID in hand, permissions pre-granted, during agent hours.

4. My Aadhaar OTP never arrives — what do I do? The OTP goes only to the mobile number linked to your Aadhaar. If that number is one you no longer use, the OTP lands on a dead SIM. Update your Aadhaar-linked mobile at an enrolment centre — there’s no remote shortcut, because UIDAI requires an in-person mobile update. If the number is correct, wait the full delivery window, check you have signal, and request one resend (don’t spam it). Or skip OTP entirely and fetch Aadhaar via DigiLocker.

5. What is the Aadhaar offline XML and why does it fail? It’s a digitally signed, machine-readable XML file from UIDAI, protected by a “Share Code” you set when generating it. The 3 common failures: a wrong Share Code (re-enter it exactly, or regenerate), a stale file (some apps want a freshly generated one), and uploading the unzipped contents instead of the ZIP. Upload the ZIP exactly as downloaded. The XML is valid for a lifetime, but DigiLocker is cleaner because it skips the loose-file dance.

6. Should I use DigiLocker instead of uploading photos of my documents? Yes, almost always. DigiLocker delivers a digitally signed “equivalent e-document” with the same legal validity as the original, and RBI authorises regulated entities to accept DigiLocker OVDs. Because there’s no photo and no OCR, it removes the blur/glare/crop failure class entirely. It fixes 3 of the 7 failure types at once (Aadhaar XML, address proof, document quality) plus improves face-match. The only thing it can’t fix is wrong data on your underlying record.

7. My address proof keeps getting rejected — which documents actually count? Only an OVD (Officially Valid Document) counts, and there are just 6 of them: passport, driving licence, proof of possession of Aadhaar, Voter ID, NREGA job card, and an NPR letter. A mobile bill or credit-card statement is not an OVD. The simplest valid address proof is your Aadhaar, which proves identity and address together — fetch it from DigiLocker. If your Aadhaar address is outdated, update it at UIDAI first; no document with a stale address will pass.

8. The app blocked me for being underage but I’m an adult — what now? The app reads the date of birth on your verified ID, so a block means a document shows a DOB under 18. If you’re genuinely an adult, your Aadhaar or other ID has the wrong DOB — correct it at UIDAI (which permits one DOB update with valid proof), then re-verify. The app can’t override your government record; you fix the record. If your DOB is right and you’re still blocked, raise a support ticket with a clear DOB document. If you’re actually under 18, there is no legitimate fix — RMG is closed to minors by law.

9. Why does the app say “document not clear” when my card looks fine to me? The app’s OCR has to read the text, and a card that looks fine to your eye can still defeat it. There are 8 image problems that break OCR — the top ones are glare on the lamination across the data line, blur from a moving hand, a cropped edge, and compression from a forwarded image. Re-scan the full document, flat, in even light, with flash off, using the original (not a WhatsApp-forwarded copy). Better still, fetch it from DigiLocker, which has 0 OCR steps to fail.

10. What is CKYC and can it save me from re-verifying? CKYC is a centralised KYC record managed by CERSAI; finishing KYC once gets you a 14-digit CKYC number usable across all RBI/SEBI/IRDAI/PFRDA-regulated institutions. If a payment partner behind the app can pull your existing CKYC record by number or PAN, you may not need to re-do the whole selfie/document flow. The catch: your CKYC record carries whatever data you submitted, so if your address or name has since changed, a stale record fails the cross-match. Check whether you have one before re-verifying from scratch.

11. Is my data safe when I do KYC on a gaming app? A legitimate app captures and stores KYC inside an encrypted, India-hosted flow — RBI’s V-CIP norms require end-to-end encryption and data stored on systems located in India. The danger isn’t the compliant flow; it’s the scam version. If anyone asks you to send documents or a selfie over WhatsApp, read an OTP to a person, or pay a “KYC fee,” that’s fraud — real verification never does any of those. Report it to 1930 / cybercrime.gov.in.

12. A “KYC support agent” asked for my OTP to verify my account — is that normal? No — it’s a scam, full stop. An OTP goes into the app, never to a human, and no legitimate verification ever asks you to read one aloud. Anyone requesting your OTP or UPI PIN over a call or chat is trying to take over your account or empty it. Hang up, don’t share anything, and report the number to the cybercrime helpline 1930 and cybercrime.gov.in.

13. Do I have to pay any fee to complete KYC? No. KYC is free, by law and by every legal app’s design. The number of legitimate fees to complete identity verification is 0. A demand for a “KYC fee,” “verification charge,” or “deposit to activate withdrawals” is a theft pattern — and post-PROGA a new deposit into a money game is also illegal. If you’re asked to pay even ₹1 to verify, stop and report it to 1930.

14. Can I still verify and recover my balance from a discontinued cash app after PROGA? Yes for recovery, no for new play. PROGA 2025 (Rules in force 1 May 2026) banned online money games, but operators and banks kept the withdrawal/recovery flow open for verified accounts. So you still must pass KYC to release a stranded balance — complete it cleanly via DigiLocker, expect the usual checks, and never deposit again to “unlock” anything, because that deposit is now illegal. The verification fixes on this page apply the same way to a recovery KYC.

15. I’ve tried everything and it still won’t verify — what’s my last resort? Climb the ladder: a single clean re-submit (Day 0), an in-app ticket demanding which check failed (Day 1–3), an explicit request for a live-agent V-CIP session (Day 4–7), then a final-notice email plus source-authority fixes (Day 8–14) — UIDAI for a wrong Aadhaar, your bank for CKYC, the National Consumer Helpline 1915 if the app is holding a clean account hostage. If the app is an offshore or clone operator that simply ignores a valid identity, your leverage is limited — which is the strongest reason to only verify on a clearly legal, licensed platform.

Sources & method. The verification rules, timelines and document standards on this page are built from primary regulatory and government sources — not personal KYC tests. Key references: the RBI Master Direction on KYC and its V-CIP FAQs (V-CIP provisions amended 4 January 2024); RBI V-CIP norms on live interaction, geo-tagging, liveness, India-only IP, and end-to-end encryption; UIDAI guidance on Aadhaar face-authentication capture and lighting and stricter low-light face matching; UIDAI on Aadhaar Paperless Offline eKYC (XML / Share Code) and registered-mobile OTP delivery; DigiLocker as RBI-accepted, IT-Act-equivalent e-documents and DigiLocker/CKYC in KYC flows; the OVD list and CKYC 14-digit identifier via CERSAI and CKYC reuse across regulated institutions; the Promotion and Regulation of Online Gaming Act, 2025; and fraud reporting at cybercrime.gov.in / helpline 1930 and the National Consumer Helpline 1915. This page is information, not legal or financial advice — verify each step against your operator’s current Terms, UIDAI, and your bank’s KYC policy.