Surfaces
Google Wallet Config
Digital pass class identity, branding, activation state, and support links.
First created Last updated
Overview
Google Wallet Config controls the shared digital pass identity for an event. It defines the class label, branding, colors, images, homepage link, and support link used when attendee passes are generated.
This surface should match Details. If the event name, artwork, venue, or support link differs between the public event page and wallet pass, attendees may not trust the pass.
Dashboard route
/ems/manage/google-wallet-config?id=:eventId
Inputs and controls
| Input or control | What it changes | Before saving |
|---|---|---|
| Wallet class status | Shows current wallet setup state, issuer ID, and suggested class ID. | Use it to confirm whether the class is still loading, draft, under review, or active. |
| Issuer name | Organization name shown through the wallet pass infrastructure. | Use the event or organizer identity approved for attendee-facing passes. |
| Event name | Label displayed on the pass. | Match the public event name unless there is a clear pass-specific reason. |
| Class ID | Technical identifier for the wallet pass class. | Use the suggested ID unless coordinating a migration. |
| Use suggested ID | Copies the system-suggested class ID into the Class ID field. | Prefer this unless the wallet operator has a specific naming requirement. |
| Activation state | Draft, review, or active readiness state for the pass class. | Do not move toward public use until branding and links are final. |
| Background color | Pass color. | Check contrast against text and images. |
| Logo URL/image | Logo shown on the pass. | Use a clean, recognizable image that works at small sizes. |
| Hero image URL | Larger pass artwork where supported. | Confirm the image loads and is safe for public display. |
| Homepage label | Text for the homepage link. | Use a short label such as Event website. |
| Homepage URL | Link attendees can open from the pass. | Point to the public event page or organizer page. |
| Support label | Text for the support link. | Use clear wording such as Support or Contact organizer. |
| Support URL | Help link shown from the pass. | Use a route that attendees can actually reach. |
| Save controls | Writes the pass class settings. | Save after verifying Details and support links. |
Status card states
| State | What it means | Operator impact |
|---|---|---|
| API credentials not configured | The environment cannot sync with Google yet. | Saving stores the event-specific class config so sync can resume when credentials exist. |
| No saved config | The event has no wallet class config yet. | Set issuer, event name, class ID, and activation state before saving. |
| Draft saved | The class is saved but not submitted for approval. | Use this while branding and links are still being reviewed. |
| Under review | The class has been submitted to Google. | Wallet buttons stay hidden until Google approval is confirmed. |
| Approved | Google has approved the class. | Attendee and Dealers Den wallet buttons can appear where eligible. |
| Rejected | Google rejected the class. | Update the configuration and save again to resync. |
Class ID behavior
| Control or state | What it does | Operator impact |
|---|---|---|
| Suggested class ID | Builds a class ID from partner organization name and rego prefix. | Prefer this for new events so class IDs stay predictable. |
| Use suggested ID | Copies the suggestion into the Class ID field. | Use before the first save unless a wallet operator supplied a specific ID. |
| Locked class ID | Prevents ordinary edits after first save. | Only FPH super admins can override an existing class ID because changing it can break pass continuity. |
Activation state options
| Option | Meaning | Public impact |
|---|---|---|
| Draft | Saves wallet setup without asking Google to approve the class. | Wallet remains hidden from attendee flows. |
| Under review | Syncs the class for Google approval. | Passes become available once Google marks the class active. |
Class ID rules
Google Wallet class IDs must use the issuerID.identifier format and only letters, numbers, dots, underscores, and hyphens. Changing class identity after passes exist can create pass migration work, so confirm the ID before review.
Flowchart context
The Create an Event flowchart asks whether Google Wallet support is needed after payment setup. Configure this page before final registration testing so generated passes can be checked with the rest of the attendee flow.
Common mistakes
Do not put temporary test URLs into homepage or support links before activation. Wallet links can remain visible after attendees save a pass.