Where the wallet-pass QR takes people

Every ticket carries a QR code — on the wallet pass and in the confirmation email. That one code does two different jobs depending on who scans it, and Turtini sends people to the right place automatically.

Staff scanning checks people in:
At the door, your check-in scanner reads the QR and marks the attendee as arrived (see "Check-in and attendance"). Nothing changes here — the scanner always checks people in, no matter which page the same code would open in a phone camera.

A regular phone camera opens the event page:
If a curious guest scans the same QR with their phone's normal camera instead of your scanner, it opens the event's public page rather than hitting a dead end.

Which event page? Your own domain when you've published there:
If you've placed the event on a page served by your org's own custom domain — using an Event Tickets builder block bound to that event — the QR opens the event page on your domain. So the guest lands on your brand, your site, your URL. If the event isn't published on your own domain, the QR falls back to the event's page on turtini.com (turtini.com/events/your-event).

How to get the "own domain" destination:
1. In Builder, add an Event Tickets block to a page and bind it to this event.
2. Publish that page on a site that has your custom domain attached.
That's it — the next passes and confirmation emails point their QR at your domain. Passes already in Wallet refresh over the air where supported.

Good to know:
• Turtini re-checks that the domain still maps to your site before using it, so a stale setting can never misroute a scan.
• The check-in behavior is unaffected either way — staff always check people in from the QR.