Google Wallet pass maker
Google Wallet Pass Maker: Create Passes Without Code
Design a branded loyalty card, coupon or membership pass, share it with a QR code, and reach Android customers on their lock screen. No developer account. No API. No app.
Quick answer
- To create a Google Wallet pass yourself, you need a Google Pay & Wallet Console issuer account, Google's approval for publishing access, and code that calls the Google Wallet API.
- A Google Wallet pass maker like PushNotice skips all of that: pick a template, add your logo and colors, and share a QR code or link.
- Customers tap Add to Google Wallet. There's no app to download and no account to create.
- Once the pass is saved, you can update it and send notifications to the customer's phone. Google allows up to 3 notifying messages per pass in 24 hours.
- PushNotice is free to start (up to 100 customers) and issues the same pass to Apple Wallet for iPhone users.
Updated 14 November 2026 · Platform rules checked against Google's developer documentation
Search for how to create a Google Wallet pass and almost everything you find is written for developers. Google's documentation explains Passes Classes, Passes Objects, signed JSON Web Tokens and REST endpoints. Enterprise vendors sell API platforms priced for airlines and banks. Very little of it helps a café, salon or gym owner who just wants their loyalty card on customers' Android phones by the end of the day.
This page is for that owner. It explains what a Google Wallet pass is, the two ways to make one, how to create one in a few minutes without code, which pass type fits your business, and what you can do once the pass is on a customer's phone. That last part is where the value is.
The basics
What is a Google Wallet pass?
A Google Wallet pass is a digital card (a loyalty card, coupon, membership card, gift card or ticket) that customers save to the Google Wallet app on their Android phone. Unlike a screenshot or PDF, the business can update a saved pass and send notifications to it.
Google Wallet comes built into Android, so customers don't install anything. A pass shows your logo, colors, your program details (the reward, offer, membership level, expiry) and a QR code or barcode your staff can scan. Google supports several specialized pass types, such as loyalty cards, offers, gift cards, event tickets and transit passes, plus a generic type for anything that doesn't fit those.
In Google's terms, a Passes Class is the template shared by every pass in a program (your brand, program name, terms). A Passes Object is one customer's copy (their name, balance and code). A pass maker creates and manages both for you.
Because the pass is a live object rather than a static image, it can change after it's saved: a new offer appears, a coupon expires, a headline changes. You can also send it a message that lands as a notification on the customer's phone. That makes a Google Wallet pass a marketing channel, not just a card. For the wider strategy, see our Google Wallet marketing guide.
Your options
Two ways to create a Google Wallet pass
You can build Google Wallet passes yourself with the Google Wallet API, which means an issuer account, Google's review and a developer. Or you can use a pass maker that has already done that work and gives you a visual editor. For most small businesses the second route is faster and cheaper.
Here's what the do-it-yourself route involves, based on Google's own setup process:
- Create an issuer account in the Google Pay & Wallet Console. New issuer accounts start in Demo Mode, where passes can only go to test accounts.
- Complete your Business Profile, including a payments profile that identifies your business.
- Build at least one Passes Class and take screenshots of your pass integration.
- Request publishing access. The Google Wallet team reviews the account before you can issue passes to the public.
- Write the code to create a Passes Object for each customer, sign the "Add to Google Wallet" link, and call the API whenever a pass needs to change.
None of this is unreasonable for a company with an engineering team. For a business with one location and no developer, it's a project that rarely gets finished. And it only covers Android: iPhone customers need a separate Apple Wallet pass, which means another developer account and another integration.
| Build it yourself (Google Wallet API) | Use a pass maker (PushNotice) | |
|---|---|---|
| Google issuer account | You create it and pass Google's review | Not needed |
| Developer needed | Yes: API calls, signed links, hosting | No: visual editor |
| Time to first live pass | Days to weeks, including review | Minutes |
| iPhone customers | Separate Apple Wallet build | Same design, both wallets |
| Sending notifications | Write code against the Add Message API | Write a message and press send |
| Full control of the data model | Total | Templates and fields |
| Cost | Developer time plus hosting | Free plan; paid from $29/month |
Do-it-yourself steps summarized from Google's "Requesting publishing access" documentation. PushNotice details from pushnotice.io pricing, November 2026.
If you're an airline, a bank, a ticketing platform, or an app business that needs passes wired deeply into your own systems, use the API directly. If you run a shop, studio, salon, café or gym, a pass maker gets you the same customer-facing result without the project.
Step by step
How to create a Google Wallet pass in 4 steps
To create a Google Wallet pass with PushNotice: pick a template, add your branding and fields, publish to get a QR code and link, then let customers tap Add to Google Wallet. It takes a few minutes and no code.
-
1
Pick a template
Start from a loyalty card, coupon, membership or rewards template. Each one is a starting point you can fully change.
-
2
Add your branding and fields
Upload your logo, set your colors, and choose what the pass shows: the reward, your current offer, membership level, perks or an expiry date. The editor previews the Google Wallet and Apple Wallet versions as you go.
-
3
Publish and share
Publishing gives you a QR code and a link. Print the QR on your counter, receipts or window, and put the link in emails, texts, social posts or your website.
-
4
Customers tap "Add to Google Wallet"
Android customers save the pass in one tap; iPhone customers get the Apple Wallet version. From then on you can update the pass and send offers to the customer's phone.
Make your first Google Wallet pass now, free for up to 100 customers.
Start free →Choosing a format
Which Google Wallet pass should you make?
Choose by what you want customers to do. Loyalty cards bring people back, coupons drive one visit, membership cards prove access, and a rewards card can cover both points and perks. Most local businesses start with a loyalty card.
| Pass | Best for | What it shows | Typical first message |
|---|---|---|---|
| Loyalty / stamp card | Cafés, salons, car washes, bakeries | The reward and how to earn it | "Two stamps away from a free drink" |
| Coupon | Launches, slow days, win-backs | The offer, expiry date, code | "20% off ends tonight" |
| Membership card | Gyms, studios, clubs, associations | Membership level, perks, expiry | "Your renewal is 7 days away" |
| Rewards / VIP card | Retail, restaurants, multi-location brands | Tier names, member perks | "VIP hour: free upsize 2–4pm" |
PushNotice templates. Google Wallet also supports gift cards, event tickets, boarding passes and transit passes, which are built for those specific industries.
Google Wallet loyalty cards
A Google Wallet loyalty card is the most common starting point because the habit is already there. Customers understand "buy nine, get the tenth free" without explanation. The difference from paper is that the card is always on their phone and you can reach the people holding it, with a double-stamp day, a new item or a reminder to come back. Automatic visit tracking, where staff scan the pass and the stamp count updates by itself, is rolling out to pilot businesses now. Ask us if you want it. If you're replacing a paper punch card, our guide to digital loyalty cards covers reward design and thresholds.
Distribution
How customers add your pass to Google Wallet
Customers add your pass by scanning a QR code or tapping a link, then pressing Add to Google Wallet. There's no app download, account or password. The fewer steps between seeing your offer and saving it, the more customers sign up.
The QR code at your counter is usually your best sign-up channel because the customer is already in front of you and waiting. Our field guide to QR codes that convert covers placement and wording. These are the places most businesses share their pass:
Counter QR code
A small sign by the till or card reader. Customers scan while they wait.
Receipts & packaging
Print the QR on receipts, cup sleeves, bags or takeaway menus.
Window & tables
A window sticker or table card catches people who don't come to the counter.
Email & text
Send the link to customers you already have contact details for.
Social posts
Post the link in your bio or a story: "Save our card, get a free drink on your 10th visit."
Your website
Add the link as a button on your homepage, booking page or order confirmation.
Signage alone converts slowly. A one-line prompt at the till ("Want your stamps on your phone? Scan this, it takes five seconds") is usually what turns a QR code into a list.
After the save
What you can do once the pass is in Google Wallet
After a customer saves your pass, you can change what it shows, send messages that appear as notifications on their phone, and (on paid plans) trigger location-based alerts near your business. This is the difference between a wallet pass and a printed card.
- Update the pass with each campaign. When you send a campaign, PushNotice updates what the pass shows and adds your message to it. Nothing is reissued. (Automatic per-visit stamps are in pilot.)
- Send messages that notify. Promote a slow afternoon, announce a new item, or remind someone their reward is waiting. Messages also appear on the pass's details screen.
- Reach customers nearby. Google Wallet supports location-based notifications when a customer is near one of your locations. PushNotice offers this as Smart Location on the Starter and Pro plans.
- Target the right people. Tag customers and send to a segment, such as VIPs or people who haven't visited in a month (Tagging & Segmentation is on the Pro plan).
- See what's working. Track installs, visits and campaign results in your dashboard.
Google allows a maximum of 3 notifying messages per pass in any 24-hour period and may throttle senders it considers spammy. Customers must have Google Wallet notifications turned on, and Google controls how the notification looks on the lock screen. Plan a few useful messages a week, not several a day.
Google Wallet began rolling out an in-app notification feed (a bell icon at the top of the app) that collects updates about saved items in one place. It's arriving gradually, so not every customer has it yet. Even so, your messages are getting a permanent home inside Wallet, not just a moment in the notification shade.
For what to send and how often, see our guide to lock-screen marketing.
Key takeaways
- A saved pass is a channel: you can update it and message it for as long as the customer keeps it.
- Google caps notifying messages at 3 per pass per 24 hours. A few well-timed messages beat volume.
- Location alerts and segments turn one broadcast into the right message for the right customer.
iPhone and Android
One pass design for Google Wallet and Apple Wallet
Google Wallet covers your Android customers, and Apple Wallet covers iPhone. PushNotice issues the same pass design to both, and the customer's phone picks the right wallet automatically, so you share one QR code instead of two.
This matters more than it seems. If you build the Google pass yourself, you've covered only part of your customers, and the Apple Wallet version is a second project with its own developer account and signing. With a pass maker, both versions come from one design, one customer list and one campaign screen. When you send an offer, it goes to both wallets.
There are small platform differences worth knowing. Apple shows a lock-screen notification when a pass field with a change message is updated, while Google uses messages and field-update notifications under its own rules. The customer experience is close enough that you can plan one campaign calendar. For the iPhone side, see our Apple Wallet pass maker page and the Apple Wallet marketing guide.
Decision guide
How to choose a Google Wallet pass maker
A good Google Wallet pass maker issues real wallet passes (not images), lets you update and message them after they're saved, covers Apple Wallet too, and charges in a way that fits a small business. If a tool can't send a notification to the pass it made, it's a card printer.
What to look for
- Issues genuine Google Wallet and Apple Wallet passes, not a PDF or screenshot
- Lets you update offers and messages on passes already saved
- Sends notifications to saved passes and respects Google's limits
- Works without your own Google issuer account or a developer
- Gives you a QR code and link you can use anywhere
- Supports location-based alerts and customer segments as you grow
- Shows installs and campaign results
- Has a free tier so you can test with real customers first
| Static card generator | Developer pass platform | PushNotice | |
|---|---|---|---|
| Real wallet pass | Often an image or PDF | Yes | Yes |
| Updates after saving | No | Yes, via API | Yes, from the dashboard |
| Notifications | No | Yes, via API | Yes, write and send |
| Needs a developer | No | Yes | No |
| Built for | One-off cards | Engineering teams | Local businesses & agencies |
Comparing the three kinds of tool you'll find when you search for a Google Wallet pass maker. For a vendor-by-vendor look, see PushNotice vs PassKit.
From experience
Common Google Wallet pass mistakes
The most common mistakes are making a pass that can't be updated, cluttering the front of the card, launching with no sign-up plan, and then going silent once customers have saved it.
- Using a static image. A screenshot in a photo gallery isn't a wallet pass. It can't update, notify or be scanned reliably.
- Crowding the front. Show your brand, the reward and the code. Put terms and details on the back.
- No sign-up moment. A QR code with no staff prompt and no visible reward ("free drink on your 10th") collects few saves.
- Over-messaging. Google's 3-per-24-hours cap exists for a reason. Customers who feel spammed delete passes.
- Forgetting iPhone users. An Android-only pass leaves out a large share of customers in markets like the US.
- Going quiet. The pass is the start of the relationship. Plan your first three messages before launch: welcome, a near-reward nudge and a slow-day offer.
Launch checklist
- Template chosen and reward clearly stated on the pass
- Logo and colors legible on a small screen
- QR code printed at the counter, plus one other place
- Staff know the one-line prompt
- First three messages written and scheduled
- Tested on one Android and one iPhone before launch
Pricing
Can you create a Google Wallet pass for free?
Yes. PushNotice's Free plan lets you create a Google Wallet pass (with the Apple Wallet version included) for up to 100 customers and 4 campaigns a month, with no credit card. Paid plans add more customers, more campaigns and location-based alerts.
- 100 wallet customers
- 4 campaigns / month
- 1 pass design
- Basic analytics
- 2,500 wallet customers
- 100 campaigns / month
- 1 pass design
- Smart Location
- Detailed analytics
- 25,000 wallet customers
- 1,000 campaigns / month
- 2 pass designs per workspace, 5 workspaces
- Smart Location
- Tagging & segmentation
Plans as listed on pushnotice.io in November 2026. Annual billing saves 10%. Agencies managing several clients can ask about white-label workspaces.
Get started
Create your Google Wallet pass today
Design it once, share one QR code, and reach Android and iPhone customers on their lock screen. No issuer account, no code, free to start.
Glossary
Key terms
- Google Wallet pass
- A digital card saved in the Google Wallet app that the issuer can update and send notifications to.
- Issuer account
- The Google Pay & Wallet Console account a business needs to issue passes directly through Google's API.
- Publishing access
- Google's approval to issue passes to the public. Until it's granted, an issuer account is in Demo Mode.
- Passes Class / Object
- The shared template for a program (Class) and one customer's individual pass (Object).
- Add to Google Wallet
- The button or link a customer taps to save your pass.
- Wallet marketing
- Using wallet passes and their notifications as a channel to bring customers back. Full guide.
FAQ
Frequently asked questions
How do I create a Google Wallet pass for my business?
Can I create a Google Wallet pass for free?
Do I need a Google Wallet issuer account or developer account?
Do my customers need to download an app?
Does a Google Wallet pass work on iPhone?
Can I send push notifications to a Google Wallet pass?
How many notifications can I send to a Google Wallet pass?
Can I update a Google Wallet pass after a customer saves it?
What types of Google Wallet passes can I create?
Can I make a Google Wallet loyalty card or punch card?
How do customers add my pass to Google Wallet?
Can Google Wallet passes send alerts when customers are nearby?
Does it work in the UK?
Is a Google Wallet pass better than a loyalty app?
How much does PushNotice cost?
Sources
Sources
Platform rules on this page were checked against Google's documentation on 14 November 2026. Google changes these rules from time to time, so check the source if a detail matters to your launch.
- Google Wallet: Trigger push notifications (3 notifying messages per 24 hours, notification settings, nearby notifications)
- Google Wallet: Requesting publishing access (Demo Mode, Business Profile, review)
- Google Wallet pass development flow (pass types, Classes and Objects)
- 9to5Google, 21 Oct 2026: Google Wallet notifications feed
Keep reading
Related guides
Your first Google Wallet pass is free. Live in minutes, no code.
Start free →