Release Version 4.28.0 (January 30, 2025)

30. 01. 2025

Pre-deployment steps

To be done before deployment

Check configuration changes and apply them in the application.yaml if the default configuration has been overridden there.

Post-deployment steps

–

New functionality

Feature	Description	Benefits
Ability for service users to open investigation for the chosen transaction with AML or Fraud reasons on UI.	Service users can open an investigation for the chosen transaction with AML or Fraud reasons.	Investigations functionality allows to address AML or fraud concerns efficiently and ensure compliance with regulatory requirements
	This is the initial part of the Investigations functionality. Investigations management will be introduced in future versions.
Ability for service users to attach files and add note to the investigations	Service users can attach files or add note to the investigations
	This functionality is currently available in the APIs and will be incorporated into the UI in future versions.
Ability for service users to manage the status of the document attached to the investigations.	Service users can manage the status of the document attached to the investigations, document can be approved or declined.
	This functionality is currently available in the APIs and will be incorporated into the UI in future versions.
Ability for service users to select required monthly fee when copying contract	Service users can select required monthly fee when copying the contract.	Enhances flexibility in contract management.

	This functionality is only about setup, applying a monthly fee will be implemented in future versions.
Ability for service users to manage business users’ notifications on UI.	Service users can manage business users’ notifications:	Empowers service users to efficiently manage business users’ notifications, ensuring timely updates on critical events
	· KYC identification status change
	· Profile update is required
	· Reset identification request approved
	· Account was blocked
	· Password recovery
Ability for cashiers and service users to view cash desks operations including requests for top-ups and withdrawals initiated by business users	Cashiers and service users can view cash desks operations including requests for top-ups and withdrawals initiated by business users	This is the initial phase of the cash desk functionality, aimed at enhancing the cash management process and offering business users an additional method to perform withdrawals or top-ups.
	This functionality is currently available in the APIs and will be incorporated into the UI in future versions.
Ability for service users to view requests to change phone number used for login on UI	Service users can view requests to change the phone number used for login on UI	The end-to-end flow enables business users to change the login phone number in the SDK.finance mobile application if they no longer have access to it
	The ability for business users to change the login phone number if they no longer have access to it will be implemented in the SDK.finance mobile application

Improvements

Feature	Description
Commission accounting has been changed to make it smoother and enhance performance.	All commission paid to 3rd parties for operation processing is accounted at the `system_gate_commission` wallet with collector `PROVIDER`.
	All commission earned by the system is accounted at the `system_commission`wallet with `ACCOUNTING` or `CIRCULATION` usage.
Validation for the file format has been added to the API for uploading localization files.	To the API `POST /i18n/import` was added validation to make it impossible to upload JSON or XML files.
	Message code `exception.wrong_file.content` will be returned in case of wrong file format

Fixes

–

API changes

In the Swagger API description, the required permissions have been removed. Instead, information about the new API GET /api-list has been added, where permissions and the roles that have these permissions can be found.

Updated

GET /v1/coins
GET /v1/organizations/{organizationId}/coins

removed query param showClientSystemCommission

Parameter monthlyFee was replaced with monthlyFeeId in the request body of API POST /contracts/{contractId}/copy

so monthlyFee will no longer be recognized if passed in the request body

POST /contracts/{contractId}/copy

Added monthlyFeeId property

PATCH /investigation/{investigationId}

extended with the ability to add the document

Example request:

  "updateReason": "ADD_DOCUMENT",

  "documents": ["some-media_file_id", "another-media_file_id"]

}

POST /transactions/view

added new filter parameter initiator

POST /i18n/import

added validation for file format.

Added

POST /bank-withdrawals/commission

GET /contracts/{contractId}/monthly-fees

GET /investigation/{investigationId}/document/{documentId}

POST /investigation/{investigationId}/document/view

PATCH /investigation/{investigationId}/document/{documentId}

POST /my/cash-desk-operations/view

POST /management/cash-desk-operations/view

POST /note

POST /note/view

GET /note/{noteId}

PATCH /note/{noteId}

DELETE /note/{noteId}

Deprecated/Deleted

–

Configuration changes

Default configuration is changed from

compliance:</span></code></span></div>
<div class="code-block cc-wroouh" style="padding-left: 40px;"><span class="prismjs cc-zn1qqt" data-code-lang="" data-ds--code--code-block="" data-testid="renderer-code-block"><code class="language-"><span class="" data-testid="renderer-code-block-line-2" data-ds--code--row="">documents:</span></code></span></div>
<div class="code-block cc-wroouh" style="padding-left: 80px;"><span class="prismjs cc-zn1qqt" data-code-lang="" data-ds--code--code-block="" data-testid="renderer-code-block"><code class="language-"><span class="" data-testid="renderer-code-block-line-3" data-ds--code--row="">- organization-types: [ 'individual','merchant']

compliance:

documents:

- organization-types: [ 'individual','merchant','corporate' ]