Skip to content

Published services, current details, and clear categories.

Explore APIs

Voter ID OCR API

Read an uploaded voter ID image and get the printed name, EPIC number, relation name and address back as structured fields instead of typing them in.

Consent capturedpurpose · electoral roll checkcns_7dK2QpELECTOR PHOTO IDXYZ1234567one-time codeauthorises the roll lookupepic_numberXYZ1234567ON THE ROLL***part 042 · section 7
Request and response

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

You send

A voter ID (EPIC) card image or PDF page, including the reverse where the address is printed there

You receive

Structured name, EPIC number, relation name, gender, age or date of birth and address fields

Coverage
Voter ID (EPIC) cards issued in India, across the layouts and scripts the reader supports
Typical users
Lending, fintech, staffing, logistics, real estate and telecom onboarding teams
Coverage note
Reads the printed card; the details are not checked against the electoral record
Overview

What you can do with the Voter ID OCR API

Voter ID OCR reads an image of an Elector's Photo Identity Card, commonly called a voter ID or an EPIC card. It returns the details printed on it as structured fields. It is one of the few widely held Indian documents that carries a full residential address in printed form. That makes it a practical capture document where a journey needs an identity and an address together. The response may carry name, EPIC number, relation or guardian name, gender, age or date of birth, and the address block with its components. The fields you get back vary with the data source and with the individual record. Card layout, regional-script printing and the age of the card all change what can be read. OCR reports what appears on the supplied image. It does not establish that the card is genuine, and it does not check the details against the electoral record.

  • Identity and address from one document

    The voter ID is one of the few widely held Indian documents that prints a full residential address. A single capture can serve both the identity and the address side of an onboarding form. What the response carries varies by data source and by record.

  • Handles the variety these cards come in

    Cards issued in different years and different states differ in layout, and many print the holder's details in a regional script alongside or instead of English. What can be read from a Devanagari, Bengali, Tamil or Telugu printing may differ from an English one.

  • Address block and its components

    The reader can return the printed address block along with the components it manages to identify, such as house, locality, district, state and postal code. Components are the part most likely to come back partial. Keep the raw block alongside them for confirmation.

  • Stops short of the electoral record

    OCR reports what appears on the supplied image. It cannot tell you that the card is genuine or still current, and it does not test the details against the electoral record. Pair it with a verification service where the decision needs assurance.

How it works

The five-step Voter ID OCR API workflow

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

Step 1

Capture the front, and the back for an address

The applicant photographs or uploads the card inside your app, agent tool or web journey, with consent recorded. If the address is your reason for reading it, capture the reverse as well.

Step 2

Submit both images together

Your application sends the captured images in one request. Accepted formats and size limits are set by the selected service contract.

Step 3

Get the identity and address fields

The printed details that could be read come back as labeled fields, with the address returned as a block and as the components that could be identified.

Step 4

Confirm the parsed address

Show the parsed address back to the applicant. They can fix a missing line or an abbreviated district while they are still in the journey.

Step 5

Move the details into KYC or induction

Pass the confirmed details into your onboarding, KYC or induction workflow, keeping what you captured separate from anything a verification service later confirms.

Industries

Where teams use Voter ID OCR API

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

  • Lending and NBFCs

    Capture identity and address in small-ticket and rural lending

  • Fintech and PSPs

    Fill a signup form from a photographed card instead of typing

  • Staffing and gig platforms

    Enroll riders and field workers at the doorstep

  • Logistics and fleet

    Record driver identity and address details at induction

  • Real estate

    Capture tenant details during rental document collection

  • Telecom

    Capture subscriber identity and address at doorstep activation

What Voter ID OCR does

Voter ID OCR reads an image of an Elector's Photo Identity Card, the EPIC card most people simply call a voter ID. It returns the details printed on it as structured fields.

The voter ID is one of the identity documents Indian applicants are most likely to have to hand. It is also one of the few that carries a full residential address in printed form.

That makes it a practical capture document for journeys needing an identity and an address together. It matters most outside the metros, and for applicants who hold neither a passport nor a driving license.

What Voter ID OCR does not check

What comes back is a reading of the file you supplied, and nothing beyond it. Whether the card is genuine, whether it is still current, and whether the elector record agrees with it are all questions this step leaves open.

Keep that boundary visible inside your own systems. Capture with OCR, confirm with a verification service where the decision needs assurance, and store the two results as separate facts. A reviewer should never mistake a reading for a check.

Fields printed on an EPIC card

The card prints a name, an EPIC number, a relation or guardian name, gender, age or date of birth, and an address. Which of them the response carries varies by data source and by record.

Card design is the complication. Layouts differ by issue year and by state, the script differs by region, and on newer cards the address has moved to the reverse.

So a correction step belongs inside the flow. Expect a response that comes back complete for one applicant and partial for the next.

Capturing the right side of the card

Capture the side that carries what you need. If the address is your reason for reading the card, the reverse is not optional.

Beyond that the usual rules apply: the whole card in frame, reasonable focus, even light, and no direct glare on the lamination these cards almost always carry.

Older cards are frequently faded or hand-laminated. Build a retake prompt into the capture screen, and expect to use it more often than with a freshly issued document.

Who reads a voter ID at onboarding

  • Lending and NBFCs. Capture identity and address where the voter ID is the document the applicant actually has, which is common in small-ticket and rural lending.
  • Fintech and payment service providers. Fill a signup form from a photographed card instead of asking for a long address to be typed on a phone.
  • Staffing and gig platforms. Enroll delivery riders and field workers at the doorstep, where a voter ID is often the only document in the wallet.
  • Logistics and fleet. Record driver identity and address at induction, alongside the license checks the role itself requires.
  • Real estate. Capture tenant details during rental document collection, where an address proof is the point of the exercise.
  • Telecom. Capture subscriber identity and address at doorstep activation, where the address on the form has to match the document the agent is holding.

Why an Indian address is hard to parse

An Indian address on a printed card is rarely a tidy set of lines. It runs past the field boundaries, abbreviates a district, omits a state, or carries a landmark where a street name should be.

A reader can return the block along with the components it manages to identify, such as house, locality, district, state and postal code. The components are the part most likely to come back partial.

Design for that. Show the parsed address for confirmation, let the applicant fix a line, and keep the raw block alongside the components so nothing is lost in the parse.

Handling partial reads and retakes

Read the card at the point of capture, while the applicant can still retake the photograph. Treat a partial response as ordinary and send it to a short correction screen.

Keep a small human queue for cards that cannot be read, and watch which layouts land in it. A regional format that keeps reappearing in the queue is usually a capture-guidance problem. A line of on-screen help fixes it more cheaply than a reviewer does.

The selected service contract states which formats and file sizes you can send.

Everything printed on this card is personal data, and the residential address is the most sensitive part of it. Read it only for a purpose you have stated, with the applicant's consent on record.

Restrict who can open the raw image, log access, and retain the file only as long as your policy and the rules applying to your business allow.

Never use the constituency and electoral context printed on the card for anything beyond the identity or address check the applicant agreed to. Write that limit into your own policy explicitly.

FAQ

Common questions

What teams ask before they integrate Voter ID OCR API.

An interface that accepts an image of a voter ID (EPIC) card and returns the details printed on it as structured fields. Your application fills an identity and address form from the document instead of asking someone to type it in.

Get started

Add Voter ID 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.