How TikoYetu QR Tickets Work: From Payment to the Door
By Otieno Odhiambo · 12 August 2026 · 1 min read
A QR ticket only exists after a payment provider verifies the transaction server-side — here's the real chain from payment to the scan at the door, and why it can't be faked.
A QR code is only trustworthy if the system generating it is strict about when it does so. Here's exactly when and how TikoYetu creates one.
No verified payment, no QR code
The QR code isn't generated at checkout, and it isn't generated because your browser displayed a "success" message. It's generated only after the payment provider — M-Pesa or a card processor — confirms the transaction directly to TikoYetu's own server. That ordering is deliberate: it's the difference between a ticket that's real and one that's just a nice-looking image.
What's actually encoded
Each QR code corresponds to a specific ticket record tied to a specific verified order — not a generic pattern that could be screenshotted and reused across different people. Scanning it at the door checks that specific ticket's status, not just whether the image looks like a valid QR code.
Why you can't get two tickets from one payment
The system that issues tickets is built to be idempotent: if a payment confirmation is somehow delivered more than once by the provider (which does happen, as a reliability feature on their end, not a bug), TikoYetu recognises the duplicate and doesn't issue a second ticket for the same payment. One verified payment, one ticket, no matter how many times the confirmation arrives.
At the door
The door scan checks the ticket's actual status in real time, not a static list printed beforehand — so a ticket that's already been scanned, or one tied to a refunded order, is caught at the point of entry rather than only being discovered afterward.
— Otieno Odhiambo