Skip to content
99tests Blog
Testing guides

How to Test Aadhaar eKYC in Your App: 40 Cases That Catch Real Failures

A practical guide to testing Aadhaar eKYC: OTP consent, masking, offline KYC, DigiLocker handoff, PAN name matching, liveness and video KYC on budget phones and weak networks.

Hand-drawn sketch of an ID card, a fingerprint, a phone and an OTP code with a tick
In this article
  1. What the flow covers
  2. Set up before you test
  3. 1. Happy path: prove each method works once
  4. 2. Validation and negative cases
  5. 3. Edge cases where genuine users get stuck
  6. 4. Interruptions and network
  7. 5. Device and OS
  8. 6. Security and privacy
  9. 7. Accessibility and language
  10. Where to start if you only have a day
  11. Get the full test case set

KYC is where a fintech, lending or investing app loses the most users who actually wanted to sign up. The code path usually works in the lab. What breaks is the real world around it: the Aadhaar OTP goes to a parent's phone, a budget Android kills the app while the user is in DigiLocker, the video KYC call drops in a lift, or the PAN says "R K Sharma" while Aadhaar says "Rajesh Kumar Sharma".

This guide walks through how to test Aadhaar eKYC end to end. It's based on the free Aadhaar eKYC test case set in the 99tests test case library: 40 cases across seven sections, each with steps, expected results, priority and whether it needs a real phone.

What the flow covers

A complete eKYC test plan should cover six parts of the journey:

  • Aadhaar OTP eKYC with consent and masking
  • Offline paperless KYC (where supported) and DigiLocker fetch
  • PAN verification and PAN-Aadhaar name matching
  • Selfie liveness and face match
  • Video KYC booking and call quality
  • Document capture from camera and gallery

Leave back-office review tools, lending decisions and periodic re-KYC for separate plans. They have different owners and different failure modes.

Set up before you test

Most eKYC test runs stall on setup, not on bugs. Have these ready first:

  • Sandbox identities from your KYC provider, including mismatch cases: different surnames, initials, single names, year-only birth dates.
  • Printed dummy ID cards with obviously fake details for camera and video tests.
  • The right phones: a 3–4 GB RAM Android with the maker's battery saver left on, a dual-SIM Android and an iPhone.
  • Jio, Airtel or Vi SIMs plus a Wi-Fi network you can switch off.
  • Video KYC test slots and a test agent who is available when you need them.

Never type the real Aadhaar or PAN of staff or friends into a test build. Keep negative inputs format-invalid so they can't belong to anyone.

1. Happy path: prove each method works once

Start by completing KYC once through every method the app offers:

  • Aadhaar OTP eKYC. Tick consent, enter the sandbox Aadhaar, enter the OTP. The app should show the fetched name, date of birth, gender and photo for confirmation, with the Aadhaar number masked.
  • Offline KYC with the ZIP file and share code, where supported. It should complete without asking for an Aadhaar OTP.
  • DigiLocker fetch. Sign in, allow the documents and wait for the redirect without tapping anything. The app should reopen on the KYC screen with documents listed. This one needs a real phone, because the handoff to the DigiLocker app or browser and back differs by phone.
  • PAN verification for the same identity.
  • Selfie liveness in good indoor light.
  • Video KYC. Book a slot, check the slot time shows in IST on both the confirmation and the reminder, then join from the reminder.
  • Document upload from the in-app camera.

2. Validation and negative cases

These are cheap to run and catch embarrassing bugs:

  • Aadhaar with 11 digits, with a 13th digit typed, and with one digit changed. No OTP should be sent for the mistyped number.
  • Consent unticked by default, with Get OTP blocked until it's ticked. Treat this as P1.
  • Wrong OTP until the attempt limit, then check that neither Resend nor the correct OTP bypasses the block.
  • Wrong share code, then a photo renamed to .zip, in offline KYC. The app shouldn't crash.
  • PAN in the wrong format, too short, or typed in lowercase.
  • A clear PAN-Aadhaar surname mismatch. KYC must not be marked verified, and the user should see a next step.
  • A selfie that doesn't match the Aadhaar photo. There should be a retry and a fallback such as video KYC.

3. Edge cases where genuine users get stuck

This section is where real users get pushed into manual review or drop off:

  • Minor name differences: initials versus full names, extra spaces, dots, "Mr", letter case. Each variant should get a consistent outcome on repeat runs, following the product's written matching rules. Get those rules written down before testing.
  • Single-name users with no surname. No field should force them to invent one.
  • Date of birth shifting by a day when the phone's time zone is outside India, and year-only records. A one-day shift fails the PAN match.
  • The Aadhaar-linked mobile is a family member's phone. The screen should say the OTP went to the Aadhaar-linked number, not the login number.
  • The same Aadhaar used on a second account.
  • Resuming KYC hours after leaving midway.
  • Liveness in low light, with glasses or a cap or dupatta. The app should give a specific hint, not a generic failure.

4. Interruptions and network

In the field, this is where most eKYC journeys fail:

  • A delayed Aadhaar OTP SMS in a basement, then Resend.
  • Leaving to read the OTP on a Xiaomi, Realme or Vivo phone with default battery settings. The OTP screen should still be there, or reopen on the OTP step without restarting consent.
  • Network lost right after submitting the OTP. Retry should show the result the server already recorded.
  • Coming back from DigiLocker after the system killed the app on a 3–4 GB RAM phone. This is P1. Landing on the home screen with the result lost is a common failure.
  • Locking the screen or taking a call during liveness.
  • A video KYC call moving from Wi-Fi to mobile data, or dropping to 3G in a lift. The user should be able to rejoin the same session without booking a new slot.
  • An ordinary phone call during video KYC.

None of these can be reproduced faithfully on an emulator. Emulators feed a virtual camera and don't kill apps the way budget Android phones do.

5. Device and OS

  • OTP auto-read with the Aadhaar-linked number in SIM 2, then SIM 1.
  • Returning from the system camera on a low-RAM phone without losing the captured image.
  • Picking an ID image from the gallery on Android 13+, older Android and iPhone, including "selected photos only" access.

6. Security and privacy

All of these deserve P1 attention:

  • Aadhaar shown only masked (XXXX XXXX 1234) everywhere: confirmation, profile, summaries, notifications and emails.
  • Screenshots blocked, and KYC details hidden in recent apps, including the maker's own screenshot gestures.
  • An edited offline KYC XML rejected as tampered.
  • Liveness spoofing with a printed photo or a video replayed on another phone.
  • Shared family phones: after logging out, the next account sees none of the previous user's KYC data.
  • Selfies and ID captures kept out of the phone gallery.

7. Accessibility and language

  • TalkBack and VoiceOver through consent, Aadhaar entry, OTP and confirmation. The masked number should be read as "ending in 1234", not as a string of X's.
  • The largest font and display size on consent, OTP, PAN and slot booking screens.
  • Consent and buttons in Hindi, and Devanagari or Hinglish name entry.

Where to start if you only have a day

If time is short, run the P1 cases first: OTP eKYC, DigiLocker fetch and return, PAN match and mismatch, liveness, video KYC network switching, masking, tampered XML, spoofing and shared-phone logout. Then run the interruption cases on a budget Android with its battery saver on. That's where your conversion drops.

Get the full test case set

The complete Aadhaar eKYC test cases are free to use. They include steps and expected results for all 40 cases, the real-device reasons, and an FAQ. You can copy them into your test management tool.

If you'd rather have the real-phone cases run for you, 99tests runs exploratory testing sessions on real Android phones and iPhones across Indian cities and networks. Packages start at ₹9,999 + GST, with a bug report in 3 business days.