General
Template
A template defines the structure and design of a pass. It controls what fields exist, how they are labeled, and where values appear.
In Wallet Crew terms, a template often maps to a pass type. For tickets, you typically start from the Event ticket template.
What a template does
A template controls:
Visual design (colors, logos, images).
Field layout (front fields, back fields, messages).
Which dynamic placeholders you can use.
Provider-specific constraints (Apple vs Google).
A template does not decide whether a ticket is valid. Your source system (like Secutix) remains the source of truth for validity.
Why a template is required
Wallet apps don’t render arbitrary ticket data. They render a pass that matches a predefined shape.
You need a template so you can:
Define a stable schema (which fields exist, and their meaning).
Decide where each value is shown (front vs back, labels, ordering).
Keep branding consistent across all issued passes.
Enforce wallet constraints early (required fields, image sizes, supported field types).
Without a template, you can still have ticket data. You just can’t reliably turn it into a wallet pass.
Why you may need multiple templates
Most projects can ship with one template. You should split templates when the pass needs different layout or rules.
Common reasons:
Different event brands under one tenant.
Different ticket products (standard vs VIP).
Different legal text or display rules per product.
Different languages or branding requirements.
Different partner distribution surfaces needing different look.
Impact on Secutix routing
If you have multiple ticket templates, you must decide how Secutix selects the right one.
The Secutix connector supports:
a
WALLETcomfort variable set on the eventmapping by product family subtype
a custom pass type finder hook for advanced rules
Last updated