Google Wallet Opens Digital ID to Third-Party Apps as Google Pay Adds Cross-Device Biometric Approval

Close-up view of the rear camera modules and Google logo on three Google Pixel 3 smartphones in black, pink, and white colors, showcasing the minimalist design and camera technology of these mobile devices.

Google has detailed new identity and biometric verification flows for Google Wallet and Google Pay on Android, part of a wallet update tied to its I/O developer conference. The changes open digital ID verification inside Wallet to third-party apps and add cross-device biometric approval to Pay for desktop purchases authorized from a trusted Android device.

On the Wallet side, Google is opening the digital ID stored on a user’s Android device, such as a state-issued mobile driver’s license or a US passport credential, to third-party verification. Uber and Intuit are named as early adopters. The companies can prompt a user inside Google Wallet to share specific attributes of an ID rather than the full credential, an approach aligned with selective disclosure principles in the ISO mobile driver’s license standard. The change extends the digital ID footprint Google has built on Android across a growing set of US states, and complements broader Wallet privacy work that has included zero-knowledge proof support for sharing ID attributes without revealing the underlying document.

On the Pay side, the update introduces cross-device authentication for desktop purchases. When a user reaches checkout on a desktop browser, Google can route the approval to their trusted Android device through a secure push notification or a QR code scan. The user then approves the payment on the phone with face unlock, a fingerprint, or a device PIN, completing the transaction without entering card details on the desktop session. Google framed the flow as a way to meet multi-factor authentication needs and regional strong customer authentication requirements such as those in the European Union and the United Kingdom.

The two updates approach verification from different angles. The Wallet change uses an issued, government-anchored credential to confirm who a person is to a third party, while the Pay change uses on-device biometrics to confirm that the rightful account holder is approving a specific transaction. Both put the user’s existing Android device at the center of the verification, rather than introducing a separate authenticator or document upload step.

Google said the digital ID verification flow for Wallet and the cross-device biometric approval flow for Pay are rolling out as part of the broader Wallet refresh.

Sources: 9to5Google, Google Wallet Identity developer site

By the Mobile ID World Editorial Team