White-label ID verification

White-label ID verification means the guest thinks they are dealing with the event, while a specialist product does the capture. At signup or checkout, that distinction matters. A generic “identity partner” screen feels like a bank. Your own name feels like part of buying the ticket.

Protect Events puts your display name, colours and copy on the hosted flow. The sentences people read, from the intro through the face and document steps, are yours to set. The mechanics stay fixed, because the mechanics are the product: guided face capture, passport or licence, then a photo holding the document. Your team still works in the Protect Events console, and you still manage the review pipeline. Guests get your brand. The pipeline looks the same on every event, which is how a new person on the team learns it once.

What is worth branding, and what is not

Worth branding: the name at the top, the colour of the button, the sentence that explains why you are asking. A members’ club and a 5,000-capacity show should not open with the same greeting. Tell them it is so they are checked before they arrive.

Not worth reinventing: the order of the steps, the document types, the age comparison. Those are how you get a result you can compare across events. If every promoter redesigned the capture, you would no longer have one check.

The service model behind this is ID verification as a service. The wiring, if the link is created by your ticketing stack, is API-based ID verification.

Promoters, venues, and whose name appears

A promoted night inside someone else’s building has two brands. Put the show’s name on the guest’s phone if that is who they bought from. Keep the pipeline operational: event, age, outcome, and the cases waiting for your team. People working the review need “approved, 21, minimum 18” more than they need a logo. The nightlife version of the same idea is in age checks for nightlife and festivals.

A short brand setup

1. Set the display name to the words guests already use for you.
2. Set a primary colour with enough contrast that the button is obvious on a phone.
3. Keep the intro to a sentence. Tell them it takes about two minutes, that it happens before they arrive, and that the camera is only used for this check.
4. Run one member of your team through it as a guest before the public does.
5. Look at the result in the pipeline, not only on the phone. The branded step can be pretty and still fail if your team cannot see who is waiting for review.

White-label is a trust gesture. It is not a disguise. If someone asks what was checked, the answer should still be plain: a face capture, a passport or driving licence, and an age against the number you set. Processing runs in the UK, and ID images are deleted after 30 days unless a review is still open.