PAN Verification: How to Check a PAN Card’s Validity and Match It to a Name

PAN verification confirms three things: that the PAN number exists in the Income Tax Department’s records, that the name and date of birth entered match what’s on file for that PAN, and whether the PAN’s status is active or not. A PAN’s status shows as either “Active/Operative”, meaning valid with the name and date of birth matching Income Tax Department records, or “Inoperative.”

One thing that makes a PAN inoperative: unlinked PANs that weren’t connected to Aadhaar by the deadline became inoperative from 1 July 2023, per a CBDT circular. Another: holding more than one PAN is prohibited under the Income Tax Act, so where a person is found to hold multiple PANs, the duplicate or improperly issued ones get deactivated.

Every PAN’s fourth character identifies the category of holder it belongs to, under Section 139A of the Income Tax Act. That single letter tells you, at a glance, whether you’re looking at an individual’s PAN or an entity’s.

For how a related identity number is checked, see how Aadhaar verification works.

Individual, one-off checks use the e-Filing portal above. Businesses that need to verify PAN as part of onboarding, and government-linked bodies that need to verify PANs in bulk, use a system the Income Tax Department has built for scale.

The Income Tax Department has authorised Protean eGov Technologies Limited to enable authorised agencies, including RBI, banks, and RBI-approved NBFCs, to run online PAN verification. According to Protean’s own description of the service, it supports three methods: screen-based verification for single PANs, file-based verification for bulk PAN validation, and API-based verification for integration into business applications. This three-way split is Protean’s own terminology, not an official Income Tax Department classification. API-based verification, specifically, validates a customer’s PAN in real time against authoritative sources and returns standardised responses for name, status, and other permitted attributes.

Separately, the Income Tax Department runs its own bulk PAN/TAN verification service, available only to external agencies (Central Government, State Government departments/undertakings, and recognised autonomous bodies) registered on the e-Filing portal. The process works off a CSV template covering up to 100 records per submission, with fields for PAN number, name components, date of birth or incorporation, gender, and organisation name. That CSV is converted to JSON for upload, the system generates a token or transaction ID, and results come back as a downloadable CSV comparing the submitted data against the CBDT database.

This mirrors how businesses handle other bulk-verification needs: see GST verification and GSTIN checks for the equivalent process on the GST side.

“PAN verification failed” on the EPFO UAN portal

A commonly reported cause is a name mismatch between the name recorded against the UAN/EPFO and the name on record with the Income Tax Department for that PAN. The two systems don’t always talk to each other cleanly, so a failure can happen even without an actual name mismatch, purely because integration between the two systems isn’t seamless.

To fix a name mismatch, EPFO subscribers can submit an EPF Joint Declaration Form (listing both the incorrect and correct name) through their employer, or raise a grievance via the EPFiGMS portal under “KYC Related Issues of Subscriber Pertaining PF Office.”

PAN vs Aadhaar

These are separate identifiers from separate authorities: PAN is issued by the Income Tax Department for tax purposes, Aadhaar by UIDAI as a biometric-based identity number. PAN-Aadhaar linking is a distinct process from PAN verification. It cross-references the PAN registry against the Aadhaar repository and checks consistency of name, date of birth, and gender across the two records.

Rule 114B of the Income Tax Rules, 1962, in effect since 1 November 1998 and amended over time, requires quoting PAN for a specified list of financial transactions: cash deposits with a bank or co-operative bank exceeding ₹50,000 in a day, purchase of bank drafts, pay orders, or banker’s cheques in cash exceeding ₹50,000 in a day, motor vehicle sale/purchase, opening bank accounts, applying for credit/debit cards, opening demat accounts, life insurance premium payments above ₹50,000, and sale/purchase of immovable property above ₹10 lakh.

Where someone doesn’t have a PAN, Form 60 can be furnished as a declaration in lieu of PAN for these Rule 114B-covered transactions, under specified conditions.

PAN and PF/EPF withdrawal

PAN matters for EPF withdrawal specifically through TDS treatment, not as a blanket requirement for withdrawal itself. Under Section 192A, TDS applies where continuous service is less than 5 years and the withdrawal amount is ₹50,000 or more. The rate is 10% if PAN is submitted without Form 15G, 20% if neither PAN nor Form 15G is submitted, and nil if Form 15G is validly submitted and eligibility conditions are met. Without a PAN, the higher TDS rate applies and Form 15G can’t be used to avoid TDS. There is no source confirming PAN as an absolute precondition for EPF withdrawal outside this TDS-rate context, so treat “PAN required for PF withdrawal” as scoped to the tax-deduction rate, not withdrawal eligibility itself.

For regulated entities, PAN verification isn’t a standalone check. It’s one input into a broader due-diligence process. Under the RBI’s KYC Master Direction framework, regulated entities (banks, NBFCs, payment banks, small finance banks) require PAN or Form 60 in addition to an Officially Valid Document (OVD) as part of customer due diligence, and are expected to query the Central KYC Registry (CKYCR) using the customer’s PAN, Aadhaar, or CKYC Identifier Number before running fresh KYC. Regulated entities, including NBFCs, must upload CKYC records to CERSAI within 3 working days of account opening.

Vendor reporting indicates that on 28 November 2025, RBI consolidated its regulatory instructions into 238 Master Directions, including ten sector-specific KYC Master Directions, with the standalone 2016 KYC Master Direction repealed and NBFCs now referring to a dedicated NBFC KYC Direction. This specific consolidation detail comes from a secondary vendor summary rather than a primary RBI text, so treat it as reported rather than independently confirmed.

PAN verification typically sits alongside other document and identity checks in a digital onboarding flow: see how this connects to eKYC and digital KYC verification more broadly.

Why the same PAN can fail verification in two different systems

Read together, the EPFO name-mismatch problem and RBI’s CKYCR-query requirement point to the same underlying issue: PAN verification is only as reliable as the record-matching behind it, and different government and regulatory systems don’t always hold identical name records for the same person. The EPFO “PAN verification failed” error can occur purely from a lack of integration between UAN/EPFO records and Income Tax Department records, without any actual mismatch. This suggests a “failed” verification result doesn’t always mean the PAN itself is invalid; it can mean a name mismatch between the two systems, or simply that the two systems aren’t well integrated. For a regulated entity running CKYCR queries against PAN, Aadhaar, or a CKYC Identifier Number, the practical implication is that PAN verification is one data point in a due-diligence chain, not a single pass/fail gate.