> ## Documentation Index
> Fetch the complete documentation index at: https://docs.proofage.net/llms.txt
> Use this file to discover all available pages before exploring further.

# What the person sees

> Every screen of the verification, from consent to the final screen, on desktop and phone.

The hosted verification is a short sequence of screens. It runs in a window over your page ([Browser SDK](/integration/web/browser-sdk)), in a new tab, or on its own page after a [redirect](/integration/web/redirect).

## The screens

<Steps>
  <Step title="Start">
    What the check is and how it works, with the steps to come. On a document check it asks the person to have a valid, undamaged ID ready.
  </Step>

  <Step title="Consent">
    The consent text, with the minimum age when the workspace has one. Nothing is captured before the person accepts.
  </Step>

  <Step title="Document">
    KYC and age verification by ID document only. The person chooses the document type, then photographs the front and, unless it is a passport, the back. Each photo is checked as it is taken, and the person retakes it if the document is cut off, blurred, glary or unreadable.
  </Step>

  <Step title="Selfie">
    The person takes a selfie with the live camera, following short prompts to turn their head. Uploading a photo is not possible.
  </Step>

  <Step title="Processing">
    A progress screen while the images are checked, usually a few seconds.
  </Step>

  <Step title="Final screen">
    "Verification Complete", with "Your identity verification session is complete." or "Your age verification session is complete." The screen is the same whether the person was approved or declined: the outcome goes to your backend, and you decide what to tell the person. After about three seconds the browser returns to your site.
  </Step>
</Steps>

On a **Facial age estimation**, the person takes only the selfie. If the estimate cannot confirm their age, the widget explains that a document is needed and continues with the document steps in the same verification.

When a check asks for a **retake**, the widget says what to fix and returns to the step concerned.

## From a computer to a phone

A document check needs a good camera. On a computer, the start screen shows a QR code: the person scans it, finishes on their phone, and the computer's screen updates when they are done. The phone then tells them to return to the browser where they started.

## Languages

The verification is available in 28 languages: Bulgarian, Czech, Danish, German, Greek, English, Spanish, Finnish, French, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Lithuanian, Dutch, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Swedish, Thai, Turkish, Chinese (Simplified), Chinese (Traditional).

The widget picks its language in this order: the link's `?lang=` parameter, the Browser SDK's `language` option, the browser's language, and then English. A language it does not support is skipped.

## Camera access

If the browser blocks the camera, the widget explains how to allow it for that browser and device, and suggests another browser or device when the block is outside the browser. See [Browser and device support](/getting-started/browser-device-support).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.