38.1 Overview

The Google Wallet feature allows the account owner to create digital passes that recipients can save to their Google Wallet accounts.

The installed Google Wallet integration supports several pass formats, including:

The generator provides a real-time pass preview, type-specific content fields, optional text modules, links, images, and a generated Google Wallet link that can be copied and distributed. The add-on’s published interface shows the five pass types above and a pass list containing Type, Link, and Created At information.

38.2 What a Google Wallet Pass Is

A Google Wallet pass is a digital item saved inside a customer’s Google Wallet.

Depending on the selected type, it can represent:

1. A boarding pass
2. An event ticket
3. A gift card
4. A loyalty or membership card
5. A general business or identification pass
6. A reservation or confirmation
7. A digital business-card experience

Google Wallet defines specialized pass types for common uses and provides a flexible Generic pass for uses that do not fit the specialized categories.

38.3 Google Wallet Pass Versus a Payment Card

The Google Wallet generator does not create a customer’s credit card, debit card, or bank account.

A pass can display information such as:

It should not be used to collect or expose:

38.4 Google Wallet Versus the VCard Contact Download

The system contains two different digital-card functions.

VCard Contact Download

Creates a .vcf file that imports contact information into a device’s Contacts application.

Google Wallet Pass

Creates an Add to Google Wallet link that allows the recipient to save a visual digital pass in Google Wallet.

A Google Wallet pass does not automatically import the cardholder into the recipient’s telephone contacts.

A VCF contact does not automatically create a Google Wallet pass.

38.5 Google Wallet Versus NFC Cards

Google Wallet and physical NFC Cards are also separate.

Google Wallet

A digital pass saved through the recipient’s Google account.

NFC Card

A physical card or device that can open a programmed digital destination when tapped.

An NFC Card may be used to open a Google Wallet pass link, but creating one does not automatically create the other.

Accessing Google Wallet

38.6 Opening Google Wallet

To open the feature:

1. Sign in to the customer dashboard.
2. Locate Google Wallet in the main menu.
3. Select it.
4. Wait for the Google Wallet pass list to load.

The main customer menu points Google Wallet to the google-wallet.index destination when the Google Wallet module is installed and active. The menu is programmed in the primary account-owner context rather than the organization subuser context.

38.7 Google Wallet Menu Is Missing

The menu may not appear when:

1. The Google Wallet add-on is not installed.
2. The add-on is disabled.
3. The user is signed in through an organization subaccount.
4. The page has not refreshed since the module was activated.
5. The browser session is outdated.
6. The installation is incomplete.

Sign out and sign back in after the administrator confirms that the Google Wallet module is active.

38.8 Account Owner Access

The installed menu logic displays Google Wallet for the main customer account when the module exists.

An organization employee or subuser should not automatically expect to see the same menu.

The primary account owner should control pass creation unless another access workflow has been specifically implemented.

Understanding the Google Wallet Pass List

38.9 Pass-Management Screen

The Google Wallet page contains:

The published interface screenshot shows a searchable pass list with an Add Google Wallet button and rows for Flight, GiftCard, Loyalty, Generic, and EventTicket passes.

38.10 Type Column

The Type column identifies which Google Wallet pass format was generated.

Examples:

Use the Type to distinguish passes that may otherwise have similar links or creation dates.

38.11 Link Column

The Link column contains the generated Google Wallet save destination.

A Google Wallet save link normally follows this structure:

Google identifies this as an Add to Google Wallet link containing an encoded and signed JSON Web Token. The link can be distributed through websites, email, messaging, or other places that support hyperlinks.

38.12 Copy-Link Action

A copy icon appears beside each generated Link.

To copy a pass link:

1. Locate the correct pass.
2. Confirm its Type.
3. Review its Created At date.
4. Select the copy icon.
5. Wait for the copy confirmation where provided.
6. Paste the link into a temporary internal document.
7. Confirm that the complete link was copied.
8. Test it before distributing it.

Do not manually highlight part of the link when the copy action is available.

38.13 Created At Column

The Created At column identifies when the pass link was generated.

Use it to:

1. Distinguish old and new versions
2. Identify a corrected replacement
3. Locate a campaign pass
4. Remove outdated links from marketing materials
5. Confirm when testing was completed

A later creation date does not automatically mean the later pass is correct. Test the actual content.

38.14 Searching Passes

Use Search to narrow the list by information supported by the table, such as pass Type or another indexed value.

Examples:

When Search returns no results:

