Xcelerate, Socure Add mDL Support in Login.gov

Login.gov now accepts mobile driver’s licenses

Xcelerate Solutions and Socure said on Sept. 29, 2026 that they are adding mobile driver’s licenses as an accepted form of ID for remote unattended identity verification inside Login.gov. The new check works with state-issued digital credentials that follow ISO/IEC 18013 standards, and it runs inside Socure’s FedRAMP Moderate environment.

Why this matters, and why it is not a miracle

This is useful, but it is not magic. If a user can present an mDL from a supported wallet, Login.gov can verify identity with less friction than the old routine of document photos and selfie capture. That means fewer abandoned signups and less room for obvious fraud.

For a 30-person company, this does not change your internal network overnight. It does matter if your team deals with government portals, regulated workflows, or identity proofing for vendors, clients, or contractors. We care about anything that cuts steps without turning security into a guessing game.

The contract angle is the real story

This announcement builds on the 2024 Login.gov Next Generation Identity Proofing Blanket Purchase Agreement. It also ties back to a five-year, $163 million call order that GSA awarded on May 1, 2026, with Socure as a subcontractor. That is the part worth watching. The government is not treating mobile IDs as a side experiment. It is putting real money behind the plumbing.

Login.gov was also described as accepting mDLs from select digital wallets, including Google Wallet and Samsung Wallet. That tells us the rollout is practical, not theoretical. People are already carrying these credentials on phones they use every day.

What we would do in a small business

We would not rush to build a project around this. That would be a waste for most mid-sized shops. What we would do is make sure our identity and access stack is ready for more mDL-style verification where it makes sense, especially for onboarding, account recovery, and partner access.

We would also check a few basics now:

• Whether your login and identity vendors support digital credentials from trusted wallets.
• Whether your onboarding steps still force users through extra manual review that could be replaced.
• Whether your security team has a fraud path for accounts that fail identity proofing.

The plain verdict

This is a sensible upgrade, not a headline that should send anyone into a buying spree. It points to faster identity checks and less friction in government services, which is good. If you are running a business in San Diego County and you want to know whether this changes your Microsoft, Google, VPN, or endpoint setup, the answer is usually no. If you want help figuring out where identity verification actually belongs in your stack, IT911Now can help. Start by reviewing the systems where customer or employee identity still depends on email links, document uploads, and manual review.