# Parameters

This section describes which settings are available in the **KYC Scenario Editor → Web SDK**, how they affect the widget, and on which screen they appear. All changes are immediately visible in the preview on the right, and users will see them in the embedded widget.

## 1) Color theme

The top toggle defines which theme is used to design the interface:

* **Dark** / **Light** — the selected theme is used in the preview and as the default at widget launch (unless overridden by `theme` during initialization).
* Logos and contrast elements are configured separately for each theme (see “General”).

## 2) General

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FaH6EZ7CQ0SwbHLxHJOEc%2F01-general.jpg?alt=media\&token=b5ccfbd0-773a-4f8f-a18e-7c3abd516c19)

The **“General”** tab controls branding and legal links:

* **Logo**

  * *For dark theme* — upload a logo variant that is well visible on a dark background.

  * *For light theme* — separate variant for light background.

  > Recommendations: PNG/SVG with transparent background, avoid thin light‑gray lines on light theme and vice versa for readability.
* **Terms & Conditions (URL)** — link to your T\&C.
* **Privacy Policy (URL)** — link to your privacy policy. These links appear on the start screens and help meet legal requirements.
* **Allow desktop camera usage** (checkbox)
  * Enabled — user can complete verification **on this device** (button “Continue on this device”), camera and upload work in desktop browser.
  * Disabled — user is prompted to switch to phone using QR code/link; capture occurs on mobile.

## 3) Colors

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FVWIWhXwVmvSs3hBSTUDe%2F02-colors.jpg?alt=media\&token=a45214f1-65c3-4914-a4c8-b6ce9cedf6fb)

The **“Colors”** tab allows full widget branding:

* **Backgrounds**: primary, secondary, block background.
* **Text**: primary and secondary colors.
* **Primary colors**:
  * *Primary* (brand/accent),
  * *Success* (e.g., green checkmark),
  * *Error* (error/warning color).
* **Additional**:
  * **loader** color,
  * **shadow** (cards/modals),
  * **borders** (separators).
* **Primary Button**: text color (background comes from primary colors).
* **Secondary Button**: text, background, and border color.

> Contrast tips:\
> — Verify readability of buttons and inputs in all states (hover/active/disabled).\
> — Maintain sufficient text-to-background contrast (WCAG 2.1 AA).

## 4) Text

On-screen texts are grouped into several sections. All edits are visible immediately in the live preview on the right — use arrows to switch scenario steps.

### 4.1. Start screen (onboarding + QR)

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2F0yN0LTUymLpyeFe9i9FN%2F03-intro-text.jpg?alt=media\&token=a765ea2a-1503-405c-8265-081659c35b38)

You can customize:

* Title (“Identity Verification”).
* Instruction points (prepare document, enable camera, check lighting, etc.).
* Legal note for data processing consent (editable as regular text).
* Block with **QR code** and caption (and alternative link “Copy this link…”).
* Caption for “Continue on this device” (if desktop camera is allowed).

Add/remove instruction points with “+ / trash” buttons. Rearranging is possible via drag‑and‑drop.

### 4.2. Document capture instructions

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FbSpV7zL56BIFBVeRxdH2%2F05-doc-text.jpg?alt=media\&token=f0c81920-5f41-4d82-bf9b-e42bbe85e1b5)

This screen provides hints **on how to properly photograph the document**. Typical examples:

* Remove the document from a cover;
* Place it on a flat surface;
* Hold the phone vertically;
* The document must be fully visible, do not cut edges.

Keep instructions short and clear. Avoid ambiguity: better split points like “no glare/fingers covering fields” into separate items.

### 4.3. Selfie with document instructions

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FAWjXzu6eMPGJs76BecpF%2F06-selfie-text.jpg?alt=media\&token=8c0417c2-2cb0-4165-b415-a6d966c30774)

Hints **on how to take a selfie with the document**:

* Hold the document in your hand and look at the camera while taking the photo.
* Both the document and the face must be fully visible (document next to the face, not covering parts of it).

### 4.4. Status/success texts

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FeKCK7VghI23qEkh64jiK%2F07-success-text.jpg?alt=media\&token=2ec446c6-a759-4fcf-bcbd-d60edd08693c)

Here you can modify labels shown after completing a step (e.g., “Thank you, we have received your document”, button “Continue”).\
If recognition fails, the widget displays an error screen automatically (see “Errors” in the general KYC section).

## 5) Languages

![](https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FVVJaKbrAZpCFAT75uww0%2F04-languages.jpg?alt=media\&token=f0f76c28-53af-4bd7-9273-f6df382183c3)

In the **“Languages”** tab you enable available UI locales. Common options: **English, Español, Deutsch, Français, Português**, etc.\
The widget shows a language selector; the user can choose from enabled languages.

> Recommendations:
>
> * Enable only languages relevant to your audience to avoid overloading the selector.
> * If using custom text from “Text” tab, ensure proper localization (especially for corporate wording).

***

## What appears where in the widget

* **Logos and colors** — on all steps (header, buttons, success/error icons).
* **Legal links** — on the start screen and hints where a disclaimer slot exists.
* **Texts** — on corresponding scenario steps: intro/QR → document → selfie → success/result.
* **Languages** — in the language switch menu (shown in top‑right corner).

***

## Practical branding tips

* Upload **two logo versions** — for dark and light themes.
* Use **SVG or PNG** with transparent background.
* Check button and input **contrast** in all states.
* Keep texts **short**, requirements — **list‑based**.
* On camera screens always remind about **full document visibility** and **no glare/obstructions**.

***

## Where to adjust widget behavior (non‑visual parameters)

Styling and texts are configured here, in the Web SDK Editor. Technical launch parameters (such as `schemaId`, `clientKey`, `theme`, `successCb`, `closeCb`) are passed during widget initialization on your website/app — see [**Connection**](https://nv-global.gitbook.io/docs/produkty/kyc/api-i-integraciya/web-sdk/installation) and [**Working with clientKey**](https://nv-global.gitbook.io/docs/produkty/kyc/api-i-integraciya/web-sdk/clientkey).

***

**Done.** After saving Web SDK settings, all new KYC sessions will show the widget with your branding and text content.