OEM/ODM since 2016 Exported to 100+ countries CE · FCC · ISO9001 · RoHS · IP65 24/7 technical support
Technical

ICAO 9303 Passport Readers: MRZ, OCR, RFID Chip Reading and SDK Integration Guide

By MHY Engineering Team · Updated

A passport reader looks simple: a slot or a glass plate, a green light, and a name appearing on a screen. Behind that moment are several distinct technologies, each with its own failure modes: optical character recognition of the machine-readable zone, contactless chip reading, image capture for visual checks, and the software that turns all of it into a record in your hotel, visitor or border-control system. This guide explains how an ICAO 9303 reader actually works, what to specify when you buy one, and how to integrate and test it so that it works on the thousandth document as well as on the demo passport. If you are still deciding which kind of reader suits your project, start with how to choose a passport and ID reader for self-service kiosks; this guide goes deeper into the standard, the chip and the integration.

1. What a passport reader actually reads

A travel document carries the same identity data in up to four places, and different readers use different ones:

  • The visual inspection zone (VIZ): the printed, human-readable data page: name, photo, dates, signature, document number. Full-page readers capture an image of it.
  • The machine-readable zone (MRZ): the two or three lines of capital letters, digits and "<" filler characters at the bottom of the data page, designed for optical reading.
  • The RFID chip: in an e-passport (and many national ID cards) a contactless chip stores the same data electronically, plus a digital photo, signed by the issuing state.
  • Security features: printing and materials that react to ultraviolet or infrared light, used for screening.

ICAO Document 9303 is the international standard that defines the layout of machine-readable travel documents and the chip data structure. A reader described as "ICAO 9303 compliant" is built around reading these zones; it does not by itself decide whether a document is genuine.

2. The MRZ: formats and check digits

The MRZ comes in three standard sizes, and a reader must handle all the document types you expect to see:

FormatLayoutTypical documents
TD32 lines × 44 charactersPassports
TD22 lines × 36 charactersSome ID cards and travel documents
TD13 lines × 30 charactersMost credit-card-size ID cards

Visas use similar two-line layouts (MRV-A at 44 and MRV-B at 36 characters). The MRZ holds the document type and number, the issuing state and nationality, the holder's name, date of birth, sex and expiry date. Crucially, it also holds check digits: one each for the document number, date of birth, expiry date and optional data, plus a composite check digit. Each is calculated by weighting characters 7, 3, 1 in repeating order and taking the sum modulo 10.

Check digits are the first line of defense against misreads. A good SDK validates them and flags a result as unverified when one fails, instead of silently passing "J0HN" for "JOHN". When you evaluate readers, ask whether the SDK returns the check-digit status per field, not just a pass/fail for the whole line.

3. OCR versus chip reading: speed versus authority

Reading the MRZ by OCR is fast, usually a fraction of a second to about a second once the document is in position, and works for every ICAO-style document, including those with no chip. But what OCR returns is a printed text that could, in principle, be a forged or altered page. The chip is different.

In an e-passport the chip is read over a contactless link (13.56 MHz, ISO/IEC 14443 Type A or B). Before the chip will answer, the reader must prove it has seen the document, which is why the MRZ read comes first:

  • BAC (Basic Access Control) derives a key from the document number, date of birth and expiry date taken from the MRZ.
  • PACE (Password Authenticated Connection Establishment) is the newer, stronger mechanism, also based on the MRZ (or a card access number printed on the document).

