How to confirm a hosted age check without receiving ID documents
Yes. A custom booking site can send visitors to a hosted age check and make its booking decision from the confirmed result. The key design choice is to separate the visitor’s return to your site from your server’s confirmation of the result. Build a recovery path for people who finish the check and never reach the return page.

In this article
Give the provider the capture flow
Safe Passage’s server integration starts with your server creating a verification session. The visitor completes the check on the hosted Safe Passage page. Your site can associate the pending session with the signed-in user and the booking in progress, then send the visitor to the hosted page. [1]
The Sessions API documents the result your server can work with. It includes the access decision, session and user references, and other metadata such as the policy applied. The documented response contains no ID document or selfie files. Your application can use the outcome to decide what happens to the booking without taking custody of those files. [2]
Confirm the result before advancing the booking
Use the browser return to resume the booking flow and look up the pending session on the server. Safe Passage’s server guide checks the result with Validate Session, matches it to the expected user, and advances only when the access decision permits it. Keep the site’s booking rules in the application so a completed check advances only the booking it belongs to. [1] [2]
Consider a site where a visitor starts an age check for an age-restricted event. They finish the check and return while the booking is still waiting. The site looks up the session and confirms that it belongs to the visitor and the pending booking. If the confirmed result allows access, checkout resumes. If the check is unfinished, the booking stays pending and the site can offer the visitor a way to continue.
Think through how long a pending booking can hold an inventory slot. If the slot expires while someone is away, the site can acknowledge the verified result and let the visitor choose an available booking. That keeps the booking decision separate from the age-check outcome.
Use webhooks to recover from interrupted returns
A signed webhook gives your application another way to learn that verification completed, including when the visitor closes their tab. Safe Passage documents at-least-once delivery, so the same completion event can arrive more than once. Verify the signature, match the event to the expected session and user, and make repeat delivery safe. Dashboard test events should leave access unchanged. [3]
Use a single pending booking record for the return and webhook paths. For example, the return page can check the result during an active checkout, while a valid later event can update the same record for someone who comes back. If both arrive, advance the booking once. Safe Passage documents that a failed webhook delivery does not change the underlying verification result, which remains available via Validate Session. [3] [1]
Decide what your application needs to keep
Start with the smallest record that supports the booking decision and the questions your team needs to answer about it. That might be the booking reference, a session reference, the confirmed outcome, and when your application recorded it. If you need more information for a specific purpose, document the reason. Check what your application copies into logs, analytics, and customer support tools as well as its database.
The UK Information Commissioner’s Office gives a yes-or-no age-threshold result as an example of data minimisation in its Children’s Code age assurance guidance. That example helps frame the design question. Session references and outcomes can still be personal information when linked to a person. Decide what you need for your own service and how long you need it. [4]
Test the handoff before launch
Run these cases in a test environment. Inspect both what the visitor sees and the state your booking system records.
- Complete a check and confirm that the expected booking advances only after the server has confirmed the matching result. [1] [2]
- Leave a check unfinished. Confirm that the booking stays pending and the visitor has a clear way to continue. [1] [2]
- Complete a check without returning to the booking page. Verify the signed completion event updates the right record. Repeat delivery and confirm it produces one state change. [3]
- Test a result that belongs to a different user or session in your test environment. Confirm that it leaves the booking pending. [1] [2]
- Inspect the booking record and downstream logs. Check that they contain only the fields you selected and no copies of identity documents or selfies. [2] [4]
Sources
- Server integration Safe Passage
- Sessions API Safe Passage
- Webhooks Safe Passage
- Age assurance for the Children’s Code: data minimisation and storage limitation Information Commissioner’s Office