PIING
Reading Wallet passes and cardsSend a test push
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
- Where to send from
- Choose the test type
- Confirm it was delivered
- If the test does not arrive
- A good test routine
- Next steps
Search or browse documentation
Wallet passes and cards 7 / 8
Send a test push
How to choose a real customer, send an instant Wallet test or run a real visit trigger, and read the per-channel result.
Before enabling a trigger at scale, send a real test to a chosen customer. Piing reports Apple Wallet, Google Wallet, and optional OneSignal separately, so a successful channel is never inferred from a generic green banner.
Where to send from
Open Notifications, then Send a test notification. The recipient picker starts with recent pass holders. Search by customer name or email to find somebody else; customers without a pass are labelled before you send.
Choose the test type
There are three current choices:
- Test message. Sends immediately through every available customer channel and reports Apple Wallet, Google Wallet, and web push as Sent, Failed, or Skipped.
- Welcome trigger. Runs the real
first_visit trigger for the chosen customer. It queues only if an enabled trigger matches.
- Milestone trigger. Runs the real
milestone_visit trigger with a test visit count of ten. It also queues only if an enabled trigger matches.
A recipient is required. There is no anonymous or blank-recipient send.
Confirm it was delivered
An instant test renders the per-channel result directly beneath the form. Trigger tests report how many notifications were queued; their final status appears under Recent deliveries, usually within a minute. The delivery table is a recent troubleshooting view, not a permanent audit log.
If the test does not arrive
- Confirm the recipient badge shows Apple Wallet, Google Wallet, or both. A customer without a pass can only receive the instant test if OneSignal is configured and that customer has a matching subscription.
- For a trigger test, confirm an enabled trigger matches the event. Zero matches means nothing is queued.
- Check today's Wallet message allowance. A customer-visible message over the limit is held and logged with its reason.
- Read the individual channel detail. One platform can fail while another succeeds.
- If the pass itself is stale, save the current design to repaint installed passes, then test again.
A good test routine
When you set up a new trigger or template, send one test to yourself first, confirm it appears as expected on the pass or lock screen, then send a second to a willing customer or colleague before switching the trigger on for everyone.
Next steps
Related guides
Was this guide helpful?
Next guide in Wallet passes and cards
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.
Still need a hand? Contact us