Reading the redemption history
Per-scan log lets you troubleshoot count disputes on multi-pass tickets.
Last updated 25 April 2026
Every ticket has a redemption history β a per-scan audit log. Useful for resolving "this is wrong" disputes.
Where to find it
Owner Portal β Ticket Hub β click into any ticket β scroll to Redemption history
What it shows
| Column | Meaning |
|---|---|
| Action | What happened (consumed / revoked / refunded / reissued) |
| Actor | Who did it (host email or system) |
| When | Exact timestamp |
| Reason | Free-text note (only on revoke / refund) |
Common dispute scenarios
"My 5-pack says 3/5 but I've only been twice"
Redemption history shows the third scan β date, time, who scanned. Usually it's:
- A double-scan from a busy day (within the 10s window we deduplicate, but if 11s apart, both count)
- A staff training scan that wasn't cleared
- The buyer's friend used the QR
"I never used my ticket but it shows redeemed"
History shows the staff member who scanned. Cross-check with their shift β sometimes the wrong code was typed during manual lookup.
How to fix mistakes
For an over-counted scan:
- Acknowledge to the buyer
- Issue a goodwill replacement ticket via the Reissue flow
- Note in the new ticket why ("Reissued due to mis-scan on 14 May")
We don't currently support "undo a redemption" directly β reissue is the path.