Skip to main content
Where: Consumer wallet save controls, when enabled on your deployment. For device steps, follow Save a native wallet pass.

Concept illustration. Native pass issuance requires configuration; check Kardy for live progress.

Apple Wallet and Google Wallet saving and stamp updates are enabled. Google Wallet is no longer restricted to invited testers. Use your Kardy browser wallet if your native wallet option is unavailable. The Apple endpoint produces a signed .pkpass. Google produces a signed save link for an existing Generic class; Kardy does not create issuer classes or contact Google when generating the link. Members choose whether to open and save it.

​
Stamp progress and updates

When enabled, merchant passes show the stamp count, goal and reward. The universal pass keeps progress for up to ten programmes separate; your browser wallet shows the complete membership list. After a stamp or redemption, Kardy queues the new progress. A background service updates the Google Wallet pass, or asks Apple Wallet to download the latest pass. Failed attempts are retried. Updates can take time and do not guarantee a visible notification. Open Kardy if you need to check progress while a saved pass catches up. Both update services use a 15-minute recovery check. Larger backlogs can trigger earlier processing, with follow-up runs while ready work remains. This is not a promise that a device refreshes within 15 minutes. Delivery and display still depend on the device and provider; keep the browser wallet available as a fallback.

​
Sync and remove a saved pass

After saving, confirm Yes, added on this device in Kardy. This is your confirmation in the current browser, not automatic detection of your phone’s wallet. Confirmed passes show a sync action and removal instructions instead of another Add action. Another browser or device can save and confirm independently. Sync queues the latest state; it does not award stamps or guarantee an immediate phone refresh. Requests are limited to once per minute per pass. Last synced on the pass means when Kardy prepared its data, not when your phone received it. Remove the pass in Apple Wallet or Google Wallet, then confirm removal in Kardy. This clears the browser’s confirmation, not your membership. Google Wallet can sync across devices signed into the same Google account, so removal may affect those devices too. Clearing browser storage also clears the local confirmation.

​
Your membership QR

Passes carry the same opaque account QR across Kardy and merchant branding. Replacing the account QR invalidates the old Kardy account QR and native passes using it; members must save fresh passes and remove old ones. Historical membership QR tokens and manual member codes remain unchanged and continue to be accepted by the scanner. Revocation does not remotely delete a pass from a device. The public coffee-claim preview is a Kardy PWA scene, not an Apple Wallet screen. Its iPhone-style notification is a concept and does not represent native pass updates or enabled push delivery. Follow claiming a reward for the actual confirmation workflow. See Feature availability for rollout status, or contact Kardy if you need help with a saved pass.

​
Browser cards and other integrations

Native passes do not inherit every browser card design option. Use the browser wallet for current reward progress. Merchant MCP provides scoped, read-only agent access. Kardy does not publish a general write API or webhook contract. Do not rely on internal app routes as stable integration APIs; contact Kardy before planning a custom integration.