1. Clear the Search field.
2. Confirm spelling.
3. Refresh the page.
4. Review another page of results.
5. Confirm that the pass was successfully generated.

38.15 Sorting

Where a sortable column indicator appears, select the column heading to change the order.

The published pass list shows sorting controls for Type and Created At.

Sorting is useful when several passes have similar Types.

38.16 Results Per Page

Use the results control at the bottom of the list to change how many pass records appear on one page.

When the required pass is not visible:

1. Increase the results count.
2. Use Search.
3. Open the next page.
4. Sort by Created At.

Planning a Google Wallet Pass

38.17 Information to Prepare

Before creating a pass, prepare:

Type-specific passes can require additional information.

38.18 Choose the Correct Pass Type First

The selected Type determines which content fields appear and how Google Wallet presents the pass.

Changing the Type can change:

1. Required fields
2. Pass layout
3. Preview
4. Date fields
5. Identification fields
6. Product or event information
7. Travel information

Do not select a Type only because its preview looks attractive.

Use the Type that most accurately represents the pass’s purpose.

38.19 Use Accurate Issuer Information

The Issuer Name identifies the organization providing the pass.

Examples:

Use the approved public business or program name.

Do not use:

1. An employee’s private note
2. A temporary test name
3. Another organization’s trademark without authorization
4. A misleading airline, event, or merchant identity

38.20 Plan the Pass Distribution

Determine how recipients will receive the link.

Possible channels include:

The distribution method should match the intended audience and privacy level.

Creating a New Google Wallet Pass

38.21 Opening the Generator

To create a pass:

1. Open Google Wallet.
2. Select Add Google Wallet.
3. Wait for Generate Wallet Business Card to open.
4. Select the Google Wallet Card Type.
5. Complete the required Contents.
6. Add optional Module Data.
7. Review the real-time preview.
8. Select Generate.
9. Confirm that the new pass appears in the list.
10. Copy and test its Link.

The published generator is titled Generate Wallet Business Card and contains a Type selector, Contents panel, central Google preview, Module Data panel, and Generate button.

38.22 Generator Layout

The generator is divided into three principal areas.

Contents

Contains the main required and optional fields for the selected pass Type.

Preview

Displays a visual representation of the Google Wallet pass as information is entered.

Module Data

Provides additional text, links, and images that can be attached to the pass.

38.23 Selecting the Google Wallet Card

At the top of the generator, open the google wallet card selector.

Choose:

The fields below change according to the selected Type.

Review the form again after changing the Type because information entered under one Type may not apply to another.

38.24 Required Fields

Required fields are marked with an asterisk.

A pass cannot be expected to generate successfully until every required field for the selected Type is completed.

When Generate fails:

1. Return to the top.
2. Review each required field.
3. Check dates and times.
4. Check image URLs.
5. Check web links.
6. Correct the highlighted information.
7. Select Generate again.

Selecting the Appropriate Pass Type

38.25 Flight Pass

Use Flight for airline or boarding-pass information.

The visible Flight generator fields include:

Additional flight-related fields can appear farther down the form. The real-time preview presents route, terminal or gate, departure information, flight number, and scheduled departure information.

38.26 When to Use Flight

Suitable uses include:

1. Airline-issued boarding passes
2. Authorized flight confirmations
3. Travel-program testing
4. Airline demonstration data

Do not use the Flight Type to create a false boarding pass or to misrepresent travel authorization.

A business travel itinerary that is not an actual airline pass may be better represented by a Generic pass.

38.27 Flight Issuer Name

Enter the airline, travel authority, or authorized issuer.

Example:

Do not enter a travel agent’s name as though it were the airline unless the business is authorized to issue the pass in that form.

38.28 Review Status

The Flight form includes a Review Status selector, with Draft visible in the published interface.

Use the available status according to the organization’s actual Google Wallet publishing workflow.

A pass in a draft, test, or review state should not be described to customers as a fully published production boarding pass.

38.29 Departure Date and Time

Enter the correct scheduled departure date and time.

Confirm:

1. Date
2. Time
3. Time zone
4. Flight schedule
5. Passenger communication
6. Whether the time is local to the departure airport

An incorrect departure time can make the pass operationally unsafe.

38.30 Carrier IATA Code

The Carrier IATA Code identifies the airline through its recognized airline code.

Use the actual code associated with the carrier.

Do not invent a code for a nonairline business.

38.31 Flight Number

Enter the correct flight number.

