Wizards
The Wizards tool provides you with an opportunity to configure some parts of workflow on the side of the Back Office.
Adding and configuring the wizards is carried out at the level of the system source code. For each wizard, a list of default steps and a list of available steps are set. On the Back Office side, you can add/remove steps from the available ones, change their order and priority.
You can have more than one configured wizard for each workflow scenario. In this case, you need to select the default one which will be used by the B2Core UI. The other scenarios can be used by external systems to perform the actions via the API.
The following is a list of wizards supported in B2Core. The steps that will be added to wizards by default are marked as required.
Registration
Registering a new client in the system. Each step of the wizard can have display restrictions (for example, restrictions by user type or by country). For this wizard adding the custom fields is available for steps Main form and Additional information.
Step |
Description |
Priority |
---|---|---|
Main form required |
The system waits for basic client information |
First |
Client registration required |
Registering a new client based on the previously entered data |
Last |
Client type |
The system waits for information about the type of client being created |
Not the first and not the last |
Confirmation by email |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the first and not the last |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Not the first and not the last |
Captcha |
Captcha creation |
Not the first and not the last |
Client phone number form |
The system waits for information about the client’s phone number |
Not the first and not the last |
Additional information |
The system waits for additional information about the client |
Not the first and not the last |
Password Recovery
Recovery of the client’s password via the B2Core UI.
Step |
Description |
Priority |
---|---|---|
Client identification required |
Search for a client in the system by the email sent in the request |
First |
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the first and not the last |
Password change required |
The system waits the new entered password from the client and registers it as the current one |
Last |
Password change
Changing of the client’s password via the B2Core UI.
Step |
Description |
Priority |
---|---|---|
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the last |
Password change required |
The system waits the new entered password from the client and registers it as the current one |
Last |
Client type change
Changing of the current client type to corporate.
Step |
Description |
Priority |
---|---|---|
Blank form required |
— |
First |
Detailed corporate information |
The system waits for detailed corporate information from the client |
Not the first |
Additional corporate information |
The system waits for additional corporate information from the client |
Not the first |
Bank information |
The system waits for information about the bank from the client |
Not the first |
Bank information |
The system waits for information about the bank from the client |
Not the first |
Representative person information |
The system waits for information about the representative from the client |
Not the first |
Director and shareholders information |
The system waits for information about the director and shareholders from the client |
Not the first |
Confirming the previously entered information |
The system waits for the client to confirm that all information entered in the previous steps is correct and up-to-date |
Not the first |
Uploading corporate documents |
The system waits for the client to upload files confirming the previously entered information |
Not the first |
Profile change
Changing of the basic information about the client.
Step |
Description |
Priority |
---|---|---|
Update information required |
The system waits for updated client profile information |
Single |
Phone change
Changing of the client’s phone number.
Step |
Description |
Priority |
---|---|---|
Update phone number required |
The system waits for client’s new phone number |
First |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Last |
Address change
Changing of the client’s address.
Step |
Description |
Priority |
---|---|---|
Update address required |
The system waits for client’s new address |
Single |
2FA change
Disabling 2FA.
Step |
Description |
Priority |
---|---|---|
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the last |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Not the last |
Disabling 2FA required |
The system disables 2FA for the client |
Last |
Whitelist creation
Creating white lists for wallet addresses.
Step |
Description |
Priority |
---|---|---|
Creating white list required |
The system creates a new white list for entered |
First |
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the first |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Not the first |
Whitelist delete
Deleting a previously created white list.
Step |
Description |
Priority |
---|---|---|
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Any |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Any |
Whitelist change
Disabling a previously created white list.
Step |
Description |
Priority |
---|---|---|
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the last |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Not the last |
White list disabling required |
The system disables the white list |
Last |
Withdrawals
Processing the withdrawal operations. A Client Request will be created, the status of the created withdrawal will be set to Pending
.
Step |
Description |
Priority |
---|---|---|
Creating new withdrawal required |
The system creates a new withdrawal operation with status |
First |
Confirmation by email required |
The system sends a verification code to the client by email and waits for this code to be entered |
Not the first |
Confirmation by phone |
The system sends a verification code to the client by the phone and waits for this code to be entered |
Not the first |
Wizards
In the Wizards subsection of the Back Office you can a view a list of all available wizards and its statuses:
- ID
Wizard identifier in the system
- Name
Internal system name of the wizard
- Type
Type of workflow
- Enabled
If
Yes
, the wizard is active- Default
If
Yes
, the wizard is used by default for the selected type of workflow (for example, if you have several configured registration wizards at the same time)
To see wizard details, click the Edit button. Detailed information contains the following tabs:
Wizard — main wizard parameters.
Workflow — steps of the wizard with priority. You can add/remove available steps and configure Country/Client Type restrictions for each step (Actions).