Back

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 are displayed. 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 switch specifies the theme in which the interface is being designed:

  • Dark / Light — the selected theme is used in the preview and as the default when launching the widget (if not overridden by the theme parameter during initialization).
  • Logos and contrast elements are configured separately for each theme (see “General”).

2) General

The General tab is responsible for branding and legal links:

  • Logo
  • *For the dark theme* — upload a logo variant that is clearly visible on a dark background.
  • *For the light theme* — a separate version for a light background.

Recommendations: PNG/SVG with a transparent background, without thin light-gray lines on a light theme and vice versa — for good readability.

  • Terms & Conditions (URL) — a link to your “Terms & Conditions”.
  • Privacy Policy (URL) — a link to your Privacy Policy. These links are displayed in the widget on the start screens and help meet legal requirements.
  • Allow desktop PC camera usage (checkbox)
  • Enabled — the user can take the course on this device (the “Continue on this device” button), and the camera and photo upload work in the desktop browser.
  • Disabled — prompts to switch to a phone via QR code/link; recording is performed on a mobile device.

3) Color

The “Color” tab allows you to fully brand the widget:

  • Backgrounds: primary, secondary, block background.
  • Text: primary and secondary colors.
  • Main color:
  • *Starter* (accent/brand),
  • *Success* (e.g., a green checkmark),
  • *Error* (error and warning color).
  • Additional:
  • color of the loader,
  • shadow (for cards/modals),
  • borders (borders/dividers).
  • Primary Button: primary button text color (background inherits from the primary colors).
  • Secondary Button: text color, background, and border of the secondary button.

Contrast tips: — Check the 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 edited in several groups. All changes are immediately visible in the live preview on the right — you can scroll through the scenario steps using the arrows.

4.1. Start screen (onboarding + QR)

Here are set:

  • Heading (“Identity Verification”).
  • Introductory instruction points (prepare the document, turn on the camera, ensure proper lighting, etc.).
  • Legal disclaimer regarding consent to the processing of personal data (configured as plain text).
  • Block with a QR code and its caption (as well as the alternative link “Copy this link…”).
  • Button label “Continue on this device” (appears if the PC camera is allowed in “General”).

Add/remove instruction steps using the «+ / trash» buttons. The order can be changed by dragging.

4.2. Instructions for photographing the document

A separate screen with tips on how to properly photograph a document. Examples of typical points:

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

Try to formulate short and clear requirements. Avoid ambiguity: it is better to list “no glare/fingers obscuring the fields” as a separate point.

4.3. Instructions for a selfie with a document

Tips on how to take a selfie with a document:

  • Hold the document in your hand and look at the camera when taking the photo;
  • The document and your face must be fully visible (the document should be next to your face, not covering any part of your face).

4.4. Status/success texts

Here you can change the labels on the screens after completing the step (for example, “Thank you, we have received your document”, the “Continue” button text, etc.). If recognition fails, the widget will automatically render a screen indicating the reason (see the “Errors” section in the general KYC section).

5) Languages

In the “Languages” tab, available interface locales are checked. They often include: English, Español, Russian, Deutsch, Français, Português, and others. A language switcher is displayed in the widget; the user can select a preferred language from the enabled ones.

Recommendations:

* Include only the languages that are relevant to your audience to avoid overloading the switcher.

* If you use custom wording in “Text”, coordinate the translation with localizers (for corporate wording).

What is displayed where in the widget

  • Logos and colors — on all steps (top area/header, buttons, success/error icons).
  • Legal links — on the start screen and in tooltips, where space is provided for a disclaimer.
  • Texts — at the corresponding steps of the scenario: introduction/QR → document → selfie → success/result.
  • Languages — in the language switcher menu (visible in the top right corner of the widget).

Practical branding tips

  • Upload two versions of the logo — for dark and light themes.
  • For logos, use SVG or PNG with a transparent background.
  • Check the contrast of buttons and fields in all states.
  • Make texts short, requirements — itemized.
  • On screens with a camera, be sure to remind about the full visibility of the document and the absence of glare/obstructions.

Where to edit widget behavior (non-styling parameters)

The design and texts are configured here, in the Web SDK editor. Technical launch parameters (for example, schemaId, clientKey, theme, successCb, closeCb) are passed during widget initialization on your website/application side — see the Installation and Working with clientKey sections.

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