Review it against the airline or authorized travel record before generating the pass.

A visually correct preview does not independently validate the flight.

Event Ticket Passes

38.32 EventTicket Pass

Use EventTicket for admission or attendance information related to an event.

The visible EventTicket generator includes:

The generator also supports optional Module Data on the right side.

38.33 Suitable EventTicket Uses

Examples include:

1. Conferences
2. Workshops
3. Concerts
4. School events
5. Business expos
6. Training programs
7. Fundraisers
8. Private events
9. Sporting events

The pass should accurately state whether it is:

1. An actual admission ticket
2. A registration confirmation
3. An invitation
4. An information pass

Do not describe a confirmation as guaranteed admission when additional approval is required.

38.34 Event Name

Enter the official public Event Name.

Example:

Avoid internal names such as:

38.35 Hero Image

The Hero Image field accepts an image destination.

The visible placeholder uses a web URL format:

Use a publicly reachable HTTPS image where possible.

The image should:

1. Belong to the event
2. Be approved for use
3. Remain available
4. Have an appropriate aspect ratio
5. Avoid confidential information
6. Load without requiring a login

38.36 Event Content Description

The Content Description should explain the Hero Image or important event content.

Keep it clear and accurate.

Example:

Do not paste a complete legal policy into an image-description field.

38.37 Event Information Accuracy

Before distributing an EventTicket pass, verify:

Do not assume the pass generator checks the event organizer’s external system.

Gift Card Passes

38.38 GiftCard Pass

Use GiftCard when the pass represents stored value or a business-issued gift card.

A GiftCard pass may be appropriate for:

1. Retail gift credit
2. Service credit
3. Promotional gift value
4. Customer reward
5. Prepaid business package

Google Wallet provides a specialized Gift Card pass type rather than requiring these uses to be created as Generic passes.

38.39 Gift-Card Information to Prepare

Prepare information such as:

Complete only the fields displayed by the installed generator.

38.40 Gift-Card Balance

The displayed balance must agree with the business’s source-of-truth system.

The Google Wallet pass should not be treated as the only financial record.

Maintain balances through the approved:

1. Point-of-sale system
2. Accounting system
3. Gift-card system
4. Customer ledger
5. Redemption database

38.41 Gift-Card Security

Do not expose an easily reusable redemption code in a publicly shared pass link.

A pass containing transferable stored value should be distributed only to the intended recipient through an approved process.

38.42 Gift-Card Terms

Explain:

1. Where the card can be used
2. What it can purchase
3. Whether it expires
4. Whether it can be transferred
5. Whether cash redemption is permitted
6. What happens when it is lost
7. How balances are verified
8. Applicable restrictions

The pass should not contradict the business’s published gift-card policy.

Loyalty Passes

38.43 Loyalty Pass

Use Loyalty for a customer membership, rewards, or loyalty-program card.

Suitable uses include:

Google Wallet provides a dedicated Loyalty pass type for these programs.

38.44 Loyalty Information to Prepare

Prepare:

Use the actual fields displayed after selecting Loyalty.

38.45 Membership Identifier

Do not use sensitive identifiers such as:

1. Social Security number
2. Banking account number
3. Password
4. Full payment-card number
5. Medical record number

Use a dedicated loyalty or membership ID.

38.46 Loyalty Points

When displaying points or rewards, confirm that the pass agrees with the approved loyalty system.

Do not promise that editing the pass alone changes the member’s actual points balance.

38.47 Loyalty Program Terms

Explain:

1. How points are earned
2. How points are redeemed
3. Whether points expire
4. Whether rewards can be transferred
5. Which Products or services qualify
6. How account errors are corrected
7. How the customer can contact support

Generic Passes

38.48 Generic Pass

Use Generic when the pass’s purpose does not fit Flight, GiftCard, Loyalty, or EventTicket.

Google describes Generic passes as flexible passes for uses such as membership cards, parking passes, library cards, insurance cards, reservation confirmations, and other custom use cases.

38.49 Generic Business-Card Use

A Generic pass can be used to create a wallet-based business-card experience.

Possible content includes:

The exact available fields depend on the installed generator.

38.50 Generic Membership Use

Generic passes may also be suitable for:

1. Organization membership
2. Student program access
3. Training-program confirmation
4. Volunteer identification
5. Conference registration confirmation
6. Service-plan identification
7. Parking authorization

Do not use the pass as official government identification unless the organization is authorized and the use complies with applicable requirements.

38.51 Sensitive Information

