Face check-in that guests choose.
FacePing checks that the person at the gate is the one who bought the ticket. Guests opt in when they buy, gates verify on the device, even offline, and face data is deleted after the event.
Free for one event of up to 500 guests. No card needed.
- Opt-in only
- 1:1 ticket match, not surveillance
- Works offline
- Deleted after the event
- Always a non-face lane
How it works
From ticket page to turnstile in three steps.
FacePing slots into the ticketing flow you already have. Your systems keep the tickets; we only confirm that the face matches the ticket.
Guests opt in
After checkout, buyers can choose face check-in in our widget on your ticket page. They read and accept the consent wording themselves and take a quick selfie. Anyone can say no.
Gates sync, then go offline
Gate devices download an encrypted pack of the event's face templates. Matching runs on the device, so a dropped connection never stops the queue.
Scan, look, walk in
The guest scans their ticket and looks at the camera. FacePing checks it's a live person and that the face matches that ticket, and nobody else's.
Privacy by design
Built for GDPR and biometric law from day one.
Face data is the most sensitive data there is. FacePing collects the least it can, keeps it for the shortest time, and proves it's gone.
Consent from the guest
Guests give consent themselves, in wording written for UK GDPR, EU GDPR or US biometric law. Under-16s need a parent or guardian.
One-to-one, never a crowd scan
The gate compares a face with the ticket being scanned. It doesn't search crowds or identify passers-by.
No photos kept
We store a numeric face template, not the selfie. Packs on gate devices are encrypted and wipe themselves when the event's data expires.
Automatic deletion
Templates are deleted 7 days after the event by default, never later than 30. Every deletion is logged, without personal data, so you can prove it.
Liveness checks
A photo or a phone screen held up to the camera won't get in. Gates check for a live person before they match.
Never the only way in
Every event must keep a non-face lane. Guests can withdraw at any time and their template is erased at once.
For developers
A few lines on your ticket page.
Your server asks for a single-use enrolment token, and the widget does the rest: consent, camera and upload. Then point your gate app at the SDK.
- REST API with examples for Node, Python, PHP, .NET, Java, Go and Ruby
- Drop-in enrolment widget, or enrol from your own systems
- Offline gate SDK for .NET MAUI, with Swift and Kotlin next
- Guests, usage and the deletion log in your dashboard
// After checkout: a single-use token for this ticket const res = await fetch( `https://api-eu.faceping.ai/v1/events/${eventId}/enrolment-tokens`, { method: "POST", headers: { "X-Api-Key": process.env.FACEPING_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ ticketId: order.ticketId }) }); const { token } = await res.json();
<!-- Your order confirmation page --> <div data-faceping-token="{{ token }}"></div> <script src="https://faceping.ai/widget.js" async></script> <!-- Optional: react when the guest is done --> <script> window.addEventListener("faceping:enrolled", () => showMessage("Face check-in is ready for your ticket")); </script>
// .NET MAUI gate app: sync before doors, then verify offline var gate = await gateFactory.CreateAsync(eventId, deviceToken); await gate.SyncAsync(); using var session = await gate.OpenAsync(); var result = session!.Verify(scannedTicketId, cameraFrame); if (result.Outcome == GateOutcome.Match) turnstile.Open(); else SendToStaffedLane(result.Outcome);
Pricing
Pay per guest who opts in. Gate checks are free.
Guests who don't choose face check-in cost nothing. Start with a free pilot, then pick the plan that fits your season.
Pilot
Try it at one real event.
Free
for 30 days
- 1 event
- Up to 500 guests
- Widget, API and gate SDK
- Full privacy toolkit
Pay as you go
Occasional events, no commitment.
5p
per enrolled guest
No monthly fee
- Unlimited events
- Unlimited gate checks
- Billed monthly in arrears
Growth
Regular events and busy seasons.
£99
a month, 5,000 guests included
then 2p per guest
- Unlimited events
- Unlimited gate checks
- Lower price per guest
Scale
Ticketing platforms and large venues.
£399
a month, 30,000 guests included
then 1p per guest
- Unlimited events
- Unlimited gate checks
- Lowest price per guest
Enterprise
Very large volumes, custom contracts or dedicated regions. We'll quote.
A guest is counted once per event, when they enrol. Monthly fees are paid in advance; extra guests are billed at the end of the month. Prices exclude VAT or sales tax, added at checkout where it applies. Every account is approved before use: we check each use case is lawful and fair.
FAQ
Questions organisers ask.
What happens to guests who don't want face check-in?
They use the normal lane with their ticket, exactly as today. Every FacePing event must keep a non-face lane, and choosing it is never a disadvantage.
Does it need an internet connection at the gate?
Only to sync before doors open. After that, gates verify offline from an encrypted pack on the device, and sync again when they're back online to pick up late enrolments and withdrawals.
Who is responsible for the data?
You, the organiser, are the controller; FacePing is your processor under a data processing agreement. We provide the consent wording, a DPIA template and a guest privacy notice template to make your part easier.
How long do you keep face data?
You choose 0 to 30 days after the event (7 by default). Then templates are deleted automatically from our servers and from every gate device, and the deletion is logged.
Where is the data hosted?
In the EU, on Microsoft Azure. UK and US regions will follow as customers need them; tell us where you operate when you apply.
Why do I have to apply?
Face recognition can be misused, so we approve every customer and use case first. We reply to applications within 2 working days.
Run your next event with FacePing.
Start with a free pilot of up to 500 guests. We'll help you set it up.