Watch 4 wifi and google pay

[me just saying]

was using google pay and noticed it is not charging the card on the screen. Contacted google but they said it is not their problem and to contact my bank. Cannot contact my bank till Monday. Just wondering if anyone here has had the same problem. I really don't think it is a bank problem unless they pulled the card from being used for mobile payments.

What it is doing is one card is on the screen but it charges the next card instead. I made sure the watch was updated and rebooted it. I do not want to delete the card and put it back since it will require a phone call to the bank for verification which again, cannot be done till Monday.

Any thoughts?

 

[Talderon]

Honestly, I use Samsung Pay, not Google Pay. Have you tried that?

 

[kikbxr1969]

I have not noticed that. But, I only keep one card on my watch. If I want to use a different card, then I use my phone. I don't know if that is an option for you. But, that may fix your issue.

I quit using Samsung pay myself when they got rid of MST on the phones. Google Wallet just works better (at least for me), and I don't see any reason for S Pay any longer as they no longer have the features that made them unique have instituted the PIN requirement at every transaction. At least with Google Wallet, I only have to unlock after I take my watch off.

Edited to add: Looks like it is not just you. It appears to be happening to other users of the Galaxy Watches specifically. (Which means it is likely to be a watch issue and not a Google Wallet issue). One poster recommends cycling back and forth through the cards every time you use it regardless of whether the card you want to use is the default.

https://www.reddit.com/r/GalaxyWatch/comments/vc8n1y/wrong_card_being_charged_in_google_pay/

https://www.reddit.com/r/GalaxyWatch/comments/sa490v/google_pay_using_wrong_card_on_galaxy_watch_4/

 

[tismydroid]

I have not had this problem with my GW5. The Reddit posts that Kikbxr1969 linked are 7 months to a year old so it does seem that this must have been a problem. I follow those reddits and haven't noticed anyone posting the same problem recently so it seems they may have fixed this issue in an update. Does your watch have the latest updates?

Sent from my SM-S908U using AC Forums mobile app