Create Google Wallet Passes: A Step-by-Step Guide 2026

A café owner checks the till at close, sees repeat customers coming back, and still hears the same complaint from staff, “I left my card at home.” That is exactly where Google Wallet passes fit, because the pass lives on the phone customers already reach for, alongside the payment habit they already trust. In the UK, that habit is no longer niche, with the Financial Conduct Authority finding that 20% of UK card users now use a digital wallet for more than half of their card transactions, and UK Finance reporting that over half of UK adults now use mobile wallets, while cash fell to 4.4 billion payments in 2024 and dropped below 10% of all payments for the first time (NFCW's summary of the FCA and UK Finance reporting).

For local merchants, that matters because the pass is not a separate habit to teach from scratch. It sits inside an existing wallet routine, which is why loyalty cards, coupons, tickets, and membership passes can work as everyday retention tools in cafés, salons, gyms, quick-service restaurants, and retail shops. BonusQR's Apple Wallet loyalty feature follows the same practical logic for merchants who want wallet-based loyalty without building everything manually.

Understanding Google Wallet Passes

A Google Wallet pass is not just a digital image of a loyalty card. It is a structured record that lives in Google Wallet and can be presented at checkout as a barcode or QR code. Google's own support documentation says users can add a pass with Add pass on the website or in the Wallet app, then show it by scanning the code at a reader (Google Wallet support).

The class and object model

Google Wallet issues passes through two linked parts, a Passes Class and a Passes Object. The class is the reusable template, while the object contains the customer-specific data, and both are required to add a pass through a signed JWT that carries the object ID into Google Wallet (Google Wallet developer docs). For a merchant, that means one stable template for the brand, then one object per customer, reward, or ticket instance.

That structure maps neatly to real loyalty flows. A loyalty card should use the class for the fixed design and rules, while each object can carry the customer's name, points balance, or membership state. A coupon can use the same model for offer terms plus one-off redemption data, and an event ticket can use the class to define the event format while the object holds the attendee details.

Practical rule: if the pass design changes often, the class should stay stable and the changing data should stay in the object. That keeps the wallet tidy and avoids unnecessary rebuilds.

Operationally, that is the main reason the model works for repeat-visit businesses. Class-level edits flow to linked passes, so a merchant can adjust branding or shared wording without rebuilding every stored pass. Object-level data stays individual, which is what makes every customer's pass useful at the till.

Google Wallet also fits into a broader identity and essentials ecosystem in the UK, where Google says residents will soon be able to create digital ID passes with UK passports and keep essentials in one app (Google's UK Wallet update). That reinforces the point that Wallet is already moving beyond payments into everyday utility.

Preparing Your Business for Google Wallet Passes

The cleanest setup starts before any pass design. A merchant needs a Google Cloud project, the Wallet API, a service account, and the right permissions so pass signing and issuance can happen without friction. Google's Wallet support also makes the customer journey simple once the setup is live, because the pass can be added from the website or app and used straight away at the reader (Google Wallet support).

What to line up first

• Create the cloud project. This keeps Wallet work separate from other business systems and gives the merchant one place to manage access.
• Enable the Wallet API. That is the connection point between the business and Google Wallet itself.
• Create a service account. This is the identity used for secure API access and JWT signing.
• Grant the correct permissions. Without those roles, pass issuance breaks at the point where the business tries to create or update objects.

These are the boring steps that save the most time later. If they are done late, every template, field map, and QR flow becomes harder to test because the issue is usually at the account layer rather than in the design itself.

For merchants comparing paid media and wallet-based retention, Come Together Media's PPC guide is useful context because it shows how acquisition and retention can sit side by side. A wallet pass won't replace discovery, but it can keep new customers visible once they arrive.

The market is already ready for that combination. The FCA found that 20% of UK card users now use a digital wallet for more than half of their card transactions, while over half of UK adults use mobile wallets (NFCW summary of the regulators' reporting). That makes the setup work worth doing now, not later.

Building Your Pass Template

A pass template should be built like a storefront display, not a spreadsheet. The customer sees the brand first, then the data, then the action they need to take. Google Wallet passes are operationally designed for everyday UK use because customers can add a pass through Add pass and present it by scanning a barcode or QR code at checkout (Google Wallet support).

Brand first, fields second

The class template is where the merchant locks in the shared look and feel. That means logo, colours, title, and the core field layout should be decided before creating live objects. If the logo is oversized or the field list is cluttered, the pass becomes harder to recognise on a busy phone screen.

A better approach is to keep the fields tightly focused:

• Customer name for identification at the till.
• Points or stamps balance if the programme is visit-led.
• Expiry or renewal date when offers need time limits.
• Membership tier if the business runs simple status-based rewards.

The strongest templates are the ones staff can read quickly and customers can recognise at a glance. That matters because the pass may be hidden among other cards in the wallet, and Google's own help notes that users may need to swipe to find a pass (Google Wallet help). Clear naming and simple layouts reduce that friction.

Why field mapping matters

A pass template only works when the business maps its own data cleanly into Google's fields. If a merchant calls one field “visits” in one place and “stamps” in another, customers and staff end up reading different things from the same pass. That is why field mapping should be consistent before the first object is issued.

BonusQR's builder can sit in front of that complexity by translating common loyalty fields into a repeatable structure, which is useful for merchants who want QR-based enrolment without hand-coding every card. For stores that need both Google Wallet and Apple Wallet coverage, the wider wallet design should stay consistent even if the platform output differs.

Distributing Wallet Passes with QR Codes

QR codes are the fastest practical way to get a pass into a customer's wallet. Google Wallet already supports barcode and QR presentation at the point of use, so the same visual language that gets a customer into the pass also helps them use it at the counter (Google Wallet support). In the UK, that matters because wallet-style usage is already established in both store and online settings, with 30% of respondents saying they used Google Pay at point of sale and 20% saying they used it online between July 2023 and June 2024 (Statista UK adoption figure).

What the QR should contain

The QR code should point to a deep link or a signed pass token that opens the save flow immediately. If the link is buried behind extra clicks, people drop off. If it is visible on a receipt, poster, email footer, or SMS, the pass becomes a low-friction follow-up after a purchase.

For local shops, the best placements are the obvious ones. Counter signs work because the customer is already at the till. Post-purchase email works because the transaction is still fresh. SMS works when the business already uses it for reminders or loyalty nudges.

Proven QR code ideas for local shops can help merchants think beyond the wallet pass itself and place QR codes where scanning is natural, not forced.

Keep the code big enough to scan quickly, then keep the message short. If customers have to read a paragraph before they know what the code does, the poster is already failing.

Using QR distribution well

A merchant can also embed the pass token inside a QR generated by a loyalty platform or pass tool, then reuse that same QR across print and digital. That is the point where a system like BonusQR is practical, because it already centres the workflow on QR enrolment, while Google Wallet handles the stored pass once it is added. The important part is not the tool name, it is making the journey from discovery to wallet save feel immediate.

Best Practices for Google Wallet Passes

Google Wallet passes work best when they are easy to find, easy to trust, and easy to update. Google's help documentation notes that users may need to swipe to find a pass, so pass naming should be short and obvious rather than clever or branded beyond recognition (Google Wallet help). A customer is far more likely to present a pass called “Coffee Loyalty” than a pass buried under a campaign slogan.

What to get right from day one

A strong pass strategy usually comes down to a few essentials:

• Use clear pass names. Staff should recognise them immediately at checkout.
• Keep class updates conservative. Shared template changes should be deliberate, not frequent.
• Map fields carefully. Missing or mismatched fields create awkward checkouts.
• Design for both wallets if needed. Google Wallet alone can miss iPhone users.

That last point is the trade-off many merchants skip. UK Finance says over half of UK adults now use mobile wallets, but cards still account for 67% of payments, so a dual-wallet strategy can reach Android users without losing iPhone customers (UK Finance). For many small businesses, that is the more sensible answer than betting on one wallet ecosystem alone.

Avoiding the usual mistakes

The first mistake is changing the class too often. That makes the pass feel unstable and can create avoidable support issues. The second is overstuffing the object with every possible field, which makes the pass harder to scan quickly and less useful at the till.

The third mistake is ignoring where the customer will use it. A gym member needs a pass that is easy to find at the desk. A café regular needs something staff can validate in seconds. A salon client needs a pass that reflects a simple reward or membership state, not a mini profile.

Routine audits matter too. If offers expire, update the text. If a campaign ends, remove the distraction. If the wallet pass is still live, it should still look current.

Next Steps with BonusQR to Boost Loyalty

A wallet pass becomes useful when it sits inside a wider loyalty system, not as a one-off download. BonusQR supports QR-based enrolment, wallet passes, stamps, points, cashback, visit thresholds, spend thresholds, and coupon-style rewards, which makes it a practical fit for merchants that want one customer profile rather than scattered tools. The simplest way to move forward is to connect the pass to repeat-visit behaviour, then let campaigns do the follow-up.

loyalty platform pricing gives merchants a quick way to compare entry options before they build a full programme. That matters because the pass itself is only the front door, while the primary value comes from how often the customer comes back.

The strongest next move is usually straightforward. Launch the pass, watch which offers get redeemed, then use the same customer list to send welcome bonuses, birthday coupons, and seasonal offers. That turns a static wallet item into an active retention channel.

If the shop already relies on QR codes at the counter, BonusQR is the easiest place to keep that workflow organised and extend it into Google Wallet and Apple Wallet without adding hardware. Start with one simple pass, test it in-store, and build the rest of the loyalty logic around the behaviour customers already show.

Set up your first Google Wallet pass, test the QR save flow at the counter, and then connect it to a simple loyalty offer that brings customers back. If the business wants a single place to manage QR enrolment, wallet passes, and repeat-visit campaigns, start with BonusQR's free plan and launch the first pass this week.