Topic starter
14/07/2026 6:07 pm
TL;DR: A $37.4 million GSA contract was awarded to support Login.gov’s next-generation remote unsupervised identity proofing, aiming to improve verification accuracy, reduce fraud, and preserve privacy across government services, according to Incode. The signal for practitioners is that digital identity assurance is moving toward higher-friction controls that must still scale.
Editorial analysis by NHI Mgmt Group, based on content published by Incode: “Diamond Capture and Incode Awarded $37.4M Contract to Support Login.gov”.
By the numbers:
- The contract award is worth $37.4 million.
Key questions
Q: How should public-sector teams govern mobile-first identity proofing?
A: Public-sector teams should govern mobile-first proofing as a risk-based assurance process, not a simple digital form.
Q: Why does remote eKYC increase the risk of identity fraud compared with face-to-face checks?
A: Remote eKYC raises risk because the verifier no longer controls the capture environment.
Q: What are the biggest mistakes teams make in identity proofing programmes?
A: The most common mistakes are over-collecting personal data, applying the same proofing level to every use case, and failing to connect proofing results to downstream access decisions.
Practitioner guidance
- Define assurance thresholds for every identity journey Set explicit acceptance, step-up, and fallback criteria for remote proofing so every service uses the same risk logic.
- Minimise biometric and identity evidence retention Limit storage of documents, selfie data, and decision artefacts to what is required for fraud detection, audit, and legal retention.
- Test exception handling and recovery paths Exercise the flows used when proofing fails, including manual review, alternate evidence, and recovery after suspected fraud.
Bottom line: Remote identity proofing is becoming a core governance control for public-sector access, not a back-office onboarding step.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/07/2026 6:12 pm
Digital identity proofing is becoming a governance control, not just an onboarding step. When government services rely on remote verification, the proofing decision directly shapes downstream access risk, fraud exposure, and user trust. That makes identity assurance part of the control plane for public-service access, not a peripheral verification task. Practitioners should govern proofing as an access policy with measurable assurance thresholds.
A few things that frame the scale:
- Nearly 60% of companies reported that fraud losses were still increasing in 2025.
A question worth separating out:
Q: How do identity verification and fraud prevention work together in digital services?
A: Identity verification establishes who is entering the service, while fraud prevention checks whether the session, device, or transaction looks legitimate. In mature programmes, both share telemetry and escalation paths so suspicious behaviour can be challenged before an account takeover or payment loss is completed.
👉 Read our full editorial: Incode's Login.gov contract shows why digital identity verification is tightening