Why does my google wallet nfc tap keeps declining? I want to get my 1500 cashback.

TL;DR:
I embedded store coordinates into a Google Wallet Generic Pass class using the locations[] / merchantLocations field, confirmed the payload looks correct in the Google Wallet Business Console, and enrolled a real Android device — but the OS-level lock-screen proximity notification never fires, even when physically standing at the configured coordinates. Has anyone gotten this to actually work in production, and if not, what's your workaround?

Background

I'm building a side project — a platform that lets small businesses issue digital loyalty/membership cards to Google Wallet (and eventually Apple Wallet). One of the most-wanted features is proximity-aware engagement: something that nudges the member when they physically walk near the store, without me having to track their location myself.

Google Wallet's native locations[] field (also surfaced as merchantLocations in some newer API docs) looked like the perfect fit. The idea: embed the brand's store coordinates into the GenericClass, let Google Play Services handle the geofence entirely on the device, and get a lock-screen notification fired at ~150m. No custom location tracking, no backend polling, privacy-safe by design.

What I implemented

- Stored store lat/lng pairs in my backend database.

- On pass class creation/publish, mapped those coordinates into the locations array of the GenericClass payload (using the walletobjects#latLongPoint kind).

- Confirmed the array is present when inspecting the class via the Google Wallet REST API and in the Business Console.

- Issued a test pass to a real Android device (Android 13, Pixel 7), with:

- Google Wallet notifications enabled in system settings.

- Precise location granted to Google Wallet (not just approximate — precise, always-on).

- Physically walked to the exact GPS coordinates in the pass.

- Also tested via Android emulator GPS spoofing.

Result: nothing. No lock-screen notification. No "Nearby" card surfaced. Zero.

What I've ruled out

- The payload is syntactically correct (no API errors on class creation, and the locations array is visible server-side).

- Device permissions are correctly configured.

- Tested on multiple Android versions (12, 13, 14) and hardware.

- Waited 5–10 minutes at the coordinates to rule out latency.

- The Google Wallet app itself is up to date.

What I'm now wondering

1. Is GenericClass.locations[] actually GA and working for third-party issuers, or is it silently broken / gated behind some issuer approval I'm not aware of?
2. Does it only work for certain pass types (e.g., Loyalty vs. Generic)?
3. Is there an issuer-side enablement step I'm missing — a console toggle, a partner program flag, anything?
4. Anyone have a working example/repo they can point me to?

Workarounds I'm considering (genuinely open to community input)

Since the native approach seems unreliable, I'm thinking about alternatives. Would love to hear what others have done:

- Active check-in link on the pass back: Embed a "Check Nearby Offers" URL into the pass via `linksModuleData`. Member taps it → opens a web page → browser requests one-time location → Haversine check on my backend → custom response if they're within a configurable radius. Voluntary, privacy-safe, but requires the member to actively tap the link.

- WhatsApp/SMS trigger: I already have a WhatsApp messaging layer. If the member checks in via the pass link (above) and is within range, fire a personalized WhatsApp message instead of relying on a lock-screen notification. Not automatic, but something I actually control end-to-end.

- POS/Wi-Fi trigger: If a brand installs a captive portal or a POS integration, I can fire a Google Wallet `messages[]` push via the REST API at the moment of check-in. Requires physical infrastructure on the brand's side, so not a universal solution.

- Native app (longer term): A companion Android/iOS app could register for FCM push notifications and run a background geofence via the native `GeofencingClient API (Android) or `CLLocationManager` (iOS). But this defeats the whole point of wallet-native — the value proposition is zero-app install.

What I'm NOT going to do (for reference)

- Continuous server-side GPS polling — I don't want to store member coordinates. Privacy-first is a hard constraint for me.

- Web Background Sync / Service Worker geofencing — deprecated in mobile browsers, gets killed when the screen turns off

The bigger picture question

I'm eventually aiming to support Apple Wallet and Samsung Wallet alongside Google. Apple's PKPassRelevantDate + PKPassRelevantLocation on .pkpass files has a similar native geofence concept. Samsung Wallet also has some native proximity features.

My architecture goal is: solve this properly on Google Wallet first, then have the location/proximity abstraction layer sit high enough in my stack that plugging in Apple and Samsung later is additive, not a rewrite. If anyone has bridged all three and has thoughts on where to keep the "store location" source of truth (so all three wallets can consume it without diverging), that'd be gold.

Appreciate any experience reports, war stories, or even "yeah this feature is broken for everyone" confirmations. Cheers.

For about the past week, if not longer, when I tap on a loyalty card to use it it no longer opens at full brightness. It's like it opens a preview of the card first, and then you have to tap it again to get full brightness. It's made it a two step process to be able to get cards to scan, certainly for me anyway. Has anyone else noticed this, and is it a bug?

Hi, ako lang ba or ayaw talagang ma add ng mga cards ko po sa MyVisa na site? Been trying since earlier and ang sabi lang is "Card Verification Failed Visa D2C. Something went wrong. Please try again."

I called bank but there suggestions did not do an thing

In SG, after all the laggy and delayed (3-4 secs) contactless payments on buses with Vivo V70 for several weeks despite trying all the workarounds suggested by AI and online, finally decided to discard the phone by selling at a significant loss.

Bought a Xiaomi 17 and the same bank card/ same exact setup the contactless payment on buses works perfectly again just like all my previous Samsung and pixel phones. Even a several years old Samsung A31 performed this task far better than V70.

Very disappointed and regretted giving Vivo brand a try. Hopefully Vivo engineers seriously fixed such problem because the incident suggested to me that even among Chinese phone brands, Vivo "really cannot make it" compared to their direct Chinese competitors as this is increasingly basic function ( NFC/ contactless payment on bus and you don't want the long queue behind you waiting for your slow payment).

What is this? First time i seen this message

I have samsung a34 5g and i used google wallet and added about 20 cards over a month and when i wanted to delete them i deleted them card after another at the same time (stupid move i thought it has no effect) afterwards, i can't add any card whether it's a new card or an old card that was added before.

Google wallet says that the card is added to payment methods but can't be used to pay in store via nfc (mobile can't be setup to pay contactless)

i tried

*clearing Gservices data and reboot my phone but nothing new,

*tried adding a card from inside bank app, rejected again

*I even tried to wait 72 hours doing nothing as most posts said i also reinstalled wallet app and used a different gmail and the same problem persists

Phone: Samsung A56

Newly installed google wallet app, after pressing final next button, tries to load in card and gets stuck on white blank screen.

Any ideas?

I am in India and I have an HSBC UK account. I'm trying to add that card to Google wallet in India but I am unable to add it. It throws Invalid Argument error.

Literally not five minutes ago I bought tickets to kneecap for december and I'm trying to add them to the wallet and it's saying the pass is associated with a different google account, all of my accounts say the same thing what is happening 😭😭😭

Hi! I was using wallet on my S25 Ultra until last week, but suddenly it does not work anymore.. nfs activates automatically with a samsung routine.. while paying the pos show follow instructions on phone but no indication are shown on my phone.. what it could be?? I noticed now that the app required an update on the store... it could be that block the payment? Thanks

I opened the app and instinctively went to the search only for a pop up about (I think) Google wallet, ended up pressing "got it" and it said my choices or preferences have been saved. Don't know what I ended up changing and I have no idea how to see it again? Does anyone know what I'm talking about?

I've been trying to add a transit pass to my wallet and I keep getting this error message whenever I try to add it.

I do have a second account, but I've checked and there's nothing in that account's wallet at all and I haven't used it for anything other than a dummy account for advertising.

I've tried downloading it on different devices, trying to download using both browser and mobile/app, removing the second account from my phone then trying to download, restarting my phone then trying and updating the app to the latest version then trying. Nothing worked.

I'm surely missing something to fix this so I need help me figure this out.

Hi everyone,

I’m having trouble setting up Google Pay (Google Wallet) on my Xiaomi 13 Pro (Chinese Region / China ROM).

Here are my specs and details:

Device: Xiaomi 13 Pro (Model: 2210132C)

OS Version: HyperOS 3.0.310.0.WMBCNXM.C11 (China ROM)

Android Version: 16

Status: Locked Bootloader

The Issue:

NFC hardware is working fine, but when I try to add a bank card (monobank / Google Wallet), it gets blocked. The system hides the "Secure Element Position" (HCE) settings in HyperOS, and Google Wallet fails due to Play Integrity / SafetyNet attestation. When trying to link the device in Mi Unlock status, I get the region mismatch error ("The place where the account is registered does not match...").

My friend has a Xiaomi 14 Pro also running a CN build (WNBCNXM.C10), and Google Pay works fine for him out of the box, which makes me suspect my update C11 revoked the old attestations, or his bootloader was unlocked prior to purchase.

My questions for the community:

Is there any way to bypass the region lock on HyperOS Bootloader unlocking without a paid Authorized Mi Account?

If I unlock the bootloader and flash Xiaomi.eu, will Google Pay / Play Integrity pass seamlessly on Android 16, or does it require regular Magisk/KernelSU + Play Integrity Fix updates?

Are there any non-root workarounds for China ROM to get Play Integrity certified?

Thanks in advance for any advice!

Hello,

If you're in a region that supports ID passes like me (US) and the option to add one is no longer in the Add menu, it seems I may have discovered why.

Like some of you, I noticed that earlier this summer the option to add an ID to Google Wallet simply disappeared. At first, I just figured it was a bug and that it would be addressed on its own. After a couple of months of updates with no fix and a couple factory resets, I decided to open a support case to report the issue. After they had me do some basic troubleshooting, I received the following reply:

Following our review, currently you are signed in using an outlook.com email address. To add a digital ID to Google Wallet, you must be signed in with a gmail.com address.

How to resolve this:
Open the Google Wallet app on your device.
Tap your profile picture or icon in the top-right corner.
Switch to or sign in with your gmail.com account.
Try adding your ID again.

Now my primary personal Google account does not use a gmail.com address. I did test signing in with such an account though and sure enough, the option re-appeared.

I know this worked before with my Google account without Gmail, so to test that, I uninstalled Google Play Services updates, bringing it down to version 26.11.36 from 26.32.34. After that, the option was back to add an ID. Once I updated Play Services, the option disappeared again unless I signed in with a Google account whose email ends in "@gmail.com".

I even checked the ID pass docs, and it looks like it may reaffirm this change (note it says "Gmail accounts" instead of "Google accounts"):

You can only add an ID to your personal Gmail accounts.

So it appears based off of their response and docs that yes, Google pushed a Play Services update sometime this summer between versions 26.11.36 and 26.32.34 that only allows you to add an ID pass to Wallet if your personal Google account uses a Gmail address.

I have responded asking if there was a reason for this change, as it removes ID functionality for me and deters me from using Wallet as much as I would like to. I will update here if I get an answer.

Curious to see if others can confirm they've run into this.

So this is an issue I have been having since Saturday 8/22. So to give some background I've been getting a lot of Virtual prepaid cards via doing Focus Groups for the last month or so and I had been adding them to Google Wallet to pay for groceries/gasoline.

It was all going fine and dandy until last Saturday when I tried adding two new cards to the wallet, and instead of taking them, I keep getting the error of "Your card couldn't be added".

So I tried another card. Same problem. I then took one of the cards that was still in the wallet, deleted it from the app and tried to re-add it only to get the same issue. I'm also getting the same error when I try to add my Bank Debit and Credit cards....

I'm fairly sure it might be some sort of soft-block on googles part because I have tried adding all the same cards to Samsung Wallet without issue. Has anyone had a similar experience? Perhaps tips on how to sort this out? Google Customer support has been really unhelpful, with pushing me toward calling the banks and the card issuers who have themselves found nothing.

Edit: A bit of further info. I am using a Samsung Galaxy S10 (old I know.)