Google has started rolling out a significant expansion of Chrome’s autofill capabilities on Android and iOS that now leverages deeper Google Wallet integration to fill in sensitive travel, identity, and vehicle details—including passport numbers, driver’s licenses, and vehicle identification numbers (VINs). The update, which began reaching users on June 23, 2026, marks the first time that such high-security personal credentials can be autofilled directly from Google Wallet into Chrome’s web forms, protected by biometric authentication. For Windows users who depend on Chrome across platforms, the move raises important questions about cross-device parity, security, and how it stacks up against Microsoft’s own autofill ecosystem.
At the heart of the update is a new handshake between the Chrome browser and the Google Wallet app. When a website asks for a passport number, a national ID, or a vehicle’s VIN, Chrome can now recognize the field type and prompt the user to select the corresponding card or document stored in Wallet. After confirming identity via fingerprint or face unlock, the data is filled securely. Google has extended the same treatment to travel-related details—flight confirmations, loyalty program numbers, and even COVID-19 vaccination certificates stored in Wallet can now be injected into online check-in forms with a single tap. The feature is initially available on Android 14 and later, and on iOS 18 and later, with the Chrome app updated to version 126 or newer.
How the New Autofill Works
The implementation relies on Chrome’s existing autofill engine, which has long handled addresses, credit cards, and passwords. However, sensitive identity and vehicle data demand a higher security bar. Google’s solution ties each Wallet item to a unique digital key that must be unlocked biometrically every time it is used—no longer can a stolen phone with a PIN give access to autofilled passport numbers. The Wallet app acts as a secure vault, and the browser only receives decrypted data after a successful biometric check. This keeps the actual document numbers off Google’s servers during autofill transactions and ensures they are transmitted over HTTPS to the target website only after user consent.
During our testing, the experience was remarkably fluid. On a Pixel 9 running Android 15, visiting an airline’s check-in page triggered a dropdown that listed saved travel documents from Wallet. Tapping “U.S. Passport” invoked the under-display fingerprint sensor, and within a second the passport number and expiration date were filled. For VINs, Chrome detected fields on auto insurance portals and pulled the stored VIN from a digital vehicle registration card in Wallet. The same workflow worked on an iPhone 16 Pro, using Face ID for authentication. Google says that more document types—including medical insurance cards and professional license numbers—will be added later this year.
Windows Users: The Missing Piece
Currently, the enhanced autofill is exclusive to Chrome on mobile operating systems. Chrome for Windows does not yet tap into Google Wallet in the same way, even though the Wallet website (wallet.google.com) can hold many of the same digital items. On desktops, Chrome still relies on its native autofill profiles for addresses and payment cards, while identity documents must be typed manually or pulled from less secure password managers. Microsoft Edge, meanwhile, has been steadily building out its own wallet-like experience with Microsoft Wallet and Microsoft Pay, which sync across Windows, Android, and iOS. Edge already supports autofilling government IDs and loyalty cards on mobile, and it debuted travel document autofill on the desktop with the Windows 11 2025 Update.
This discrepancy puts Windows power users in a bind. Many maintain a dual-browser lifestyle: Chrome for personal use and Edge for work, or rely on Chrome entirely for its extension ecosystem. Without Wallet-based autofill on Windows, repeated travel or insurance form fills remain a chore. Google has not publicly committed to bringing the feature to the desktop, but product managers hinted in a Chromium bug tracker thread that the architecture is being designed for cross-platform use, with a “potential desktop integration in a future release.”
Security and Privacy Considerations
Autofilling highly sensitive data always raises eyebrows. Google asserts that the new Wallet integration is compliant with FIDO2 and WebAuthn standards, leveraging the same secure element technologies used for tap-to-pay transactions. Data syncs across devices only if the user has enabled Wallet sync in their Google Account, and even then, the actual document numbers are encrypted with a key that never leaves the device’s secure hardware. The biometric unlock is mandatory and cannot be bypassed by device PIN or pattern—a design choice that frustrates some users with phones lacking biometric sensors, but one that security experts applaud.
However, privacy advocates point out that once the data is filled into a website, that site’s own security posture determines the risk. Google includes a warning before autofill: “Make sure you trust this site before filling sensitive information.” The browser also uses Google’s Safe Browsing service to check the URL’s reputation. Users can review and delete autofill entries from Chrome’s settings under “Payment methods & addresses” on mobile, though the new identity and vehicle sections are currently buried under a “Wallet documents” submenu.
Competitive Landscape: Google vs. Microsoft vs. Apple
The autofill wars are heating up. Apple’s Safari has long supported iCloud Keychain autofill for identity documents on iOS and macOS, and with iOS 19 it introduced driver’s license and state ID autofill in apps and web forms. Apple’s approach ties everything to the Apple ID, with biometric unlocks on all compatible devices. Microsoft’s Edge browser, on the other hand, uses Microsoft Account to sync payment and identity information, but on Windows it can also leverage Windows Hello’s biometric stack to fill in sensitive fields from the Microsoft Wallet app. Edge’s recent “Travel” feature even scrapes confirmation emails from Outlook and offers to autofill check-in pages automatically.
Google’s move with Chrome and Wallet is a direct counterpunch. By extending Wallet’s reach into the browser, Google can offer a consistent, secure autofill experience that works across nearly any website—a significant advantage over Apple’s tighter ecosystem control. For Windows users, the battle lines are clear: if you’re deep in the Google ecosystem with Android and Chrome, you get this new capability on mobile but not yet on desktop. If you’re in the Microsoft world, Edge and Wallet already deliver a more unified cross-device story, though with a smaller set of supported document types.
What This Means for Daily Workflows
Consider a common scenario: a Windows user planning an international trip. They switch between a desktop PC (where most booking occurs) and a phone (for last-minute check-ins and digital boarding passes). With the new Chrome mobile update, they can breeze through airline check-in and rental car forms on their phone by autofilling passport and VIN details. But back on the Windows machine, they’re stuck copying those numbers from a password manager or—worse—pulling out the physical documents. This friction erodes the seamless experience Google promises.
Microsoft has an opportunity here. If Edge can perfect its own wallet autofill and market it as the no-compromise solution for Windows users, it could sway some Chrome loyalists. Already, Edge’s built-in coupon and price comparison tools, along with its deep Office integration, have won converts. A stronger autofill narrative might tip the balance.
Developer and Website Adoption
For the new autofill to work, websites must use standard HTML autocomplete attributes consistently. Fields asking for passport numbers should be tagged with autocomplete="passport-number", VINs with autocomplete="vin", and so on. Many travel and government sites already do this, but smaller insurers and car rental firms often miss these tags, relying instead on custom JavaScript. Google is working with web standards bodies to formalize a new set of autocomplete values for identity and vehicle data, and it has published documentation encouraging developers to adopt them.
Website developers who implement the correct attributes will see an immediate improvement in conversion rates, as fewer users abandon forms due to tedious manual entry. Preliminary data from Google’s early access program suggests a 17% reduction in form abandonment on travel booking sites that properly support the new autofill types.
Broader Implications for Digital Wallets
The blurring line between browsers and wallets points toward a future where your digital identity is unified across apps and the web. Google Wallet already holds payment methods, transit cards, loyalty passes, and even digital car keys. Adding identity documents and vehicle registrations transforms it into a comprehensive mobile credential platform. Chrome becomes the presenter of those credentials, just as it already presents saved passwords.
For Windows users, this future demands an answer from Microsoft. The company has been building its own set of digital identity APIs under the “Microsoft Entra Verified ID” umbrella, which could eventually tie into Edge. If Microsoft can deliver a similarly seamless experience on Windows with hardware-backed security, it could leapfrog Google in the enterprise space, where handling employee credentials and vehicle fleet information is a daily task.
Looking Ahead
Google has not announced a timeline for bringing the new Wallet autofill to Chrome on desktop platforms, including Windows, macOS, Linux, and ChromeOS. However, code commits spotted by Chromium watchers suggest that a “desktop passthrough” mode is in the works, which would allow a phone with Wallet to securely stream credentials to the desktop browser via a QR code or Bluetooth proximity, similar to Apple’s Handoff. That could be a quick interim solution.
For now, Windows users who want the smoothest travel form experience have two options: keep using Chrome on mobile for last-minute tasks, or consider switching to Edge on both desktop and phone for a more integrated Wallet sync. The next few months will be critical as Google, Microsoft, and Apple all race to make physical documents a thing of the past. As of June 23, 2026, Google has fired the latest shot—but the front lines haven’t yet reached the desktop.