Objective
Build sufficient evidence for the relying organisation to establish an identity for a defined purpose rather than merely running a biometric match.
CHECKID · IDENTITY PROOFING
Identity Proofing
Identity proofing is an evidence journey; e-Verification can be a component of that journey but is not a synonym for it.
SERVICEPurpose → Method → Result
TRUSTSource → Evidence → Scope
OPERATIONSSaaS · API · SDK · SLA
PROOFING JOURNEY
From evidence to an identity that can be relied upon
Acquire → validate → bind → assure → evidence
Evidence acquisition
Collect document/eID/authoritative attributes/biometric evidence according to the configured method.
Validation
Evaluate quality, consistency, provenance and the relevant verification methods.
Holder binding
Bind the present actor to the evidence where the journey requires it; PAD and 1:1 matching are separate steps, not synonyms for proofing.
Assurance
The relying organisation’s policy determines evidence sufficiency; CheckID does not invent a regulatory assurance level without source evidence.
Evidence output
The proofing outcome should be traceable to process, source, method, result and evidence references according to the data contract.
SERVICE & CAPABILITY
Identity Proofing uses e-Verification but is not the same service
Service composition is explicit.
| Component | Role |
|---|---|
| e-Identification | Determine subject/identity source |
| e-Verification | Verify specific claim/evidence |
| Biometric Verification/PAD | Holder binding where applicable |
| Identity Assurance | Evaluate evidence sufficiency against policy |
| Evidence | Record results and provenance |
TECHNICAL REFERENCES
Definition and standards references
A reference does not by itself mean CheckID conforms to or is certified against the document.
NIST SP 800-63A-4
Identity proofing and enrollment reference
ETSI TS 119 461 V2.1.1
ETSI identity-proofing reference for regulated trust contexts