The last tragic incident that caused data loss and headaches for Wear OS users was a glitch. Their switch to Google Wallet is almost as hassle-free as its highly convenient tap-to-pay solution, which now requires the input of a PIN code before any transaction. It’s also heartening to know that Google reassures us, assuring us that the problem is not with a planned security update.
Feeling this pain is like a piece of cake for smartwatch manufacturers. Unlike traditional physical wallets, which might otherwise impede this instantaneous access, digital wallets like Wear OS provide a PIN code that eliminates this disadvantage. It’s surprising how quickly we get used to a routine and now pointing at four digits on a small screen has become something we’d rather avoid than a quick pinch.
They are expected to get into more trouble with Google’s release regarding future plans for Android phone authentication. The three-hour window after the phone is unlocked is an opportunity that Google Wallet “GooglePay” tap-to-pay transaction users can now take advantage of. However this feature is not on Wear OS, so it is not reflected on it.
The phone upgrade exposed a common issue with security, whereby access could only be regained after a short period of inactivity. Although this measure may cause inconvenience to a person later, it points in the direction of Google implementing financial information security measures.
While Google recently made authentication mandatory for all non-transit transactions, banks will do the same from January, except for transactions made from digital wallets. While this may disrupt the seamless payment operations that some consumers are accustomed to, it certainly represents a strong security step.
If you’re experiencing PIN issues in Wear OS, have hope that it’s a temporary bug. When Google deals with this issue, the fluidity of the tap-to-pay experience should return and customers should feel efficiency and ease.
