Capture surface
- Reader-dependent NFC/ID capability
- ID/passport reader
- Face / liveness
DEVICE · CHECKID
CheckID-R76
CheckID -R76 Wall mounted Cashless payment terminal is specially designed for scenarios such as Gas stations, Banks, Hospitals, or other places with rain shields. Touch LED screen is more convenient for customers to use.
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 | RK3568 · 2.0 GHz |
| Memory | 2 GB · 32 GB |
| Display | 15.6" · 1920×1080 |
| Camera | Binocular 2 MP · face/liveness |
| NFC / card | Reader-dependent NFC/ID capability |
| MRZ / document | ID/passport reader |
| Biometric | Face / liveness |
| Connectivity | Wi-Fi · 4G · multiple I/O |
| Physical / OS | Android 11 · printer integration |
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-R76: source-backed product specification
Source → Scope → Evidence → Limitation
Model and source
CheckID-R76 · official CheckID public product source. Source status: SOURCE_BACKED.
Source-backed hardware
Android; 15.6in; camera/liveness; reader; printer. Only these sourced attributes are promoted to public specification in .
Middleware boundary
kiosk middleware 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.