Release Version 4.15.0 (December 12, 2023)

12. 12. 2023

What’s new

A new Transaction Details form for the Administrator was implemented on the Back-office Front-end
The ability for the Administrator to create a wallet on behalf of the user was added. See “API Changes” section of the release notes to know more about changes related to API
The ability to create limits for product commissions via the Back-office Front-end was added
The accounting model for Top up via bank operation was changed
The ability for the Compliance Manager to specify additional fields for the User to update during KYC reset via Back-office Front-end was added
The ability for the Compliance Manager to review notes about users via the Back-office Front-end was added
The ability to create more than one service user with the same role was added as the default configuration.
- By default, the Users with service roles are created with parameters: ATTACH_MULTIPLE
- By default, the System organization is created with the parameters:
```
core.organizations.permission-configs[0].roles[0].member-creation:ATTACH_MULTIPLE
```
- By default, the Users with the Cashier role are created with parameters: ATTACH_MULTIPLE and USER_MANAGER permission
- By default, the Cash Desk organizations are created with the following parameters:
```
core.organizations.permission-configs[0].roles[0].member-creation:ATTACH_MULTIPLECREATE_NEW_ORGANIZATION
```

Use API POST /users to create service users and attach them to the existing System organization. Provide the user email as login, user role, and existing system organization ID. A new user with a provided service role will be created and linked to the existing System organization.

request body:

{          "login": "compliance_manager_2@sdkfinance.com",          "role": "compliance_manager"          "organizationId": "123" - existing system organization Id        }

Use API POST /users to create more than one user with the role of Cashier. Provide user email as login and user role to create a new cash_desk organization if you want to create a new Cashier user linked to it.

request body:

{          "login": "cashier_2@sdkfinance.com",          "role": "cashier"        }

OR provide the user email as login, user role, and existing cash_desk organization ID to create a new Cashier user and to link it to the existing cash_desk organization.

request body:

{          "login": "cashier_2@sdkfinance.com",

"role": "cashier"          "organizationId": "123" - existing cash_desk organization Id        }

To use API API POST /users permission USER_MANAGER is required

Improvements

The API GET /actuator/api-list was enhanced (added tag description for controllers)
The account type “client” is set by default in the request body when business users create their coins
Old amount fields were removed from API POST /transactions/view response. See “API Changes” section of the release notes to know more about changes related to API
The mapping for recipient/sender data for Transaction details for Merchant and Individual Transaction details was corrected
The auto calculation of the Amount during Invoice creation was added
The validation to prohibit overlapping of the limits was added
The ability for the Compliance Manager to see User Identification Status (organizationStatus) in the list of user identifications was added
Setting irrelevant commission configurations for supported operations was prohibited
Old irrelevant Contracts related endpoints were removed. See “API Changes” section of the release notes to know more about changes related to API
The support of russian language for localization was deleted from the SDK Core application
The permission COIN_MANAGER was added to the Accountant role by default
The validation pattern for a phone number in API endpoint PATCH /profiles/{userId}/person was changed (min 10 digits changed to 9 digits). See “API Changes” section of the release notes to know more about changes related to API
The “amount” field was added to POST /transactions/view for all supported operations. See “API Changes” section of the release notes to know more about changes related to API

Fixes

The issue with the updating commission rule condition after trying to set invalid values was fixed
The issue with the password as a mandatory field when confirming user registration was fixed
The Code for exception when there are no commission rules for gate-commission-profile was fixed. Added 404 Not Found with code explanation that “There are no commission settings for GateCommissionProfile”
Status Code when trying to perform operations where a commission is greater than the amount of operation was fixed. 500 status code was replaced by 400 Bad Request
The multiple issues with the New UI ToolKit were fixed
The Code for exception when gate-commission-rule is inactive was fixed. Added 404 Not Found
The issue with the Main Menu that is visible to the user after clicking on the logout button was fixed
The issue with different paddings of placeholders was fixed
The issue with the scroll option on the Individual “Transactions” tab was fixed
The issue with the “statuses” component of the dropdown for Individual was fixed
The sending of request POST /invoices/view when the Administrator view Transactions was removed. Invoices as all other transaction returns in the response on POST /transactions/view
The issue with using values from exceptions.parameters instead of keys in alerts was fixed
The issue with the callback for MerchantPayment was fixed
Multiple Front-end issues with icons were fixed
The duplication of operations in Counter Service was fixed
The issue with scrolling on the Individual “Accounts” tab after performing transactions was fixed
The issue with performing transactions when two or more business_commission coins are created in the system was fixed
The issue with commissions fields viewing in POST /transactions/view for Merchant payment was fixed

API Changes

Endpoint	Updated
PATCH /profiles/{userId}/person PATCH /profiles/my/person POST /profiles/my/contact POST /profiles/{userId}/contact	In request and response: validation of the field phoneNumber was changed from min 10 digits to min 9 digits.
POST /transactions/view	1. irrelevant amount fields were removed from the response: commissionnetAmountoperationAmountDetailscashAmountcashCommissioncashNetAmountinvoiceAmount 2. amount field was added to the response foroperations: · Merchant payment · Invoice · Withdrawal via cash desk · Top up via cash desk · Top up via bank · Withdrawal via bank amount filed represents an amount that was entered by the user during transaction creation.
Endpoint	Added
POST /coins/organization/{organizationId}	new API to create a wallet on behalf of the User by Administrator was added permission COIN_CREATOR required organizationId the Organization Internal Identifier, for which the wallet will be created request body: { "name": "string", "currencyId": "string", "type": "regular_commission"} response body: { "serial": "string", "name": "string", "amount": 0, "availableAmount": 0, "futureAmount": 0, "heldAmount": 0, "creditLimit": 0, "currency": { "id": "string", "sn": "string", "code": "string", "symbol": "string" }, "active": true, "type": "regular_commission", "main": true, "smartCards": [ { "id": "string", "cardNumber": "string", "expirationDate": "string", "name": "string", "expirationStatus": "ACTIVE", "active": true } ]}
Endpoint	Deprecated/Deleted
GET /v1/contracts/{contractId}/gate-commission-profiles/{profileId}/commission-settings-records View commission settings of gate commission profile POST /v1/contracts/{contractId}/gate-commission-profiles/{profileId}/commission-settings-records/set-up-commission-settings Set up commission settings GET /v1/contracts/{contractId}/gate-commission-profiles/{profileId}/exchange-settings-records View exchange settings of gate commission profile POST /v1/contracts/{contractId}/gate-commission-profiles/{profileId}/exchange-settings-records Create new exchange settings record GET /v1/contracts/{contractId}/gate-commission-profiles/{profileId}/product-commission-settings-records View product commission settings of gate commission profile POST /v1/contracts/{contractId}/gate-commission-profiles/{profileId}/product-commission-settings-records/set-up-product-commission-settings	Endpoints was removed