Explore Release Notes

Release Version 4.44.0 (October 15, 2025)

15. 10. 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

Check if the release contains migrations. Migrations can affect deployment and downtime.

Use GET /i18n/export/{fileName} to download files with current i18n properties. Check if the downloaded file is correct.

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 POST /i18n/import to upload and apply previously downloaded i18n file with added new properties.

Changes to notice

Changes to notice

GET /working-days

Response changed: the field workingDayAmounts (array) was changed to workingDayAmount (object)

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

GET /profile-documents/view-document-types

GET /organizations/{organizationId}/profile-documents/view-document-types

POST /profile-documents

POST /organizations/{organizationId}/profile-documents

POST /profile-documents/identifier

POST /organizations/{organizationId}/profile-documents/identifier

GET /profile-documents

GET /organizations/{organizationId}/profile-documents

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 PATCH​/v1​/coins​/{serial}.

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 PDF format.

Added a new REST endpoint GET /receipts/{transactionId} that returns a PDF receipt for the specified transaction.

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 GET /reporting/coins response added new fields.

Front-end changes: menu Chats is shown if the user has one of the following permissions:

  • CONVERSATION_MESSAGE_CREATION_EXECUTOR

  • CONVERSATION_VIEWER

  • INVESTIGATION_CONVERSATION_VIEWER

Front-end changes: menu CFO → Reports is shown if the user has one of the following permissions:

  • REPORT_VIEWER

  • REPORT_VIEWER

  • REPORT_MANAGER

API changes

Updated

GET /working-days

Response changed: the field workingDayAmounts (array) was changed to workingDayAmount (object)

Added filter by currencyCode. This filter can accept a list of currency codes (Alfa3) separated by a comma.

POST /invoices/view

New parameters added to request filter: createdAtFrom, createdAtTo

GET /reporting/coins

New fields roundedTotalAvailableAmount, roundedAvailableAmount and availableAmount were added to the API response.

GET /management/cash-desks/{cashDeskId}

added permission to call CASH_DESK_MANAGER

Added

GET /receipts/{transactionID}

POST /organizations/{organizationId}/bank-accounts

PATCH /organizations/{organizationId}/bank-accounts/{bankAccountId}

DELETE /organizations/{organizationId}/bank-accounts/{bankAccountId}

GET /organizations/{organizationId}/bank-accounts/{bankAccountId}

POST /organizations/{organizationId}/media-files

GET /organizations/{organizationId}/profile-documents/view-document-types

POST /organizations/{organizationId}/profile-documents

POST /organizations/{organizationId}/profile-documents/identifier

GET /organizations/{organizationId}/profile-documents

POST /companies​/{companyId}​/shareholders

GET ​/companies​/{companyId}​/shareholders

DELETE /companies​/{companyId}​/shareholders​/{shareholderId}

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

GET /profile-documents/view-document-types

GET /organizations/{organizationId}/profile-documents/view-document-types

POST /profile-documents

POST /organizations/{organizationId}/profile-documents

POST /profile-documents/identifier

POST /organizations/{organizationId}/profile-documents/identifier

GET /profile-documents

GET /organizations/{organizationId}/profile-documents