EvidenceID Document Reader
ID Document Reader
Document intelligence that never leaves the building.
- Tier
- private. Real and running. Shown on a call.
- Status
- Private. Demo on request.
- Form
- One Docker image, networking disabled
- Stack
- Python, OpenCV, ONNX, ZXing
- Role
- Sole engineer
Send it a passport, a driving licence, a bank statement or a deed. It returns all the text, the structured fields, a portrait, and for every field a label that says how it was verified.
A passport number is checksum verified because an ICAO check digit proved it. A surname on the same page is not, because no check covers it. A bank statement balance is verified when the running balance chain reconciles. A chip read is cryptographically verified only when the data groups hash, the signature verifies and the signer chains to a trusted anchor.
It reads the name twice, once from the machine readable zone and once from the printed page, and cross validates them through the transliteration rules each issuing state may use. A genuine mismatch goes to review rather than being resolved away.
It runs as a single container with networking disabled. Nothing about a document is logged. Large jobs go through an idempotent queue, so a retry joins the running job instead of starting a second one. It does not claim to detect forgery or liveness, and it says so.
What transfers to a fund
KYC document capture without a cloud vendor in the data path, and a definition of verified that holds up in an audit.
The code is private. I can walk you through it on a call.