Release Version 4.44.0 (October 15, 2025)
- Pre-deployment steps
- Post-deployment steps
- Changes to notice
- New functionality
- Improvements
- API changes
Pre-deployment steps
To be done before deployment |
---|
Check configuration changes and apply them in the |
Check if the release contains migrations. Migrations can affect deployment and downtime. |
Use |
Post-deployment steps
To be done after deployment |
---|
Verify permission changes and assign or remove required permissions if they have been overridden |
Add new properties from the I18n properties changes to the downloaded i18n properties file and add translation for them if needed. Use |
Changes to notice
Changes to notice |
---|
Response changed: the field |
The following API operations are marked as deprecated and will be removed starting from version 4.48.0. New APIs specified in the table should be used instead: |
Old API operation |
New API operation |
---|---|
|
|
|
|
|
|
|
|
New functionality
Feature |
Description |
Benefits |
Ability for merchants to see incoming invoices and pay them. |
In the merchant portal, merchants can see incoming invoices and pay them. |
Extend merchant functionality. |
Ability for users who lost access to their mobile to create several phone number change requests. |
Users who lost access to their mobile can create a phone number change request and upload documents for identification. In case of mistake, users can create several phone number change requests, and the last can be approved by compliance. |
Enhance user experience. |
We’ve started developing Business Account functionality.
This release introduces several foundational features listed below.
Future releases will continue to expand this area to enable full business account capabilities for legal entities.
Business account implementation will improve flexibility for users who operate as legal entities.
Feature |
Description |
Ability for users to link bank accounts for the created companies |
Users can link one or more bank accounts to the created companies. Company bank accounts will be used for representation and compliance purposes. |
Ability for users to upload company documents. |
Users can upload mandatory and optional company documents for compliance review. |
Ability for compliance to review, and approve/decline company documents. |
Compliance can review, approve or decline company documents. |
Ability for users to specify shareholders for the created companies. |
Users can specify one or more shareholders for company. Shareholder information and documents will be used for compliance review. |
Improvements
Feature |
Description |
Front-end was migrated to the VUE.JS 3.5 version |
|
Users are prohibited from activating their wallet if it was previously deactivated by the service user. |
Validation added to the API |
When the same service role initiates transactions export with the same parameters, the system reuses the existing export. |
If an export with the same parameters exists, it will be linked to the new report. |
Ability to generate a receipt in |
Added a new REST endpoint |
UI changes for Cash desks: representation has been changed from currency tabs to a currency list to improve performance. |
|
Ability to show for user the total available balance on all wallets in the specified currency. |
To the API |
Front-end changes: menu Chats is shown if the user has one of the following permissions:
|
|
Front-end changes: menu CFO → Reports is shown if the user has one of the following permissions:
|
|
API changes
Updated |
Response changed: the field Added filter by |
New parameters added to request filter: |
New fields |
added permission to call |
Added |
|
|
|
|
Deprecated/Deleted |
The following API operations are marked as deprecated and will be removed starting from version 4.48.0. New APIs specified in the table should be used instead: |
Old API operation |
New API operation |
---|---|
|
|
|
|
|
|
|
|