How to view ticket transfer history at check-in
See the ticket's current holder at check-in time — and keep old QRs from cancelled transfers out.
Tickets can be transferred between people on Baila. At check-in it matters that staff see the current holder (not the original buyer) and that old QR Codes — from cancelled or invalidated transfers — are rejected automatically.
What the check-in screen shows
When a valid QR is scanned, the screen shows:
- The current holder's name — after a transfer, this is the name of whoever holds the ticket now
- The tier and the ticket number (for example, "Ticket 1 of 2")
Why it matters
A common scenario: John bought a ticket and transferred it to Mary. John's old QR Code was invalidated the moment Mary accepted. If John tries to get in with an old screenshot, the staff screen shows "Ticket transferred — old QR is no longer valid" — making it clear that QR has been passed along, even though it was legitimate once.
Pending transfers at check-in time
An important rule: if a transfer is pending (not accepted) at check-in time, the system automatically cancels that transfer and frees the ticket for the current holder to use. That takes care of the "I started a transfer but the recipient vanished" case — the current holder can still get in as normal.
The full flow
- Staff scans the QR Code
- The backend checks: is the signature valid? is the status
VALID? does it belong to this event? who is the current holder? - If a pending transfer exists: it is cancelled automatically and the ticket is freed for the current holder
- The ticket is marked
USEDand entry is allowed
The transfer report in the dashboard
On the event detail page, in the Transfers section, you get the full log with these columns:
- Sender and Recipient (who passed it on and who received it)
- Tier and Date
- Status: Pending, Accepted, or Cancelled
- Resolution
Useful for post-event auditing and for spotting abuse of transfer chains.