Fitbit Pay FAQ

Recent Updates

October 8, 2024

  • Google Wallet on Fitbit available in Taiwan and Japan.
  • Any legacy Fitbit Pay tokens with issuers in Japan, Saudi Arabia, or Taiwan will be deleted on January 13, 2025.

Overview

Fitbit is updating our contactless payments feature from Fitbit Pay to Google Wallet. Fitbit Pay will no longer be available starting on July 29, 2024. Starting March 26, 2024, Google Wallet will now be available on Charge series, Sense series, and Versa series devices that support contactless payments. These updates apply to all markets except Saudi Arabia, Japan, and Taiwan. These updates are applicable to Japan and Taiwan after October 8, 2024.

Google Wallet on Fitbit is already the default payments solution for new devices launched after November 2022 (Versa 4, Sense 2, Charge 6) outside of Japan and Taiwan.

  • Google Wallet on Fitbit is already the default payments solution for new devices launched after November 2022 (Versa 4, Sense 2, Charge 6) outside of Japan and Taiwan.
  • This change will impact all cards and cardholders supported. Fitbit Pay supports Visa and Mastercard globally and Amex in the US.
  • Issuers are advised to update or remove references to Fitbit Pay on customer facing marketing assets (websites, mobile app, emails etc.) and customer service channels starting after April 02nd but no later than July 29th.

Background

As part of Google's acquisition of Fitbit in 2019, Google has been working to migrate Legacy Fitbit Pay into the Google Pay ecosystem.

In addition to Host Card Emulation (HCE), Google has launched support for Secure Element (SE) tokenization to support Fitbit and other wearable devices.

Issuers should note that Secure Element tokenizations will have a different Token Requestor ID (TRID) than Host Card Emulation. Mastercard has created a new TRID for SE tokenizations, where Visa will reuse the previous Fitbit TRID for SE tokenizations. Refer to the Network Bulletins sent by each Network and reach out to them for any questions.

  • Visa Article ID: AI12091 sent June 2nd, 2022
  • Mastercard Article ID: AN 5976 sent June 1st, 2022

Lastly, in support of the legacy migration transition, all issuers globally are required to support all available TRIDs as of the update to Google Pay Standard Issuer Agreement terms released in May 2023. If there are additional questions regarding the migration, review the FAQ below.

FAQ

Transition from Fitbit Pay to Google Wallet

Which Fitbit devices now support Google Wallet?

  • Sense 2, Versa 4, Charge 6
  • Sense 1, Sense 2, Versa (Special Edition), Versa 2, Versa 3, Versa 4, Charge 3 (Special Edition), Charge 4 and Charge 5.

What is the plan for terminating the existing Fitbit Pay contracts?

As we're discontinuing Fitbit Pay entirely, all current Fitbit Pay Agreements will be terminated. Google Wallet on Fitbit, which replaces Fitbit Pay, will fall under our existing GPay Issuer Agreement.

Does this change impact existing Google Pay contracts in any way?

We're only terminating existing Fitbit Pay agreements. Google Pay Issuer Agreements will oversee Google Wallet on Fitbit, and no changes are necessary in them.

What if you don't have a Google Pay contract in place? What's the right process to follow?

Initiate the process mentioned on the Get Started page.

In the UX, will users be directed to Google or the Issuer for any customer support related questions?

In the UX, the user is not directed to Google or issuer for customer support. Google will be providing customer support using our Help Center article.

What will happen to users of legacy Fitbit devices that did not migrate to Wallet before the deprecation date?

Google Wallet will request for these users' tokens to be removed from their Fitbit Pay wallet. These users will no longer be able to access their cards on their mobile or Fitbit device. Users will be able to still update to Google Wallet after the deprecation date and add their cards.

Why do all marketing assets need to be updated by July 29th and what happens if you can't meet that deadline?

Google strongly encourages issuers to scrub Fitbit Pay branding from their surfaces and marketing assets by July 29 at the latest to avoid potential risk of false advertising to users.

General

Why should an issuer integrate with Google Pay SE (Google Wallet on Fitbit)?

  • As of November 2022, all new Fitbit devices that support NFC payments are using Google Pay on Fitbit instead of Fitbit Pay.
  • Cardholders have a better experience when there is consistent issuer parity across devices regardless of form factor. It is a confusing experience if a user can add a card to their mobile Wallet, but not to their Fitbit Wallet.

What is the difference between Legacy Fitbit Pay and Google Pay on Fitbit?

  • Fitbit Pay is the legacy Fitbit wallet. Google will switch fully to Google Pay on Fitbit but Legacy Fitbit Pay is still available on previous Fitbit devices until July 29, 2024. After July 29, all legacy Fitbit Pay tokens will be removed with the exception of tokens from issuers in Saudi Arabia, Japan, and Taiwan. Tokens in these markets will be removed after January 13, 2025.

  • Google Pay on Fitbit is the extension of Google Pay wallet to Secure Element technology, under Google Pay Wallet ID and a different Token Requestor ID (TRID) for Google Pay SE versus Google Pay HCE.

