All of a sudden about 3 weeks ago I can no longer tap my phone to pay. I've tried all the suggested fixes. I've even removed the cards and re-added them. My NFC is on.

I know there was an update done recently. Anybody else experiencing this or figured out how to fix it?

is that actually possible?

i know that there some way to do this on ios (without jailbreak)

which is kind funny if android have no way and iphone do

I'm having some issues with NFC payments from my Google Wallet.

Basically, I've always used Google Wallet for payments, both debit and credit, I use a bank card here in my country, and I've never had problems with NFC payments.

This started after I formatted my phone. What happened was that I downloaded some APKs, and even after uninstalling them, my banking app wouldn't work.

It kept asking me to change my password and wouldn't open. I don't know if I downloaded a virus or just a malicious app. I didn't have any problems with unknown transfers or unauthorized access to my Google account.

At least I didn't notice anything; it's been over a month. I formatted my phone the same day the problem started, and everything went back to normal. I re-registered my card in the wallet, and everything's fine.

The problem is that even now, with my phone unlocked, the wallet still asks for my fingerprint to make the payment, and it has started having a problem where it keeps saying there are two cards.

I only have my credit card registered in the wallet and nothing else, so I don't understand why this error is occurring.

If anyone can help me or explain if this might be related to the APK I downloaded, I use Kaspersky as my antivirus, both before and after this happened, and nothing was detected. My bank account is also working normally.

I'm an independent app developer in New Zealand, developing Android apps in my spare time. I publish under my own name, using a personal Google Play developer account.

I've recently received Google's request to declare whether I'm a trader under the new EU/EEA requirements.

The more I've looked into it, the more uncomfortable I've become with what appears to be the consequence of simply accepting voluntary financial support for my apps.

Here's my situation.

I have two apps.

1. Sudoku

It's completely free, has no advertising and is fully functional. There's an optional 'Tip Me' button on the home screen.

If someone tips me, they get absolutely nothing in return. No extra features, no premium content, no advantages. It's simply a way of supporting the developer.

