Socure announced on 30 September that it has added U.S. mobile driver’s license verification to DocV, its identity verification product, letting organizations cryptographically check a license presented from Google Wallet or Samsung Wallet during remote onboarding and step-up flows. Socure mDL verification follows a joint statement from five federal regulators on 8 September confirming that a verifiable digital credential can satisfy the Customer Identification Program rule. Socure is positioning the product as the workflow that turns that permission into something a bank can deploy. The details are in the BusinessWire release.

What the 8 September regulatory guidance allows

FinCEN, the Federal Reserve Board, the FDIC, the OCC and the NCUA jointly issued FAQs on 8 September 2026, and FinCEN’s guidance page carries the document as a PDF. As Socure describes them, the FAQs confirm that an unexpired, government-issued verifiable digital credential can qualify as documentary evidence under the CIP Rule.

The permission comes with three conditions. The institution must have the technology or systems needed to extract the required information. A digital credential is not automatically sufficient where there are indications of fraud. And the institution must still form a reasonable belief that it knows the customer’s true identity. Those conditions matter more than the headline, because they decide what a compliance team has to build.

How Socure mDL verification works in remote flows

Most mDL deployments have supported in-person presentation, the airport-checkpoint tap covered by Part 5 of the ISO/IEC 18013 standard, according to Socure. Remote presentation under Part 7 has been supported unevenly across wallets. Socure mDL verification in DocV adds remote presentation from Google Wallet and Samsung Wallet, so the license is checked against the issuing state rather than inferred from a photograph of a plastic card.

The check starts with cryptographic validation that the state DMV issued the credential and that it has not been altered. Socure then layers device, behavioral and identity intelligence on top to judge whether the person presenting it should be trusted. The company says Socure mDL verification complements its physical document capture instead of replacing it, giving organizations a second path. Google Wallet’s Alan Stapelberg describes the integration as offering “a high assurance, low friction verification experience.”

The adoption numbers behind Socure mDL verification

ABI Research projects that the U.S. mDL install base will grow from 21.7 million in 2025 to 143 million by 2030. Socure says 21 states issue mDLs conforming to the ISO/IEC 18013 standard, more than 8 million credentials are active, and roughly 45% of Americans live somewhere one is available.

The release also notes an extension of Socure’s partnership with Xcelerate Solutions for public sector use under the Login.gov Next Generation Identity Proofing Blanket Purchase Agreement. That work runs in Socure’s FedRAMP Moderate environment and gives agencies a mobile-native way to verify state-issued digital credentials.

Why Socure mDL verification is a fraud bet as much as a convenience feature

The pitch for Socure mDL verification is lower friction: no photo of a card, no retakes, verification in seconds. The stronger argument is fraud. A photographed license can be forged or altered, while a credential signed by the issuing state and checked cryptographically is much harder to fake. The regulators’ own conditions point the same way. A credential is not automatically enough when fraud indicators are present, so the device and behavioral layer that Socure sells is close to what the guidance expects an institution to have in practice.

The limit is supply. Eight million active credentials is small next to the U.S. driving population, and Socure’s own framing, a second path beside document capture, concedes that most applicants will still photograph a card. The commercial value of Socure mDL verification will come from the applicants who can use it and from the fraud it filters out, not from replacing the incumbent flow.

Fintechbits has followed Socure’s widening reach across onboarding, including Binance.US’s selection of Socure and Socure’s identity verification on Circle’s Arc blockchain. The mDL launch moves from crypto exchange onboarding to bank onboarding.

What to Watch Next for Socure mDL verification

The first test is whether a named bank or fintech puts Socure mDL verification into production onboarding and reports what share of applicants present a digital credential. That figure would show whether wallet-based checks are a meaningful channel or a niche.

The second is wallet coverage for Socure mDL verification. The release names only Google Wallet and Samsung Wallet, and remote presentation under Part 7 is described as uneven, so any expansion to other wallets will change how useful the product is. The third is examiner behavior, since the reasonable-belief standard in the FAQs leaves room for interpretation and the first supervisory reviews will show how much.