Skip to content

Published services, current details, and clear categories.

Explore APIs

PAN Card OCR API

Read an uploaded PAN card image and get the printed name, PAN, date of birth and parent name back as structured fields. Your onboarding, lending or vendor workflow can use them directly.

Consent capturedpurpose · tax identity checkcns_7dK2QpPANABCDE1234Fone-time codeauthorises the record lookuppanABCDE1234FNAME MATCHED***five letters · four digits · one letter
Request and response

You confirm the required fields and consent steps with us during onboarding.

You send

A PAN card image or PDF page, captured or uploaded by the applicant

You receive

Structured name, PAN, date of birth and parent-name fields, where legible on the card

Coverage
PAN cards issued in India, across the older and current card designs the reader supports
Typical users
Lending, fintech, insurance, marketplace, staffing and finance operations teams
Coverage note
Reads the printed card; confirming the PAN against a source is a separate verification step
Overview

What you can do with the PAN Card OCR API

PAN Card OCR reads an image of a PAN card and returns the details printed on it as structured fields. The card can arrive photographed, scanned, or supplied as a page of a PDF. The PAN is the identifier most Indian financial workflows are built around. It appears on loan files, merchant applications, investment accounts, vendor masters and payout records. The response may carry the name as printed, the PAN itself, the date of birth, and the parent or guardian name on the card. Available fields vary by data source and by record, since card design, worn print and glare all change what can be read. OCR reports what is printed. It does not establish that the card is genuine or that the details match the issuing source. Capture with OCR, then confirm with a verification service where the decision needs that assurance.

  • The fields a finance workflow needs

    Name as printed, the PAN, date of birth and the parent or guardian name come back as labeled values. They are ready to map onto your application form or vendor master. The fields on offer vary by data source and by record, and worn or partly cropped cards may return fewer of them.

  • A shape you can check the PAN against

    A PAN has a fixed shape. A structural check on the value it returns catches many misreads early. A well-formed value is still only a reading, which is why a confirmation screen belongs in the flow.

  • Keeps keying errors out of payout records

    A mistyped PAN does not fail at capture. It fails months later at reconciliation, when a payout is held or a filing is rejected. Reading the card and confirming it at the point of capture keeps that error out of the record entirely.

  • Reads the card without vouching for it

    OCR reports what is printed on the supplied image and cannot tell a genuine card from a convincing forgery. Place it ahead of a verification step, never in place of one, and keep the two results distinct in your records.

How it works

The five-step PAN Card OCR API workflow

Our team walks you through the exact request and response for this service during onboarding.

Step 1

Photograph the PAN card

The applicant photographs or uploads the PAN card inside your app, web journey, agent tool or partner portal. Record the consent you have taken for that purpose.

Step 2

Upload the card to the API

Your own application sends the captured file. Which formats and file sizes are accepted depends on the selected service contract.

Step 3

Get the name, PAN and date of birth back

The details the reader could resolve come back as labeled values. Anything it could not read comes back marked as unread, never guessed.

Step 4

Check the PAN on screen

Show the read PAN and name back to the applicant or a reviewer. Character confusion in an identifier is the failure worth catching while the person is still present.

Step 5

Write the confirmed values to your records

Pass the confirmed values into onboarding, underwriting, vendor or payout records, and keep captured data distinct from anything a verification service later confirms.

Industries

Where teams use PAN Card OCR API

These sectors build the check into a decision they already make.

  • Lending and NBFCs

    Open a credit file from the card the applicant photographed

  • Fintech and PSPs

    Capture merchant details during digital merchant signup

  • Insurance

    Record proposer details at proposal and at high-value claim stage

  • Marketplaces

    Collect seller details before a payout account is activated

  • Staffing and gig platforms

    Capture contractor details for payout records

  • Real estate

    Capture buyer details for high-value transaction records

What PAN Card OCR does

PAN Card OCR reads a PAN card file and returns the printed details as structured fields your application can use directly. The card arrives as a photograph, a scan or a page inside a PDF.

The PAN is the identifier almost every Indian financial workflow is built around. It appears on loan files, merchant applications, investment accounts, vendor masters and payout records.

Collecting the card is easy. Getting the ten characters, the name and the date of birth off it accurately, at volume, without a person retyping them, is the part that costs time.

Does PAN Card OCR confirm the card is real?

No, OCR reports what is printed on the file you supply. It does not establish that the card is genuine, that it is current, or that the details match the record held by the issuing source. A convincing forgery reads just as cleanly as a real card.

So the reading step belongs before a verification step. Capture the fields with OCR, confirm them where the decision needs assurance, and keep the two results distinct in your records. A reviewer can then always tell captured data from confirmed data.

What the PAN card reading returns

The response may carry the name as printed, the PAN itself, the date of birth, and the parent or guardian name shown on the card. What comes back depends on the card and on what is legible. Which values you receive varies by data source and by record.

Older card designs, worn print, glare and partly cropped frames all change what can be read.

The fixed shape of a PAN helps here. A structural check on the returned value catches many misreads before they reach your database. A value that looks well formed is still only a reading.

Photographing a PAN card so it reads cleanly

Capture quality decides most of the outcome. The whole card inside the frame, reasonable focus, even light and no direct glare will read far better than a hurried snapshot across a counter.

The failure worth designing around is character confusion inside the identifier, because several letters and digits look alike in the fonts used on these cards. Show the read value back to the applicant for confirmation before a payout or a tax filing depends on it.

Where a PAN reading is used

  • Lending and NBFCs. Open a credit file from the card the applicant photographed. The file starts with structured fields instead of an image in a folder.
  • Fintech and payment service providers. Capture merchant details during digital merchant signup, where the PAN drives both the risk file and the settlement record.
  • Insurance. Read proposer details at proposal, and again where a high-value claim requires the identity to be recorded on file.
  • Marketplaces. Collect seller details before a payout account goes live. The tax record and the bank record then come from one source.
  • Staffing and gig platforms. Capture contractor details for payout and withholding records at signup.
  • Real estate. Read buyer and tenant details during document collection for high-value transactions.

Where the PAN sits in an onboarding flow

In most Indian journeys the PAN is the join key. The name on the card is the name your records should carry. The identifier is what later ties a customer to tax reporting, to a bank record, and to the verification services you run against them.

That makes an OCR error expensive in a particular way. It does not fail loudly at capture. It fails quietly months later at reconciliation, when a payout is held or a filing is rejected.

Confirming the value while the applicant is present is far cheaper than tracing it at reconciliation.

Running PAN capture at volume

Read the card immediately after capture, while the applicant can still retake a poor image. Treat a partly filled response as ordinary and route it to a short correction screen.

Keep a small human queue for cards that cannot be read at all. Some documents arrive in batches, from a channel partner or a bulk vendor-onboarding drive. Run them through the same path as single uploads.

The formats and size limits you can send are set out in the selected service contract.

Handling a PAN copy responsibly

This card is personal data, and the identifier on it is a tax number, which raises the stakes on where a copy ends up. Read it for a purpose you have stated to the applicant, with their consent on record. Keep the raw image behind an access control.

Log access, and retain the file only as long as your policy and the rules applying to your business allow. Avoid copying the identifier into systems that have no reason to hold it. Where a downstream team needs to recognize a customer but never has to file anything, an internal reference is usually enough.

FAQ

Common questions

What teams ask before they integrate PAN Card OCR API.

An interface that accepts an image of a PAN card and returns the details printed on it as structured fields. Your application fills a form from the document.

Get started

Add PAN Card OCR API to your workflow

Tell us how you plan to use it. Our team sets up API access, agrees your pricing and takes you through onboarding.