Read an ID document's MRZ and NFC chip with the Regula Document Reader SDK and run the full authenticity check suite (Passive, Active, Chip, and Terminal Authentication)
domain: regulaforensics.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Initialize the Document Reader SDK (mobile or server) with a license scoped for MRZ, barcode, and NFC/RFID chip reading
Scan the document's visual/MRZ zone to extract and validate machine-readable fields per ICAO 9303 (or ISO 18013 for licenses)
Use the extracted MRZ data to derive the chip access key and initiate NFC reading of the embedded RFID chip
Run Passive Authentication (signature/hash verification), and where supported, Active Authentication, Chip Authentication, and Terminal Authentication against the chip
Cross-check the MRZ-derived data against the chip's data groups and flag any mismatch as a potential tampering indicator
Run Automatic Authenticity Control checks on the physical security features (UV/IR/axial imaging) when a hardware document reader is in use, in addition to chip checks
Known gotchas
NFC chip reading requires accurate MRZ or CAN input to compute the access key — a single misread MRZ character will cause chip access to fail outright rather than degrade gracefully
Terminal Authentication is only relevant for a small subset of document types (e.g., certain eID cards with restricted-access data groups); most passport/ID integrations will only exercise PA/AA/CA
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?