Google Wallet for Pixel Watch might roll out PIN code entry before tap-to-pay

Google Wallet for Wear OS appears to be undergoing a significant security update as Pixel Watch users may soon find themselves prompted to input a PIN code before completing tap-to-pay transactions. This adjustment mirrors recent changes in authentication procedures observed on Android phones.

Reports suggest that this added layer of security marks a departure from previous practices, where Wear OS users could seamlessly tap their watches to make payments without entering a PIN. While the motivation behind this change is undoubtedly rooted in enhancing security measures, its implementation raises questions about the user experience and the underlying trust in Wear OS.

This convenience factor was a major selling point for contactless payments via smartwatch, capitalizing on the fact that most users wear their watches consistently. However, the imposition of a mandatory PIN entry before executing tap-to-pay transactions on Wear OS devices appears somewhat disruptive for Google Wallet users.

It is reasonable to infer that this alteration implies a mandatory initial failure upon tapping the device, prompting users to open the Google Wallet app and authenticate themselves before attempting the transaction again. This introduces an additional step in the payment process, potentially undermining the seamless user experience that Wear OS aims to deliver.

On Android phones, Google Wallet currently allows a three-minute window after unlocking the device to perform contactless payments. If this window elapses, users will need to re-authenticate (via PIN, fingerprint, etc.) before attempting another tap-to-pay transaction. However, opening the Google Wallet app itself bypasses this requirement.

Interestingly, Google recently confirmed this change for phones as an intentional update aimed at enhancing security for in-store payments. Users now receive a prompt requesting identity confirmation through PIN, pattern, fingerprint, or a Class 3 biometric unlock (depending on the device’s capabilities). Notably, the option to bypass verification for transit fares remains available.

However, the official Google Wallet support documentation does not explicitly mentions a device in its explanation of the update. This ambiguity has led some to believe that the update pertains solely to phone-based transactions.

For users who found the phone update inconvenient, Wear OS previously offered a more streamlined alternative. Unfortunately, with the potential addition of a PIN requirement, this advantage might disappear. Undoubtedly, fingerprint unlocking on a phone is considerably more convenient than entering a PIN on a smaller smartwatch screen. So I hope that Google takes a decision that’s in the best interest of everyone involved.