Skip to content
stampaki
Wallet experiences

Built for the Wallet — and honest about its rules

Apple Wallet and Google Wallet are different platforms with different rules. Stampaki uses each one natively and tells you exactly what customers will and won't see.

Apple Wallet
Google Wallet

What customers experience in the Wallet

Add in one tap

From their web card, customers tap 'Add to Apple Wallet' or 'Add to Google Wallet'.

Balances that refresh

When the balance changes, Stampaki updates the pass so the card on the phone matches.

Store locations

Up to 10 store locations per card. The phone may surface the card nearby; it's never guaranteed, and Stampaki never tracks the customer.

Native layouts

We use each platform's own card layouts and images. The richer web card isn't squeezed into the Wallet.

No personal data in the code

The QR on the pass carries a random signed ID only.

Lost phone? Reissue

Customers restore their card by email; the old pass and QR stop working.

  • Apple: signed passes with update web service
  • Google: loyalty classes and objects via the official API
  • Up to 10 locations per card
  • Pilot: being verified with live provider accounts

Stampaki is in its pilot phase. Apple Wallet and Google Wallet issuance is built into the product and is being verified with live provider accounts before general availability.

Frequently asked questions

Can I send push notifications to iPhone users?
Apple Wallet doesn't allow promotional push messages. Stampaki updates the card's content instead; Apple's rules allow change notifications only for important changes such as a reward becoming available.
How many Google Wallet notifications can I send?
Google allows up to three notifying messages per card per day. Stampaki tracks this and sends further messages silently.
Will the card always appear when customers are near my shop?
No. Location relevance is a hint to the phone, which decides whether to show the card. Device settings and platform limits apply.

Every visit counts.