Skip to main content
You maintain one template per program, and Stell renders it for both wallets. Apple Wallet follows your template closely — it’s what the editor preview shows. Google Wallet uses a more standardized card layout, so the same template comes out simpler there. Knowing the differences saves surprises.

​
What carries over to Google Wallet

​
What doesn’t carry over

  • Strip image — Google Wallet has no strip-image concept; the card relies on your background color and logo.
  • Pass style — Store Card, Coupon, and the other styles are Apple layouts. On Google, every program uses the standard card layout.
  • Background image and poster artwork — not used on the Google card.
  • Notification icon — Apple-specific.

​
What this means in practice

  • Don’t put critical information only in an image. A points balance baked into the strip image is invisible on Google Wallet — keep values in fields, which render on both.
  • Pick a background color that stands alone. On Apple the strip image dominates; on Google the background color is the design.
  • Mind the front-field budget. Google shows at most 3 rows × 3 fields on the front; anything beyond that moves to the details section. Your most important fields should be in the primary and secondary areas so they win the front-row spots on both wallets.
  • Test on both. After significant template changes, issue a test pass for each wallet type and look at them side by side.
The customer enrollment flow issues passes for both wallets, matched to the customer’s device. Passes can also be issued from the portal or via the API.