# Learn wallet fundamentals

<figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2FwQtX0NRpm6UFjJTFxStt%2Fimage.png?alt=media&#x26;token=c23b21f0-f9de-4110-a831-6146137a7cc4" alt="Wallet fundamentals"><figcaption></figcaption></figure>

Mobile wallets like Apple Wallet and Google Wallet are no longer just digital folders for coupons. They’ve become central to how people organize the essentials of daily life. Customers add passes to their wallet because it keeps the most-used items (loyalty cards, tickets, offers, and more) at their fingertips without digging through emails, apps, or physical cards. Having a pass in the wallet means instant access when it matters: at checkout, at the gate, or at an event entrance, making each experience smoother and faster for customers.

Beyond simple passes, mobile wallets securely store customers’ **bank cards**, enabling contactless payments from a phone or smartwatch, which makes wallet apps a daily habit for purchases, travel, and access. Adding branded passes, such as a rewards card, concert ticket, or store offer, fits naturally into that routine, keeping the Brand visible each time customers open their wallet. Wallets also act as a **single, always-available hub** for personal credentials, where tickets, membership cards, boarding passes, and other passes live side by side, and this frequent, practical usage increases the likelihood that customers keep and engage with the passes a Brand provides, driving repeat interactions and deeper loyalty over time.

### One place for daily credentials

The Apple Wallet app and the Google Wallet app group items customers need in the moment. That includes coupons, loyalty cards, membership cards, event tickets, and more. Customers do not have to search emails or install an app.

<div data-with-frame="true"><figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2Fgit-blob-090b701a341354905388e9e508dcdc7d24ab4036%2Fintroduction_to_mobile_wallets_1.png?alt=media" alt="Apple Wallet and Google Wallet shown as the two main mobile wallet apps used by customers on iOS and Android."><figcaption><p>Mobile wallets are where customers keep their pass day to day.</p></figcaption></figure></div>

### Instant access at checkout or entry

Most Apple Wallet passes and Google Wallet passes are redeemed with a barcode or QR code. Some use NFC when compatible scanning hardware is available. Customers open the pass and present it in seconds.

### Always up to date

A pass is not a static PDF. An Apple Wallet pass and a Google Wallet pass can refresh over time. This matters when points change, balances decrease, or ticket details update.

