Pass fields explained
Updated June 29, 2026
Fields are the rows of text on a pass: a name, a balance, a date, a seat. They're organized into four groups by importance and position. Each group has its own size and a limit on how many fields it can hold.
The four groups
- Primary (up to 1) — the headline of the pass, shown largest. Use it for the one thing that matters most: the event name, the member's name, the points balance.
- Secondary (up to 2) — a row beneath the primary field, smaller. Good for a date, a tier, or a location.
- Auxiliary (up to 2) — a further row beneath secondary, smaller still and optional. Use it for supporting detail.
- Back (unlimited) — long-form content shown when someone taps to flip the pass over. Ideal for terms, instructions, contact details, and anything that doesn't need to be visible at a glance.
Label and value
Every field has two parts:
- The label is fixed in the template. It's the small caption, like "SEAT" or "BALANCE".
- The value is what sits under the label. You can set a default value in the designer, but the real value is usually supplied per pass when you issue it.
A field can also be marked required, which means issuing fails if no value is provided. Use that for anything a pass can't be valid without.
Field keys are how the rest of Passmint refers to a field. The barcode message and
any integration both reference values by key, like {{fieldValues.seat}}. Keep
keys short and memorable.
Keep it readable
Wallet passes are small, and the front of the pass is glanceable by design. Resist the urge to fill every slot. A pass with a clear primary field and one or two supporting rows reads far better on a lock screen than one crammed with text. Push the detail to the back of the pass, where there's room for it.