Topic starter
11/11/2026 6:01 pm
TL;DR: FinCEN says mobile driver’s licenses and other verifiable digital credentials can support CIP verification, according to Socure. Identity teams now have to treat wallet support, attribute validation, and fallback handling as part of one governed onboarding flow.
Editorial analysis by NHI Mgmt Group, based on content published by Socure: “FinCEN Clarifies Digital ID for CIP: How Socure Is Putting mDL Verification to Work”.
Key questions
Q: How should banks use digital credentials in CIP onboarding?
A: Banks should treat digital credentials as one evidence source inside the Customer Identification Program process, not as a stand-alone trust decision.
Q: What is the difference between mDL verification and document scanning?
A: mDL verification checks a digitally signed mobile driving licence credential against the issuing authority, while document scanning reads data from a physical ID or its image.
Q: How do mobile driver’s licenses work in identity verification?
A: A mobile driver’s license is a government-issued digital credential stored in a wallet and presented as signed identity data instead of a photographed document.
Practitioner guidance
- Define accepted digital credential sources Set explicit trust criteria for which wallets, issuers, states, and credential types can satisfy CIP verification in your onboarding flow.
- Build a fallback path for unsupported presentations Route any failed or unsupported wallet presentation into a clean alternative journey so the digital-ID path does not become a dead end.
- Map required attributes to decisioning logic Document which identity attributes must be returned, how they map to existing verification rules, and which outcomes trigger review or step-up.
Bottom line: FinCEN’s guidance puts mobile driver’s license verification inside the existing CIP rule, so digital identity is now a regulated onboarding option rather than an experimental exception.
Glossary terms: Mobile Driver’s License, Wallet-based Verification, Verifiable Digital Credential, Customer Identification Program
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:06 pm
Cryptographic identity proofing is now an operating model, not a future concept: FinCEN’s clarification moves mDL verification from the edge of experimentation into the regulated onboarding path. That matters because the assurance question is no longer whether a phone can display an ID, but whether the institution can govern issuer trust, attribute scope, and fallback decisioning as one control sequence. Practitioners should treat digital credentials as a governed identity evidence source, not a separate channel.
A question worth separating out:
Q: What should teams do when a wallet or jurisdiction is not supported?
A: Teams should route the user to an alternate proofing path when a wallet or jurisdiction is not supported. That usually means document verification, remote identity proofing, or another accepted credential type, with manual review where policy requires it. Unsupported wallets should be treated as unavailable, not as lower-assurance credentials.
👉 Read our full editorial: FinCEN guidance lets banks use mDLs for CIP verification