Google provides separate controls and review requirements for Generic Private passes involving sensitive information.

The ordinary customer generator should not be used to place confidential health, financial, government, or identity data into a public or easily transferable pass.

Contents Panel

38.52 Type-Specific Contents

The Contents panel changes when the Google Wallet Card Type changes.

Examples visible in the published interface include:

EventTicket

Flight

38.53 Complete Required Contents First

A recommended workflow is:

1. Select the Type.
2. Complete required Contents.
3. Review the central preview.
4. Correct formatting.
5. Add Module Data.
6. Review the preview again.
7. Generate.

Entering optional Module Data before the required Contents can make troubleshooting harder.

38.54 Image URLs

Where an image field requests a URL, use a complete public web destination.

Recommended:

Avoid:

The Google Wallet service must be able to access the image.

38.55 HTTPS Images

Use HTTPS image destinations where possible.

Confirm that:

1. The certificate is valid.
2. The image opens directly.
3. No login is required.
4. The link does not expire shortly.
5. Hotlink protection does not block Google.
6. The file is an actual image.

38.56 Date and Time Fields

When the selected Type contains date fields:

1. Confirm the calendar date.
2. Confirm the displayed time.
3. Confirm AM or PM where applicable.
4. Confirm time zone expectations.
5. Compare with the official event or travel record.
6. Review the preview.

Do not rely on the preview to correct an incorrectly entered time.

Real-Time Preview

38.57 Purpose of the Preview

The center panel displays a Google-branded visual preview of the pass.

The add-on’s published description specifically identifies real-time previews as part of the pass-creation experience.

Use the preview to evaluate:

1. Text placement
2. Main title
3. Image
4. Route or event information
5. Length of values
6. General visual balance

38.58 Preview Is Not Final Validation

The preview does not prove that:

1. The pass will generate successfully.
2. Google will accept every field.
3. The image URL is permanently available.
4. The event information is accurate.
5. The flight is valid.
6. The gift-card balance exists.
7. The customer can redeem the pass.
8. The pass is approved for production.

Complete an actual save test.

38.59 Long Text in the Preview

When text is cut off or difficult to read:

1. Shorten the title.
2. Shorten the issuer name.
3. Move supporting information into Module Data.
4. Use concise descriptions.
5. Avoid repeating the same information.

Do not reduce clarity merely to make text fit.

38.60 Preview Does Not Update

When the preview remains unchanged:

1. Click outside the field.
2. Confirm that the correct Type is selected.
3. Review validation errors.
4. Refresh the page if information has not been saved.
5. Try another browser.
6. Remove browser extensions that interfere with scripts.
7. Reenter one field and test again.

Do not select Generate repeatedly while the page appears unresponsive.

Module Data

38.61 Module Data Overview

The right side of the generator contains:

The visible fields include:

Text Modules Data

38.62 Header

The Text Module Header acts as a short label or title.

Examples:

Keep the Header concise.

38.63 Body

The Body contains the information related to the Header.

Example:

Do not place extremely long policy text in one module.

38.64 Suitable Text Modules

Useful examples include:

38.65 Avoid Sensitive Text

Do not place:

inside a normal pass module.

Links Modules Data

38.66 URI

The URI field stores the web destination.

Examples:

Use only link types supported by the generator and Google Wallet.

38.67 Link Description

The Description explains the purpose of the link.

Examples:

Do not use vague labels such as:

when a clearer description is possible.

38.68 Linking to a VCard

A useful business-card pass can link to the account owner’s public VCard.

Recommended procedure:

1. Open the public VCard.
2. Confirm that it is active.
3. Copy its complete URL.
4. Paste it into the Module URI.
5. Enter Open Digital Business Card as the Description.
6. Generate the pass.
7. Save it to a test Google Wallet.
8. Open the link from the saved pass.

Google Wallet supports links within pass module data that can direct recipients to a related website or application experience.

38.69 Link Security

Do not add a link containing:

1. Administrator login tokens
2. Private file credentials
3. Password reset token
4. Private payment key
5. One-time authentication secret
6. Unprotected customer document

A recipient may be able to share or inspect the pass.

Image Modules Data

38.70 Image URI

Enter the complete public location of the image.

Example:

The link must remain accessible after the pass is distributed.

38.71 Content Description

The Content Description explains the image.

Example:

or:

Use a description that identifies the image’s purpose.

38.72 Suitable Module Images

Examples include:

