What did Socure announce for mobile driver's licenses?

mDL verification in its DocV product, accepting remote presentations from Google Wallet and Samsung Wallet, with cryptographic validation of DMV issuance followed by device, behavioral, and identity risk assessment around the presentation.

How many Americans have mobile driver's licenses?

Twenty-one states issue mDLs today with more than 8 million active credentials, and ABI Research projects the install base growing from 21.7 million in 2025 to roughly 143 million by 2030 across about 40 issuing states.

Does cryptographic mDL validation prove who is presenting?

No: it proves genuine issuance and device possession. Stolen devices and fraudulently provisioned wallets pass validation, which is why risk-bearing actions warrant a liveness-anchored match against the credential's signed portrait.

What should verification programs do about mDL acceptance?

Consume presentations as weighted evidence in one decision policy, maintain equal-assurance routes for non-mDL users, tier present-person binds by action risk, and keep per-decision acceptance records for the examinations that will follow the adoption curve.

Back to News

The Deep Brief · Oct 5, 2026 · 4 min read

Socure wires Google and Samsung mDLs into KYC flows

Socure added Google and Samsung wallet mDL verification to DocV after federal CIP guidance, as the US mDL base heads from 21.7 million toward 143 million.

Rosalie Chirip

Senior Editor at deepidv

A hand tapping a smartphone wallet on a contactless reader

The mDL acceptance wave has reached the commercial KYC stack. Socure has added mobile driver's license verification to its DocV product, accepting remote presentations from Google Wallet and Samsung Wallet, the same wallets Login.gov switched on in August, and the company is explicit about the trigger: the federal guidance confirming banks may use qualifying government-issued digital credentials in customer identification programs, the CIP opening that turned wallet credentials from novelty into regulated-market input.

The design Socure describes is the layered one this publication has argued the credential era requires: cryptographic validation first, confirming the mDL was actually issued by a state DMV, then device, behavioral, and identity intelligence around the presentation, because a valid credential and a safe presentation are different facts. "Mobile driver's licenses represent a major shift in how consumers prove who they are online," said Socure's head of document verification Deepanker Saxena, and the market numbers back the sentence: 21 states currently issue mDLs with more than 8 million active credentials, and ABI Research projects the US install base growing from 21.7 million in 2025 to 143 million by 2030, with roughly 40 states issuing by then.

The acceptance stack becomes table stakes

The announcement's structural meaning is bigger than one vendor's feature list. With the federal front door accepting mDLs under the $163 million Login.gov program, where Socure also sits via its Xcelerate partnership, and commercial KYC vendors now shipping acceptance, the mDL has crossed from pilot to production on both sides of the public-private line in a single quarter. Every verification provider will field the same roadmap question this month, and the answer architecture is converging on three layers: credential validation against issuer trust lists, risk intelligence around the presentation, and, the layer that separates mature implementations, a present-person bind for actions whose risk exceeds what device possession proves, the mDL mechanics covered in our explainer.

The 143-million projection also quantifies the fraud economy's new target: provisioning. When a sixth of the country carries a cryptographically perfect credential, stolen identities enrolled into wallets become the attack that matters, because every downstream acceptance, Socure's included, validates the issuance, not the enrollment. Issuer provisioning posture, which states proof enrollment with liveness and which accept a scan and a quiz, becomes a risk input acceptance stacks will need to weight, and the first mDL provisioning scandal will sort the market into vendors who priced it and vendors who discover it.

What relying parties should take from it

Three moves follow for banks, fintechs, and platforms watching the wave. Build credential intake as policy, not plumbing: mDL presentations should land in the same decision plane as documents and biometrics, weighted by issuer posture, with equal-assurance fallbacks for the 29 states' residents who cannot present one. Tier the present-person bind: wallet possession suffices for low-stakes checks, while onboarding, payouts, and recovery keep a liveness-anchored match against the credential's signed portrait. And log acceptance like the regulated input it now is: issuer, trust-list version, checks run, and supplementary binds, per decision, because examiners who permitted credentials will eventually audit how they were accepted. The wallet era's winners will be the stacks that treated acceptance as a risk discipline rather than a checkbox, and this week the discipline officially went mainstream.

Mobile Driver's License KYC FAQ

What did Socure announce for mobile driver's licenses?: mDL verification in its DocV product, accepting remote presentations from Google Wallet and Samsung Wallet, with cryptographic validation of DMV issuance followed by device, behavioral, and identity risk assessment around the presentation.
Can banks use mDLs for KYC now?: Yes: federal FAQs confirmed banks may accept qualifying government-issued digital credentials in Customer Identification Programs, the regulatory clarification Socure cites as the trigger for commercial acceptance.
How many Americans have mobile driver's licenses?: Twenty-one states issue mDLs today with more than 8 million active credentials, and ABI Research projects the install base growing from 21.7 million in 2025 to roughly 143 million by 2030 across about 40 issuing states.
Does cryptographic mDL validation prove who is presenting?: No: it proves genuine issuance and device possession. Stolen devices and fraudulently provisioned wallets pass validation, which is why risk-bearing actions warrant a liveness-anchored match against the credential's signed portrait.
What should verification programs do about mDL acceptance?: Consume presentations as weighted evidence in one decision policy, maintain equal-assurance routes for non-mDL users, tier present-person binds by action risk, and keep per-decision acceptance records for the examinations that will follow the adoption curve.