Help Center
Our products knowledge base for customers
Steps
Steps
Steps are used to configure the basic KYC procedure and additional verification levels. Each step in the platform is created by linking an existing questionnaire to it. The exception is a step with the Connector provider: no questionnaire is linked to it.
![]()
The steps in the table are represented by records containing the following fields:
| Name | Description |
|---|---|
| ID | Unique identifier of the step in the platform. |
| Name | Step name. |
| Step type | Step type (Internal - a questionnaire created inside the platform, Sumsub - a questionnaire created in the Sumsub service, Document - a step containing a document template previously created in the Documents section, Connector - a step that uses a connector). |
| Step content | Name of the questionnaire or other content used in the step. |
| Expiration time | Validity period of the step after verification. If a period is set, once it expires, the client must complete the step again and receive a new verification. |
| OTP Required | Set to Yes if one-time password signing is enabled for the step. |
| Unavailable without previous step's verification | When set to Yes, the client cannot proceed to this step until the previous mandatory steps have been verified by the broker. |
| Auto accept | Set to Yes if the step is verified automatically once the client submits it for verification. |
| Code | Step code that can be used in the Documents section. |
Each step can be opened for editing by clicking Edit in its row.
Please note! The steps in the table are always sorted in ascending order of ID.
Creating a new step
The Create step button opens the sidepage for creating a new step. To create a step, select a Provider, specify its Name for the required locales, and link an existing Questionnaire to it (a step with the Connector provider does not need a questionnaire). After clicking Create, the new step becomes available for use in the KYC settings.
![]()
Please note! Each created questionnaire can only be used in one step.
When creating a step, you can also specify:
| Name | Description |
|---|---|
| Code | Step code for further use in the Documents section. |
| Expires in | Validity period of the step after verification. Specified in years, months, and days. |
| OTP Required | Enables page signing using a one-time password. |
| Unavailable without previous step's verification | Prevents proceeding to the current step until the previous mandatory steps have been verified by the broker. |
| Auto accept | Automatically verifies the step once the client submits it for verification. |
The OTP Required checkbox in the step settings enables page signing using an SMS or WhatsApp message. In this case, when submitting the questionnaire for verification, the client must enter the code from the message sent to their phone number or WhatsApp.
If the Unavailable without previous step's verification checkbox is enabled, the client cannot proceed to the current step until the previous mandatory steps have been verified by the broker in the Applicants tab. This restriction applies both to the basic KYC procedure and to additional verification levels.
A client who has submitted a questionnaire for verification but has not yet received confirmation will see the following message: "Next verification steps will become available once this stage is completed. Thank you for your patience!"
If the Auto accept switch is enabled, a step submitted by the client for verification is verified immediately: the broker does not need to confirm it in the Applicants tab. The client receives a notification that the step has been verified and can no longer edit the submitted questionnaire. The Expires in period starts from the moment of automatic verification. This setting is intended for steps in which the client does not enter any data, for example, steps consisting only of text.
Please note! The OTP page signing feature works if the corresponding authorization method - phone number or WhatsApp - is enabled in the authorization block of the broker settings.
Creating a step containing a document
Please note! To create such a step, document templates must first be created in theDocumentssection. The document templates that will be displayed on the questionnaire page are specified in theDocument templatefield.
![]()
Fields to fill:
| Name | Description |
|---|---|
| Provider | Document |
| Name | Step name. |
| Code | Step code used to display OTP-related formulas in the Documents section. |
| Document title | Title displayed in the document window when completing KYC. |
| Document description | Document description. |
| Document footer | Text displayed to the client in the document footer. |
| Document template | Selected document templates from the Documents section that will be shown to the client at a specific KYC step. |
| Expires in | Document validity period before the client needs to upload it again. |
| OTP Required | When enabled, the client must verify the questionnaire using an OTP code. |
Please note! If an expiration period is set for the step, this field will be locked for editing during verification.
Important! In theFormulastab of the Documents section, formulas related to signing questionnaires usingOTPare displayed only if aCodeis specified for the step.
Creating a step with a connector
Please note! A step with a connector is not available for all brokers: it requires a KYC App connector to an external client screening service. Unity staff connect the service. The fields the service needs and the rules by which it sets the step status depend on the connected service.
A step with a connector sends client data to an external screening service. No questionnaire is linked to such a step: the data is taken from questionnaire fields the client filled in at previous steps. The step status is set by the service based on the screening result.
Fields to fill:
| Name | Description |
|---|---|
| Provider | Connector |
| Connector | The KYC App connector used for screening. The connector cannot be changed after the step is created. |
| Name | Step name. |
| Code | Step code for further use in the Documents section. |
| Provider level | Required step identifier the platform uses to match the screening result to the step. It cannot be repeated in different steps of the broker. |
| Output fields | Questionnaire fields the service response is written to. For each field, specify the Name - the parameter name in which the connector passes the service response, and the Code - the code of the questionnaire field. |
| Input fields | Fields whose values are sent to the service. For each field, specify the Name - the parameter name the connector expects to interact with the service, and the Code - the questionnaire field code. |
| Expires in | Validity period of the step after verification. |
The Code is selected from the list of codes set for fields in the Fields section. If none of the broker's fields has a code, the Output fields and Input fields blocks are not displayed in the form.
The Name is entered manually. The set of valid names is defined by the connector to the connected service - Unity staff provide it. Names are not validated when the step is saved: a mistake in a name shows up only when a client is screened.
OTP signing is not available for a step with a connector.
The Content block sets the texts the client sees at the step. The texts are filled in separately for each locale:
| Name | Description |
|---|---|
| Title | Title of the data submission confirmation screen. |
| Description | Description on the data submission confirmation screen. |
| Notes | Note on the data submission confirmation screen. |
| Pending message | Text the client sees while screening is in progress. |
| Success message | Text the client sees after successful screening. |
| Reject message | Text the client sees if the step is rejected. |
If the Request confirmation to send setting is enabled, the client opening the step sees a screen with the Title, Description and Notes texts and submits the data for screening with a button. If the setting is disabled, the data is submitted for screening as soon as the client opens the step.
Important! The questionnaire with theInput fieldsfields must come before the step with a connector inSteps in flow. If a field the service needs is not filled in, screening is not performed: the client sees an error message, and the step status does not change.
Editing a step
The Edit button allows you to edit an existing step. Depending on the step type, you can change its Name, Code, linked Questionnaire, Expires in period, as well as the OTP Required, Unavailable without previous step's verification, and Auto accept settings. After clicking Update, the changes are applied.
![]()
To delete a step, click Delete.
Please note! A step can only be deleted if it is not used in the KYC settings, including the basic verification step order and additional verification levels.