The Design Studio is where you set the branding, barcode, and fields on your mobile wallet pass and publish it to Apple Wallet and Google Wallet. Live previews update as you edit.
Design & Content › Wallet Pass › Design Studio
https://app.fanmaker.com/admin/content/wallet_pass/design
The Design Studio is available to full admins and above. If you see a Create New Pass screen instead of the studio, your program doesn’t have a wallet pass yet. Contact your Fanmaker representative to get one set up.
Save draft: saves your changes and uploads new images. Drafts aren’t visible to fans.
Publish Apple / Publish Google: builds the pass for each wallet. Found in the Status panel.
Status (ON / OFF): shows whether your program is using the Design Studio pass. This isn’t a switch you control. Fanmaker turns it ON once your Readiness checklist is green and both platforms are published.
The Design Studio has three tabs: Shared, Google Wallet and Apple Wallet. A red number on a tab shows how many blocking checklist items live there.
Identity: Program name (shown on the lock screen and on the Google Wallet card) and Issuer (shown beside the logo on Google Wallet).
Barcode: the barcode format. The barcode encodes your program’s configured member identifier, shown under Format. It can’t be changed in the studio. If you choose an iOS 27-only format, check Add a QR fallback for iOS 26 and earlier. Without it, iOS 26 devices show no barcode.
Featured Actions: up to two shortcut buttons, in priority order. They appear as tiles on iOS 27 and as links in the pass details on Google Wallet. On iOS 26 they’re hidden. Each needs an https link, or a tel: link for a call action.
Membership themes: different pass colors for members on a membership level, or with an expired membership. Theme colors are set on the Apple and Google tabs.
Google Wallet class: Google requires a class for your pass before members can add it. Fanmaker sets it up when your pass is first created. On this tab, press Create Google Wallet class to confirm it exists in Google. Pressing it again is safe, because it only creates what’s missing. Publishing to Google is blocked until it succeeds.
Google images: Google logo (660×660 px, shown as a circle, so leave a margin), Google hero image (1032×812 px), and an optional Google wide logo (1280×400 px). The older 1032×336 hero size still works.
Colors: Automatic (recommended, Google picks from your hero image and logo) or Custom.
Fields: the rows shown on the card. Google shows at most three rows (six fields). These are the same fields as the Apple legacy pass, so editing them here changes Apple too.
Links: up to 10 extra links in the pass details (https only). Your site URL and Featured Actions are added automatically.
Colors: Background, Foreground and Label are all required. Without them Apple shows a white pass with blank labels.
Apple images: Icon (114×114 px) and Logo (150 px tall, 150–480 px wide) are required. The Strip image (1125×432 px) is required for the iOS 26 and earlier pass. The iOS 27 poster needs both a Primary logo (90 px tall) and Poster artwork (1074×1344 px). Without both, your pass ships without the poster, and nothing else is affected.
Fields:
Legacy pass (iOS 26 and earlier, shared with Google): up to 3 header, 1 primary, 4 secondary and 4 auxiliary fields.
iOS 27 poster pass: one header, up to two primary (side by side), and one footer.
Back of pass: text shown on the back of the pass (up to 10 fields).
Import: drop a passModel.zip on this tab to fill the Icon, Logo and Strip slots in one step.
Use the iOS 27 · Poster and iOS 26 · Legacy buttons on the preview to check both versions.
The Readiness checklist shows what’s complete. Blocking items must be green before Fanmaker can switch the design on. These include:
Identity (program name, description, issuer, and an https site URL)
Apple signing certificate
Apple colors
Google Wallet class and its confirmation
The required images
At least one legacy field
A valid barcode
Valid Featured Action links
Image sizes are advisory (amber). Only a missing required image blocks. The poster fields item blocks only once both poster images are uploaded.
These steps are handled by Fanmaker, not by you:
Your first wallet pass. Created by Fanmaker when your program starts using wallet passes.
Apple Pass Type ID and signing certificate. Created, renewed, and re-issued by Fanmaker engineering. Until it’s in place, the “Apple signing certificate” and “Developer setup” items stay red, members can’t add the pass, and the pass is skipped by updates.
Google Wallet class. Fanmaker creates it. You confirm it with the Create Google Wallet class button.
Switching your program ON. Done by Fanmaker once the checklist is green and both platforms are published.
Google classes for membership themes. One per theme, created by Fanmaker.
Fixed pass details. Your pass identifiers, Google issuer, and which member fields (points, balance, level) a pass may show. To change these, contact Fanmaker.
Add to Wallet buttons. Whether members see the Add to Wallet button on their profile. This appears in the checklist as an advisory item.
If any of these checklist items are red, contact your Fanmaker representative.
Installed Apple passes update on the device’s next refresh. Google passes update on Google’s next sync.
Changing the program name or logo re-renders every installed Google pass.
The poster design only appears on iOS 27 and later.
Publishing pushes updates to installed passes. This is limited to 6 pushes per hour per platform, with 10 minutes between pushes. Publishing while your program is OFF doesn’t push anything.
Wallet Pass Stats · Wallet Pass Scoring · Mobile Wallet Pass Distribution via Email
