PIING
Reading Wallet passes and cardsClaim links and QR codes
Wallet passes and cards
- Apple Wallet passes
- Google Wallet passes
- Physical NFC cards
- Issue and manage passes
- Where to place Piing blocks in Shopify
- Wallet messages and optional web push
- Send a test push
- Claim links and QR codes
In this guide
- 1. Publish the design
- 2. Choose the right URL
- 3. What the customer does
- The claim page is yours
- The route with no email step
- The pass they get
- Where to put the link
- Test it on your phone
- Next steps
Search or browse documentation
Wallet passes and cards 8 / 8
Claim links and QR codes
Publish a pass, choose the reusable public route for campaigns and signage, and understand the short-lived customer install handoff Piing creates behind it.
A public pass route is how a Wallet pass reaches the customer's phone. Add a supported Piing block to a compatible storefront, customer-account or post-purchase slot, or use a reusable URL in campaigns, websites and printed assets. Installing the app does not place every block automatically. Start under Wallet Studio, then Distribution, and use Where your pass appears to choose and configure the customer touchpoints you need.
Publish the design
A pass design has to be published before a claim link can install anything. The Publish status card shows Published or Unpublished with a single button. If Publish is unavailable, finish the wallet setup it names first, per platform.
Apple and Google publish separately, as do optional tier-specific designs. The Distribution page reports installed Apple and Google passes and adds from the last 30 days.
Choose the right URL
Piing uses two layers:
- Reusable public route. Use this for email, SMS, another website, a link in bio, or permanent printed signage. It remains the public front door while the design is published.
- Customer install handoff. Piing creates this after it knows the customer and platform. It is short-lived and single-use so it cannot be passed from one customer to another.
If a customer sees an expired or already-used message, bring them back through the reusable public route to create a fresh handoff. Avoid copying a final /install/ URL into a campaign or print file.
What the customer does
- They open the public route on their phone or scan its QR code.
- If the surface has verified the signed-in Shopify customer, Piing skips sign-in. Otherwise, the customer signs in through the store's account journey.
- Piing uses that verified identity to create a short-lived install handoff. Typing an email address alone is not proof of identity and cannot claim someone else's pass.
- The customer taps Add to Apple Wallet or Save to Google Wallet.
There is no separate Piing app to download. Shopify controls account sign-in. Test installation on an iPhone and Android device. Google also supports adding eligible loyalty passes through wallet.google.com on the web; that does not replace checking the pass on the customer's phone. Google Wallet release notes.
Note
A final customer handoff expires and is single-use. The public campaign or storefront route should create a fresh one when the customer returns.
The claim page is yours
The public page uses the merchant's pass title, logo, colours, pass preview and available Wallet badges. An unsigned email submission cannot be used to look up a customer's pass.
The route with no email step
The native Profile, Order status and Thank you blocks can use Shopify's signed customer session. A public email, SMS or printed QR does not carry that session by itself: the customer may still need to sign in. Point of sale reads a pass; it does not install one on the customer's phone.
The pass they get
Passes installed from a claim link are built the same way as passes issued through every other route, so the branding is identical wherever a customer came from:
- The logo ships at the sizes Apple expects, so the wordmark renders crisp rather than stretched on every screen.
- The square logo you upload in Wallet Studio is also used for the wallet icon slot, the small square image that appears in notifications, Mail and on the lock screen. A wide wordmark squeezed into a square is what that slot used to show.
- An Apple pass can carry relevant store locations and surface close to the shop. See Wallet messages and optional web push.
Where to put the link
For storefront, account and post-purchase app blocks, see Where to place Piing blocks in Shopify. New customer accounts use the native Piing Digital Card extension; legacy accounts use a compatible theme section or a claim-link placement.
The How to send passes to customers card lists the routes most brands use:
- Your email or SMS platform. Drop the reusable public link into Klaviyo, Attentive, Ometria, or HubSpot. Trigger a follow-up from a Piing event if that route is configured.
- In store. Print the QR code for counters, receipts, window cards or signage.
- Storefront. Add the Piing wallet card widget to your theme for self-serve installs.
- Anywhere else. The link is just a URL, so social, an email signature or a message all work.
Piing does not send the emails or texts itself. Use your connected messaging tool for that. Handing out physical cards instead? See Physical NFC cards.
Test it on your phone
Open the public route from a real email and a printed QR, complete sign-in if needed, add the pass on each supported phone, then scan or tap it through the intended in-store surface. Repeat in a signed-out browser and after deleting a pass. A preview or generated download alone does not prove the pass is installed and usable.
If the design is unpublished or no claim link exists yet, the card says so and testing stays disabled until you fix that.
Next steps
Related guides
Was this guide helpful?
You’ve reached the end of Wallet passes and cards.
Still need a hand? Contact us