help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Google Wallet not working on my Pixel 6 after adding a card to Fitbit Pay wallet (Charge 5)

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎07-21-2023 00:51

‎07-21-2023 00:51

I had a weird experience with Fitbit Pay. Got a new Charge 5 and added my default card to the Fitbit Pay app, thinking I'll tap with that some day. A little while later I tried to use my phone to pay for something and it didn't register at all. Everything looked the same on my phone, NFC was on, Google Wallet showed the same default card etc. The vendor screen just wasn't registering the tap by my phone at all. 

I first thought that my NFC chip might be broken but I've since tested it with some NFC cards, it's reading them perfectly fine. This is definitely something weird related to the Fitbit setup. Any advice? I tap to pay for everything so getting this fixed quickly would be great!

I've tried deleting the card from Fitbit Wallet and deleting/readding it to my Google Wallet. Time will tell if this helps.

Best Answer
0 Votes
5 REPLIES 5

‎07-21-2023 01:15

‎07-21-2023 01:15

It is something with Google Pay services.
Not realted with Fitbit Pay - they are tootaly different services, for every new card digitalization on *Pay - bank's card issuer gives new "digiral card PAN and validity".

Check with some SafetyNet app if "CST profile match" - pass.
(eg. https://play.google.com/store/apps/details?id=rikka.safetynetchecker )

Also check default NFC payment app is phone's settings.

Best Answer
0 Votes

‎07-21-2023 01:22

In response to ChoSmile

‎07-21-2023 01:22

Thanks for your reply. I got a pass for both basic integrity and CTS profile with the safetynet app.

Pretty weird coincidence if it's not related, I used Google Pay three times yesterday, added a card to Fitbit Pay, and Google Pay didn't work afterward. Although thinking it through, I might also have installed an android update in the same period which could be the culprit. I'll hunt down the culprit eventually!

Best Answer
0 Votes

‎07-21-2023 01:23

In response to liquefry

‎07-21-2023 01:23

oh and Google Pay is still the default contactless payment app.

Best Answer
0 Votes

‎07-21-2023 01:26

In response to liquefry

‎07-21-2023 01:26

can't work out how to edit so have to reply to my own post. Checking the default payment app I noticed an option to "use default payment app" which was set to "except when another payment app is open". Could the phone have thought that the Fitbit Pay app was "open" even if I wasn't using it?

I've temporarily changed this option to "always".

Best Answer
0 Votes

‎07-21-2023 05:36

In response to liquefry

‎07-21-2023 05:36

Fitbit app is not a "payment" app and do not use NFC of the phone.

The "payment" apps are listed on same screen above option "use default payment app" / "except when another payment app is open".

And if phone is UNLOCKED and SCREEN is on - it use default app.

On some phones (for Samsung sure, for Google Pixel not sure) is possible just to WAKE-UP the SCREEN (by tap or by side button) without unlocking it and to pay by default app.

Best Answer
0 Votes