Quick answer
Apple Wallet and Google Wallet loyalty cards are digital passes a customer can save in a supported wallet application. The pass can show membership or reward information and provide a way to identify the customer at checkout. The business still needs a system that records earning and redemption.
A wallet pass is not a payment card, and saving it does not automatically connect your cash register. Understanding those boundaries helps you choose the right workflow and explain the program accurately.
How does a customer add the card?
The business supplies a supported installation link or button, commonly reached from a QR code, website, or communication. The customer follows the save instructions and confirms the card in their wallet.
Apple's official pass guide describes opening the issuing communication, using Add to Apple Wallet, and following the onscreen instructions. Google's loyalty-card documentation describes issuing loyalty passes that users add to Google Wallet.
Do not label a form submission “installed” until you have checked the actual save step. Ask someone unfamiliar with the program to join while you observe. The point where they hesitate is useful evidence for improving your instructions.
Before adopting Boomerangme, test the card on the actual iPhone and Android devices your team will encounter. Start from the customer invitation, then return to the saved card at checkout; this is a better test than viewing an enrollment screenshot.
What happens at checkout?
The customer opens the card, staff identify it through the configured scanning or lookup process, and the loyalty system applies your earning rule. The reward balance can then reflect that action according to the implementation.
The checkout method depends on the provider and integration. A visible barcode does not mean a business has an NFC setup or that every contactless payment terminal can read the loyalty pass. A manual staff scan and a POS-connected transaction are different workflows.
Illustrative example: A café uses a separate staff device to identify a member's card and add a stamp after an eligible purchase. The payment transaction happens at the register. Staff are trained to do both actions without accidentally stamping an ineligible order.
Make the pass useful at a glance
Give priority to the business name, current progress, and reward information. A decorative card that hides the balance makes returning customers ask questions the card could answer.
Keep the customer-facing terms readable. If a reward is store credit, state where it can be used. If the pass contains contact or location information, check that it is current. Test the visible card after changes rather than assuming every screen updates in the same way.
Avoid displaying sensitive information unnecessarily. The loyalty pass should help customers use the program, not expose details that have no checkout purpose.
Test both supported wallet routes
| Test | What a successful result means |
|---|---|
| New enrollment | The intended card is saved on the tested device |
| Card access | The customer can find it again without staff guessing |
| Qualifying transaction | The correct progress is recorded |
| Redemption | The reward is used once and the balance is correct |
| Correction | Staff can resolve an error using your policy |
| Messages | The tested wallet handles the configured update as expected |
Use real iPhone and Android devices where those are your intended audiences. Notification appearance and behavior are not identical across wallets. Device settings, permissions, connectivity, and platform rules can affect the experience.
Prepare a fallback for customers with an incompatible device, low battery, or limited connectivity. Do not promise a universal experience based on one successful demonstration.
Where Boomerangme fits
Boomerangme's webhook documentation names Apple Wallet, Google Wallet, and PWA installation events. That makes it relevant to businesses evaluating wallet delivery, while the exact card configuration and account features still need checking.
Bring your written earning rule into a test. Watch staff award progress, redeem a benefit, and correct a mistake. A platform demonstration should resolve your practical checkout questions, not just show a branded card.
Frequently asked questions
Do wallet loyalty cards require a custom app?
A supported pass can live in the wallet application. You still need a issuing and loyalty-management system; other delivery routes may use a web app or separate application.
Can the card charge a customer's bank account?
A loyalty pass does not by itself authorize or collect payment. Any payment functionality needs its own supported implementation and customer process.
Will push notifications look the same on both wallets?
Do not assume so. Test the exact message and card workflow on the intended devices, and explain the experience based on those tests.
Try a wallet-first loyalty workflow
If you want customers to save a rewards card on their phones, evaluate Boomerangme against your installation and checkout checklist.
Explore Boomerangme to review the platform's current options.
Sources & further reading
- Apple Wallet pass guideOfficial pass installation and use instructions.
- Google Wallet loyalty overviewOfficial wallet pass support.
- Boomerangme card eventsInstallation events include Apple Wallet, Google Wallet and PWA.
Sources reviewed October 5, 2026. Numerical examples are illustrative unless a cited source states otherwise.
