> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/google-tab.md).

# Google tab

Configure how passes of a template look and behave in Google Wallet: class, barcode, security, colors, images, layout, links, Smart Tap and messages.

The Google tab defines everything Google Wallet renders for passes of the template. Google Wallet organizes passes in classes, each with its own required information and its own layout, so part of the tab is common to every type and part depends on the type of the template. The type decides the Google Wallet class; the mapping is in [Settings by type](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration.md#settings-by-type).

<figure><img src="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2Fgit-blob-0fbcc84ba67bc22e725c35cb39b0cfe0dd0e4c21%2Ftemplate-editor-google-tab-retake.png?alt=media" alt="Google tab of a stamp card template with its sections and the Google Wallet preview of the loyalty pass"><figcaption><p>The Google tab, with its sections on the left and the Google Wallet preview on the right.</p></figcaption></figure>

## Settings common to every type

### General

**State** sets the state of the pass in Google Wallet: Active, Completed, Expired or Inactive. Expired, Inactive and Completed passes go straight to the holder's archived passes: they leave the Passes list and the home screen. The General section also holds the main texts of each kind (see [Settings by type](#settings-by-type)).

Dynamic values, for example `{{ firstName }}`, go in dedicated dynamic fields. Label fields are for static text only.

### Barcode

The barcode is what a scanner reads. The section sets its **type**, its **value**, usually an identifier of the pass (an empty value means no barcode), and an **alternate text** shown under it; without alternate text, Google shows the member ID or card number, else the barcode value.

Supported types are AZTEC, CODE\_39, CODE\_128, CODABAR, DATA\_MATRIX, EAN\_8, EAN\_13, ITF\_14, PDF\_417, QR\_CODE, UPC\_A and TEXT\_ONLY. TEXT\_ONLY shows the value as text without a barcode, and cannot have an alternate text.

A **Rotating barcode** makes Google Wallet recompute the code at regular intervals from a one-time password, so that a screenshot of it goes stale. It works with QR codes and PDF417 only, its value must contain `{totp_value_0}`, and rotating barcodes must first be set up for the tenant in **Settings → Wallet → Google**, on the **Rotating barcode** tab.

When the barcode value is used to find the pass with Pass Scanner, turn on [Persist scannable data](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/general-tab.md#scannable-data) on the General tab.

### Security

Security settings limit how the pass can be shared or copied, which matters for tickets and valuable passes:

* **Multiple devices and holders**: Multiple holders (the pass can be shared), One user all devices, or One user one device. With One user one device, the pass can only be added from the Google Wallet app on an Android phone, not from the web.
* **Security animation**: Google draws an iridescent frame around the barcode that shifts as the phone moves, so a photo or copy is easy to tell apart.
* **View unlock requirement**: when Required, the phone must be unlocked each time the pass opens, and the pass can only be added from the Google Wallet app on Android, not from the web.
* **Screenshots**: Allowed or Blocked. When blocked, screenshots of the open pass come out black; older versions of Google Wallet may still allow them.

### Colors and images

**Background color** applies to the pass. When it is not set, Google uses the dominant color of the banner, or of the logo when there is no banner.

**Images** depend on the type: a **Banner** (hero image) shown at full width on the front, and the logos of the class: **Logo** and **Wide logo** (Event ticket, Generic), **Program logo** and **Wide program logo** (Customer card, Stamp card, Gift card), **Title image** and **Wide title image** (Offer). A wide logo replaces the logo at the top left of the pass, and needs the logo too.

### Texts

Texts add information shown in the details of the pass, after the messages. Each text has a **Header** (under 35 characters) and a **Body** (under 500 characters; an empty body hides the text). A text used by the layout cannot be deleted until it is removed from the layout.

### Layout

Google Wallet decides by default which information appears where. The **Layout** section changes this, zone by zone:

* **Card rows** (front of the card): up to 3 rows under the card title, each with 1 to 3 values;
* **Barcode details** (around the barcode): up to 3 short values, two above the barcode and one below, without labels;
* **Details list** (back of the card): the list of details, in the chosen order;
* **Passes list** (Wallet home screen): two rows describing the pass in the holder's list of passes.

Each zone is either **Google default** or **Customised**. A value that is empty on a pass is hidden, and fallbacks can be added for passes where a field is empty. A layout can be copied and pasted into another template (**Copy layout**, **Paste layout**), edited as **JSON**, and each zone can go back to Google's layout with **Back to Google's default**.

<figure><img src="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2Fgit-blob-9afedcfeb15ac4c061bfdefa878a58a3ba99d517%2Ftemplate-editor-google-layout-retake.png?alt=media" alt="Layout section of the Google tab with the four zones Card rows, Barcode details, Details list and Passes list, and the Card rows zone open"><figcaption><p>The Layout section: the four zones, with the Card rows editor open.</p></figcaption></figure>

### Other common sections

* **Additional links**: links shown in the details of the pass.
* **Smart Tap**: lets NFC readers read the pass. It requires Smart Tap to be set up for the tenant; **NFC while the pass is open** can stop the phone from also handing out a payment or closed-loop transit card on the same tap.
* **Valid time interval**: start and end of validity of the pass.
* **Messages**: each message has a header and a text, shown in the details. With a **Display period** or **Notify on update**, a message becomes a new-message banner on the pass; Notify on update also sends a notification to the holder when the message is added or changed. For most cases, an automation with a notification is preferable.
* **App links**: links to the brand's apps.
* **Locations**: places near which Google notifies the holder; they are not drawn on the pass.
* **Value-added opportunities**: modules with a header, a short text, a link and a logo, each shown during its own display period.
* **Image in the details**: an image shown at full width in the details, with a description read by screen readers.
* **Grouping**: passes with the same group are stacked together in Google Wallet, for example the tickets of one order.

## Settings by type

### Customer card and Stamp card (Loyalty)

**Issuer**, **Program name**, **Loyalty points** and **Rewards** (a second balance), **Rewards tier** and **Secondary rewards tier**, **Account** (name and identifier), **Homepage**. The account is optional, and a dynamic value cannot be used on its label field. A **Program logo** is required: Google refuses the template without it, unless the pass's theme provides one.

Stamp card templates also have **Stamp images**: one **Google hero** per stamp count. The rules for the images, and how to show the count as text with the stamp variables, are on the [Stamp card](https://docs.thewalletcrew.io/guides-design/design/stamp-card.md) page.

### Event ticket

**Issuer**, **Event name**, **Event ID**, **Ticket holder name**, **Ticket number**, **Ticket type**, event dates (**Start date**, **End date**, **Doors open** with its label: Doors open, Gates open or a custom label), **Fine print**, **Venue**, **Placements** (gate, section, row, seat), **Confirmation code**, **Face value**, **Homepage**.

### Gift card

**Issuer**, **Merchant name**, **Card number** (required by Google; shown under the barcode when there is no alternate text), **Event number**, **Balance and PIN**, **Barcode redemption accepted** (tells Google the merchant accepts the gift card by barcode; nothing changes on the pass), **Homepage**.

### Offer

**Title** and **Short title**, **Issuer**, **Provider**, **Details**, **Redemption channel** (Unspecified, In store, Online, Both, or Temporary price reduction; every value renders the same on the pass), **Fine print**, **Help** link, **Homepage**.

### Generic

**Title**, **Header**, **Subheader**, **Expiry notification** (sent 48 hours before the end of the valid time interval, which must be set) and **Upcoming notification** (sent 24 hours before its start). When both notifications are on, only the expiry notification is sent.

## FAQ

<details>

<summary><strong>Why does the pass appear in the archived passes?</strong></summary>

Because its **State** is Expired, Inactive or Completed. Google Wallet sends passes in these states straight to the holder's archived passes, so they leave the Passes list and the home screen.

</details>

<details>

<summary><strong>Why is a gift card refused by Google Wallet?</strong></summary>

Google Wallet requires a card number on every gift card. Fill the **Card number** field in the General section; the preview reports it as Blocking ("Google Wallet will refuse this pass") when it is empty.

</details>

<details>

<summary><strong>Why does the loyalty pass show a blocking check about the logo?</strong></summary>

A loyalty pass (customer card or stamp card) needs a program logo. Add it in the Images section, or apply a theme that provides one.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/google-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
