Overview
Pass template types in PassEntry define layout structure, available visual assets and field placement – they do not limit how you can use a pass. You can use any template type for any scenario, whether that’s loyalty, access control, events, memberships, gift cards or insurance passes. The template type simply gives you a starting layout optimised for a common use case.In this guide
- Do pass template types restrict use cases?
- Available template types
- Visual examples
- Comparison table
- How template types differ
- Choosing the right template type
- FAQ
- What’s next
Do pass template types restrict use cases?
A pass template type:- ✅ Controls layout
- ✅ Determines which images and fields are available or required
- ❌ Does not enforce business logic or restrict usage
- A Loyalty template can be used for access control
- An Event template can also be used for non-ticket scenarios that require more visible fields or broader geo-based notifications.
- A Generic template can be used for almost any scenario
Available pass template types
PassEntry currently supports the following template types:- Loyalty
- Generic
- Stamp card
- Event
- Transit
Visual examples of pass template types
The examples below show typical layouts for each pass template type. They illustrate visual structure only – all templates can be customised and reused for different use cases.Stamp card

Progress-based layout showing completed and remaining steps (4 cups out of 7 filled – 3 more to go).
Transit

Requires two central fields (origin and destination) and emphasises route or journey details.
Template type comparison
The table below contains the main differences between pass template types including available assets, fields and features. All types support Apple Wallet and Google Wallet.| Feature | Loyalty | Generic | Event | Transit |
|---|---|---|---|---|
| Horizontal logo | ✓ | ✓ | ✓ | ✓ |
| Square icon | ✓ | ✓ | ✓ | ✓ |
| Thumbnail | – | Apple Wallet only | – | – |
| Banner | ✓ | Google Wallet only | ✓ | Google Wallet only |
| Header fields | 1 | 1 | 1 | 1 |
| Central fields | – | 1 | – | 2 |
| Details fields | 4 | 6 | 6 | 6 |
| Back fields | 5 | 5 | 5 | 5 |
| Geo-based notifications radius limit | 100m | 100m | 1000m | 100m |
| Per-pass background colour override | Apple Wallet only | ✓ | ✓ | ✓ |
How template types differ
Layout and field structure
Template types define:- Which field sections are available (header, central, details, back)
- How many fields can appear in each section
- Whether certain sections are required
- Transit templates require two central fields.
- Event templates allow more detail fields on the front, but don’t have a central field.
- Generic templates include one central field.
Images and branding assets
Template types also control which images are supported or required, such as:- Logo
- Icon
- Banner
- Thumbnail
Choosing the right template type
There is no single “correct” template type - the best choice depends on the layout and fields you need to display.
- How many fields do you need to display on the front and on the back of the pass? Remember that clickable links must be placed on the back of the pass.
- Which layout best fits the information you want to display?
- Do you need a central field, two central fields or a progress-based layout?
- Which assets (logo, banner, icon, thumbnail) do you want to highlight?
- The name of the template type
- Whether your use case matches the label exactly
Frequently asked questions
Do pass template types restrict how a pass can be used?
No. Pass template types only define layout, available assets and field structure. You can use any template type for any use case.Which pass template type should I choose?
Choose the template type based on the layout and fields you need to display on the pass, not on the name of the template type.Can I use a Loyalty template for non-loyalty use cases?
Yes. For example, Loyalty templates are often used for access passes or memberships where a membership ID is displayed in the top-right header field.If I want to use the Loyalty API and update a balance on the pass, do I need to use a Loyalty template?
Not necessarily. Any template type can be configured to use a header field as a balance field and apply loyalty balance formatting. Once the template is configured this way, you can use the Loyalty API with any template type.Do all template types support Apple Wallet and Google Wallet?
Yes. All pass template types support both Apple Wallet and Google Wallet, but the available assets (such as banners or thumbnails) may vary slightly.Can I change the template type later?
You can change the template design (colours, fields, images) at any time, but the template type itself cannot be changed after creation.What’s next?
- Learn which design assets to use for your pass template
- Explore issuing passes from template via API


