Configuration and Callbacks

This page explains how the verification tool (SDK) is set up at runtime, how it handles different languages, what happens on unsupported browsers, and how it notifies your business when a user finishes.

Where Settings Come From

The verification tool (SDK) reads settings in this order, with each source able to override the previous:

1. Link settings passed in the verification link
2. Values saved in the browser session
3. Values recovered from local browser storage (used by entity and BioLogin flows)
4. Settings downloaded from our servers for your business

Main Setting Categories

• General settings — labels, button text, visibility options, and layout behavior
• Step settings — which identity verification (KYC) steps appear, supported document types, and button labels
• Video settings — live connection (WebSocket) server, call quality settings, and audio controls
• Entity settings — document upload and company information configuration for business onboarding

Language

• The language shown is taken from the link setting or detected from our servers.
• All requests to our servers include the selected language so responses match.
• Arabic content automatically switches the layout to right-to-left.

Location Sharing and Device Information

• Location sharing (geolocation) can be switched on or off via a link setting.
• Location is only collected on secure (HTTPS) connections.
• Every upload and request includes basic device information automatically.

Unsupported Browsers

If the user's browser is not supported, the entry screen shows an unsupported-browser message and records error code 1010.

What Happens When the Journey Ends (Callback)

When the user finishes (or cannot finish), the verification tool (SDK) redirects them to your return link with the following information added:

• status — either complete or incomplete
• customer_id — the user's customer identifier
• errors — a comma-separated list of error codes when something went wrong

Example return link:

https://yourapp.example/callback?status=incomplete&customer_id=12345&errors=401,3002

Redirect Rules

• Protected screens require a valid access token and customer identifiers; missing values send the user back to the start.
• A user who has already completed verification is redirected to the Completion screen if they try to open other screens.
• A user who has not completed verification is redirected away from the Completion screen back to the start.
• Any unknown link path is redirected to the start automatically.

Common Error Codes

Code	Meaning
401	Unauthorized — the access token or session is not valid
404	Profile not found
500	Server error
1010	Unsupported browser

warning

Always validate the return link values on your own backend before finalizing your business workflow.