The strange thing about leaving a phone behind is how often one small code brings it back into the picture.
A Garmin watch can record a workout, navigate a route, play music, and pay at a checkout. Then the gym entrance asks for a membership barcode that still lives inside a phone app. The same problem appears at stores, clubs, and events: the useful part of the card is only a few black lines or a square code, yet it remains tied to the device people were trying not to carry.
Garmin users regularly look for a way to move gym passes, loyalty cards, and membership barcodes to the watch. The reason is usually simple: they want to train, run, or shop without carrying a phone and without opening messages and notifications just to show a code.
The good news is that many of these cards can work on a Garmin watch. The important part is understanding which ones.
Why Garmin Pay is not the answer
Garmin Pay and a loyalty-card wallet solve different problems.
Garmin Pay is designed for supported payment cards and NFC transactions. A typical gym or loyalty card does not make a payment. It shows an identifier to a scanner. Connect IQ apps do not have general access to the watch’s NFC hardware, so an ordinary watch app cannot clone an RFID door card or turn itself into another contactless payment wallet.
That limitation does not matter when the original card already uses a visible QR code or barcode. In that case, the watch only needs to reproduce the correct code clearly and reliably.
The distinction prevents the most common wrong turn: trying to add a gym pass to Garmin Pay when the real solution is a code wallet.
First check whether the code stays the same
Before moving any card to a watch, one question matters more than the brand of the gym, store, or club: does the encoded value remain unchanged?
Many physical loyalty cards and printed membership passes contain a static identifier. The same value appears every time the card is scanned. These are good candidates for a watch wallet.
Some phone apps work differently. They rotate the code, attach an expiry time, or generate a signed token to prevent sharing. A screenshot of such a code may look perfect and still stop working minutes later. If the decoded value changes when the official app opens again, the official app remains the correct tool.
The screenshot is not the card
Even with a static card, copying the picture is not always enough.
The visible image represents hidden data. A scanner cares about the exact value and the format used to encode it. A missing leading zero can identify a different account. A wrong check digit can make a retail number invalid. The same digits drawn as QR, EAN-13, or Code 128 may all look convincing while only one matches the system at the counter.
This explains a common frustration: a phone can read the image, but the shop or gate still rejects it. A modern phone camera tries several formats and compensates for angle, focus, and exposure. A fixed retail reader may accept only the format selected by the organisation.
The reliable approach is to preserve the complete decoded value and its original format. Rebuilding every card as a generic QR code may produce a valid QR image, but not necessarily the card the reader expects.
Screen size and scanning
Garmin watches vary more than they first appear. Some use bright AMOLED panels; others use reflective MIP displays. Instinct models have compact shapes, while older watches operate with tighter memory limits.
Good rendering matters because machine-readable codes are not ordinary pictures. QR modules need to remain square and undistorted. Linear bars need enough width to stay distinct. The blank field around the code must remain clean. Making a symbol fit on the screen is not the same as making it useful to a scanner.
No watch app can guarantee acceptance by every reader. The realistic goal is narrower: preserve the original data, render it cleanly for the actual Garmin display, and fail clearly when a value cannot be represented safely.
What a practical solution looks like
For a compatible static card, the useful workflow is deliberately ordinary. Add the card through Garmin Connect IQ settings or the watch’s own card editor, synchronise once, and open it from the wrist when needed. The saved value remains available without a phone connection or internet access.
WalletPro generates supported QR and barcode cards on the Garmin device. It does not send card values to a developer-operated server and does not use web requests.
The boundaries are equally important. WalletPro is not Garmin Pay, an NFC access wallet, or a place for bank cards. It cannot clone RFID credentials, refresh a rotating retailer token, or make an unsupported scanner accept a different format. Dynamic passes should stay in the issuer’s app.
For static gym, store, club, parkrun, and membership codes, the result is much simpler: the identifier that normally requires a phone unlock is already on the wrist.
The first real scan is the final test
Keep the physical card or official app available for the first attempt, open the saved code on the watch, and try it at the actual reader. If it works, the fallback can stay at home next time. If it does not, the failure usually points to a dynamic value, the wrong format, or a scanner that cannot read that watch display reliably.
This is a small problem, but it appears at exactly the wrong moment: at the gym door, club desk, or checkout, when opening a phone feels unnecessary.
WalletPro is available free in the Garmin Connect IQ Store.
The goal is not to turn a Garmin watch into another phone. It is to remove one more reason to reach for the phone at all.