Collect the applicant's identity evidence: for remote IAL2, obtain at minimum one piece of Superior evidence (e.g., a Real ID-compliant driver license or passport) or two pieces of Strong evidence (e.g., a state-issued ID plus a utility bill or financial account document).
Perform document forensic validation: check security features, font consistency, and MRZ (machine-readable zone) checksum on the captured document image using an automated IDV vendor; record the authenticity score and any detected anomalies.
Bind the evidence to the applicant via biometric comparison: capture a selfie, run face match against the document portrait, and run a liveness/PAD check (ISO 30107-3 PAD Level 1 or 2); record the match confidence score and liveness result.
Validate identity attributes against authoritative sources: confirm name and date of birth via a database check (eCBSV for SSN, DLDV for driver license data, or a credit bureau lookup at NIST Fair evidence level).
Conduct identity resolution: confirm the identity presented is unique in your system and not a duplicate of an existing enrolled account by searching on name, DOB, and document number.
Document the complete proofing transaction record: evidence type, strength classification, validation method, binding method, attribute verification results, and timestamp, for audit and compliance review.
Known gotchas
Evidence strength classification (Superior, Strong, Fair, Weak) is defined in 800-63A-4 Table 4 and depends on the document type and the validation method used; incorrectly classifying a document as Superior when it was only authenticated at Strong level results in a proofing gap.
Remote IAL2 requires both validation of the evidence and verification of binding to the applicant; a strong document check without biometric binding (selfie + face match) does not satisfy IAL2 regardless of evidence quality.
NIST 800-63A-4 permits attribute verification via a single Fair evidence source (e.g., a KBV question answered correctly) only to supplement resolution, not to satisfy the verification requirement; using KBV as the sole attribute verification method is non-compliant.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp