Passes for Google Wallet, issued, tapped and kept live.
Walletap issues loyalty and stamp cards, memberships, gift cards, offers, event tickets and transit tickets to Google Wallet, from the same template that issues them to Apple Wallet. Customers save a pass from a link, check in with Smart Tap, and see every change on the pass they already hold.
58,000+
Smart Tap check-ins validated in real time
3,200+
passes saved to Google Wallet
25+
merchant accounts with passes in Google Wallet
Pass types
One template, from loyalty cards to transit tickets.
Design a pass once. Walletap builds the native Google Wallet class and object for its type, and the Apple Wallet version from the same template.
Loyalty and stamp cards
Points or stamps on the face of the card, updated as soon as a visit or purchase is recorded.
Memberships
Member name, number and validity date, updated automatically when a plan renews or is cancelled.
Gift cards
A balance in your currency that your own systems top up or spend through the API.
Offers and coupons
A unique code for each customer and a validity window. When it ends, Google Wallet moves the pass to expired passes.
Event tickets
Event name, date, venue and seat. Several tickets from one order save with a single link.
Transit tickets
Bus, rail and ferry tickets with zone, platform and ticket status on the card, switched on for transit operators on request.
Platform
Built on the Google Wallet API, set up for every merchant.
Merchants design passes in Walletap. The Google Wallet side is provisioned and maintained for them.
A dedicated issuer account
Every merchant gets its own Google Wallet issuer account, created automatically through the API.
Smart Tap keys per merchant
Each merchant's issuer gets its own Smart Tap collector ID and authentication key, which the merchant's readers use to read its passes.
Native classes and objects
Passes are written to Google Wallet as classes and objects before anyone saves them, so a save link carries only their IDs and stays short.
Hosted in the EU
Walletap's application servers and functions run in Frankfurt, and its database and file storage in Google Cloud's EU multi-region.
Smart Tap
Tap to check in. Tap to open the door.
An NFC-enabled pass carries a Smart Tap value, encrypted for the merchant's key, that readers read over NFC. Walletap checks the pass in real time, so an expired or revoked pass does not get in.
At the front desk
The Walletap desktop app for Windows and macOS reads passes on USB NFC readers and shows staff the member who just tapped.
At the door
Door readers let a member in only while their pass is valid and within the opening hours set for the location.
Smart Tap compatible readers
In production on desk and door readers from terminal providers on Google's list of Smart Tap compatible providers.
Every tap recorded
Each check-in is logged with its location and result, and feeds visit analytics.
After the save
Passes that stay current in the customer's wallet.
Live updates
Change a balance, a validity date or a seat, and the saved pass changes with it. Nothing is reissued.
Push messages
Message one holder or everyone holding a pass: now, on a schedule, or a set number of days before it expires.
Expiry and revocation
A revoked pass moves to the customer's expired passes on its own, and readers refuse a pass once it has expired.
Saves and removals
Google Wallet reports saves and removals through signed callbacks, and Walletap turns them into installs, removals and active passes, shown separately for Google Wallet and Apple Wallet.
Distribution
One link, every channel.
Every pass gets its own link: on Android it offers Google Wallet, on an iPhone Apple Wallet.
On your website
A sign-up form for your site that hands each new customer their pass straight away.
In store
Printable QR posters for the counter, and the Walletap staff app for issuing a pass on the spot.
Email and SMS
Each new pass can go out by email, SMS or a messaging app, carrying its link.
REST API
Issue and update passes from your own systems with scoped API keys. Each new pass comes back with its Google Wallet save link.
Zapier
Create and update passes and send notifications from the apps your team already uses, without code.
MCP server
AI assistants issue and manage passes through Walletap's hosted MCP server.
Questions about Google Wallet passes.
No. Walletap creates a dedicated Google Wallet issuer account for each merchant through the API and manages its classes, passes and Smart Tap keys. Merchants design and issue passes in Walletap.
Yes. One template issues the pass to both Google Wallet and Apple Wallet, and the pass page offers the right one for the customer's phone.
Walletap runs Smart Tap on desk and door readers from terminal providers on Google's list of Smart Tap compatible providers. The documentation lists the readers Walletap supports and how to connect them.
Yes. Balances, validity dates, seats and other fields update on the saved pass, and merchants can send push messages to its holder. Nothing has to be reissued.
In the EU. Walletap's application servers and functions run in Frankfurt, and its database and file storage in Google Cloud's EU multi-region. A saved pass is also held by the wallet the customer saved it to.
Yes. The REST API, the Zapier app and the MCP server all issue and update passes. The API returns each new pass with its Google Wallet save link.
Put your passes in Google Wallet.
Tell us what you issue and where your customers use it. We will show you the setup, from the first template to the first tap.