The redemption log
Updated July 8, 2026
Every pass has its own scan history. Open a pass and go to its Redemptions tab to see how its redemption policy is playing out and every scan that's been made against it.
What's at the top
- Policy: a summary of the pass's current redemption policy and where it stands: for example, "Single use, redeemed," "Reusable (3 scans)," or "Count-limited (2/5)."
- Total redeemed: the pass's running redeemed count, the same number the policy check compares against on the next scan.
The scan list
Below that is every scan made against the pass, newest first, with:
- Result: accepted or rejected.
- Device: the name of the scanner that made the scan (the name you gave it when you set it up).
- Reason: blank for an accepted scan; for a rejected one, why it was rejected (already redeemed, use limit reached, voided, wrong mode, out of scope, or not found). See how scanning works for what each reason means.
- When: how long ago the scan happened.
If no one has scanned the pass yet, the tab just tells you so. Pair a scanner and scan the pass to see it show up here.
Rejected scans are recorded here so you have a full audit trail, but they do not
fire a pass.redeemed event. Only an accepted scan does. If you're using webhooks
to react to redemptions, a rejected scan won't trigger anything downstream. Check
this log instead for the full picture of every attempt.
Related articles
How scanning worksThe scan, verify, and redeem loop, and what each accepted or rejected result means.Redemption policiesChoose whether a pass is single-use, reusable, or valid for a fixed number of scans.Set up a scannerPair an iPhone or iPad running Passmint Scanner, or your own device, to check passes at the door.