Hi, I need help adding a card to gpay.
The card cannot be added for contactless payments. I don't know what it is or what could have happened while playing rom. In the original, everything worked well. After that I switched to alexis rom and everything worked. After some time I tried xFire rom and also nothing. I wanted to try the resurrection remix because it's my favorite rom from previous phones and I don't know there because I left it due to problems with the Gear S3 Frontier parking. Using Odin, I recorded the original rom and the problems started. The card could not be added at all, but it was resolved with the bank. The problem was logging the card on multiple devices and the bank fixed it. The card can be added manually, but the settings for contactless payments cannot be completed. The process ends when the card is verified at the bank. I thought it was a rom problem, but I tried several roms and the problem is the same.
I tried to set the card on my older asus zenfone max for m1s HavocOS and the card was added to gpay without any problems. So the problem must be in the phone.
Could someone please help how to fix this? I'm really desperate. Sorry English, I use google transalator
Are you rooted?
Yes. Currently alexndr rom. Magisk hide. Neither the banking app nor the gpay app report root. Safenet check pass
The strange thing is that a week ago on alexis rom it still worked. Now it is not possible to add for contactless payments on any rom. Manually yes, but only for online payments. The contactless payment setup ends during the verification process at the bank.
jampce said:
Yes. Currently alexndr rom. Magisk hide. Neither the banking app nor the gpay app report root. Safenet check pass
The strange thing is that a week ago on alexis rom it still worked. Now it is not possible to add for contactless payments on any rom. Manually yes, but only for online payments. The contactless payment setup ends during the verification process at the bank.
Click to expand...
Click to collapse
I have no idea what to suggest then, it can't be root related because safety net passes, have you tried adding another card to google pay?
Sent from my SM-G960F using Tapatalk
I tried to add a girlfriend card and it ends the same way. My card on my old phone can be added normally .. That's why I don't understand .. I already received an answer from Google support that everything is fine on their part ..
So there must be something wrong with the phone. But what .. Bootloader I have for sure flash as well. The only thing that comes to mind can be influenced by CSC? I don't know what it was originally like, but I chose XEZ (Czech) when installing alexis, which it probably should be. But there was a card to add and after replacing other roms it doesn't even go there.
I'm still thinking. Before flash original rom using odin, I twrp wipe all the partitions (including vendor and preloaded). It still seemed to me that everything was not right, so I did it. Couldn't it be wrong? If so, can it be fixed? Although I assume odin will record everything again
Related
So I tried doing the systemless root thing. I tried confirming that android pay would still work by removing my cards then attempting to re-add them and it failed. I tried undoing what I did by flashing stock recovery, boot, and system. Still a no-go. I tried running the flash-all.bat (i removed the "-w" so I would keep my data). Still can't add a card.
I resorted to running the flash-all.bat, build MDB08M, to be 100% stock. I STILL CANNOT add a card. The message has been the same every single time "Android Pay cannot be used - Google is unable to verify that your device or the software running on it is Android compatible"
Am I missing something? I don't understand how a 100% stock flash is not able to work.
If it makes you feel any better I've been running 100% stock since day 1 and tried using Android Pay for the first time today. Failed same as yours saying device or software couldn't be verified. I had originally set it up using my card that was already set up on my Google account. When this card didn't work I removed it and tried adding the card again manually. Couldn't even add a card. Tried rebooting several times and disabled developer options. Still not working.
I can select a card already on my google account, accept the terms, then the message pops up. Happens with two different cards associated with my account.
I'm fully stock, but unlocked bootloader.
Android pay used to work as recently as 4 days ago, but failed today with the error unable to verify.
Not willing to relock bootloader. Was there an update of Google play services that changed the way they check for modifications to include bootloader unlock?
I went back to complete stock relocked bootloader and Android paid don't work for me because chase bank stopped supporting Android pay so I went back to custom ROM
Just to note my bootloader is unlocked, otherwise I am 100% stock.
I manually tried updating Google play services to the latest version, but Android Pay gave me the same message but at a different point in the process - right after I clicked "Add a credit or debit card." I wasn't even able to see cards already associated with my account like before. I ended up uninstalling the update because it seemed to make things worse.
I just tried this app and it says I'm failing the SafetyNet check:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Same here. Completely stock 5x with nova. Had added a card, but wasn't working so I deleted it to try to re-add. No luck... Pretty annoying actually. I don't use it that often, but there have been several occasions I forgot my wallet going to the grocery store and paid with android pay cause it's all I had. Hope it gets fixed soon.
Looks like it is working all of a sudden. I was trying the safetynet checking app a few times a day... just tried now and it finally passed. Gave android pay a whirl and both cards were able to be added without issue. So apparently something happened on Google's end. Google play services is the same version now as it was when android pay failed to work.
I was failing the safetynet API yesterday. I still am.
I was also unable to pay with anything yesterday, but today I was able to add a card. Presumably it's partially fixed.
I went completely stock with relocked bootloader and STILL failed the test.
If it's working again, it's probably something wrong on Google's part. I'll try adding a card with systemless root
Ugh, what a headache, I ended up deleting everything for no reason.
Anyone else find it to be working now? I ran the safety net check last night and it passed. Tried adding my card and this time it worked. Big G must have fixed something on their end.
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Google Pay can be used under rooted device?
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
sb1893 said:
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Click to expand...
Click to collapse
JD_dadada said:
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
Click to expand...
Click to collapse
I've always been able to leverage the root hiding capabilities offered by the root providers I have used. Originally suhide for SuperSu...then when I moved to Magisk MagiskHide. Both have worked well for my root (and unlocked bootloader) hiding purposes. I've always been able to use Android/Google Pay, banking apps, alarm system apps, Netflix, etc...Occasionally, the cat and mouse game catches up with the root hiding solution, but the developers have been pretty quick to overcome any of the challenges encountered thus far.
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Zaczero said:
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Click to expand...
Click to collapse
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
javlada said:
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
Click to expand...
Click to collapse
Looks like I found the problem (at least in my case).
Some ROMs got issues with fingerprint scanner. I noticed that in my bank app after adding the fingerprint unlock it started to crash. Also in google play I couldn't add fingerprint as payment confirmation.
In Google Pay one of the steps of verifying cc is fingerprint check. I think that this fingerprint bug may cause the google pay to fail.
After installing a ROM with fingerprint scanner working properly (now I'm on LineageOS) the issue went away. Got my cc verified successfully with root and rom
Hey guys just updated to the latest magisk manager and magisk root on my pixel a few days ago but i just noticed that my Google pay had removed my bank card. Checked magisk manager and went into the magisk hide list and nothing was checked so i manually checked necessary apps including Google pay. Now even after that and after a reboot and clearing data of Google pay AND despite magisk passing a safetynet check Google pay still refuses to accept my bank card. Should i roll back to an earlier version when it was working? Is there something broken in the lastest magisk manager?
Thanks in advanced.
February security update
Magisk manager 7.0
Magisk 18.1
ElentalX-P2-2.09
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
CyberpodS2 said:
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
Click to expand...
Click to collapse
Thanks so much for confirming must be a problem on my end. I've been getting random freezes at night which had me waking up with no alarm. Guess it's time for a clean install because obviously something went wrong on my end. Thanks again G.
Yeah....there's a (good) chance that it's just as what happened with @acheney1990 and me...
you can read all about it HERE, but suffice it to say; it can easily be on the banking's end "flagging" with all the validation that's needed -- which is it's own headache trying to understand why they keep tripping it up this way....
Hey did you ever happen to get a solution on this? I seem to have run into the same problem because everything is setup the same as before, but since I've upgraded to Pie in Feb security, I can't use Google Pay (unable to pay in store), Zelle, or the Chase app (force closes immediately, apparently on checking my GPS location it seems).
My problem started when I updated my Moto x4 to latest Pie update 29.69-26-5. I was on Magisk 18.1, and Manager 7.0 which I had to uninstall to get the update. After reinstalling Magisk, Passing safety net, I get a message at the POS saying my phone won't work with Google Pay. My debit card (Chase) is still listed in Google pay on my phone but when I try to add another card I get "This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way"
if I clear the storage and uninstall and re-install Google Pay, it still has my debit card listed, so for whatever reason, it's keeping my payment info even though I cleared the storage.
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Itachisasuke said:
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Click to expand...
Click to collapse
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
simplepinoi177 said:
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
Click to expand...
Click to collapse
That is exactly what has been suggested and even outlined here and there. I tried a couple different scenarios but it became too cumbersome trying to juggle it all. I'll just wait for an update to be released. Lol
FIX:
1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
2. Add Google Pay and Google Services Framework to Magisk Hide
3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)
Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
mine is fine
try re flash your rom
i42o said:
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
Click to expand...
Click to collapse
Long thread and a lot of moving parts, so work backwards on the thread. Personally, I am just waiting until a final and formal fix is found on stable Magisk and up to date Play apps.
https://forum.xda-developers.com/app...ssion-t3906703
My experience with this issue is I run GPay, go back to Magisk, safetynet fails on both.. So I force close Magisk, clear cache and data.. reboot. Open Magisk back up, Safetynet passes.. Gpay sets up fine. Sometimes you have to do this several times and it's a real pain but it's always worked for me..
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
dipstik said:
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Click to expand...
Click to collapse
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
jbarcus81 said:
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
Click to expand...
Click to collapse
Get a 2.83 build. Xda shortens links and you lose them on copy text
dipstik said:
Get a 2.83 build. Xda shortens links and you lose them on copy text
Click to expand...
Click to collapse
I know.. it's ridiculous, appreciate the clarification!
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
rob42ert said:
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
Click to expand...
Click to collapse
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
TonikJDK said:
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
Click to expand...
Click to collapse
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
sliding_billy said:
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
Click to expand...
Click to collapse
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
TonikJDK said:
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
Click to expand...
Click to collapse
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
sliding_billy said:
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
Click to expand...
Click to collapse
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Bogega said:
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Click to expand...
Click to collapse
And the doubt kicks back in, LOL. Luckily, I just carry a real card until this is formally solved (hopefully).
Bogega said:
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
Click to expand...
Click to collapse
Sadly this method only works for a limited time.
Overnight GPS updates to version 15 by its own self and GP stops working.
I'm not sure I'm ready to to this procedure daily just for Google pay. For the time being I'll use my card until Magisk developer finds solution to this problem.
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
yeah nothing worked for me even when I uninstalled magisk and tried the steps above on stock. Ended up factory resetting. but thats the last move to do
TonikJDK said:
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
Click to expand...
Click to collapse
Google Pay is a real asshole and doesn't let you know something is wrong until you actually tap to pay.
It's happened to me a couple of throughout my ownership of Pixels.
Hello guys, I've been getting annoyed by this problem, that's about adding my credit card on google play.
I'm rooted with magisk, android 8.0 latest security patch and the safetynet is working, the same for magisk hide, netflix and pokemon go. But when the issue is registering the card on google play, it just tells me every single time that the numbers are wrong, and this is happening for like almost a year... I've already scanned the card to add it, typed the numbers manually and nothing seems to work...
Is there anybody else having this problem?
You can also try and add it from a pc on their site, it has a Payment Methods on the left side and once you click that you get the option to add a payment method. I know it's basically a workaround for your issue but figured it would still help you
Hir0xM said:
You can also try and add it from a pc on their site, it has a Payment Methods on the left side and once you click that you get the option to add a payment method. I know it's basically a workaround for your issue but figured it would still help you
Click to expand...
Click to collapse
thanks for trying, but didn't work.. it just says that there's an error on my card info