What are the TRIDs for Legacy Fitbit Pay vs Google Pay SE?

  • Visa (Legacy Fitbit Pay and Google Pay SE): 40010077056
  • Mastercard (Legacy Fitbit Pay): 50174158869
  • Mastercard (Google Pay SE): 50101881415

Integration and Testing

How does an issuer integrate with Legacy Fitbit Pay?

  • All integration projects are managed by TSPs Visa and Mastercard.
  • Google is not actively onboarding new issuers onto Legacy Fitbit Pay.

How does an issuer integrate with Google Pay on Fitbit?

  • Issuers who support Google Pay have been auto enabled for support with Google Pay on Fitbit.
  • Contact your network if you have any questions around supporting Google Pay on Fitbit.

How does tokenization work for Legacy Fitbit Pay and Google Pay on Fitbit?

  • Fitbit devices use Secure Element tokenization technology.
  • Secure Element is an embedded hardware chip which provides cryptographically secure storage and computing environment on a mobile or a wearable device. It can be used to enable various Wallet use cases, like tap-and-pay, transit, access badges, car keys, ID verification, and others.
  • All Fitbit NFC devices are embedded with Secure Element chips.
  • For more information contact your TSP.

Which ID&V methods do Legacy Fitbit Pay and Google Pay on Fitbit support?

  • Legacy Fitbit Pay: SMS, email, Call Center
  • Google Pay: SMS, email, Call Center, In-app verification

Is Push provisioning available with Legacy Fitbit Pay or Google Pay on Fitbit?

  • Push provisioning is not supported for Fitbit devices at this time. Google is working on supporting this feature for Google Pay on Fitbit in 2024

What if an issuer wants to test Legacy Fitbit Pay within a test environment?

  • Google is not actively onboarding issuers onto Legacy Fitbit Pay. For any sandbox testing on new Google Pay on Fitbit, see the next FAQ.

What if an issuer wants to test Google Pay on Fitbit within a test environment?

  • Issuers will need their own Fitbit devices, Google does not provide test devices.

  • Use the adb command to toggle sandbox mode for Google Wallet on Fitbit on Android:

    To turn sandbox mode on, add an empty file and reboot the device.

    adb shell touch /sdcard/Download/android_pay_env_override_sandbox
adb reboot

    To switch back to production mode, delete the file and reboot the device.

    adb shell rm /sdcard/Download/android_pay_env_override_sandbox
adb reboot

Check if your device is in sandbox or production mode.

To see if your Android device is in sandbox or production mode, you can go to Android Settings > Google > Settings for Google apps > Google Wallet or Android Settings > Google > Account Services > Google Wallet.

  1. Open the top left Menu button and select Settings.
  2. Go to the bottom of Settings page.
  3. If you see a message that says "Your environment is SANDBOX because of a file override," the device is configured for the sandbox environment. Otherwise, the device is configured for the production environment.

User Experience and Branding Guidelines

What is the user experience difference between Legacy Fitbit Pay and Google Pay on Fitbit?

  • Both provisioning processes start from the Fitbit app.
    • For Legacy Fitbit Pay the full provisioning process is done in the Fitbit app.
    • For Google Pay on Fitbit, provisioning starts from the Fitbit app, requires login with a Google Account and finishes in a Google Wallet workflow.
  • Payment experience is the same using tap & pay feature with the Fitbit devices
  • Transactions history can be viewed in the Fitbit app in both cases.

I just added a card onto Google Wallet on Fitbit, why do I see emails/texts mentioning Fitbit Pay?

  • For Visa, Legacy Fitbit Pay and Google Pay on Fitbit are using the same TRID. Since some issuer emails and texts could use wallet names based on the TRID, it is possible that Legacy Fitbit Pay TRID is used for Google Pay on Fitbit end user communications.

How should I manage end user comms with Visa Legacy Fitbit Pay TRID which is the same as Google Pay SE TRID?

  • Reference Fitbit Pay™ or Google Pay™ where applicable. (Example: Cardholder set up confirmation emails/notifications)
  • We also suggest issuers should be neutral in end user comms (Example: Thanks for adding your IssuerXX card to your Fitbit Device. You're now able to make contactless payments with IssuerXX using your Fitbit).

What are Fitbit's branding guidelines?

Support

Who can I contact if I have a technical question or have a bug to report for Legacy Fitbit Pay or Google Pay on Fitbit?

What are Fitbit Pay T&Cs?

What are end user info pages on contactless payments of Fitbit?