1. Company logo
2. Event map
3. Product image
4. Venue image
5. Membership artwork
6. Program banner
7. Approved profile image

Do not use:

1. Copyrighted images without authorization
2. Customer photographs without permission
3. Confidential documents
4. Screenshots containing private data
5. Images that contradict the pass information

Generating the Pass

38.73 Final Review Before Generate

Before selecting Generate, confirm:

38.74 Selecting Generate

After reviewing the pass:

1. Select Generate.
2. Wait for processing.
3. Do not select the button repeatedly.
4. Review any validation message.
5. Return to the pass list after success.
6. Locate the new record.
7. Confirm Type and Created At.
8. Copy the Link.
9. Complete a real save test.

38.75 Successful Generation

A successful pass should appear in the Google Wallet list with:

The published list interface does not show ordinary Edit or Delete columns for generated passes. It primarily presents the Type, save Link, and creation date.

38.76 No Ordinary Edit Action

When an error is discovered after generation, the visible workflow should not be assumed to provide ordinary editing.

A safe correction process is:

1. Identify the incorrect pass.
2. Record its creation date.
3. Create a new corrected pass.
4. Test the new Link.
5. Stop distributing the old Link.
6. Replace it in websites, messages, QR codes, and VCards.
7. Clearly identify the replacement internally.

Do not assume that creating a new pass automatically removes the old pass from recipients’ wallets.

38.77 No Ordinary Delete Action

The published customer list does not display a standard Delete action.

Do not attempt to remove a pass through direct database changes.

When an obsolete generated record must be revoked or removed from the platform, contact the platform administrator and provide:

Saving the Pass to Google Wallet

38.78 Testing the Generated Link

To test:

1. Copy the generated Link.
2. Open it in a supported browser or device.
3. Sign in to the intended Google account.
4. Review the pass preview shown by Google.
5. Select Add to Google Wallet.
6. Open Google Wallet.
7. Locate the saved pass.
8. Review all visible information.
9. Test its links.
10. Test images.
11. Confirm dates and times.

Google states that saving through an Add to Google Wallet link occurs in the context of a signed-in Google identity.

38.79 Google Account Requirement

The recipient may be asked to sign in to a Google account before saving.

The business should not request the recipient’s Google password.

Google authentication occurs through Google’s own interface.

38.80 Test Account Versus Recipient Account

Do not complete the only test using the account that configured the integration.

Also test with an authorized ordinary recipient account.

This can reveal:

1. Demo-mode restrictions
2. Publishing-access problems
3. Account permission issues
4. Image-access problems
5. Link-distribution problems

38.81 Test-Only Passes

When the Google Wallet issuer account is still in Demo Mode, passes may display [TEST ONLY] and may be limited to administrator, developer, or specifically added test accounts. Publishing access is required before general public issuance.

When a recipient cannot save a test pass, the platform administrator should review the Google Wallet issuer configuration.

Distributing a Google Wallet Link

38.82 Distribution Methods

The generated Link can be distributed through approved channels such as:

Google Wallet save links are designed for use anywhere normal hyperlinks can be delivered, including web pages, email, chat, and SMS.

38.83 Email Distribution

When sending by email:

1. Confirm the intended recipient.
2. Use a clear subject.
3. Explain what the pass represents.
4. Insert the Link behind descriptive text.
5. Explain that a Google account may be required.
6. Include a support contact.
7. Avoid exposing links for sensitive individual passes to multiple recipients.

Example:

Select “Add Your Event Pass to Google Wallet” to review and save the pass.

38.84 WhatsApp Distribution

When sending through WhatsApp:

1. Confirm the customer conversation.
2. Explain the pass purpose.
3. Paste the complete Link.
4. Ask the recipient to verify the issuer and pass details.
5. Avoid sending a private pass into a group.
6. Retain the communication according to policy.

38.85 Website Distribution

For a public general pass:

1. Add a clearly labeled button.
2. Use the generated Link as the destination.
3. Test desktop and mobile.
4. Confirm the Link opens Google.
5. Replace the Link when the pass is recreated.

For individual tickets, balances, or memberships, do not place the same private link on a public webpage.

38.86 VCard Custom Link

A Google Wallet Link can be added as a VCard Custom Link when appropriate.

Suggested label:

or:

After adding it:

1. Preview the public VCard.
2. Select the Custom Link.
3. Save the pass.
4. Confirm that the link opens in a new tab where configured.
5. Test on a phone.

38.87 QR-Code Distribution

A QR code can direct a recipient to the generated Google Wallet Link.

