The moment many Android Wear users have been waiting for has come to pass, with Android Pay/ NFC payments are coming to the platform. Yes, that’s right: something we’ve been dreaming of and screaming for since the launch of Android Wear has finally been confirmed by Google. We’ve touched on this already, but it deserves a heading of its own.
The only watch on the market now that will support Android Pay, at this stage, is the LG Watch Urbane 2nd Edition with LTE, though it looks like it will extend to other Android Wear devices with capable hardware in due course. The better news? If you use Android Wear on iOS, it’ll work there too, though we’re told the workflow will be a little different. To be clear, Android Pay will work on Android Waer devices paired with an iOS device (read: an iPhone), not with an Apple Watch device.
This is, however, a real blow to any other Android Wear device currently on the market (especially seeing as it’s next to impossible to actually get an LG Watch Urbane 2nd Edition LTE in Australia), as of this moment I have officially removed that ZenWatch 3 from my birthday present list.
While it’s still a wonderful device, I use Android Pay multiple times a day, and having it integrated on my wrist would be beyond cool, and I’m all about that. We’ll have to see which NFC-capable smartwatches get Android Wear 2.0 when it’s finally released.
I even can’t use normal Android pay using my Pixel. Poor CBA customers.
That a bet kid!!!???
I don’t think paying with a watch is a useful feature because of the screen size which makes me to think against this update, i am eagerly waiting for its consequences.
One problem I see with paying with a watch is I don’t think you’ll be able to see the screen, so you won’t know when you can move your hand away. When paying with a card, you see the stores readers screen. When paying with a phone, you see your phones screen.
Another problem would be, if you wear your watch on your left hand, and have to pay on a Tyro payment device (that has the reader on the left of the device). That’s going to be a difficult wrist twist to get it to scan.
I had thought the second issue (have to admit thinking of it at drive throughs and the like. Even if it stops the need for taking out the phone at most places, the ones it doesn’t make sense there will still be the phone.
The first issue you raise, I assume they will have a sound and/or vibration the way the phone does that shows it has been successful.
These issues must have possible solutions as the Apple Watch already supports Apple Pay and the Samsung Watches (or maybe just one of them) supporting Samsung pay.
I’m going to take a break, Phillip has all the discussion covered like a pro!
Hi Duncan, do you not worry about skimmers taking $100 out of your account just by walking past you in the street? I use Android Pay on my Nexus 5X, but it will not scan unless I deliberately unlock the screen. And that is a good thing. I see Android Pay on my phone as more secure than carrying my actual PayWave Mastercard. On a watch without a locked screen what will happen?
A) lets see the implementation
B) Android Pay has a dispute mechanism built straight in so I am assuming if you notice the buzz of a “skimming” attempt, you can instantly dispute it and good luck the skimmer explaining why it should not be backed out!
c) Its a one off, as I understand, credit card number so they can’t steal that either.
JMTC
all of this, well said Phillip
You don’t get a new token on every transaction you get a token when you setup and it’s used for every transaction untill it’s removed not exactly one off
Worrying is like a rocking horse, it won’t get you anywhere but it gives you something to do!
Let’s see how it works before we worry