Capture
Camera · NFC · MRZ/OCR
DEVELOPERS · CHECKID
Mobile SDK Architecture
Boundaries between customer app, CheckID SDK, CheckID/CheckID backend and RP backend.
CONTRACTVersioned API / SDK
AUTHOAuth2 / environment
OUTPUTResponse · result code · evidence
CHECKID MOBILE SDK
Mobile SDK Architecture
Boundary view connects client capture to the source-driven CheckID REST lifecycle.
CUSTOMER APPUI · Consent · Journey
↓
CHECKID MOBILE SDKCamera · NFC · MRZ/OCR · Biometrics · Evidence capture
↓
SECURE API SESSIONOAuth2 Client Credentials · Bearer · Subject · Process
↓
CHECKID / CheckIDDocument trust · Verification · Assurance · Evidence
↓
RP BACKENDDecision · workflow · downstream service
Biometrics
Face / liveness · supported modalities
Session
Subject → Process → Perform
Result
Evidence · verified claims · callback
SDK ARCHITECTURE
Mobile SDK: boundaries and publication status
Customer App → CheckID Mobile SDK → Secure API Session → CheckID Backend → Relying Party Backend
Architecture source
docs/MOBILE_SDK_ARCHITECTURE.md confirms the architecture pattern but does not
contain authoritative class/method signaturess.
No fabricated API
Public documentation does not invent class names, methods, callbacks, Gradle/CocoaPods packages or minimum OS versions without SDK release sources.
Security boundary
Server OAuth client secrets are not assumed to be embedded in the mobile SDK. Client/server credential responsibilities require the SDK/security integration guide.
Capability publication
NFC/biometric/capture capabilities are called supported only when SDK/device compatibility evidence confirms the platform/version.
Lifecycle
Initialization, permissions, capture, backgrounding, cancellation, errors and upgrade behavior require an authoritative SDK source.
Production readiness
SDK documentation is marked implementation-ready only with release/version/compatibility matrices and executable examples.