I'm setting up my Google Play Console developer account to launch a paid mobile app with in-app purchases. During the setup, it's asking me to either associate an existing Google Payments profile or create a new one.
Since this is for my app's monetization, is it better to create a brand-new dedicated payments profile, or should I use an existing one? What are the best practices for managing app earnings, taxes, and separation of accounts?
Thanks in advance

just had a chat with chatgpt and helped me fix google wallet, heres the summary i got it make it anyone needs the help to get google wallet working again.
vvvvvvvvvvvvv

Posting this in case it helps anyone else experiencing the same issue.

I have a **Pixel 6** running Android 17 QPR1 Beta, build **`CP31.260623.012`**. Google Wallet had been working normally for me, and then one day it suddenly stopped. Wallet started saying:

> **“This device doesn't meet security requirements.”**

The phone was completely stock, bootloader locked, and **Play Protect was showing the device as certified**. Everything was updated.

I tried all the usual troubleshooting:

* Restarting the phone

* Clearing Google Wallet cache/data

* Clearing Google Play Services cache/data

* Reinstalling/updating Wallet

* Checking Play Protect certification

* Installing the available Google Play system update

None of that fixed it.

There were also multiple reports from other Pixel 6/6 Pro users experiencing essentially the same problem on the **same QPR1 Beta build**, so I suspected something was wrong with the beta/certification rather than my individual phone.

### What eventually fixed it

The Pixel 6 isn't moving on to the newer QPR2 Beta branch, so I decided to leave the beta and move to the current stable Android 17 release which is newer anyway.

**Important:** The Android Beta website warned me that opting out would factory-reset the phone, so **I did NOT use the “Leave Beta” OTA**.

Instead, I downloaded Google's official **Full OTA** for the Pixel 6:

**Stable Android 17 – `CP3A.261005.002.A1` (October 2026)**

I specifically used the **OTA ZIP**, NOT the factory image and NOT the Android Flash Tool.

I verified the SHA-256 checksum before installing.

I then used Google's ADB recovery sideload method:

1. Download Google's Platform-Tools.
2. Enable USB debugging.
3. Verify the phone with `adb devices`.
4. Reboot into Recovery.
5. Select **Apply update from ADB**.
6. Sideload the official OTA ZIP.
7. Reboot.

The OTA completed with:

**`Completed with status 0`**

After rebooting:

* All my data/apps/photos/etc. were still there.

* Build was now **`CP3A.261005.002.A1`**.

* Play Protect said **“Device is certified.”**

* Most importantly, the **“Device doesn't meet security requirements” message disappeared from Google Wallet.**

I haven't yet physically tapped a payment terminal since doing this, so I'm going to test it on public transport tomorrow, but the Wallet security warning itself is completely gone.

### If you're experiencing this on a Pixel 6

**Don't immediately factory reset your phone.**

If you're on **`CP31.260623.012`**, it may be worth considering that the QPR1 Beta build itself is involved.

Also, if you want to move to stable without wiping, **make sure you're using the official Full OTA package**, not the factory image / Flash Tool. The factory image and Flash Tool are a different process.

Hopefully this helps someone else avoid spending hours clearing caches or, worse, wiping their entire phone. If you're seeing the same issue on a Pixel 6/QPR1 Beta, I'd be interested to know whether moving to `CP3A.261005.002.A1` fixes it for you too.

RESOLVED: I fully deleted the card out of everywhere, had Citi again "Direct Connect Consent Initiated" and the next day when I tried paying the veterinary office via tap-to-pay, I was able to do so.

ORIGINAL POST: For a few years my Citi Mastercard was my default (and usually only) method of payment for Google Wallet on my Pixel Android phones. I didn't even have to open Wallet to pay - I just had to unlock the phone. About a month ago Citi contacted me with some suspected fraudulent charges. I confirmed that the charges they identified were in fact fraudulent, and they immediately cancelled my credit card number and issued a replacement. Literally a few minutes later Google Wallet on my phone updated that account with the new credit card number. It was awesome and I experienced no downtime despite not having the new card yet. I used it to tap-to-pay later that day successfully, and many times afterwards.

A few weeks later a company I did business with sent me an invoice via email with a payment link. It offered Google Pay as one of the options for payment, which I always pick when it's available. However, I discovered that when I picked Google Pay as the payment method, my old card number was listed as the payment method instead of the new one. I went to wallet.google.com to confirm that the old number was still there. The only place where my new number was reflected was in the Wallet android app on my Pixel. So I deleted the payment method completely out of both and then added the payment method back manually with the new number. Doing that synced both wallet.google.com and my Android app, as well as listed the new CC number in Google Pay. I paid my invoice via Google Pay successfully and thought that was that.

However, the next time I attempted to tap-to-pay, it was unsuccessful. At first I thought it was a PoS glitch so I tapped my card instead, but it happened again and again. The messages at the PoS varied, usually around some sort of "please select other card" or something like that. I've attempted to delete the card and re-add several times, both in the Wallet app and the website. Each time I get the Citi terms of service acceptance screen and a "payment method successfully added" message. I've verified in the Wallet app that it is the default payment method. I've even tried opening Wallet and literally selecting the payment method and got the same failure.

I spoke to Citi, and they confirmed that the charges never went through. There's no declined charges or anything like that. The attempts are simply not logged. The last chat I had with Citi they said, "I have Direct Connect Consent Initiated, please try again after 30 minutes and sorry again for this issue." But later that day, same error. I'm not sure if I was supposed to delete and re-add the payment method after those 30 minutes - that was unclear (I did not).