Before printing:

1. Create the QR code using an approved tool.
2. Scan it from more than one device.
3. Confirm the correct pass.
4. Confirm the correct issuer.
5. Confirm the correct Type.
6. Retain the source Link.
7. Avoid regenerating the pass after printing unless the QR destination can be updated.

A static QR code pointing to an obsolete pass link can be difficult to correct after distribution.

Business-Card Pass Workflow

38.88 Recommended Generic Business-Card Pass

A practical business-card workflow is:

1. Select Generic.
2. Enter the approved Issuer Name.
3. Enter the cardholder or business title in the available main field.
4. Add an approved logo or profile image.
5. Add a Text Module for telephone or contact instructions.
6. Add a Link Module pointing to the public VCard.
7. Add another Link Module for appointments where appropriate.
8. Review the preview.
9. Generate.
10. Save to a test Google Wallet.
11. Add the generated Link to the public VCard or QR campaign.

38.89 Keep Contact Details Current

A generated wallet pass can contain information that later becomes outdated.

Review it after changes to:

When the installed customer interface does not provide pass editing, create and distribute a corrected replacement.

38.90 Link to the Current VCard

A useful strategy is to keep permanent detailed information on the public VCard and use the wallet pass to link to it.

This reduces the amount of information that must be repeated inside the pass.

The recipient can open the current online VCard even when some visible pass text is older.

Event-Pass Workflow

38.91 Recommended EventTicket Process

1. Confirm event approval.
2. Select EventTicket.
3. Enter the official Issuer Name.
4. Enter the official Event Name.
5. Add the approved Hero Image URL.
6. Add the image Content Description.
7. Complete all additional event fields displayed.
8. Add a Link Module for the event page.
9. Add a Link Module for directions.
10. Add important instructions through Text Modules.
11. Review the preview.
12. Generate.
13. Save to a test Wallet.
14. Confirm dates, venue, and links.
15. Distribute through the approved registration process.

38.92 Event-Ticket Privacy

When a pass is unique to a ticket holder:

1. Do not publish its Link publicly.
2. Do not post it in a social group.
3. Do not reuse the same private ticket for several people.
4. Do not expose a barcode or admission code unnecessarily.
5. Verify the recipient before resending.

Gift-Card Workflow

38.93 Recommended GiftCard Process

1. Confirm that the gift-card value exists.
2. Confirm the intended recipient.
3. Select GiftCard.
4. Enter the approved issuer and card information.
5. Confirm the balance and currency.
6. Enter redemption information.
7. Add Terms through a suitable module or linked policy.
8. Generate.
9. Test the pass.
10. Deliver the Link privately.
11. Record issuance in the financial system.

38.94 Gift-Card Source of Truth

The Google Wallet pass should display or reference the value, but the actual balance should remain controlled by the approved financial or gift-card system.

Do not manually promise a balance based only on the visual pass.

Loyalty-Pass Workflow

38.95 Recommended Loyalty Process

1. Confirm the customer’s membership.
2. Select Loyalty.
3. Enter the approved issuer and program name.
4. Enter the membership identifier.
5. Enter points or status only when accurate.
6. Add a support or program Link.
7. Add relevant terms.
8. Review the preview.
9. Generate.
10. Test using an authorized Google account.
11. Deliver the Link privately.

38.96 Loyalty Data Reconciliation

Periodically compare the pass information with:

1. CRM
2. Loyalty database
3. Purchase records
4. Customer account
5. Rewards ledger

Do not allow the visual pass and the actual loyalty record to remain inconsistent.

Privacy and Security

38.97 Treat Pass Links as Shareable

A generated Google Wallet Link can be copied and forwarded.

Do not assume that only the original recipient can ever see it.

Use caution when the pass contains:

38.98 Avoid Highly Sensitive Information

Do not place highly sensitive personal information in an ordinary pass.

Examples include:

1. Government identification number
2. Social Security number
3. Full date of birth unless necessary and authorized
4. Health diagnosis
5. Complete banking information
6. Password
7. Security answer
8. Private access credential

38.99 Service-Account Credentials

Google Wallet integrations use service-account credentials to authenticate pass generation, and Google identifies the service-account key as highly sensitive. These credentials must remain private and should be managed by the platform administrator, not entered into customer-facing pass fields.

Never paste a Google service-account JSON key into:

1. Issuer Name
2. Text Module
3. Link Module
4. Image URL
5. VCard Custom Link
6. Email
7. Support message

