TL;DR: Banks can now verify new customers with mobile driver's licenses under updated FinCEN guidance, according to Hopae, which removes the ambiguity that kept mDLs at the edge of onboarding. Customer identity checks now shift from image-based document review to cryptographic verification of issuer-signed credentials.
Editorial analysis by NHI Mgmt Group, based on content published by Hopae: “Banks can now accept a mobile driver's license. Here's what actually changed.”.
Key questions
Q: What checks should a bank perform before accepting a digital ID?
A: A bank should check the identity proofing method, the assurance level, the issuer or trust framework, document authenticity, liveness or possession evidence, and whether the digital ID is bound to the presenting person.
Q: Why does cryptographic verification reduce document fraud risk?
A: Cryptographic verification reduces document fraud risk because signatures, certificates, and integrity checks let a verifier confirm that the document was issued by a trusted authority and has not been altered.
Q: How do mobile driver's licenses work in bank onboarding?
A: Mobile driver's licenses are cryptographically signed identity credentials issued by a government authority and presented from a wallet app.
Practitioner guidance
- Define an mDL acceptance policy Specify which onboarding journeys can accept mobile driver's licenses, which issuers or wallet types are in scope, and what evidence must be stored for audit and dispute handling.
- Verify issuer signatures and revocation status Build the onboarding workflow so it validates the credential cryptographically, checks issuer trust material, and confirms the mDL is current before account opening.
- Separate presentation risk from document review Replace manual image inspection with controls that record device binding, presentation channel, and verification outcome for each onboarding transaction.
Bottom line: The policy change is about verification method, not a new identity standard, so the main work shifts to how banks prove a credential was valid at onboarding.
Glossary terms: Mobile Driver's License, Customer Identification Program, Verifiable Credentials (VCs), Device binding
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
mDL acceptance is a verification governance change, not a simple format update. The important shift is that banks move from judging a document to validating a credential. That changes evidence handling, trust anchors, and auditability across onboarding flows. Institutions that keep treating mDLs as a scan-and-check problem will miss the control differences that matter most.
A question worth separating out:
Q: What happens when banks rely on scanned IDs for CIP checks?
A: When banks rely on scanned IDs for CIP checks, they can accept altered, copied, or synthetic documents because a scan alone does not prove the document is genuine or that the presenter is the rightful holder. Stronger controls include document authenticity checks, biometric or liveness comparison, and validation against trusted issuing sources.
👉 Read our full editorial: mDL acceptance turns bank onboarding into cryptographic verification