09-27-2022
08:47
- last edited on
10-09-2022
18:14
by
LizzyFitbit
09-27-2022
08:47
- last edited on
10-09-2022
18:14
by
LizzyFitbit
So I just got the Versa 4 today, but it's impossible for me to get Fitbit Pay working. After I fill in the cardnumber and name, press Next it says: 500 internal server error. I already mentioned it to the customer service, and they are trying to find a solution, but maybe someone else here knows how to fix this?
I already re-installed the app, removed my device, tried wifi and mobile network, turn off/on bluetooth....no luck.
At the moment I am really considering to return the Versa 4, because I miss a lot of features (Google Assistant, Spotify, 3rd party apps, Google Maps, etc). Unfortunately my Versa 2 battery is dying (i need to charge every 2 to 3 days), so I really need a new one.
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
10-09-2022
18:19
- last edited on
05-08-2024
06:31
by
MarreFitbit
10-09-2022
18:19
- last edited on
05-08-2024
06:31
by
MarreFitbit
Hi everyone, and welcome to our new members.
Thanks for the detailed information, as well as your efforts while working on this matter. Let me share this issue affecting the Versa 4 and Sense 2 has been escalated to our team and they're working to identify a solution. I apologize for the inconvenience this has caused and we'll update this thread as soon as we receive more details from them.
In the meantime, please keep syncing your watches and make sure the Fitbit app is updated.
09-27-2022 13:39 - edited 09-27-2022 13:39
09-27-2022 13:39 - edited 09-27-2022 13:39
I have the same issue with Fitbit Pay (500 server error) and am also very disappointed that we can not (yet?) install apps on the Versa 4. I did not own one of the previous Versa's, but I expected that the 4 would at least have the same features.
09-29-2022 23:14
09-29-2022 23:14
Just keep trying. Their servers are likely having stability issues. I thought Google will have more cloud resources but not.
09-30-2022 00:05
09-30-2022 00:05
I tried a lot, it's just not working. When I switched back to my resetted Versa 2 it worked immediately. So this is not a server problem, but a watch problem.
But don't bother, cause I returned my Versa 4 yesterday. It was so disappointing.
09-30-2022 00:09
09-30-2022 00:09
I managed to get ABNAMRO Creditcard working, but not ABNAMRO Maestro Debitcard. So it looks like a serverproblem at ABNAMRO, not a watch problem (?).
However, still very disappointed with the Versa 4 in general (no 3th party apps).
10-01-2022 01:00
10-01-2022 01:00
Seems it is a Maestro problem for these specific new watches then....
10-02-2022 00:18 - edited 10-02-2022 02:01
10-02-2022 00:18 - edited 10-02-2022 02:01
Customer services (Fitbit) told me to wait for an upcoming update this week
10-02-2022 00:19
10-02-2022 00:19
Cust service from the Bank of from Fitbit?
10-02-2022 02:04 - edited 10-02-2022 02:06
10-02-2022 02:04 - edited 10-02-2022 02:06
Edited my previous message;
I spoke with customer support Fitbit (2days ago), they are aware and are working on an update somewhere this week/ week and a half I was told. After the update we should be able to add bankcard and complete te proces to start using Fitbitpay. So its not a bankproblem, but Fitbit issue.
10-04-2022 09:02
10-04-2022 09:02
This morning there was an update, unfortunatly it still doesn't work for me.
10-04-2022
09:04
- last edited on
10-22-2022
12:38
by
DavideFitbit
10-04-2022
09:04
- last edited on
10-22-2022
12:38
by
DavideFitbit
It gives "500 Internal server error" when I try to add my ABN AMRO Maestro card to the Fitbit Pay in my Versa 4. I called the bank and they said that when I try to add the card in Fitbit app, they don't even see any incoming request to their end and therefore the problem should be within the Fitbit.
Is anyone facing the same issue ?
+ I followed the same steps and added my Visa card without any issue. But I really expect a fix for above issue.
10-04-2022
13:03
- last edited on
10-22-2022
12:39
by
DavideFitbit
10-04-2022
13:03
- last edited on
10-22-2022
12:39
by
DavideFitbit
The Fitbit update didnt do much for me either, hoping they ment te versa update. Giving it a change till end of the week before I call back.
There is another post about this topic; Fitbit said there will be an update soon. They are aware
10-09-2022
18:19
- last edited on
05-08-2024
06:31
by
MarreFitbit
10-09-2022
18:19
- last edited on
05-08-2024
06:31
by
MarreFitbit
Hi everyone, and welcome to our new members.
Thanks for the detailed information, as well as your efforts while working on this matter. Let me share this issue affecting the Versa 4 and Sense 2 has been escalated to our team and they're working to identify a solution. I apologize for the inconvenience this has caused and we'll update this thread as soon as we receive more details from them.
In the meantime, please keep syncing your watches and make sure the Fitbit app is updated.
10-10-2022 12:41
10-10-2022 12:41
Hope there is an update soon, very soon for this 500 internal server probllem. Otherwise i realy have to bring the versa 4 back to the store asap. This is a big bug.
10-12-2022 13:34
10-12-2022 13:34
How long did it take you to get your refund once you returned your new watch?
10-17-2022 01:08 - edited 10-17-2022 01:10
10-17-2022 01:08 - edited 10-17-2022 01:10
Still no updates for versa4.
Just checked on my charge3 and installing fitbitpay on there is still a 1 minute succesfull proces, so I am still very confident we need an update for Versa4. Also because more options still dont work.
Meanwhile counting down the 45 days for a possible return if not fixed in time.
10-17-2022 01:21
10-17-2022 01:21
I returned my watch because of this bug, if it's a bug. Maybe it can be solved with a firmware update.
But I decided to return the watch and that was no problem and I bought the versa 3.
This watch works perfectly to install Fitbit Pay. So I don't regret my decision and this watch meets all my expectations.
10-20-2022 02:39
10-20-2022 02:39
Me too, I'm having the same problem.
Very disappointed about this
10-20-2022 02:58 - edited 10-20-2022 02:58
10-20-2022 02:58 - edited 10-20-2022 02:58
Its messed up this post got a “best answered” status while nothing is solved. The changes are good to none no one of significance will read this anyway. My suggestion is to report it and keep reporting it directly to customer support to keep spreading awareness!
10-20-2022 03:10
10-20-2022 03:10
yep, already done.