# CheckID: eID reading and identity verification

Covers three intake channels: a service desk, a mobile app and a website handing off to an appropriate capture component. It distinguishes card reading, data/chip checks and verification of the presenting person.

## Problem

Successful capture does not establish that every check passed. Fields may be absent depending on card type and access rights; channel handoffs must preserve the case and session.

## Scope

- Desk Agent/readers and native NFC on iPhone/Android under tested combinations.
- Separate document/chip checks, facial matching and PAD.
- The Backend validates outcomes before updating the case.

## Boundaries

Do not assume support for every device, OS, card type or field. Web orchestration does not mean browser-based NFC chip reading.

## Prerequisites

- Fix the device model, firmware, driver/SDK/Agent, OS and card types.
- Define authorised checks, required fields and channel handoff design.

## Pilot

Accept one specific combination: card reading, verification, expired session, unsupported card, cancellation and duplicate results. Record field provenance and each check outcome.

## Source document

https://docs.mobile-id.vn/Proposals/MobileID_CheckID_eID_Integration_Proposal_V3%201.pdf

V3; 51 pages; Vietnamese PDF.

Observed source version; confirm implementation scope.
- Value and channels: 3
- Devices and Agent: 7
- Mobile and handoff: 13
- Biometrics and chip checks: 17
- Architecture and data: 29
- Handover and acceptance: 34