Release Version 4.46.0 (November 10, 2025)

11. 11. 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.
New keystore file must be created. Follow file naming convention by the template `.{company_name}.{environment}.jceks` (example: `.sdk.local.jceks`). To create a keystore file and the required keys, follow the next steps: Adjust commands by changing keystore filename value (example: `-keystore.sdk.local.jceks`). Execute the following commands one by one. Use the same password for encrypting the keystore file and for the secret key (strong password is required). Make sure to back up the generated keystore file and password. `keytool -genseckey -alias sensitive-data-encryption-aes-128 -keyalg AES -keysize 128 -keystore {keystore_file_name} -storetype JCEKS` `keytool -genseckey -alias gate-payer-data-encryption-aes-128 -keyalg AES -keysize 128 -keystore {keystore_file_name} -storetype JCEKS` `keytool -genseckey -alias gate-provider-settings-encryption-aes-128 -keyalg AES -keysize 128 -keystore {keystore_file_name} -storetype JCEKS` `keytool -genseckey -alias secure-memory-store-encryption-aes-128 -keyalg AES -keysize 128 -keystore {keystore_file_name} -storetype JCEKS` Configure the following parameters: `keystore.path: ${KEYSTORE_PATH:PathToTheFile} keystore.type: ${KEYSTORE_TYPE:JCEKS} keystore.password: ${KEYSTORE_PASSWORD:ChangeMe}`

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

The Business Account functionality is now nearly complete.
Upcoming releases will focus on final adjustments and enhancements to fully finalize this area.
The implementation improves flexibility for users operating as legal entities.

Feature	Description
Ability for service users to see company details in the Client profile.	Service users can see the following company details in the Client profile (UI changes): company information and documents company bank accounts company representatives company shareholders and their documents
Ability for Compliance to approve shareholders when all their documents are approved, or decline shareholders.	Compliance can approve shareholders when all their documents are approved, or decline shareholders (API changes).
Ability for Compliance to approve companies when all their shareholders and documents are approved, decline companies, or send for update.	Compliance can approve companies when all their shareholders and documents are approved, decline companies, or send for update (API changes).
Ability for service users to create Contracts for companies.	Service users can create Contracts for companies. Default Contracts for companies are created: Base, Standard, Gold, VIP.

Improvements

Feature	Description
Keystore file management was changed to improve security. The keystore file creation process was separated from the core application, and keystore modifications are prohibited.	Check the Pre-deployment steps and Configuration changes.
Ability to update the value for the existing bundle keys.	API `POST /i18n` adjusted to allow updating values for existing bundle keys only (creation is disabled).
API to get transaction names is used instead of hardcoding on front-end.	API `GET /transaction-types` is used.
UI changes: The Accept and Decline buttons are not displayed for transactions that are already in a terminal status on the CFO → System accounts → Transaction list page.
UI changes: Transactions on the CFO → System accounts → Transaction list are displayed in descending order by the createdAt field.
UI changes: In the Clients → Bank accounts → Add bank account side-bar, Bank account number and IBAN are marked as non-mandatory.

Fixes

Merchant payment/Invoice can be finished after the previous flow with interrupted OTP confirmation.

UI fix: unnecessary statuses were removed from the Status filter on the CFO – Cashier page.

API changes

Updated

API POST /i18n adjusted to allow updating values for existing bundle keys only (creation is disabled).

Added

POST /organizations/{organizationId}/identification

Deprecated/Deleted

APIs in Export transactions controller are marked as deprecated; APIs from the Reports controller should be used instead.

Configuration changes

The following keys were removed from the environment configuration:

keystore.path.prefix-folder-property (KEYSTORE_PATH_PREFIX_FOLDER_PROPERTY)

keystore.path.suffix (KEYSTORE_PATH_SUFFIX)

secure-in-memory-store.key-alias

secure-in-memory-store.key-rotation-schedule

New keys added to the environment configuration:

keystore.path: ${KEYSTORE_PATH:classpath:.sdk.local.jceks}

keystore.type: ${KEYSTORE_TYPE:JCEKS}