Once access is granted, the reader can read the logical data structure. The data groups most integrators use are DG1 (a copy of the MRZ data) and DG2 (the holder's digital face image, useful for face comparison with a live camera). Fingerprint and iris data groups are protected by additional mechanisms and are available only to authorized states; a commercial hotel or visitor reader should not expect them.

To trust the chip data, software performs passive authentication: it verifies the digital signature on the Document Security Object (EF.SOD) back to the issuing country's signing certificate. This proves the data was issued by the state and has not been altered. Certificates are distributed through bilateral exchange and through the ICAO Public Key Directory. A reader supplies the chip data; the verification layer is usually part of your software or of a dedicated inspection system. Be clear with your supplier about which layer does what.

4. Optical modes: white, infrared and ultraviolet

Full-page readers image the data page under different light sources. White-light images feed the OCR and the visual record. Infrared illumination can reveal the MRZ text on documents where visible-light contrast is poor, and can show features that differ under IR. Ultraviolet illumination makes certain printed security features and fluorescent fibers visible. These modes support screening and give an operator or a software rule something to compare. They are an aid, not a forensic examination: a reader with UV and IR does not certify a document as genuine, and your procedures should keep a trained human or a dedicated document-verification system in the loop where the risk justifies it.

5. Form factors: full-page, compact and embedded

TypeWhat it capturesBest for
Full-page desktop readerEntire data page image, MRZ OCR, optional RFID, UV/IRFront desks, visitor management, border and police counters
Compact / slim slot readerMRZ OCR and contactless reading in a small footprintHotel counters, kiosks, tight cabinets
Kiosk-embedded readerSame modules mounted behind a bezel with guidance graphicsSelf check-in, self-registration

MHY builds all three families. The ID and passport reader range covers compact USB readers that recognize the MRZ in about 1.3 seconds with ISO 14443 A/B contactless reading, and full-page models such as the MR200 desktop reader, which reads the full page in under a second and offers optional RFID chip reading and UV/IR imaging. For self-service, the same modules sit inside the premium passport check-in kiosk and the hotel check-in kiosk with key card issuance.

When comparing, ask for the time to read measured from document placement to a validated result, not only the OCR step, and whether that time includes the chip read, which takes longer than OCR and varies with the chip.

6. Integration: from document event to your system

A reader is only useful when its result lands in the right place. The standard flow is the same across hotels, visitor systems and kiosks:

  1. Detect. The reader signals that a document was inserted or placed (an event, callback or polling call in the SDK).
  2. Capture and OCR. The SDK returns the parsed MRZ fields, the check-digit status, and, for full-page models, one or more images.
  3. Chip read (optional). Your software passes the MRZ-derived keys to the reader to read DG1 and DG2 and fetches the SOD.
  4. Validate. Check digits, expiry date, issuing state allow/deny rules, and passive authentication if you perform it.
  5. Confirm with the person. Show the name and photo on screen; for attended counters, the operator confirms; for kiosks, compare a live camera image with DG2 or the printed photo.
  6. Write the record. Send the verified fields to the property management system, visitor system or watch-list service through its API.

Hardware connects by USB or RS-232 depending on the model, and SDKs are provided for Windows and Linux on desktop models, with Windows and Android on compact models; always confirm the exact operating system and version for the model you intend to buy. If your application is a web page or a different platform, ask whether the vendor provides a local service or a browser bridge so that you are not forced to build one. For fleet issues such as updating drivers across hundreds of kiosks, see our guide to kiosk software and remote management.

7. Where passport readers are used

  • Hotels and serviced apartments. Guest registration, self check-in and key-card issuance. Many jurisdictions require guests' identity to be recorded; the exact rules differ by country, so confirm local requirements. See our hotel self check-in guide and the hospitality solutions page.
  • Airports and border control. Self-service gates and counters where speed and document screening both matter. See the airport and border-control page.
  • Visitor and contractor management. Registration at office, factory and event entrances.
  • Car rental, telecom and banking. Identity capture for contracts, SIM registration and know-your-customer onboarding.

8. Data protection: store less than you can

A passport reader collects some of the most sensitive personal data a business handles. Design for privacy from the start: capture only the fields your process needs, avoid storing full-page images unless a rule requires it, encrypt data in transit and at rest, define a retention period, and restrict who can view records. Kiosks need physical protection against tampering and a clear on-screen privacy notice. Rules such as GDPR, and local registration and retention laws, differ by country, so this guide is not legal advice; involve your data-protection officer before deployment.

9. Specification checklist

QuestionWhy it matters
Which document types and MRZ formats (TD1, TD2, TD3, visas)?Determines the optics and the OCR engine you need
Is RFID chip reading included, and which protocols (BAC, PACE)?Chip reading is often an option, not standard
Does the SDK return per-field check-digit status?Lets you reject or review uncertain reads
Which operating systems and languages does the SDK support?Avoids a rewrite late in the project
Is there sample code and a test tool?Shortens integration time
Time to result including the chip?Sets queue time at the counter or kiosk
Operating temperature, dust and scratch resistance of the glass?Decides durability at a busy desk
Interface (USB or RS-232) and power?Fits your cabinet and computer
Certification documents (CE, FCC, RoHS) for the exact model?Required for import and tenders; see the certification guide

10. A pilot test plan that finds real problems

A demo with one passport proves little. Build a test set and run it before you commit to volume:

  • Variety: passports and ID cards from the main nationalities your customers carry, different issue years, laminated and worn pages, and at least one visa.
  • Conditions: bright and dim rooms, a dirty glass, documents inserted skewed, and fast repeated insertions.
  • Measurements: OCR success rate on the first attempt, time to a validated result, number of check-digit failures, chip read success and chip read time.
  • Failure handling: what the user and the operator see on a failed read, and whether manual entry is possible.

Record the results per document type and feed them back to the supplier. Reputable manufacturers welcome this; it is cheaper to tune settings or update firmware during a pilot than after rollout.

11. Next steps

If you are specifying a reader for a hotel, kiosk or visitor system, send us your document types, target operating system and expected daily volume. MHY engineers will recommend a reader or kiosk configuration, provide the SDK and sample code, and arrange a test unit. Browse the passport and ID reader range, review OEM/ODM options for custom housings and branding, or request a quote.

Need help specifying hardware for your project?

Tell us your use case and volume — our engineers will recommend a configuration and quote it.

Request a Quote

← Back to all insights

More Insights