Release Version 4.48.0 (December 10, 2025)

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

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.

New functionality

Feature

Description

Benefits

Ability for service users to enable or disable notifications at the system level (UI flow is now available).

Service users can enable or disable notifications at the system level:

if notification is enabled at the system level, it should be sent according to the user level settings
if notification is disabled at the system level, user settings should be ignored, and notification should not be sent

More flexible notifications management

The Business Account functionality

Feature	Description
Ability for individuals or service users to change the contract for the company (API flow).	Individual or service users can change the contract for the company: An individual user can operate only with companies that belong to them Service users can operate with companies accordiing to permissions
Ability for individuals to add existing individual users to the company as members (API flow).	Individual can add existing approved individual users as members for the approved company: An individual user can operate only with companies that belong to them Added members have the same permissions as owner of the company, except for member management
Ability for individuals or service users to close the company if all company accounts are closed.	Individual or service users can close the company if all company accounts are closed: An individual user can operate only with companies that belong to them Service users can operate with companies accordiing to permissions If the company is closed: company information and documents, representatives information, shareholders information and documents are visible, company status is closed there is no ability to edit company information and documents, representatives information, shareholders information and documents there is no ability to create account for company there is no ability to reopen company
Ability for individuals or service users to delete the company in `None` status, without accounts, bank accounts, representatives, documents, and shareholders.	Individuals or service users can delete the company in `None` status, without accounts, bank accounts, representatives, documents, and shareholders: An individual user can operate only with companies that belong to them Service users can operate with companies accordiing to permissions

Improvements

Feature	Description
Document “Account details” is generated on the back-end side instead of the mobile application.	API `GET /account-details/{serial}` generates the account details PDF for a specific wallet (by its serial) and returns it inline with the appropriate headers for file download.
Ability for the user to add a bank account by specifying BIC or SWIFT without bank existence in the bank catalogue.	The system will check bank existence depending on the configuration `bank-catalog.bank-existence.required`.

API changes

Updated

PATCH /contracts/{contractId}/organization extended to change the contract for the organisation with type business

A new field bicOrSwift was added to the details object, bank-related data was moved from details object to a new bank object in the response.

Response structure changed in the following APIs:

POST /organizations/{organizationId}/bank-accounts
PATCH /organizations/{organizationId}/bank-accounts/{bankAccountId}`
POST /bank-accounts/{bankAccountId}/approve
POST /bank-accounts/{bankAccountId}/reject
GET /bank-accounts/view
GET /my/bank-accounts
POST /my/bank-accounts/view
GET /my/account-overview

New field bicOrSwift added to the response of the following APIs

POST /my/bank-accounts/coin/{coinSerial}/with-bank

Added

GET /organizations/{organizationId}/members/{memberId}

DELETE /organizations/{organizationId}/members/{memberId}

POST /organizations/{organizationId}/members

GET /organizations/{organizationId}/members

PATCH /companies/{companyId}

DELETE /companies/{companyId}

GET /account-details/{serial}

Deprecated/Deleted

–

Configuration changes

Added new flag to configure if a presence of bank in bank catalogue is required or not on a system level:

bank-catalog.bank-existence.required ${BANK_CATALOG_BANK_EXISTENCE_REQUIRED:false}

Permission changes

New permissions created:

COMPANY_MEMBERS_MANAGER
COMPANY_MEMBERS_VIEWER

Both permissions were granted to:

individual
administrator
customer_success_specialist
ceo