Updates are part of the core lifecycle. For update mechanisms and delivery constraints, see [Push notifications](https://docs.thewalletcrew.io/engage-and-animate/push-notification). For identifiers and data model basics, see [Structure](https://docs.thewalletcrew.io/develop/architecture/structure).

## Pass types you can configure in The Wallet Crew

The Wallet Crew lets Brands create templates for several **Apple Wallet pass** and **Google Wallet pass** types. Each pass type comes with Apple and Google constraints. The template then defines layout, fields, images, and barcode.

When the template choice is unclear, [Type of pass](https://docs.thewalletcrew.io/design/general) helps narrow down the right starting point. When the pass type is already known, the relevant section below is the right entry point. Configuration then happens in the Template Designer.

{% hint style="info" %}
Wallet apps can store payment cards for contactless payments (Apple Pay / Google Pay). The Wallet Crew covers wallet passes (loyalty, tickets, offers, gift cards), not payment cards.
{% endhint %}

### Loyalty card

A loyalty card is a loyalty program **Apple Wallet pass** / **Google Wallet pass**. It rewards customers for coming back. It also makes the loyalty program feel tangible.

* **Best for:** points, stamps, tiered membership, and account identification at POS.
* **Key fields:** member ID, barcode/QR, points balance, tier/status, and key links.
* **Typical redemption:** scan at checkout to identify the customer, then update points/tier.

For the Brand, the goal is retention. Brands reward customers who purchase repeatedly. Brands can offer points, discounts, gifts, and other benefits. A loyalty card can also be an entry point to a customer account. This helps centralize data and personalize experiences.

For customers, the value is immediate. They can see their loyalty status and rewards. They do not need to remember a card number or bring plastic.

When the loyalty card is added to Apple Wallet or Google Wallet, it becomes easier to use. Customers can open the wallet app and select the card in seconds. They do not miss reward opportunities because points and perks stay visible on the pass.

<details>

<summary><strong>Real-world examples</strong></summary>

* Retail: points balance and tier (Silver/Gold) updated after each purchase.
* QSR: stamp card (buy 8, get 1 free) with progress displayed on the pass.
* Beauty: member ID used at checkout, plus birthday reward shown as a field.

</details>

More details: [Design > Loyalty card](https://docs.thewalletcrew.io/design/loyalty-card-template-configuration).

### Event ticket

An event ticket is an access-control **Apple Wallet pass** / **Google Wallet pass**. It is built for fast scanning at the entrance. It also makes it easy for attendees to find the right ticket.

* **Best for:** events with controlled entry and a “scan at gate” workflow.
* **Key fields:** event name, date/time, venue, seat/section, gate, barcode/QR.
* **Typical redemption:** scan at the entrance to validate entry and prevent duplicates.

For organizers, dematerializing tickets reduces loss and fraud risks. It speeds up entry because staff can scan a QR or barcode. It also supports last-minute changes. The same installed ticket can be updated when seat, gate, or schedule changes.

For attendees, adding a ticket to wallet is simple. They can add it from an email link, directly from a ticketing website, or by scanning a QR code on-site. At the venue, the ticket is ready to present in a few taps.

<details>

<summary><strong>Real-world examples</strong></summary>

* Concert: seat info + QR scanned at the gate, with “doors open” time on the pass.
* Museum: timed entry ticket, where the date/time changes after reschedule.
* Festival: multi-day pass, with the same pass updated each day with new info.

</details>

More details: [Design > Event ticket](https://docs.thewalletcrew.io/design/event-ticket).

### Gift card

A gift card is a stored-value **Apple Wallet pass** / **Google Wallet pass**. It is meant to be redeemed over time. The key requirement is keeping the balance accurate after each redemption, top-up, or refund.

* **Best for:** stored value that decreases over time (balance use, top-ups, refunds).
* **Key fields:** card number, balance + currency, barcode/QR (or NFC), expiry date.
* **Typical redemption:** scan at checkout, apply partial or full amount, then update balance.

For Brands, gift cards generate revenue upfront. Customers often spend more than the card value. Gift cards are also frequently given to someone else. That makes them a strong acquisition channel for new customers.

For customers, a wallet gift card is easier to keep and use. The pass can display the current balance and a scannable barcode or QR code. It also reduces “lost card” scenarios because the gift card stays on the phone.

<details>

<summary><strong>Real-world examples</strong></summary>

* Retail: gift card issued with €100, then balance updated after each redemption.
* Hospitality: voucher sold online, used in multiple partial payments on-site.
* Customer care: goodwill credit added as a top-up, then spent over time.

</details>

More details: [Design > Gift card](https://docs.thewalletcrew.io/design/gift-card).

### Offer

An offer is a coupon-style **Apple Wallet pass** / **Google Wallet pass**. It is used for discounts and time-bound incentives. Offers are often redeemed once, then become invalid.

* **Best for:** discounts, promo codes, and short campaigns with clear expiry rules.
* **Key fields:** offer title, expiry date, conditions, barcode/QR or promo code.
* **Typical redemption:** scan in-store or enter the code online, then mark as redeemed.

For Brands, offers are a practical way to drive traffic and conversion. They can also support segmentation. Different offers can be issued to different audiences. An offer can also be stopped or expired without requiring a reinstall.

For customers, wallet offers are easy to retrieve at checkout. The pass can display the expiry date and conditions clearly. It can also present a scannable barcode or a code to enter online.

<details>

<summary><strong>Real-world examples</strong></summary>

* Retail: “-20% this weekend” coupon with an expiry date and single-use barcode.
* E-commerce: promo code shown on the pass, redeemed in checkout.
* CRM: win-back offer sent to inactive customers, then marked as redeemed in POS.

</details>

More details: [Design > Offer](https://docs.thewalletcrew.io/design/offer).

### Generic

Generic is the most flexible **Apple Wallet pass** / **Google Wallet pass** type. It fits use cases that do not match a dedicated template. It is a good fit for credentials that must be shown or scanned.

* **Best for:** membership cards, staff badges, warranty cards, pickup credentials, and “other”.
* **Key fields:** a stable identifier, barcode/QR, status, key facts, and support links.
* **Typical redemption:** visual check or scan, depending on the operational workflow.

For Brands, Generic helps when a custom layout is needed. Fields and display order are fully configurable. This is useful for membership cards that are not loyalty programs, staff passes, partner badges, warranty cards, or pickup credentials.

For customers, a Generic pass works like any other pass. It is easy to add, easy to find, and easy to present. It can also be updated when details change.

<details>

<summary><strong>Real-world examples</strong></summary>

* Staff badge: employee name + role + QR for door access.
* Warranty card: product serial number + purchase date + support link.
* Click & collect: pickup credential with order ID + barcode for retrieval.

</details>

More details: [Design > Generic](https://docs.thewalletcrew.io/design/generic).

## FAQ

<details>

<summary><strong>Do customers need a mobile app to add a pass?</strong></summary>

No. Customers can add a pass from a Brand website or email. QR codes also work in-store or on-site. If a mobile app exists, an in-app flow can be added later.

</details>

<details>

<summary><strong>Do passes work offline?</strong></summary>

Usually yes for the moment of use. The barcode/QR and the visible fields are stored on the phone. Updates still require connectivity at some point to sync.

</details>

<details>

<summary><strong>What’s the difference between an Offer and a Gift card?</strong></summary>

Offers are for discounts and coupons. Gift cards are for stored value and balance updates. If the value can go down over time, it is almost always a Gift card.

</details>

<details>

<summary><strong>Can a pass be updated after it’s installed?</strong></summary>

Yes. This is one of the main advantages of mobile wallets. The Wallet Crew updates the same installed pass, so customers don’t need to re-add it.

</details>

<details>

<summary><strong>Can multiple pass types be used in one project?</strong></summary>

Yes. Many Brands start with one pass type (often loyalty) and add others later. Pass types can share the same distribution channels and operational setup.

</details>
