FinCEN confirms US banks can use mobile driver's licences for customer ID checks
FinCEN and federal bank regulators said on 8 September that qualifying mobile driver's licences can meet customer identification rules. No bank has to accept them, so the work shifts to wiring the credentials into onboarding systems.
The Investor · Invest desk
Share bar: about 12 of the 20 live mobile driver's licence programmes fall within Hopae's stated coverage, treating around a dozen as twelve; roughly eight fall outside it.
- Hopae-supported, around a dozen, claim 13 12 of 20 live mDL programmes 60% computed
Hopae-supported, around a dozen The rest of the 20
| Share | Part | Whole | Percent | Claim |
|---|---|---|---|---|
| Hopae-supported, around a dozen | 12 live mDL programmes | 20 live mDL programmes | 60% (computed) | 13 |
What happened
- FinCEN said the FAQs leave Bank Secrecy Act obligations as they stand and set no new supervisory expectations.
- Banks must still verify the customer's name, address and date of birth under their existing identification programmes.
- Other government-issued verifiable digital credentials qualify only with a photograph or equivalent safeguard and evidence of nationality or residence.
- ISO/IEC 18013-7, published in 2024, extends mobile driver's licence verification to online interactions, the setting remote-onboarding banks need.
Why it matters
- What it costs cost A bank that wants mobile licences has to add a technical approach different from image-based document scanning, and the spend is its own.
- What it limits constraint Handing the check to a third-party issuer does not hand over the liability, because the bank still has to verify the credential to the required standard.
- What doesn't add up contradiction Hopae calls integration the next challenge, yet says banks already on its API add mobile licences as another credential type, so the challenge is smaller for some banks than its framing.
The only account of the integration problem in the fintech.global report comes from Hopae, a digital identity provider that sells a product built for it [18]. Its conclusion is that the FAQs remove one obstacle and leave technical readiness as the next challenge [17]. The forecast comes from a vendor, and the report does not include a price for the work or a count of banks that have started it.
To qualify, a credential must carry its issuer's digital signature, be tied cryptographically to a device and sit behind a PIN or biometric check [8]. On the bank's side of the exchange, it asks the credential for a cryptographic response, checks the issuer's signature against that issuer's public key and looks up the credential's revocation status [9].
The Secure Technology Alliance's mDL Connection tracker lists 20 states and territories with live programmes built to the relevant standard [11]. Hopae says its platform handles ISO/IEC 18013-5 licences from around a dozen, among them California, Arizona, Colorado and Georgia [15]. Hopae's dozen is about 60% of live programmes [12] and leaves roughly eight outside the vendor's stated reach [13]. Even eight is loose, since "around a dozen" is not a count and the tracker and the vendor may not be counting the same things. We'd expect a bank adopting on that footing to keep its document route for customers from the remaining states. It would run two verification paths for as long as the gap lasts.
We think the cost sits in integration and falls unevenly: close to a configuration change for a bank already verifying through an API-based vendor, a build for a bank scanning documents in-house. The report's only evidence for that split is one vendor statement about its own customers [16].
If vendors ship mDL support as a default, the cost to banks shrinks to a line item in a contract renewal. If banks see little customer demand, then with no obligation to accept the credentials [2] many will leave them switched off, and the 20 live programmes [11] will go unused at the bank end.
What to watch
- Whether core-processor and identity vendors ship mobile licence support as a default setting or as a separately priced integration.
- Any change in the tracker's count of 20 live states and territories, and whether Hopae's list of about a dozen grows to match it.
- Any agency or examiner follow-up that treats declining to accept mobile licences differently from today's position that nothing is required.
Information, not investment advice. This story is general information about companies and markets, drawn from cited reporting. It is not a recommendation to buy, sell or hold any security; check the cited sources before acting.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence55
- Adoption25
- Hype gap+20
- Incentives75
- Confidence50
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
On 8 September 2026, FinCEN, alongside staff from the Federal Reserve, FDIC, NCUA and OCC, issued guidance on using state-issued mobile driver's licences and other government-issued verifiable digital credentials.
- [2]
The announcement does not introduce a new law or require banks to accept digital identification; it clarifies how existing customer identification requirements apply to qualifying digital credentials.
- [3]
FinCEN confirmed that the FAQs do not change Bank Secrecy Act obligations or establish new supervisory expectations.
- [4]
Under the clarified interpretation, a state-issued mDL can qualify as government-issued identification for customer identification programme (CIP) purposes.
- [5]
Banks must continue to verify customer information, including name, address and date of birth, in line with their existing identification programmes.
- [6]
Other government-issued verifiable digital credentials, subject to applicable requirements, must contain a photograph or equivalent safeguard and evidence of nationality or residence.
- [7]
Where a third party issues a credential, the financial institution remains responsible for verifying it to the required standard.
- [8]
A qualifying credential is digitally signed by its issuer, cryptographically bound to a device and protected by an activation factor such as a PIN or biometric authentication.
- [9]
In a digital verification process, a bank can request a cryptographic response, validate the issuer's signature against its public key and check whether the credential has been revoked.
- [10]
ISO/IEC 18013-7, published in 2024, extends mobile driver's licence verification to online interactions, which is relevant to banks that onboard customers remotely.
- [11]
According to the Secure Technology Alliance's mDL Connection tracker, 20 states and territories operate live mDL programmes built to the relevant standard.
- [12]
Hopae's stated coverage of around a dozen states and territories is about 60% of the 20 with live programmes.
- [13]
Roughly eight of the 20 live programmes fall outside Hopae's stated coverage, treating 'around a dozen' as twelve.
- [14]
Hopae argues that supporting these processes requires a different technical approach from conventional document scanning, which is commonly built around images of physical identification cards.
- [15]
Hopae says its platform supports ISO/IEC 18013-5 mobile driver's licences from around a dozen states and territories, including California, Arizona, Colorado and Georgia.
- [16]
For financial institutions already using Hopae Connect's API for CIP checks, Hopae says mDL verification can be added as another credential type within the existing integration, rather than requiring a separate project.
- [17]
Hopae's analysis concludes that the regulatory clarification removes one obstacle to adoption, leaving technical readiness as the next challenge.
- [18]
Hopae is a digital identity provider, and Hopae Connect is the company's proposed solution to the integration challenge it describes.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- fintech.globalFinCEN clarifies use of mobile driver’s licences in bank onboarding
1 article · October 14, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Bank onboarding and KYCFollow
- Digital IdentityFollow
- Financial Regulation and LobbyingFollow
Entities
- FinTech GlobalFollow
- Secure Technology AllianceFollow
- HopaeFollow
- ISO/IEC 18013Follow
- Financial Crimes Enforcement NetworkFollow