Check-in troubleshooting

A few things occasionally trip people up on event day. Here's how to handle them.

The camera won't scan

• Allow camera access — the browser must have permission to use the camera; accept the prompt, or enable it in the browser/device settings.
• Improve the conditions — good lighting and a steady QR code (screen brightness up) help the scanner lock on.
• Use a device with a working rear camera for the best results.
• Have the device plugged in, to not suddenly loose power.

The code isn't recognized

This hardly ever happens, but if a QR code simply won't scan, fall back to checking the guest in by name from the check-in view.

"Already checked in"

If the Terminal says someone is already checked in, they've likely scanned twice — check the check-in view to confirm their status.

A balance is owed at the door

If an attendee still owes money, the Terminal will show a payment notice and prompt them to pay before finishing. It might load a second, before a stripe QR code is generated and displayed.

Connection drops

The Terminal runs in the browser and needs internet to record check-ins. If the venue's connection is shaky, have a backup (a phone hotspot) ready, and keep the check-in view handy as a second device.

Still stuck? See the general troubleshooting guide.