PIING
Design a Wallet pass customers can actually use
What belongs on the front, which fields earn their place, and how to make a membership feel like your brand without fighting the Wallet layout.
In this article
Start with what the customer needs.
A good pass answers a small number of questions quickly: whose membership is this, what can I use, and how do I identify myself? A points balance is useful when there is a points programme. A simple membership does not need an invented balance to look complete.
Choose the programme first: connected loyalty, store credit, membership tiers or visits. In Piing, the programme determines which values have a real source. A field that looks attractive in a mock-up is not useful if it cannot be kept current.
Make it recognisable, not crowded.
Use your own logo, a considered colour palette and a clear piece of artwork. Keep the practical information as fields rather than baking the customer’s name or points into an image. That lets the values change without remaking the artwork.
A membership can feel distinctive through typography in its logo, illustration, pattern or photography. Keep the QR area clear. Decorative artwork should support recognition, not compete with the code or the customer’s name.
Make the pass yours.
- Logo
- Colours
- Artwork
- Fields
Make it personal.
- Points
- 2,480
- Member
- Sofia Smith
- Tier
- Gold
Choose the details each member sees.
Give every field a reason to be there.
For connected loyalty, start with points, name and tier. For store credit, put the available balance where it is easy to read. For a simple membership, name and member ID may be enough. A visit-based programme can show visit values instead.
Piing’s field picker marks unavailable data sources. Store credit needs the relevant Shopify permission. Do not treat a sample reward count, store name or referral code as a working field until the issuing data source is connected and tested.
Keep any text beneath the QR short and purposeful. A prompt such as “Scan at checkout” can help in the right setting; a long internal identifier usually adds little for the customer. The code still needs its customer-linked value even when that value is not printed underneath.
One brand, two platform layouts.
Apple Wallet and Google Wallet are separate designs, not two screenshots of the same canvas. Use the platform preview and the image-slot guidance in the editor. Google controls parts of the text appearance and layout, so check the Android version in its own right.
For current platform guidance, consult Apple’s Wallet design guidance and Google’s pass and brand guidelines. The published pass on a real device is the acceptance check; a website illustration is not one.
Test the ordinary and the awkward cases.
Preview a long customer name, a new member with no balance, a large balance and a different tier. Check that the name remains legible and the QR is unobstructed. Then install a test pass on iPhone and Android and scan each through the route staff will actually use.
QR is the starting point on both platforms. Apple Wallet phone taps need the appropriate NFC approval and a compatible reader; Piing’s Google route currently uses QR. Test physical NFC cards separately from phone taps.
Ready to build? Explore Piing’s Wallet and recognition tools, or follow the publishing and distribution guide.