Capture surface
- Contact smart card / CCID · ISO/IEC 7816 A/B/C
- USB 2.0 Type-A or Type-C
- Metal stand · long USB cable
DEVICE · CHECKID
R301-C11
R301-C11 suits customers where security concerns are the most salient and satisfies the demand for a flexible solution for ID authentication, e-commerce, e-payment, information security and access control. R301-C11 and the rest line of smart card readers offer each customer a complete solution for all manner of utilizations.
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 | Compact reader |
| Camera | — |
| NFC / card | Contact smart card / CCID |
| MRZ / document | — |
| Biometric | — |
| Connectivity | USB-A / USB-C |
| Physical / OS | ISO/IEC 7816 A/B/C · multi-OS |
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
R301-C11: source-backed product specification
Source → Scope → Evidence → Limitation
Model and source
R301-C11 · official CheckID public product source. Source status: SOURCE_BACKED.
Source-backed hardware
CCID; USB; ISO 7816 A/B/C. Only these sourced attributes are promoted to public specification in .
Middleware boundary
reader driver 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.