Join now - be part of our community!

Problems with Android Pay (in UK with mastercard credit card)

profile.country.GB.title
ezy2ezy
Contributor

Problems with Android Pay (in UK with mastercard credit card)

First I know there is an issue with some Visa based cards loaded on an Android Pay when trying to use sone terminals in certain shop chains (as it is on the Android Pay website)

Second...  UK terminals are not the same as American shop ones in that we do not get the options to "select credit" that they get.

When the payment terminal requires a security double check  (the "pin") i cant get shop card terminal which have previously accepted "touch" payment to then accept payment.  (This is more than one terminal in more than one shop, in more than one chain of shops... ie it is many different shops where the till had worked and then wont)

the phone which was just unlocked then says on the screen "Unlock to use Android pay"  and "enter your device pin to continue"

yet... 

-touching the z5 finger print scanner  

-the phones pin in the phones screen

-the card pin in the phones screen

-putting the cards pin in the terminal

 all result in "card type not supported" or words like that on the terminal screen and a failed purchase

has anyone else got android pay to work at the security double check stage or had the same problem (and solved it) ?

42 REPLIES 42
PhilJSmith67
Visitor

Bost101, what were the immediate after effects of clearing out Google Play Services storage? What had to be set up again? I don't want to do this on a trip and find that my phone is kind of jacked until I get home Slightly_smiling_Face
Bost101
Visitor

It asked my to pick a backup account as soon as I turned my phone one again. swiped the Google Play Store prefences (ie do you want icons to be added to the homescreen) but apart from that nothing major for me! 

PhilJSmith67
Visitor

Excellent. I will try it, because the system update that came through two days ago 32.2.A.0.253 didn't fix my E6603.
Bost101
Visitor

Let us know how you got on Slightly_smiling_Face
PhilJSmith67
Visitor

Bost101 you rock the house. Cleared out memory for Google Play Services and Android Pay, restarted my Z5, re-added my cards, went to my local McDonald's just to try it. Swiped to pay, and didn't get prompted even once for the screen lock code. Success!
Hillfigger
Visitor

Bost101 fix totally worked for me first time after I did it. No problems at all. Fingerprint unlock still works too. Thanks!
Bost101
Visitor

Awesome to hear guys that it worked for you :smileysmileythumbsup: if your happy it worked mark it as an accepted soultion, this will help other people see how to reslove it Slightly_smiling_Face

profile.country.GB.title
ezy2ezy
Contributor

BOST are you still having no problems with android pay?

(i had the 6.0.1 update, recently but its gone back to not working...  it briefly worked when an android app update occured, but it only worked 3 times... there was another android pay updaye this week but it didnt clear it..   as i've had the bank load the card 3 times i dont want to uninstall it and reinstall it, talk to the bank, get all the paperwork through the post again...  especially as today they rang me to confirm my card is "working" on the app... they could see the "failed" and the "worked" and just fobbed it off as android pay at the retailer end is the issue... weird as it is the same terminal that accpets one time and doesnt the next)..

poxona
Visitor

Hi all, for those with fingerprint unlock, I've experienced the same issues. Google are aware of it and are working on a solution. The steps outlined earlier in this thread do work, and once you have completed them, you are able to add fingerprint unlock back to the device. However, you MUST not unlock the phone with your fingerprint when making a purchase! Either just flick the screen on, or unlock using your second method e.g.pin. If you start to unlock with your fingerprint when making a purchase you will start to experience issues again.
spockout
Visitor

I am in the US and have the same problem it's been over a month. At some level Sony has admitted to the problem, but offer no solution.