This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin Pay cannot "provision" card, no Garmin support

I moved from an Android phone to an iPhone. Garmin Pay was successfully set up and working on my Venu with the Android phone. Once connection to the iPhone, the card was no longer in the wallet. So I tried to add it. That resulted in "Error Card Provisioning (Authorization) Failed". Every time. I removed the card from the Android phone, uninstalled the app on both phones and rebooted them and hard-reset the Venu, which of course meant finding and reconfiguring activities, watch faces, etc. No luck.

And I called my bank several times. The Garmin system isn't even trying to authorize a token. The bank isn't rejecting it; it just isn't getting a request.

I submitted a Garmin request a week ago for help on this; the auto-responder said 3 business days. Yeah, no. No response. And the situation is still the same.

This is the same card that worked before.

Any ideas what to try?

0 seilogramp over 4 years ago

Sounds like you're going to need Garmin Support on this The auto response from Garmin is 3-5 business days. It certainly shouldn't take over a week. I suggest calling or using the chat option offered from the support site.

0 Garmin-Kevin over 4 years ago

Hello 9407504. I see that you were able to speak with a Product Support agent on the phone today. Will you please update this thread with what they suggested and your results once you try their suggestion?

0 9407504 over 4 years ago

I did get in touch with them. It wasn't terribly helpful, but I'm still working with Garmin and with the bank.

0 9407504 over 4 years ago in reply to Garmin-Kevin

No, no dice. No idea if it's on the bank or Garmin's side. I did have the card cancelled and got a new card, same problem.

0 Garmin-Kevin over 4 years ago in reply to 9407504

Looks like the agent who assisted you noted that you would be calling back if the troubleshooting proved unsuccessful. I'd give them a call back, as they may want to start a case for your issue.