Documents

MRZ passport parsing guide

MRZ passport parsing guide for browser-only debugging, fixture handling, developer output, and production boundary decisions.

MRZ Passport Workbench Browse reference guides

Primary workbench MRZ Passport Workbench

Linked production route

Scope Global

Documents

Local evidence Format and character rules + Checksum/control replay

Browser-checkable work only

Boundary No live source proof

Official state remains external

Why this exists

Know what can be trusted before wiring the value into production.

MRZ passport parsing pages in ValidoHub are tool-first. This reference layer explains the checks, fixtures, developer handoff, and source-system limits so teams can integrate the live workbench output deliberately.

Use for Implementation planning

Choose normalization, storage, masking, and fixture strategy.

Use for QA and CI fixtures

Keep pass, review, malformed, and edge examples beside the code.

Use for Developer handoff

Copy the live tool JSON instead of reverse-engineering display text.

Browser checks

Local evidence the workbench can expose.

Check Format and character rules

Use the workbench for current evidence.

Check Checksum/control replay

Use the workbench for current evidence.

Check Field anatomy and parser evidence

Use the workbench for current evidence.

Official boundary

Where local validation must stop.

Boundary Official existence or legal status still belongs to the authority or source system.

Boundary Inputs stay browser-local; treat copied output as developer test data.

Integration traps

Small mistakes that create expensive debugging later.

Trap Never log raw personal, payment, or secret values when masked output is enough.

Trap Do not treat a valid checksum as proof that the value exists in an official registry.

Trap Keep malformed, short, wrong-prefix, and bad-checksum fixtures in CI.

Run the workbench

MRZ Passport Workbench

Validate, generate, inspect, copy, or export the current value in the browser.

Open live tool