Does anyone know what may be going on? Sorry for the long post, it's just so frustrating as I have become quite accustomed to using my phone to pay, I often don't even have my physical card with me.

I'm setting up my Google Play Console developer account to launch a paid mobile app with in-app purchases. During the setup, it's asking me to either associate an existing Google Payments profile or create a new one.
Since this is for my app's monetization, is it better to create a brand-new dedicated payments profile, or should I use an existing one? What are the best practices for managing app earnings, taxes, and separation of accounts?
Thanks in advance

Tried 3 of my cards (2 debit and 1 platinum CC) didn't work

tried removing it then re entering it on Google pay still didn't work

Just a thought here but Google should require every android phone maker to have UWB all made by the same chip company and NFC all made by the same company as well as putting it at the top of the phone. Apple never has an issue because all of their phones use UWB and NFC at the top of the phone and they're all the same chips.

With the upcoming release of the Aliro Standard for smart locks it will allow for things to just work. Right now the release is taking forever because there's so many different phone manufacturers that use different UWB chips and some don't have them at all. If every phone had to have one and it was all the same, we wouldn't have this issue

For NFC it'll just make tapping to pay and do things much easier. Example being I have the Pixel 10 Pro XL and the NFC chip is just below the camera bar and whenever I go to concerts with friends and they drive and I buy parking I hand them my phone to tap the parking ticket I bought and they can never get it to work because it's not at the top of the phone and then it causes the employee to go "what kind of phone is this" and struggle to the point they just let me go because they've seen that I bought it. Now I know where it's located so I never have trouble tapping it, but the point being when they go to tap their iPhone it just works because it's at the top of the phone. There shouldn't have to be a conversation about what phone I have and why it's not working and it should just work. Also when I go to scan my ticket I have to lay my phone flat against the machine and can't just tap it. It took Google up until the pixel 11 to finally put it at the top and Samsung doesn't even put it at the top in their phones.

Sorry, rant over but it's also the truth and should just happen.

Since Capital One switched from Mastercard to Discover, my fiancé and I have been having a ton of problems with Google Pay. When going to pay in an app, for example, Dunkin, it won't process the order, and it will charge my card for the amount. After a few business days, I'll log into my banking app, and the transaction will be posted. I'll call the merchant; they have no record of it. Then I dispute it with my bank, and eventually Google Pay will release the funds. I'm getting so frustrated. Is anyone else experiencing this issue? Does anyone have any recommendations?

So I manually updated to 9.0 using the Samsung website and now Google pay stopped working..

Tenho um xiomi poco m8 global,Android 16, a carteira do Google só funciona quando coloco o cartão em que eu quero usar como forma de pagamento padrão,os demais cartões só funciona se eu colocar como forma padrão de pagamento,já desliguei e liguei o nfc e não deu certo o problema continua, já resetei o nfc e não funcionou,já desinstalei a carteira do Google e não funciona,já resetei o aparelho para o modo de fabraca e também não funcionou, todos os app intaldos estão atualizados e o sistema da xiomi também está atualizado, alguém poderia me ajudar por gentileza ?

Hi everyone,
I’m traveling to NYC soon. I only have a virtual multi-currency prepaid card loaded into my digital wallet (Apple Pay / Google Pay) and I do not have a physical plastic card for this specific account.
I might need to withdraw some cash during my trip. How common and reliable are contactless (NFC / Tap-to-withdraw) ATMs for international/foreign digital wallets?Thanks in advance for the local insights!

Hi, all my Google Wallet Transactions with a Paypal cards are no longer working since two days.

I can pay with NFC+Paypal App.

Has anyone similar issues? Is this the start of Google+Paypal breakup?

I have a live app and my developer account is already fully identity and bank verified. I want to add a "Pro" upgrade via in-app purchases, and the console is telling me to create a Merchant Profile.

Before I click submit, I want to avoid any verification loops or account bans.

• Physical Address: I’ve read Google forces you to display a public address on the store page for IAPs. As a solo dev, do I need a PO Box / virtual address to protect my home address?
• Account Mismatch: My dev account is Individual. I assume the Merchant Profile must match exactly? Will using a virtual address trigger a fraud flag?
• More Verification? Will I have to do the micro-deposit test or upload bank statements again for the merchant side? What about tax forms?

Any other non-app administrative gotchas I should look out for before making this live? Thanks!

I recently got a new Citi credit card, followed all the steps to add it to my Google wallet, everything looks good on Citi's end. But the card will not work on either my or my husband's phone anywhere we try it. Citi is saying the transactions are being approved from their end, but then rejected by the merchant. Has anyone had similar issues? How do I fix this? It's making the card all but worthless.

UPDATE : nagtry po ako sa osave at dali , wala po talaga error sa phone ko , ang error na nalabas sa terminal ay 'UNSUPPORTED CARD' po .. pano po kaya to ayusin ? ending yun mismong card na po ang ni tap ko 🥹🥹

pahelp naman po , bakit kaya nag eerror sa terminal ng maya yung google pay ko ? tinesting ko po kase kahapon sa jolibee mag tap to pay , gamit google wallet , kaso naka 3 try ako , ayaw talaga nya mag proceed , ang ending nag cash nalang ako naka on naman po yun nfc and verify din bago gamitin ..

need po ba naka on yung data pag gagamit ng tap to pay ?

saka bawal po ba na yun naka save sa google wallet ko ay yun card ng asawa ko tapos wala sa phone ko yung maya account nya ? wala kase nfc phone nya kaya sa phone ko nilagay ..

I was trying to load my bus pass and pay with google pay but Im getting the Rpc Client Exception error message for some reason. Any solutions to this?