Reading the ePassport Chip: NFC Verification Beyond the Photo

Most document checks stop at the surface: a photo of the ID, an OCR pass over the printed fields, maybe a tamper scan of the image. But since 2006, most passports issued worldwide carry a contactless chip that stores the same data cryptographically signed by the issuing state. Reading that chip moves verification from "this picture looks genuine" to "this data was signed by the issuing authority." Here is how the mechanism works and where it fits.

What the chip actually holds

The electronic passport follows ICAO Document 9303. The chip stores a set of data groups: DG1 mirrors the machine-readable zone (name, document number, nationality, dates), DG2 holds the facial image, and higher groups may carry fingerprints or additional fields. Two data structures make the payload trustworthy:

• SOD (Document Security Object): a signed hash list covering each data group, signed by the issuing country's Document Signer certificate.
• Country Signing CA: the root that signs Document Signers, distributed through the ICAO Public Key Directory and bilateral exchange.

Because the facial image in DG2 is inside the signed structure, a face match against that image inherits the chip's authenticity guarantee — you are comparing the selfie to a state-signed photo, not to a photo of a photo.

Getting inside: access control and authentication

You cannot simply read the chip. Access is gated by a key derived from printed data. Basic Access Control (BAC) derives the session key from the document number, date of birth, and expiry date read off the MRZ. Newer documents use PACE, a password-authenticated key agreement that resists offline brute force. Either way, the reader must first know values printed on the page, which ties chip access to physical possession of the document.

Two authentication steps establish trust in what you read:

• Passive Authentication: verify the SOD signature chains to a trusted Country Signing CA, then confirm each data group's hash matches the signed values. This detects any alteration to the stored data.
• Active or Chip Authentication: a challenge-response using a key pair on the chip, proving the chip is genuine rather than a cloned copy of the data.

Passive Authentication alone confirms the data is authentic and unmodified; adding chip authentication confirms the physical chip has not been cloned. Both matter for high-assurance flows.

The chat-based reading problem

NFC reading needs an antenna, and that lives in the user's phone, not your server. In a messaging flow this means the read happens on the device, then the signed result is relayed to you. The practical constraints are worth naming:

• The user must hold the passport against the phone's NFC coil, which sits in different positions across models. Guidance and retry handling reduce abandonment.
• iOS exposes NFC passport reading through Core NFC; Android through its NFC APIs. Coverage is broad but not universal on older or budget hardware.
• The MRZ must be captured first — usually by OCR of the passport page — to derive the BAC or PACE key before the chip will open.

From a data minimization standpoint, the chip is efficient: you can verify the signature and extract only the fields your risk model needs, rather than storing full-resolution scans. A configurable retention policy can keep the verification result and the signed hash evidence while discarding the raw image, so an audit trail proves the check occurred without hoarding biometric data.

When it is worth the friction

Chip reading is not free. It adds a step, depends on hardware, and requires certificate management to validate signatures. For low-risk retail onboarding, a visual document check plus liveness may suffice. Chip verification earns its place where document forgery is a live threat, where regulators expect the highest assurance level, or where a single fraudulent onboarding is expensive. Treating it as a step-up option — triggered by elevated risk rather than applied to everyone — keeps the friction proportionate while giving you cryptographic certainty exactly when it counts.