38.100 Privacy Policy

The business Privacy Policy should accurately explain Google Wallet pass use where personal information is included.

It may need to address:

1. Information placed on the pass
2. Purpose of the pass
3. Google’s role
4. Links to external services
5. Data retention
6. Pass distribution
7. Customer support
8. Revocation or replacement
9. Sharing risks

Managing Generated Passes

38.101 Internal Pass Register

Maintain an internal register containing:

Do not place a full sensitive Link in an unrestricted spreadsheet.

38.102 Pass Status Terminology

Because the customer list does not display a general Active or Inactive switch, maintain an internal status such as:

This is an internal operational classification, not necessarily a programmed Google Wallet field.

38.103 Retiring a Pass

When a pass is no longer current:

1. Stop distributing its Link.
2. Remove the Link from VCards and websites.
3. Replace QR-code destinations where possible.
4. Notify affected recipients when necessary.
5. Create a corrected pass where appropriate.
6. Mark the old pass as Retired internally.
7. Contact the platform administrator when revocation is required.

38.104 Correcting a Pass

When information is wrong:

1. Do not continue distributing it.
2. Record the incorrect pass’s Type and date.
3. Create a corrected version.
4. Test the replacement.
5. update all distribution channels.
6. Notify previous recipients.
7. Explain whether they should remove the old pass.
8. Retain an authorized correction record.

Troubleshooting

38.105 Google Wallet Page Does Not Open

Confirm that:

1. The account is signed in.
2. The main account owner is being used.
3. The Google Wallet module is active.
4. The browser session has not expired.
5. The page was refreshed.
6. The URL remains under the customer dashboard.
7. Browser extensions are not blocking scripts.

38.106 Add Google Wallet Button Is Missing

Confirm that:

1. The pass list loaded completely.
2. The browser window is wide enough.
3. The button is not above the visible table.
4. The module is fully installed.
5. The account has access to the generator.
6. The browser cache was refreshed.

38.107 Pass Type Selector Is Empty

Possible causes include:

1. Module files are incomplete.
2. JavaScript did not load.
3. The installation version is incompatible.
4. The browser session is stale.
5. A server error prevented pass definitions from loading.

Refresh once and try another browser before reporting the issue.

38.108 Required Field Error

Return to the Contents panel and review every field marked with an asterisk.

Common causes include:

1. Missing Issuer Name
2. Missing title or Event Name
3. Missing date
4. Missing code
5. Missing image URL
6. Invalid URL
7. Invalid date format
8. Incomplete type-specific information

38.109 Image Does Not Appear in the Preview

Confirm that:

1. The URL is complete.
2. HTTPS is used where possible.
3. The image opens directly.
4. No login is required.
5. The file is an image.
6. The server allows external access.
7. The image has not been removed.
8. The URL does not expire immediately.

38.110 Image Appears in the Browser but Not in the Pass

The image host may block Google or external embedding.

Try:

1. Using an approved public media host.
2. Removing hotlink restrictions.
3. Using a direct image URL.
4. Confirming the content type.
5. Retesting after cache expiration.

38.111 Preview Is Blank

Confirm that:

1. A pass Type is selected.
2. Required fields contain information.
3. JavaScript is enabled.
4. The browser loaded the page fully.
5. No browser extension blocked scripts.
6. The page is not displaying an old session.
7. Another browser can load the preview.

38.112 Generate Does Nothing

1. Wait for image loading to complete.
2. Review required fields.
3. Scroll to the top for validation messages.
4. Confirm the internet connection.
5. Select Generate once.
6. Try another browser.
7. Check whether the pass appears in the list despite the missing message.

38.113 Pass Is Not Added to the List

Confirm that:

1. Generate completed.
2. The list was refreshed.
3. Search is cleared.
4. Another page of results is not open.
5. Sorting did not move the pass.
6. The correct account is open.
7. The module did not return an error.

38.114 Copy Icon Does Not Work

Use this fallback carefully:

1. Open the Link directly.
2. Select the browser address bar.
3. Copy the complete URL.
4. Paste it into an internal test location.
5. Confirm that no characters are missing.

Avoid manually copying only the visible shortened part of a long link.

38.115 Generated Link Opens an Error

Possible causes include:

1. Incomplete copied Link
2. Invalid signed token
3. Google Wallet issuer configuration problem
4. Expired or revoked credential
5. Incorrect pass data
6. Unsupported image or field
7. Demo account restrictions
8. Google account not signed in

