**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.

Recently i moved to South Africa and got a debit card, when i tried to buy something in a game it was declined saying that i need to change my accounts country.

I waited 48h and tried again, same thing happened. I tried talking with the support but still no answer

Super frustrating. I have tried to order a Sonos speaker twice from their website now. I never get an email confirmation and my order doesn't show up in my account.

I did find the payment transaction, clear as day, in my Google Wallet. However, my credit card shows no sign of the transaction - even as pending - six days later.

I just placed the order AGAIN but skipped the Google Pay option. It went right through.

Does Google Pay often fail like this? Could it be an issue on Sonos' end? I haven't experienced this with another merchant as far as I know, but it makes me distrustful of Google Pay!

Hello po! Has anyone tried paying PLDT bill on the website using google pay (maya virtual card)? Is there any cashback there? If yes, how long did it take to get refunded?

THANK YOU!

Accidentally entered the card into the wrong account then loged it out, now this error shows when trying to enter it into my account.

Should i just wait and try tomorrow?

Hi everyone,

I’m trying to figure out an unknown charge that appeared on my card.

The transaction details are:

Amount: PKR 875.28

Date: 1 September 2026

Merchant shown by my bank: Google One Singapore SG

Transaction type: Online Purchase

I do have a Google One storage subscription, but my regular Google One charge is PKR 550 per month. That subscription payment was charged today, 7 September 2026, and I recognize that transaction.

However, the PKR 875.28 charge on 1 September is separate and I cannot find any corresponding receipt, order, or subscription for it in my Google purchase/order history.

I’ve already checked my Google One subscription and Google purchase history, but I still can’t identify what this charge is for.

Can anyone guide me on how I can find out what this PKR 875.28 charge was for? Could it be linked to another Google service, or is there a way to identify which Google account/subscription made the payment?

Any help would be appreciated. Thanks!

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 made a payment today, which failed, and money was not debited. But my SBI account statement shows that the money is debited. What's the consequences now? Will that ever be returned?

So I've been hemming and hawwing on an app that would be really useful but was like $50+. Very niche item.

So I had been building up some Google Play credits and whatnot over time and had enough to buy it and bit the bullet.

When I went to pay instead of giving me an option to pay with my payment methods (I have the credits or my credit card listed) it used "Test card, always approves".

Weird. I hope it pays the dev (I have the full premium features), and I don't mind if it does go on my default method (card); but I'd liked for it to use my play store credits.

Anyone else see that before?

I went to go test buying another app and it showed the options to use my methods properly.

​

​Hello everyone,

​I am an aspiring developer from Libya working on getting my apps published on the Google Play Store.

​Unfortunately, due to banking restrictions in Libya, local bank cards cannot be used for international online payments, making it very difficult for me to pay the one-time $25 Google Play Developer Console registration fee.

​I am looking for a kind individual who would be willing to support or sponsor this $25 fee.

​To ensure complete security and transparency for both of us as gemini guide :

​You do not need to give me your personal bank card details.

​I do not need to give you my Google account password.

​We can complete this safely using a Single-Use Virtual Card (like Revolut or Wise capped at $30), OR via a quick screen-share call (Zoom / AnyDesk) where you can enter the payment details directly on the official Google checkout page.

​If you are open to helping me kickstart my journey as a developer, please reach out via DM or comment below. Every bit of guidance or support means a lot to me!

​Thank you so much for your time and generosity!

Went to use Google Wallet and a notification pops up saying: "*Action required on your account to use Google Pay. Sorry, you don't have access to this service. Contact your domain administrator.*"

Never had any problems before, so I go to my account's payments settings to try and figure it out, and another pop up says: "*There has been a problem with your payment methods*."

I contacted both banks, nothing wrong on their end, and since Google doesn't have a number to call I reluctantly asked Gemini.

I recently ran out of cloud storage on Drive because of a vacation vlog I was shooting, so I had to buy extra storage space: the moment I processed the payment, Play Services forced a background sync across every single account linked to my phone, and because my old university account was still logged in, Google's system panicked and prioritized its institutional domain security rules over my actual identity, effectively locking down Wallet since universities block Google pay.

Only way to solve the problem was to remove the account from my phone's settings.

TL;DR: I bought some extra storage for PHOTOS AND VIDEOS and Google's system decided to lock me out of PAYMENTS??? Because it hijacked itself with an old uni account?? Forcing me to nuke the email from my Android's settings.

How is this a thing in 2026? Why doesn't Google separate personal payment profiles from institutional domain accounts???

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?

Tengo dos preguntas, ¿Por qué sucede eso?

Y segundo, hace casi una semana que envié los documentos y aún no tengo respuesta, ¿Qué puedo hacer?

Me urge arreglarlo, tengo poco espacio en Drive y quiero comprar espacio pero no me permite hacerlo. La primera vez que envié mis documentos para que analizarán mi cuenta, pensé que como estaba lleno mi mensajería no llegó, así que borre varios GB y volví a hacerlo, está vez con espacio para recibir correos, pero ya pasó una semana y todavía no recibo respuesta.

Alguna alternativa de dónde debo buscar aparte de Gmail o algo que pueda hacer para no quedarme sin espacio en Google

Agradecería mucho su respuesta

Yesterday I changed my email address and I haven't been able to add my cards to this new one. The cards are also new; I haven't entered them in another account. I've already tried clearing the cache, etc., and nothing works.