DEVELOPERS · CHECKID
Integration Architecture
Separate channel, orchestration, verification service, callback and evidence retrieval.
CONTRACTVersioned API / SDK
AUTHOAuth2 / environment
OUTPUTResponse · result code · evidence
CORE DOMAIN MODEL
End User → Subject → Process
An end-user has a dossier; Subject contains identity data; Process carries files/results and belongs to exactly one Subject.
Source contractSections 2.3–2.5 · End-user · Subject · Process
END USERPerson being verifiedDossier / identity context
→
SUBJECTIdentity attributesName · DOB · document · email/mobile
1:N
PROCESSVerification instanceType · provider · state · evidence · result
PENDING→PROCESSING→ACCEPTEDREJECTEDINCONCLUSIVECANCELEDFINISHED
The source defines the state set but not every transition; does not invent a complete state machine.
AUTHENTICATION JOURNEY
From integration credential to verification result
The source sample defines a 900-second access-token lifetime; subsequent requests use a Bearer token with the request-signing context.
Source contractSections 2 and 3.1 · OAuth2 Client Credentials + Gets Access Token
Integration CredentialsRP-issued integration context
→
OAuth2 Client CredentialsSigned HTTP request
→
Get Access TokenShort-lived Bearer token
→
Subject / ProcessIdentity verification lifecycle
→
Evidence / ResultCheckID ID · result · signed claims