Garmin Pay - Known retailers

Former Member
Former Member
Has anyone see a list of retailers known to accept Garmin Pay?

I just upgraded to a 5x+ from a 5x and one of the features I was most excited about was Garmin Pay. During a run I stopped into a 7-11 (where I have used NFC payments in the past on my phone) and was surprised that the terminal reported “App not supported”

I remember seeing Starbucks in some marketing material, so I tested it and it worked great. Has the community created a list of known working payment terminals/retailers?

Failed:
1. Local 7-11
2. Home Depot

Worked:
1. Starbucks
  • Former Member
    0 Former Member over 6 years ago
    Ok so the good news.. I found another place in Southern California that Garmin Pay works at. Newer Arco Gas stations, the payment terminal seems to accept anything, Samsung Pay, Chase Wallet, Android Pay, etc... Added to the spreadsheet.

    https://docs.google.com/spreadsheets/d/1ebZ7nCCK97vRckJA4vuinzA2kSjObWnkDgMgBRIi2Gc/edit#gid=0

    The bad news, my watch on the current beta v4.61 rebooted as soon as I completed the transaction. Admittedly I was asking a lot out of it

    Scenario:
    1. Completed a run activity, with Music from watch to Bose headphones. Saved activity
    2. Still playing music on new Music app, unlocked wallet and paid for transaction
    3. Watch rebooted right away.
  • Quick question all - is the watch supposed to reboot every time you use Garmin Pay because mine does?
  • Darn, must be the new beta firmware 4.61 then... seems to be corroborated by Meccanica88’s experience too
  • Darn, must be the new beta firmware 4.61 then...


    For those folks on the 4.61 beta, this isn’t happening for everyone. Please do follow the instructions on the beta thread post to email your experiences to the team (they will read, but won’t respond unless they need more info). You may also wish to copy across any files that are in your Primary/Garmin/Debug folder; every time there is a crash, the watch should generate a err_log.txt file and possibly a ram.txt file in that folder (with a file date+time stamp corresponding to the crash/reboot). The beta team may find those files useful if you can provide them with your email description of how the crash happens.
  • Former Member
    0 Former Member over 6 years ago
    For those folks on the 4.61 beta, this isn’t happening for everyone. Please do follow the instructions on the beta thread post to email your experiences to the team (they will read, but won’t respond unless they need more info). You may also wish to copy across any files that are in your Primary/Garmin/Debug folder; every time there is a crash, the watch should generate a err_log.txt file and possibly a ram.txt file in that folder (with a file date+time stamp corresponding to the crash/reboot). The beta team may find those files useful if you can provide them with your email description of how the crash happens.


    Done. ram.txt is too large to email even compressed, also since it has to do with payments, I don't really feel comfortable with a ram dump being sent anyway. Who knows how Garmin has stored payment data to ram. I did send over steps to replicate and the err_log.txt
  • ....I don't really feel comfortable with a ram dump being sent anyway....


    Absolutey right; it’s your personal data and if you’re not happy sharing it with Garmin then you don’t have to. They are at least an accountable corporate company though (so subject to respective national data protection laws) and arguably the payment data is already in their Garmin Pay system anyway.
  • Former Member
    0 Former Member over 6 years ago
    Absolutey right; it’s your personal data and if you’re not happy sharing it with Garmin then you don’t have to. They are at least an accountable corporate company though (so subject to respective national data protection laws) and arguably the payment data is already in their Garmin Pay system anyway.


    I work with developers everyday (Software release manager for a very large healthcare dev shop), my hope is that the lower environment and test tiers do not have production data or access to prod data. But you are right, Garmin is a small dev shop and the dev team very well may have access to Garmin Pay data (but probably not)
  • Former Member
    0 Former Member over 6 years ago
    You are comparing countries the size of Texas to the whole United States. With a country this size, change in a system takes many, many years! Let alone different states within the country. I have a hard enough time finding Apple Pay compatible terminals. This will not happen any time soon. Too costly.


    Size of a country has nothing todo with it. Contactless payments is across Europe. I think its more down to the back end systems that may need to be changed. The terminals cost very little to roll out to retailers.

    However I am not an expert in this area, I am just very surprised.
  • Former Member
    0 Former Member over 6 years ago
    You are comparing countries the size of Texas to the whole United States. With a country this size, change in a system takes many, many years! Let alone different states within the country. I have a hard enough time finding Apple Pay compatible terminals. This will not happen any time soon. Too costly.


    Size of a country has nothing todo with it. Contactless payments is across Europe. I think its more down to the back end systems that may need to be changed. The terminals cost very little to roll out to retailers.

    However I am not an expert in this area, I am just very surprised.


    Totally agree with John... except that in parts of the US we are even further behind. I think our more forward states Like California, New York, Colorado, even parts of Nevada would be at least on the curve and not behind it. Some good news, I tried it at two more locations here in SoCal over the weekend (Even though Garmin Pay crashes, on the current beta when it exits) and it worked at both locations.

    https://docs.google.com/spreadsheets/d/1ebZ7nCCK97vRckJA4vuinzA2kSjObWnkDgMgBRIi2Gc/edit#gid=0 <-- Updated