Generate a controlled test pass after the administrator confirms the Google Wallet configuration.

38.116 Recipient Cannot Save the Pass

Confirm that the recipient:

1. Opened the complete Link.
2. Is signed in to a Google account.
3. Is using a supported browser or device.
4. Has not blocked the Google page.
5. Is permitted as a test account when the issuer is in Demo Mode.
6. Is viewing the latest corrected Link.

38.117 Pass Displays TEST ONLY

This indicates that the Google Wallet issuer is operating without full publishing access or within a test workflow.

The platform administrator must review:

1. Google Wallet Business Console
2. Issuer status
3. Publishing access
4. Test accounts
5. Service-account access

Do not represent a TEST ONLY pass as a completed production deployment.

38.118 Pass Shows the Wrong Information

Confirm:

1. The correct pass record was opened.
2. The latest Link was copied.
3. The old Link was not reused.
4. The correct Type was selected.
5. The correct Contents were entered.
6. The correct Module Data was used.
7. The recipient did not open an older message.

Create a corrected replacement when no Edit action is available.

38.119 Link Opens the Wrong Pass

Review:

1. Pass Type
2. Created At
3. Internal pass register
4. Email or message used
5. VCard Custom Link
6. QR-code destination
7. Website button
8. Previously copied links

Replace incorrect destinations immediately.

38.120 Flight Preview Is Incorrect

Review:

Compare the pass against the official flight record.

38.121 Event Image Is Incorrect

Open the Hero Image URL directly.

Confirm that:

1. The correct event image appears.
2. The image host did not replace the file.
3. The filename does not point to an older campaign.
4. The image does not contain expired dates.
5. The Content Description matches.

38.122 Gift-Card Balance Is Incorrect

Stop distributing the Link.

Confirm the balance in the business’s actual gift-card system.

Create a corrected pass only after the financial record is accurate.

Do not rely on visual editing to change the real balance.

38.123 Loyalty Points Are Incorrect

Review the approved loyalty database.

Correct the underlying membership record before creating a replacement pass.

Notify the customer when the error affected their benefits.

38.124 Link Module Does Not Open

Confirm that:

1. The URI is complete.
2. HTTPS is used where appropriate.
3. The page is active.
4. The VCard or Store is public.
5. No login is unexpectedly required.
6. The destination was not renamed.
7. The link was tested from the saved pass rather than only from the generator.

38.125 Old Pass Remains in a Recipient’s Wallet

Creating a new pass does not necessarily remove an older pass that the recipient previously saved.

Provide instructions to:

1. Add the corrected pass.
2. Confirm its information.
3. Remove the obsolete pass from Google Wallet where appropriate.
4. Retain only the approved version.

Google Wallet Checklist

38.126 Final Checklist

Before distributing a Google Wallet pass, confirm that:

1. Google Wallet appears in the main account menu.
2. The correct account owner is signed in.
3. The pass purpose is defined.
4. The correct pass Type is selected.
5. Issuer Name is accurate.
6. All required fields are complete.
7. Event or flight information is verified.
8. Gift-card or loyalty information matches its source system.
9. Images are publicly accessible.
10. Images are authorized.
11. Text Module Headers are clear.
12. Text Module Bodies are accurate.
13. Link Module URIs work.
14. Link Descriptions explain their destinations.
15. Image Module descriptions are accurate.
16. No passwords or credentials are included.
17. The real-time preview was reviewed.
18. Generate completed successfully.
19. The pass appears in the list.
20. Type and Created At are correct.
21. The Link was copied completely.
22. The Link was tested with an authorized Google account.
23. The saved pass was reviewed inside Google Wallet.
24. All pass links were tested.
25. Demo or TEST ONLY status was reviewed.
26. The recipient distribution method is appropriate.
27. Private passes are not posted publicly.
28. The pass is recorded in an internal register.
29. Old links are removed after replacement.
30. VCard and website destinations use the latest Link.
31. QR codes were tested before printing.
32. The Privacy Policy addresses personal pass information.
33. Service-account credentials remain private.
34. A correction and retirement process is documented.

Chapter Completion

At the end of this chapter, the user should understand how to open the Google Wallet area, review generated passes, select Flight, GiftCard, Loyalty, Generic, or EventTicket formats, complete type-specific Contents, add Text, Link, and Image Module Data, use the real-time preview, generate and copy an Add to Google Wallet Link, test the pass, distribute it securely, and replace incorrect or obsolete passes.