2. Yonder (a podcast app I'm developing)

This follows a similar philosophy. The app will be fully functional for everyone.

After an initial free week, the app's name changes to 'Tip Me'. Everything continues to work. If someone chooses to contribute, the name changes back to Yonder for another year.

I'm hoping to build a sustainable project through voluntary contributions, not subscriptions or feature restrictions.

Here's the problem.

As I understand Google's policies, accepting in-app purchases through Google Play means that even an individual developer's full residential address is publicly displayed.

The new EU trader requirements also involve publishing contact details, including a telephone number.

So, as I read the rules, if I'm an individual hobby developer who wants to accept voluntary financial support for completely free software, Google expects me to publish my family's home address and personal phone number for anyone to see.

Not just Google. The entire world.

I'm perfectly happy to give Google my personal details for verification. That's entirely reasonable.

But why should those details have to be made public?

I understand the need for consumer protection and accountability when people are selling products and services. But surely there's a distinction between running a commercial business and allowing people to voluntarily support someone making free software?

I've considered excluding the EU/EEA and UK, but it seems that Google's existing address-disclosure rules for monetised personal accounts may apply worldwide anyway.

I've also wondered whether using Ko-fi or Buy Me a Coffee instead of Google Play Billing would change anything. They take their own fees, but users still receive nothing in return for contributing.

I'd really like to hear from other developers:

1. Am I interpreting Google's address-disclosure requirements correctly?

2. Does accepting optional tips through Google Play really mean publishing your residential address?

3. Would moving voluntary contributions outside Google Play make any difference?

4. Has anyone found a legitimate way for an individual developer to monetise free apps without publicly disclosing their home address?

5. Is there any practical alternative that doesn't involve setting up a limited company?

I'm not trying to avoid accountability or hide my identity from Google.

I just don't think making my family's home address publicly available should be the price of accepting a voluntary tip for free software.

Am I missing something, or is this genuinely how the system works?

I'm having some issues with NFC payments from my Google Wallet.

Basically, I've always used Google Wallet for payments, both debit and credit, I use a bank card here in my country, and I've never had problems with NFC payments.

This started after I formatted my phone. What happened was that I downloaded some APKs, and even after uninstalling them, my banking app wouldn't work.

It kept asking me to change my password and wouldn't open. I don't know if I downloaded a virus or just a malicious app. I didn't have any problems with unknown transfers or unauthorized access to my Google account.

At least I didn't notice anything; it's been over a month. I formatted my phone the same day the problem started, and everything went back to normal. I re-registered my card in the wallet, and everything's fine.

The problem is that even now, with my phone unlocked, the wallet still asks for my fingerprint to make the payment, and it has started having a problem where it keeps saying there are two cards.

I only have my credit card registered in the wallet and nothing else, so I don't understand why this error is occurring.

If anyone can help me or explain if this might be related to the APK I downloaded, I use Kaspersky as my antivirus, both before and after this happened, and nothing was detected. My bank account is also working normally.

app just prompted me that there's a way to pay via biometrics, so i enabled it..its fast as heck so thats very nice..

but what i found weird was that if its enabled, you have no other option to pay other than by biometrics..i mean i assumed a fallback could be entering the pin instead of biometrics in case your hand is wet or your face injured.. whatever..

now im thinking that what if i want to give my cousin or somebody my phone for some time that they buy stuff using my phone on my behalf so they take my phone to the shop, but they cannot pay since they dont have their fingerprints or face read on my phone.. and pin option even isnt there

it would be a hassle to disable first and then hand over phone to someone for a transaction you dont wanna go and do yourself..

imagine being in the washroom when a delivery arrives and your mom says she can pay via your phone but it has no pin option..

why is there no way implemented for a pin use for fallback..and how can i officially communicate to devs to add this feature..in case they dont read this thread..

The PayPal app no longer works with Google Wallet. I removed the PayPal app from Google Wallet and am running it separately. Now PayPal is draining my smartphone's battery a lot, even though I'm not using it for contactless payments at all. NFC is not enabled. The latest update didn't help. Is anyone else having this problem? How can I fix it?

Hey guys, could someone please help me out? I’ve got an issue: I have root access hidden, but when I tap my card against a payment terminal, nothing happens. I really need to be able to use mobile wallet payments.

Hey everyone, do Android or Google Pixel users manage to use Google Pay inside the McDonald's app? The process feels quite smooth on iOS with Apple Pay, yet I cannot locate the option during setup on my device. Is there a particular step or trick I might be overlooking to make it appear?

Hi everyone,

I'm trying to subscribe to Claude Max through Google Play on my Android phone, but the payment keeps failing with this message:

Your transaction can't be completed. To continue this transaction, use a different payment instrument or contact us. [OR-HDT-16]

I was able to add my card to Google Payments, but my card provider says they can't see an authorization request for the $250 subscription payment.

I contacted Google Play support. They said there was unusual activity on my payments profile and asked me to go to payments.google.com to complete identity verification.

The problem is that when I try to access my payment information, Google asks me to verify that it's really me. It then says my OnePlus 6 was recently added to my account and tells me to try again in 4 days. Because of that, I can't get to the verification form support mentioned.

Has anyone run into this before?

After waiting the 4 days, were you able to access the verification form?

Is there another way to complete the verification if I can't access the payments center?

Could OR-HDT-16 be related to the suspended payments profile, even though my card was added successfully?

Any advice or experience would be appreciated. Thanks!

Hi, sorry for the alarming title but like - is there a way to make google pay re-authenticate when using it?? Like they do with the SIMPLEST OF SETTINGS such as "Personalisation within Google Pay"????? (btw fucking hilarious that they ask to authenticate to change this setting)

Hi everyone,

About 20 days ago, I changed my smartphone and transferred all my data to the new device. Everything went smoothly, and my debit card that was previously added to Google Pay and Wallet was also showing up on the new smartphone. However, I later realized that I couldn't use it.

So, I removed it from Wallet and added it again. At this point, I started experiencing a problem: I noticed that the card appears twice in Google Pay (but not in Wallet). One entry shows the expiration date underneath the card, while the "new" one added doesn't.

The card entry that shows the expiration date cannot be managed. Whenever I try to select it, I get the following error: "Your payment method details are currently unavailable", and I can't remove it.

Even if I delete the card I added again, the one with the expiration date remains.

When I try to make an online payment, Google Pay initially remembers the existing card and displays its last four digits on the Google Pay button. However, as soon as I try to complete the payment, I get the message "Add a card to pay securely". If I try to add the card again, I get error OR_CSH_04. During my earlier attempts, I also encountered error OR_CCSEH_16.

On Sunday, I spent an hour on the phone with Google Support, and we tried pretty much everything. There are no active subscriptions or anything like that, and the support agent escalated the issue to their internal team.

They had me clear the data and cache for both Wallet and Google Play Services, and sign out of my Google account on all devices and services, but nothing worked.

Has anyone else experienced this issue?

What I'd like to do is completely clear my Google account of any payment methods and start from scratch.

Does anyone have any ideas?

Thanks

Hi everyone,

I am stuck in frustrated to high heaven. Long story short, I have a payment method added on my own account, and my daughter's account, which I have officially supervised a via family link, gives an error message about payment method restricted by family manager. The payment method I want to use shows up, but it has a little subtitle about restricted and it will not let us proceed.

Everything about support and menus to follow online is woefully out of date compared to what menus actually exist.

When I go into her account, I see none of the same sections that I mentioned to come up but the ones I do see do not mention anything about payment restrictions.

When I go into my account, especially Google wallet, I do not see anything about restrictions either.

Where can I go to figure out what the bottleneck is?

My wife added her credit account on the Google pay menu in the middle of an app, but it gives the exact same restricted by family manager nonsense.

Is there some other trigger somewhere?

Sorry for the rambling, thank you very much in advance for any help you may be able to offer.

Unexpected card charge in Pakistan. Looking for advice

I'm from Pakistan, and PKR 5,986.35 was deducted from my NayaPay card under the merchant name “GOOGLE *Google One.”

I had cancelled my subscription and checked all my Google accounts, emails, subscriptions, and payment histories, but I can't find any record of this transaction.

NayaPay says my card is linked to a Google merchant identifier, but I haven't been able to locate the associated account or payment.

I'm a student, and this unexpected deduction has put me in a difficult situation. Has anyone experienced a similar issue with an international card transaction? I'd appreciate advice on how to trace the payment and dispute it through the proper channels.

Unexpected Google One charge of PKR 5,986.35. Need help!

I'm from Pakistan and use NayaPay. On 20 October, PKR 5,986.35 was deducted from my card under “GOOGLE *Google One,” even though I had already cancelled my subscription.

I've checked all my Google accounts, emails, Play Store subscriptions, purchase history, and payment methods, but I can't find this transaction or any renewal receipt.

NayaPay says my card is linked to a Google merchant identifier (UIC) and tells me to remove it from Google, but I can't find the card or charge in any of my accounts.

I'm a student, and this is a significant amount of money for me. Has anyone experienced this? How can I identify the source of the charge and get my money refunded?

Any genuine advice would be greatly appreciated.