Skip to content

What the user sees

This section is written for integrators and describes the verification interface from the end user's point of view: which screens they see, what they must do on each step and what happens on failure. Integration details and result formats are covered in Getting started and Integrations.

Try it yourself

The fastest way to understand the interface is to pass it: create a demo session for your Workflow in the cabinet and open it on a phone and on a computer. At the end of a demo session the result and a link to the session in the cabinet are shown.

The interface is the same for Remote, Widget and WebView; only the way the user reaches the first screen differs.

Overall journey

flowchart TD
    A[Loading] --> B{Camera available?}
    B -->|No, desktop| Q[QR code: continue on a phone]
    B -->|Yes| C[Consent to data processing]
    Q --> C
    C --> E[Technologies in Workflow order]
    E -->|Failure, attempts left| R[Retry screen]
    R --> E
    E -->|All passed| F[Final screen]
    E -->|Attempts exhausted or declined| F

The Workflow defines which technologies run and in which order. Some steps are switched on and off by Workflow settings in the cabinet: the consent page, the instruction page before Liveness, the QR code and the progress bar.

Which device to use

The check can be passed on a phone or a computer. The interface detects the device type from the browser (for WebView it is passed via the isMobile parameter) and adapts the path.

Phone Computer
Camera The phone's front camera. If access is denied or there is no camera, the check ends immediately with the "You did not grant access to the camera!" screen (see how to allow the camera) Webcam. If there is no camera or access is denied, a QR code is shown to continue on a phone
Liveness The phone is held upright at eye level; the instruction screen asks for motion sensor permission Camera at eye level, the user sits in front of the screen
Documents The document is captured with the phone camera The document is held up to the webcam or uploaded as a file
SMS and app codes Entered on the same device Read from the phone and entered on the computer

The recommended scenario is a phone: the camera is better, the document is easier to frame and SMS codes arrive on the same device. A computer works when the user has a webcam and the scenario does not require document scanning.

If camera access is denied

The browser remembers the refusal, so reopening the link does not help until the user changes the permission manually:

  • iPhone, Safari: tap "AA" in the address bar → "Website Settings" → "Camera" → "Allow". Or "Settings" → "Safari" → "Camera".
  • Android, Chrome: tap the lock icon left of the address → "Permissions" → "Camera" → "Allow".
  • Computer, Chrome and Edge: the lock or settings icon left of the address → "Camera" → "Allow".
  • Computer, Safari: "Safari" menu → "Settings" → "Websites" → "Camera".

After changing the permission the user taps "reload" on the failure screen or opens the session link again. If the session has already ended with a failure, a new session is required.

Switching from computer to phone

If the computer has no camera, the user scans the QR code on screen and continues the same session on a phone. The computer stays on a waiting screen and, once finished, shows the result or redirects. The Workflow setting "Forced mobile passage" always shows the QR code on a computer, even with a camera. If the QR setting is off in the Workflow, a computer without a camera ends the check with a failure.

Screens shared by all technologies

Loading

The first thing the user sees is a loading screen with the text "We are processing the data, please do not close this tab…". It normally lasts a few seconds.

If the session is not valid, the user stays on this screen. Possible messages and causes are listed under Failure reasons.

QR code

Shown when the user opened the check on a device without a camera or the Workflow is set to "mobile only".

  • No camera: "No camera found on your device! Connect a webcam and refresh the page (F5). Or scan the QR code and continue on a mobile device".

    Refresh the page only after connecting a camera

    Refreshing the page on a computer without a camera moves the session into the in-progress state and the QR code on screen stops working: the phone sees "Session is inactive" when scanning. A user without a webcam should scan the QR code right away without refreshing.

    • Mobile only: "Further verification is only possible using a phone. Scan the QR code using your mobile device".

After scanning, the check continues on the phone while the original screen waits: "We are waiting for you to complete verification on your mobile device, do not close the tab…". Once the phone finishes, the original screen reports completion and redirects.

Heading "Before you start". The user reads the terms (the link opens the document inside the interface) and taps "Accept and continue". "Decline and exit" ends the check with a failure.

The page can be hidden

The consent page is enabled by default and can only be disabled through your manager.

Progress bar

A bar with step names: "Document", "Photo", "Address", "GBDFL", "GBDUL", "Signing", "Code", "Questionnaire". It is hidden on Liveness screens so as not to obstruct the camera.

Closing the interface

A close button is available on most screens. Before closing the user sees the confirmation "Are you sure you want to finish the process?". A confirmed close ends the session with a failure attributed to the user (see Failure reasons).

Session lifetime

A session is valid for a limited time, 30 minutes from creation by default. Waiting on any screen counts towards it, including waiting for the SMS code in E-Document and E-Document Child, the reply to SMS 1414 and the PPS result. When the time is up the session ends with a failure with the EXPIRED reason, and on the next action the user sees "Session is inactive".

Retry screen

Appears when a camera technology failed but attempts remain. Heading "You did not pass the previous check, please try again", a specific reason below (for example "Not enough light. Find a place where light falls on your face") and a "Try again" button. For Liveness a "Check before the next attempt" list of tips is added.

If the camera is the cause, the heading differs: "You did not pass the previous check because you did not grant access to the camera. To finish the process, allow camera usage".

The number of attempts is set per technology in the cabinet. When attempts are exhausted the check ends with a failure.

Final screen

What the user sees at the end depends on Workflow settings:

Variant When On screen
Production Always Blank screen; with redirect_urls set, an almost immediate jump to the success or failure URL, otherwise the user stays on the blank screen and the integration closes the interface on the finish event
Demo session from the cabinet Demo sessions, QR checks, camera-access failure "Successful login" or "Unsuccessful login" and a link to the session in the cabinet; for camera failure "You did not grant access to the camera!" and a "reload" button
Signing result Workflows with digital signature "Signing completed" or "Signing failed", link "Download signed documents as a zip file"

Technology results are not shown on screen: the client's system retrieves them through the result API.

Technologies

Interface language

The language is set by the locale parameter in the session URL. Always pass it: without the parameter the interface uses the language saved in the user's browser, and failing that the domain default (Russian for remote.biometric.kz and remote.biometric.vision, English elsewhere). An unknown code falls back to the default.

Code Language
ru Russian
en English
kz Kazakh
kg Kyrgyz
de German
es Spanish
fr French
it Italian
pt Portuguese
fa Persian
ja Japanese
ko Korean
my Malay

An on-screen language switcher is enabled in the branding settings of the cabinet, see Customization.