Websites

A website asks VerifAge to create a verification request and shows it to the visitor as a QR code, a short code or, on a phone, a button that opens the app. The visitor approves the request in VerifAge; the website receives verified: true or false and nothing else.

The flow

1. Your server calls POST /api/v1/merchant/verify-requests with your API key.
2. The response contains public_code, qr_url and app_url. Show the QR on desktop and the button on mobile.
3. The visitor opens the app, sees your organisation name and approves.
4. Your server polls GET /api/v1/merchant/verify-requests/{id} or receives the callback, then lets the visitor in.

A request is valid for 72 hours. Store the verified result in the visitor's session; VerifAge does not identify the visitor, so there is nothing else to keep.

Keeping it simple

• Use a test key while developing: every request comes back approved.
• The customer never leaves your page: the QR and the code are shown inline.
• Do not block search engines on the age gate; serve the gate only to real visitors.

Details of every field are in the Merchant API.