In the 'Options' section settings of enterprise, its merchants and users can be changed. This section is available only for users who have appropriate rights.
Enterprise options
In this section settings of the enterprise can be changed. It has 'Common' and 'Banking details' tabs.
Common
Common enterprise's data is displayed on the 'Common' tab. See table below for details.
List of enterprise data that is displayed on the 'Common' tab
Name | Description |
ID | System Enterprise ID (for reference only) |
Name | Full enterprise name |
Administrative contact | Administrative contact (Name, Position, Phone, Mobile phone, E-mail) – editable fields, you can specify multiple addresses separated by commas in the E-mail field. |
Technical contact | Technical contact (Name, Position, Phone, Mobile phone, E-mail) – editable fields, you can specify multiple addresses separated by commas in the E-mail field. |
Legal address | Legal enterprise address (for reference only) |
Post address | Postal address of the enterprise (for reference only) |
Time zone | Enterprise time zone (for reference only) |
All changes are applied after pressing 'Save' button.
Only enterprise administrator can change these settings.
Banking details
The bank requisites of the enterprise are displayed on the 'Banking details' tab. See table below for details.
List of enterprise data that is displayed on the 'Bank details' tab
Name | Description |
Bank | Bank name |
BIK | Bank identity code |
OKVED | OKVED of the enterprise |
OKPO | OKPO of the enterprise |
Payment account | The enterprise payment account |
Correspondent account | The enterprise correspondent account |
TIN | The enterprise TIN |
Accountant E-mail | Accountant E-mail |
KPP | The enterprise RPP |
All changes are applied after pressing 'Save' button.
Only enterprise administrator can change these settings.
Merchant options
This section allows to see and to change merchant settings. The choice of a subsection (group of settings) is made using the menu on the right side of the screen. All subsections contain drop-down boxes in header that set the merchant which data are displayed on the subsection.
The settings subsection selection menu
Common options
The list of merchant data, which are displayed on this subsection is described in the table below.
Common merchant properties
Name | Description |
ID | System merchant ID (for reference only) |
Enterprise | The merchant's enterprise (for reference only) |
Name | Names of the merchant in different languages (editable) |
Goods and services | Goods and services that merchant provides (for reference only) |
URL | Merchant's URL (editable) |
Administrative contact | Administrative contact (Name, Position, Phone, Mobile phone, E-mail) – editable fields, you can specify multiple addresses separated by commas in the E-mail field. |
Technical contact | Technical contact (Name, Position, Phone, Mobile phone, E-mail) – (editable fields), you can specify multiple addresses separated by commas in the E-mail field. |
E-mail to receive fraud information | E-mail that is used for notifications about fraudulent transactions – (editable fields) |
Name (merchant name) can be provided in different languages. Write down the name's translations next to corresponding languages.
All changes are applied after pressing 'Save' button.
Payment options
The list of merchant data, which are displayed on this subsection is described in the table below.
List of merchant's settings displayed on the 'Payment options' subsection
Name | Description |
Base currency | Code and name of merchant's base currency (for reference only) |
Test mode | «Yes» - The merchant is in the test payment mode «No» - The merchant is in the production payment mode (for reference only) |
Timeout | Timeout (in minutes), customer can enter his personal data and card data during that time period. When time is up transaction is closed with time-out status. |
URL_RETURN | URL, which is used to redirect customer in one of 2 cases: 1) in case of unsuccessful payment if 'URL_RETURN_OK' is filled; 2) in all cases if 'URL_RETURN_OK' is not filled. 'Action after authorization' should be set in 'Redirect to merchant page' to redirect customer by 'URL_RETURN'. It is recommended to use HTTPS protocol for secure communication. |
URL_RETURN_OK | If 'Action after authorization' is set to 'Redirect to merchant page' then customer is redirected by this URL after successful payment. It is recommended to use HTTPS protocol for secure communication. |
Action after authorization | Drop-down list that sets the system behavior after finishing of payment: 'Redirect to merchant page', or 'Redirect to authorization result page' |
Secret word | Merchant’s secret word. |
All changes are applied after pressing 'Save' button.
Please note that values of 'URL_RETURN_OK' and 'URL_RETURN' are used only when 'Action after authorization' is set to 'Redirect to merchant page' and if the authorization request does not contain URL_RETURN, URL_RETURN_OK, URL_RETURN_NO (otherwise request parameters are used; request parameters have a higher priority).
Bill options
This subsection provides a reference only information about general bill settings: the algorithm of the bill numbering, template of the bill number, version of payment token and display bill settings.
In this subsection you can also view and edit such parameters as bill payment expiration period, whether to send the bill to the customer via E-mail after the bill creation, as well as whether to send notice of bill revoke.
List of merchant's settings displayed on the 'Bill options' subsection
Name | Description |
A method of forming a bill number | For reference only. |
Bill number template | Template to generate of bill numbers. For reference only. |
Token | For reference only. |
Show bill before payment | Check box. By default, bill is shown to the customer when he/she has followed by the payment link. If it is not checked then, the customer immediately goes to the payment page. For reference only. |
Period of bill payment | Expiration period of bill payment, displayed as DD.HH.MM, by default – 1 day. This field can not be empty or null. When parameter Pay_until is not passed in the bill creation via web-service then Pay_until is calculated as the bill creation time plus value of this setting. This parameter also used to determine the "Pay until" value during the bill creation in personal account. |
Send notice of bill revoke | Check box is responsible for sending of notifying about the revoking of the bill. By default, notice is send. |
Secret word | Merchant’s secret word. (for reference only). You can set it in the ” Payment options ” section. |
Check value for bills | Check box is responsible for using of check value code when creating bill. |
Default values | |
Send bill | Drop-down box: Don’t send, Send via E-mail, Send via SMS, Send via E-mail and SMS. |
Source of cheque items | Drop-down box: No (cheque items are entered manually), Price list (cheque items can be entered either manually or loaded from the price list), Only price list (cheque items can be loaded only from the price list). |
Double-stage operation mode | Check box. If it is checked then payments in double-stage operation mode on the bills of this merchant are allowed. |
First name | Payer's first name |
Last name | Payer's last name |
Part of the parameters in the "Bill options" subsection are displayed for reference only. Contact the support team to change these parameters.
All changes are applied after pressing 'Save' button.
Payment result options
The sending of authorization results to the merchant's server can be set up on the 'Payment result options' subsection.
For security reasons results are sent only on ports 443, 8443, 80, 8080. No other ports can be used to receive the results!
If sending of payment results is activated and notification sending has failed then a special e-mail notification is sent to the address, which is specified in the parameter "Technical contact" on tab "Common options" under "Merchants options."
The list of merchant data, which are displayed on this subsection is described in the table below.
List of settings on ’Payment result options’ subsection
Name | Description |
Send approve results | Check box. If it is checked then results of payments are sent. |
Send cancel results | Check box. If it is checked then cancellations results are sent. |
Send order positions | Check box. If it is checked then order positions are sent. |
Send fiscal results | Check box. If it is checked then fiscal results are sent. |
Send charge results | Check box. If it is checked then results of charges are sent. |
Send only success results | Check box. If it is checked then only successful results are sent. It is active only when at least one of above is selected. |
Sending results awarding points to the merchant server | Check box. If it is checked then results of bonus point accruals are sent. It is actual for merchants, which use 'Thank YOU' program of SberBank. |
Sending results cancellation awarding points to the merchant server | Check box. If it is checked then results of bonus point accrual cancellations are sent. It is actual for merchants, which use 'Thank YOU' program of SberBank. |
Merchant URL | URL that used for results delivery |
Protocol type | Protocol type – POST or SOAP |
Sign type | Signature type – PGP or md5 |
Secret word | Secret word for md5 signature (for reference only). You can set it in the ” Payment options ” section. |
Response type | Type of expected response on the results' sending from merchant's server (for reference only) |
Fiscal settings
You can view the current fiscal settings for the merchant on the 'Fiscal settings' subsection.
Fiscal settings *
Name | Description |
Generate a fiscal cheque for card payments | If checked then permits the generation of fiscal cheques for payments by cards to the merchant is allowed. |
Generate a fiscal cheque for e-wallets payments | If checked then permits the generation of fiscal cheques for payments by e-wallets to the merchant is allowed. |
Generate a fiscal cheque for non-electronic means | If checked then permits the generation of fiscal cheques for payments by non-electronic means to the merchant is allowed. |
Merchant works with external fiscalization | If checked then the merchant uses external fiscalization for its payments |
The stage of the cheque creation/notification | Authorization or Charge. The Charge can only be applied to the double-stage payment. |
Do not send fiscal cheque | Permission not to send fiscal cheques to customers. |
Default payment method | The default payment method (in the mode without transfer of the cheque items). |
Address of payment place | The address of the payment place, printed in the cheque (or domain address when buying online). |
Default tax rate | The default tax rate (in the mode without transfer of the cheque items). |
Default taxation system | The default taxation system (in the mode without transfer of the cheque items). |
URL of FDO | URL address of FDO |
Default text of cheque item | The default name of the product (in the mode without transfer of the cheque items). |
Default text of cheque item for external payments | The default name of the product (in the mode without transfer of the cheque items during fiscalization of external payments). |
Send notification on a failed payment | If checked then notification will be sent to the buyer in case of unsuccessful payment. |
Cheque sender E-mail | E-mail address of the cheque sender (as agreed with the merchant). |
Default customer E-mail | The default customer E-mail address. |
* All the parameters in the "Fiscal settings" table are displayed for reference only. Contact the support team to change the fiscal settings.
Registry and notifications sending options
There are two blocks of settings on this subsection. List of settings, which are related to 'Daily registry' are described in table "List of settings for Daily registry". List of settings, which are related to 'Notifications' are described in table "Notifications settings".
List of settings for Daily registry
Name | Description |
Send daily registry | If checked then every day the daily registry is sent to the specified e-mail. |
E-mail to receive registry | Sets the e-mail(s) for registry delivery (use comma (',') as e-mails list separator) |
Report type | Drop-down box that sets type of transaction that are included in the registry: All, Only successful, All except unsuccessful |
Time zone in the registry dates | Sets time zone of date/times in the registry: GMT or enterprise time zone (that is set in the Enterprise options) |
Decimal delimiter | Sets the point ('.') or comma (',') for decimal delimiters |
Send daily registry for | The control allows to enter the year, month, day as the date for which you want to resend the registry. Note. You can order the registry only for the past dates, not later than yesterday. To build and send the registry, click the "Send" button. The "Send" button is only active when the checkbox «Send daily registry» is checked. |
If sending is enabled then every day the daily registry (prepared according to selected type) is sent to the specified e-mails. E-mail message contains the TXT file with payments. If no payment were made then the file contains 'NO PAYMENTS THIS DAY' text.
Example of one row from the registry file
BillNumber:000000000000001;BillNumberExt:000000000000001.1;OrderNumber:0001-01; OrderState:Approved; OrderTest:1;OrderAmount:100.00;OrderCurrency:RUB;OrderDate:01.01.2011 07:00:05;OrderComment:тестовый платеж;CustomerName:Testov Test T.;OperationType:Approve;OperationState:Success;Protocol:NET; OperationAmount:100.00;OperationCurrency:RUB;OperationDate:01.01.2011 07:00:08;MeanType:VISA; MeanSubType:Visa Gold;MeanNumber:411111****1111;CardHolder:Testov Test;OperationResult:Success; ErrorMessage:;Recommendation:;Response_Code:AS000;ApprovalCode:F00001;ProcessingName:Name;
Notifications are e-mail messages, which are sent after finishing of the payment. Each message contains payment details
Notifications settings
Name | Description |
E-mail to receive notifications | Sets the e-mail which is used for notification delivery |
Send pay notification | If checked then notifications are sent after payment completion |
Send pay approve notification | If checked then notifications are sent after payment confirmation completion (charge) |
Send pay cancel notification | If checked then notifications are sent after payment cancellation completion |
A payment notification example:
BillNumber: 000000000000001 OperationType:Approve OrderNumber:0001-01 Total:100.00 Currency:RUB Status:Approved Comment:Test payment Response_Code:AS000 MeanType: MasterCard
A confirmation (charge) notification example:
BillNumber: 000000000000001 OperationType:Charge OrderNumber:0001-01 Total:100.00 Currency:RUB Status:Approved Comment:Test payment Response_Code:AS000 MeanType: MasterCard
A cancelation notification example:
BillNumber:000000000000001 OperationType:PaymentCancel OrderNumber:0001-01 Total:100.00 Currency:RUB Status:Canceled Comment:Test payment Response_Code:AS000 MeanType: MasterCard
Limit options
This tab shows the limits of merchant in table. The table displays:
- limit name;
- limit current values;
- thresholds values.
Active limits are checked in the 'Active' column. Limits are displayed in read-only mode. Contact the support team to change limits.
Order signature options
When the merchant uses up the order check value (MD5) and/or the order signature the settings for this checks can be configured on this tab. Parameters are described in the table below.
Order signature settings
Name | Description |
Check order code (MD5) | |
Check order code (MD5) | If checked then the order value (MD5) is verified on the request receiving. |
Secret word | Merchant’s secret word. Note! The same secret word is used for the order check value and for the payment result options. |
Check order signature | |
Check order signature | If checked then the order signature is verified on the request receiving |
New public key | You need to generate the RSA public key with length of 1024 bits and upload it as a * .pem format file by button «Select files» which allows to select a file with public key. |
Current public key | Field that displays current public key (for information only) |
Period when new and old keys are valid (days) | Period in days, during which the old key and new one are both active. It is transition period to smoothly move to a new key on the old key expiration. If the old key should be deactivated immediately after new one applied – contact the support team to settle it. |
All changes are applied after pressing 'Save' button. Message appears on save which informs that new key is activated and the old one will be deactivated soon.
If merchant has activated order check value (MD5) verification then authorization request must contain the 'Checkvalue' parameter with correctly calculated value. Otherwise requests will be denied with error. The 'Checkvalue' parameter has to be generated as follows: uppercase(md5(uppercase(md5(SALT) + md5(Х)))), where SALT – secret word; Х – result of the following parameters string concatenation: merchant_id, ordernumber, orderamount, ordercurrency (without delimiters), + means string concatenation.
If merchant has activated order signature checking then authorization request must contain the 'Signature' parameter with correctly calculated value. Otherwise requests will be denied with error. See more details about order signature in 'Setting up an enterprise's technical interaction' manual.
One Click
Merchant parameters on One Click are displayed on this subsection. Parameters are not editable and they are displayed for information only. Contact support team to change One Click parameters. One Click parameters are described in the table below.
One Click parameters
Name | Description |
Enable One Click | If checked then One Click is activated for the merchant |
Mode | Drop-down box: Standerd (the buyer can store new cards to the program or pay with previously stored cards), Payments by stored cards only (the buyer can pay with stored cards only), Cards store only (the buyer can only store new cards to the program). |
In expandable block 'Customers' of One Click tab you can see the information about a customer by his unique number (that merchant assigned to that customer and sent in the authorization request as value of parameter 'CustomerNumber'). Value of 'CustomerNumber' also must be included in the order signature.
Enter the desired CustomerNumber into the field and press 'Search'. The information about customer will be displayed on screen. If the "Customer number" field is empty and you click the "Search" button, then the full list of One Click clients of this merchant will be displayed as search results.
One Click details of the customer
Possible values of customer status:
Status name | Description |
New | Customer who have made some successful payments but not agreed to store the card for future payments. The customer will have the same status also, if his first payment was unsuccessful or closed after the timeout. |
Member | Customer who agreed to store the card for future payments. |
Not active | When the all stored cards of this member are expired or not valid. The status is set automatically. |
Deny | Customer has rejected the offer to activate One Click. |
Fraud (highlighted in red) | 100% fraud status was received from System Of Fraud Intelligence (SOFI) during the payment by this card or 'Card stolen' status received from the processing. Payments by this card are blocked. |
Suspicious (highlighted in yellow) | Received a fraud status from System Of Fraud Intelligence (SOFI) for one of the cards of this customer (when paying to any merchant). The status is set automatically, but it can also be set manually. |
By right click on the desired customer record you can change the customer status.
If a customer makes payments to a merchant with different bank cards, each of them is included in the One Click program using the same rules. With payment for the next order, the customer has the opportunity to choose the desired card from the drop-down list of his stored payment means (for which there were successful payments).
Clicking on the black triangle at the beginning of the line with the customer record allows you to open an additional window. Here you can see the data on all the saved cards of this customer in a table with the following columns.
Name | Description |
Mean number ID | Unique identification of payment mean number. |
Mean type | Payment mean type (Visa, MasterCard etc.). |
Mean number | The payment means number, for example card number. Only 6 first and last 4 digits are shown in the card number. |
Saving date | Date of saving the card with the first successful payment. |
Last success payment date | Date and time of the last successful payment by this payment mean. |
Number of successful payments | The number of successful payments by this card. |
Order | The order of the last payments on the cards of this customer. By default at the next payment, the client will be offered to pay for the order with the last used card (Order 1). |
Card state | Card state. |
COF status | COF payment type in processing. |
Possible values of customer card state:
State name | Description |
Member | One or more payments were successfully made on this card and the customer agreed to store it. |
Fraud | 100% fraud status were received from Anti-Fraud system during the payment by this card or 'Card stolen' status received from the processing. Payments by this card are blocked. |
Card expired | A card that has expired. |
Deleted | The card has been removed from the One Click service. |
Information on customer cards
By right click on the desired card record you can delete this card from One click program data base.
An additional confirmation prompt appears before the card is deleted. Before deleting the card the confirm window will appear as it shown on the picture below.
Confirm window for card deleting
More details about One Click can be found in documents of section One Click program.
Token Pay
IPS Assist provides a processing service for payments via token (e.g, Apple Pay). This tab displays information about payment permissions for this merchant via various payment services and information about certificates of the merchant. Also you can upload the signed certificate for payments via tokens through Assist system.
The top of the tab displays the following information about payment permissions via payment services:
- check-box «Allow payment via Apple Pay on the payment page»;
- check-box «Allow payment via Google Pay on the payment page»;
- check-box «Allow payment via Samsung Pay on the payment page»;
- check-box «Allow payment via Mir Pay on the payment page»;
- check-box «Allow payment via QR-code on the payment page».
This information is displayed for reference, please, contact support team for setup the payments via payment services.
Information about current merchant certificates is displayed below separately for various payment systems.
For getting rights to change token pay settings, please, contact support team ( support@assist.ru ).
Apple Pay certificates
The table of current merchant Apple Pay certificates is displayed below.
Certificate parameters for the token payment
Name | Description |
Type | Type of certificate, e.g. Apple Pay |
Public key hash | Public key hash, created by IPS Assist. |
Valid | The validity of the downloaded certificate. |
State | Current status of the certificate (Request – certificate is creating, Active – certificate is active, Expired - the certificate has expired). |
By pressing of "New Certificate" button you get the window, where you can find the description of required steps that you have to perform to receive the signed certificate. You also can upload the signed certificate here.
Uploading of the signed certificate
Click on "Upload signed certificate" opens a standard browsing window for selection of a signed certificate file.
Generation of the certificate signing request file and the upload the signed certificate can be only done by using browsers Chrome, Firefox, Edge, Opera and Safari (for Mac).
If uploading the certificate has not been completed and the upload window is closed, in the certificates table is created the certificate with the status «Request» and validity time of this certificate is missing. Uploading of the signed certificate can be done later - this action is available via the context menu
Context menu
Get CSR
Upload signed certificate
Delete
jumps to action to create and upload the certificate (Picture "Uploading of the signed certificate");
allows to upload the available signed certificate;
removes the certificate from the table row.
Mir Pay certificates
The table of current merchant Mir Pay certificates is displayed below.
Certificate parameters for the token payment
Name | Description |
Type | Type of certificate, e.g. Mir Pay |
Public key hash | Public key hash, created by IPS Assist. |
Valid | The validity of the downloaded certificate. |
State | Current status of the certificate (Active – certificate is active, Expired - the certificate has expired). |
The merchant generates a secret key and a CSR (Certificate Signing Request). In a CSR, the Organizational Unit Name (OU) field of the Subject element must be entered with the value MerchantId (the number of the merchant registered in IPS Assist). The MerchantId value must consist of 15 characters M000...00<EXTMERCHANT_ID>, where EXTMERCHANT_ID is the unique identifier generated during registration. The keyUsage element must specify the purpose of the "digitalSignature" key.
At the initial registration of the certificate, the registration of the merchant in the NSPK is obligatory. Therefore, the box "Register a new merchant in the NSPK" is checked and inactive. There is also an information that no certificate has been generated yet.
Mir Pay certificate block header
Next, you should upload the certificate request using the "Upload CSR" button, then a standard browser window will open for selecting a CSR file.
After loading the request, a certificate line is created in the table with the status "Active" and its validity period. Above the table is a link to a pre-made JSON Web Key Set (JWKS) with this certificate. The certificate can also be downloaded separately, using the context menu (Get certificate).
Mir Pay certificates table
After the successful registration of the merchant in the NSPK, the "Register a new merchant in the NSPK" checkbox becomes active and is automatically unchecked. If in the future you need to generate a new certificate (for example, the existing certificate has expired), then registration in the NSPK will no longer be required.
If, for some reason, re-registration in the NSPK is necessary, then the checkbox "Register a new merchant in the NSPK" should be re-checked before uploading the certificate request using the "Upload CSR" button, in this case a special warning is issued:
Re-registration warning
mPOS settings
The tab is intended for the merchants, which are working with the mobile application Assist mPOS.
The list of the parameters, which are displayed on this tab is described in the table below.
mPOS settings
Name | Description |
The merchant WEB service | |
URL | Address for request of the order data via web service from information system of the merchant or shipping company. |
Login | The name of the user account for accessing the web service of merchant or shipping company. The entered value for the merchant's web service is not validated. |
Password | The password of the user to access the web service of merchant or shipping company. The entered value for the merchant's web service is not validated. The password is not displayed on the screen. |
Automatic order number generation | Checkbox, enables automatic generation of order number in the Assist mPOS application, if checked. |
Options | Additional special parameters for the merchant work with the Assist mPOS application in the format: <parameter>=<value>, <parameter> =<value>. The list of parameters is currently under construction. |
All changes are applied after pressing 'Save' button.
Change password
This section is used to change password of current user.
Enter the 'Current password' then 'New password' and repeat a new password in 'Confirm password' field.
Password should be 8 to 20 symbols long and should contain Latin alphabet symbols (upper/lower case) and digits. Password must contain both – alphabet symbols and digits.
Password changes after pressing 'Save' button.
Two-factor authentication
To increase the level of security of enterprise data in the Personal Account, you can additionally use two-factor authentication. A special code, which can be obtained using a mobile device (smartphone), is used in addition to the main account password. You should download the application and choose a more convenient way to get the code.
This section displays a brief instruction on how to enable two-factor authentication, and there is also a field for entering a special verification code.
Users
In this section you can see and change users of the enterprise. Only enterprise administrator has rights to amend and create new users.
Actions over users
Enterprise administrator has rights to create a user.
In addition, administrator can perform the following action on existing users:
- User password change;
- Enabling/disabling the user possibility to change own password;
- User details change;
- User rights amendment;
- Changing of user rights on the tab "Operations";
- User – Merchant assignment change;
- User deletion.
Create new user window
For example, a user should be created to monitor orders in 'Order monitor'. The following steps should be done:
- Press 'New User' button and enter all necessary user information in the dialog box (Login, Password, Confirm password, select the 'User's type' as 'USER', select the user default language, required parameters are marked with asterisks);
- Press 'Save' button. The new user will appear in table;
- Right-click on the new user in the table and select 'Edit Rights';
- In the Roles section of the Edit Rights tab set the check mark in the 'User' row in Access column (Picture "Adding a role to user" below);
- On the 'Edit merchant list' tab the user can be assigned to merchant(s) of the enterprise. Check/uncheck the merchants to attach/detach merchant to the user (Picture "Change user-merchant assignment" below);
- Press 'Save' button.
By creating of new user note, that:
- login should be 8 to 20 symbols long and should contain at least one Latin alphabet symbol (upper/lower case), may also include digits and underscore.
- password should be 8 to 20 symbols long and should contain Latin alphabet symbols (upper/lower case) and digits. Password must contain both – alphabet symbols and digits.
Adding a role to user
Change user-merchant assignment
Now new user can login to the Personal Account and watch the orders in 'Orders monitor'.
If user should have ability to charge or cancel order payments and/or export data in the file, then the following actions should be done additionally:
- Right-click on new user in table and select 'Edit Rights';
- In Component section of the Edit Rights tab check 'Confirmations' and 'Cancellations' and/or ‘Button “Export”’ in the Access column (Picture below);
- Check that 'ACCOUNT/ACCOUNT: Order menu' is checked on;
- Press 'Save' button.
Granting rights for cancel and charge.
Now the user may confirm or cancel payments and/or export data to the file in the 'Orders monitor' of Personal account.
If the administrator wants to change a user password then following steps should be done:
- Right-click on the new user in the table and select 'Change password';
- Enter twice a new user password in the dialog;
- Press 'Save' button.
If a user should be deleted should be done by the administrator the following steps:
- Right-click on the new user in the table and select 'Delete';
- Confirm the deletion in the dialog. User will be deleted.
It is not possible to restore a user which was deleted!
Using profiles
The profile mechanism is convenient for the merchants that need to create a lot of different user accounts with the same rights. To do this, a special user profile with all the necessary rights is created. For creating the next user, the administrator will only need to set his personal data and the profile name.
The use of profiles must be coordinated with the technical support service of Assist, then at the request of the merchant, the necessary profiles will be created and the administrator is given the appropriate rights.
Clicking the «Profiles» button opens a new window, which displays information about the current profiles of the merchant.
Profile parameters
Name | Description |
Name | Profile name |
User’s type | Type of user |
Company | User profile company |
Enterprise | User profile enterprise |
E-mail default profile user address (will be automatically assigned to all users of the profile for which the own E-mail address isn’t set) | |
Level of display errors | Assigned level of display errors |
To create a user profile, call the context menu by right click and select "Create User".
The list of fields in the form for creating a new user profile is given in the table:
New user creation options
Name | Description |
User profile | Select from the list of available values of merchant’s profiles |
Login | It should be 8 to 20 symbols long and should contain at least one Latin alphabet symbol (upper/lower case), may also include digits and underscore. |
Password | It should be 8 to 20 symbols long and should contain Latin alphabet symbols (upper/lower case) and digits. Password must contain both – alphabet symbols and digits. |
First name | Text field |
Middle name | Text field |
Last name | Text field |
Text field (100 characters). E-mail user address, if not specified, then the default profile address will be automatically assigned |
To save the changes, click the "Create" button.