Incode now accepts digital IDs from Google Wallet

More than 20 US states now issue a mobile driver's license, and in September FinCEN confirmed the credential counts as valid government ID for opening a bank account. Yet when those users reach a signup flow, most are still asked to dig out the plastic card and photograph it, as if the state-signed version sitting in their digital wallet did not exist.

With Incode, that gap doesn't exist.

Incode now accepts digital IDs from Google Wallet. Within the existing Google Wallet flow, users tap to share their ID, approve the request in their Wallet, and continue. Incode handles the trust relationship with Google, so businesses don't need an integration change, just a configuration change.

Turning on Google Wallet acceptance

Businesses already running Incode can turn on Google Wallet acceptance inside the verification flow they have today. Incode manages the certificates and handles the Google Wallet registration on your behalf, while you configure the flow and launch.

Teams evaluating Incode get wallet acceptance inside the full identity and age verification suite, designed for onboarding, authentication, and advanced fraud prevention. It arrives as one capability in that suite rather than a point solution, so there is no second vendor to source for the users a wallet cannot cover.

One integration keeps pace with every wallet

Mobile driver's licenses (mDLs) and digital IDs are arriving fast, and national ID schemes are launching across the countries adopting digital identity, each on its own standard, wallet, and timeline.

Keeping pace takes real work. Accepting these credentials yourself means a separate access path for each wallet, a separate relying-party approval for each issuer, ownership of every trust list, and a re-integration each time a standard moves.

Incode verifies 30+ national wallets and ID schemes across the 160+ countries adopting digital ID.

What the user does

The whole process happens on the user's phone. They tap to share, approve the request in their wallet, and the verification is finished. The digital ID credential already sits on their device, so there is no photo upload to wait on and no manual review to clear.

Privacy is built into every request

Digital wallets respect consumer privacy by employing tokenization and encryption to share necessary information and obscure unrelated data. The user always sees which fields are requested and by whom, and approves each request before anything leaves the wallet. Requests are scoped to what the check actually needs, and nothing more.

So, a business confirming age asks whether the user is over 21 and receives a pass/fail response, but cannot see a full date of birth, document number, or address.

The credential is signed by the authority that issued it and bound to the user's device. Incode validates that signature against the issuer's published trust list.

Where wallet credentials help

The same credential covers a range of checks. These are the places where it helps most:

Account opening with a digital ID

Banks and credit unions can verify a new customer straight from their digital wallet, in branch or online. FinCEN confirmed mDLs are permitted for customer identification program (CIP) checks at US banks and credit unions as of September 2026.

Online age verification

State age verification laws keep expanding. A wallet credential indicates whether an individual meets the necessary age threshold, and the date of birth never leaves the phone.

Counter and pickup verification

Rental desks and order collection move faster because the customer is already holding their phone.

Fallback for users without a wallet credential

When a user has no wallet credential, the same session falls back to document capture and liveness. One flow covers both paths.

Ready to see how Incode's digital ID verification brings Google Wallet credentials into the verification flow you already run? Request a demo today.