Age verification for taproom events: what the ticket sale can and cannot do

What does bindro check at checkout?

Two things, and they do different work. The booker ticks a confirmation that every guest is 21 or over — that is an attestation, and its value is legal and evidential rather than technical. Separately, the booker gives their own date of birth, and that one is enforced: the 21 minimum is evaluated on the money path, so an under-21 booker is refused rather than sold to and sorted out later.

An unparseable date is refused too, rather than waved through. A rule that garbage bypasses is not a rule.

Why is the ID check recorded against the scan and not the order?

Because the order tells you who paid, and the door needs to know about who arrived. A party of four booked by one person is one order and four admissions; recording "ID verified" on the order would assert something about three people nobody looked at. Bindro therefore accepts an ID-verified flag per scan, and the console requires the operator to confirm it explicitly for verticals that declare ID verification — brewery events being one.

The retention rule follows from the same logic: the age-check compliance record for this vertical is kept for 24 months, because that is a licensing evidence horizon, not a marketing one.

What should door staff actually say?

Short, identical, every time. A script that varies is a script that gets argued with, and the argument always happens at the busiest moment of the evening.

• "Can I see ID for everyone drinking, please." — everyone, not just the person who looks young.
• "The booking confirms you are over 21; I still have to see the ID." — the attestation is not a substitute and guests are told so at booking.
• "Without ID I cannot admit you, and the booking is not refundable." — this exact wording is on the booking page before payment.
• Refusals go to a manager, not to a debate at the door.

Does the guest know about this before they pay?

Yes, and that is the point of putting it in the configuration rather than in a policy page. The confirmation checkbox says photo ID is checked on arrival and that guests under 21 will be refused entry without refund; the date-of-birth field repeats it. The refusal you never have to make is the one the guest already read about at checkout.

What is deliberately not automated here?

Bindro does not scan or store identity documents, does not run a third-party age verification service, and does not claim to have verified anyone's age on your behalf. It records that your operator confirmed ID at the door, with a time and a scan attached. A platform that pretended to verify would be worse than one that says plainly where the responsibility sits — which is with the licensee.