Capture surface
- NFC · ISO/IEC 14443 A/B
- 300 dpi dual-sided scan
- —
DEVICE · CHECKID
CheckID-SR
ID card reader/scanner. Profit from accurate data entry and verification. OEM design for ABC gates and self-service kiosks. Intuitive design helps infrequent passengers. Automated passenger screening, 24/7 operation. Reads and verifies every ID including electronic travel documents.
3-LAYER MODEL
Hardware → Middleware → Platform
The device is part of the trust chain, not an isolated catalogue item.
Driver / firmware / adapter
- Device driver / firmware as applicable
- Secure capture and local integration
- Compatibility must follow device package
CheckID integration
- SDK / adapter
- REST / Kafka where applicable
- Subject → Process → Evidence
SPECIFICATION
Source-backed technical specification
| Field | Published / source-backed value |
|---|---|
| Processor / host | Host-connected |
| Memory | — |
| Display | Desktop reader |
| Camera | Optional 2 MP / 1080p |
| NFC / card | NFC · ISO/IEC 14443 A/B |
| MRZ / document | 300 dpi dual-sided scan |
| Biometric | — |
| Connectivity | USB 2.0 |
| Physical / OS | ≈700 g · 0–50 °C |
INTEGRATION
Device → SDK → API → Evidence
Cross-navigation connects capture capabilities to CheckID process and evidence.
SDK / Adapter
Capture and session integration.
CheckID Process
Subject/process workflow selected by use case.
Evidence
Result, transaction context and audit trail.
SOURCE-BOUND REFERENCE
CheckID-SR: source-backed product specification
Source → Scope → Evidence → Limitation
Model and source
CheckID-SR · official CheckID public product source. Source status: SOURCE_BACKED.
Source-backed hardware
300 dpi scan; NFC ISO/IEC 14443 A/B; USB2. Only these sourced attributes are promoted to public specification in .
Middleware boundary
driver/firmware boundary. Concrete driver/firmware versions require separate source evidence when absent from the datasheet/matrix.
CheckID integration
SDK/API cross-link. Device capability does not imply every verification method is supported.
Publication rule
No CPU/OS/interface/certification is added beyond the matrix/datasheet. Compatibility is tied to tested configuration or source version.
Lifecycle and limitations
Where EOL, firmware compatibility or tested OS is not sourced, records a publication limitation rather than inferring it.