Skip to content

Published services, current details, and clear categories.

Explore APIs

Passport OCR API

Read an uploaded passport image and get the biographic page back as structured fields, including the machine-readable zone where the document carries one.

Consent capturedpurpose · travel document checkcns_7dK2QpPASSPORTone-time codeissued to the applicantpassport_numberZ1234567FILE CLEARED***read from the machine-readable zone
Request and response

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

You send

A passport image or scan uploaded by the holder, or captured inside your own onboarding flow

You receive

Structured identity and document fields read from the biographic page, including the machine-readable zone where present

Coverage
Passport booklets presented in India; readable output depends on the image and the document layout
Typical users
Banks and NBFCs, forex and remittance desks, travel and hospitality platforms, overseas staffing agencies, insurers
Coverage note
Available fields vary by image quality, document layout and data source. A reading captures the document; it does not verify identity.
Overview

What you can do with the Passport OCR API

Passport OCR reads an uploaded passport image and returns the details printed on the biographic page as structured fields. That includes the machine-readable zone where the document carries one. It removes the step where a person opens a photograph of a booklet and retypes what it says. Onboarding, travel, forex and staffing teams collect passports as phone photographs, and every retyped number can introduce an error that shows up much later. Which fields are available in any response varies with image quality, the document layout and the underlying data source. A passport is sensitive personal data. Collect it with the holder's consent and a stated purpose, and use the reading only for that purpose. Reading the document is a capture step, and it does not confirm that the passport is genuine.

  • Reads the MRZ where the booklet has one

    The MRZ is printed in a fixed international layout with check digits, which makes it the steadiest part of the page to read. Where a booklet is older, worn or cropped out of frame, the reading falls back on the printed text above it. The fields available vary by document and data source.

  • Biographic page fields instead of retyping

    Name, passport number, dates of birth, issue and expiry, nationality and other available attributes come back as data your form can fill. An operations team no longer reads a photograph and types what it sees.

  • Built for the images people actually send

    Passports arrive as phone photographs taken at a desk, in a car or under a ceiling light. The workflow is built around retries and correction. It never assumes a clean flatbed scan.

  • A capture step you can audit

    Keeping the submitted image alongside the structured reading gives a later reviewer both the source and the result. That is what a file needs when a decision made on it is questioned.

How it works

The five-step Passport OCR API workflow

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

Step 1

Ask the holder for the biographic page

The holder photographs or scans the full biographic page, with the machine-readable zone inside the frame, and uploads it through your application.

Step 2

Send the passport image to the API

Your application submits the uploaded file in a single request, as part of the onboarding, booking or intake journey.

Step 3

Read back what the service could recover

The response returns the identity and document fields that could be read. Available fields vary by image quality, document layout and data source.

Step 4

Let the holder fix what the image hid

Show the values that were read and let the holder correct anything the image obscured, before you commit the record.

Step 5

Carry the confirmed data forward

The confirmed fields fill your onboarding file, booking record or case, and you can keep the image alongside them for review.

Industries

Where teams use Passport OCR API

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

  • Banking

    Capture passport fields when a passport is the identity document offered at onboarding

  • Forex and remittance

    Read traveler passport details during currency purchase and intake

  • Travel platforms

    Capture passport details for international booking and check-in

  • Hospitality

    Read foreign-guest passport details when a property must file a guest record

  • Staffing and overseas recruitment

    Capture candidate passport details for deployment paperwork

  • Insurance

    Read passport fields on travel and expatriate policy proposals

What is Passport OCR?

Passport OCR reads a passport image so the details printed on the biographic page arrive as structured data instead of being typed in by hand. The page carries a name, date and place of birth, passport number, nationality, dates of issue and expiry, place of issue and a photograph. Most current booklets also carry a machine-readable zone along the foot.

Passports today mostly arrive as photographs taken on a phone. Someone opens the image and retypes what it says into a form. Passport OCR removes that retyping step.

How the Passport OCR API works

A passport OCR API lets your application send the uploaded image and receive the fields the service could read in a structured response. Document capture then happens inside the same journey as the rest of the form.

The usual alternative is a queue. Images collect, an operations team works through them, and the applicant waits. Reading the document in the flow can shorten that wait and remove the transcription slips a queue produces.

The machine-readable zone on a passport

The machine-readable zone, or MRZ, is the block of uppercase characters and chevrons set at the foot of the biographic page in a fixed international layout. That fixed layout makes it the steadiest part of the page to read.

The MRZ repeats the passport number, surname and given names, nationality, date of birth, sex and expiry date in known positions. It also carries check digits. Those let you test a reading for internal consistency.

Not every document presented will have a usable zone. Older booklets, worn pages, glare and a cropped photograph can each leave it unreadable, and the reading then falls back on the printed text above it. Which fields are available in any response varies with the image, the document layout and the underlying data source.

Where Passport OCR fits across industries

  • Banks and NBFCs. A passport is one of the identity documents an applicant may present at account opening or a loan application. Capturing it correctly decides whether the file moves forward or comes back for correction.
  • Forex and outward remittance. Currency purchase and remittance intake starts from the traveler's passport, and the desk records the number, name and expiry against the transaction.
  • Travel platforms and airlines. International booking and check-in flows collect passport details. A mistyped number surfaces at the airport, long after the sale.
  • Hospitality. Properties hosting foreign guests must record and file guest details soon after arrival, and reading the passport at the desk supports that filing.
  • Staffing and overseas recruitment. Deployment paperwork for candidates traveling for work depends on passport details being right the first time.
  • Insurance. Travel and expatriate proposals capture passport data as part of the application.

How to read a passport document online

Reading a passport online changes who does the keying. The decision still sits with your team. Four choices shape the flow before any code is written:

  • where in the journey you ask for the document
  • what the capture screen looks like on the phone in the holder's hand
  • who may open the stored image afterwards
  • how long you keep it

The last two are policy questions rather than engineering ones, and they are the ones teams postpone. Settling access and retention before launch costs far less than fitting them onto a store that already holds thousands of passport images. It is also the part a reviewer asks about first.

Building the passport step into your journey

Treat the response as a draft the holder confirms. A confirmation screen costs one tap and catches the glare and the cut-off corner. That is far cheaper than finding a wrong passport number after a booking has gone out.

Plan the second attempt as carefully as the first. Telling the person what went wrong, such as a cropped page or a zone washed out by flash, lifts capture rates on its own.

Keep the image and the structured reading together, because a later reviewer needs both what was read and what it was read from. Which document types are supported, and what checks accompany the reading, depend on the service contract you choose.

A passport is personal data, and for many people it is the most sensitive document they hold. Collect the image only where you have a stated, lawful reason to. Tell the person what you are collecting and why, and take their consent before it leaves their device.

Use the reading only for the purpose it was collected for. Restrict access to the staff whose work needs it, and keep a record of who opened it. Retain the image and the extracted fields no longer than your policy and applicable law require.

Reading a passport is a capture step. You may also need assurance that the document is valid, or that the holder is the person presenting it. Pair the reading with the verification and liveness checks your risk policy calls for.

FAQ

Common questions

What teams ask before they integrate Passport OCR API.

An interface that accepts a passport image and returns the details printed on the biographic page as structured fields. Your application captures them directly. That removes the manual read-and-retype step.

Get started

Add Passport 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.