Release Version 4.53.0 (March 9, 2026)
- Pre-deployment steps
- Post-deployment steps
- Release migations
- Changes to notice
- Fireblocks integration
- Improvements
- Fixes
- API changes
- I18n properties 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 |
Release migrations
|
Release migrations |
|---|
|
Changes to notice
|
Changes to notice |
|---|
|
Teh following APIs were deleted:
|
|
Corporate role is deleted, company creation functionality for Individual users can be used instead. |
Fireblocks integration
Fireblocks is an institutional digital asset infrastructure that provides secure custody and on-chain transaction execution, and its integration with SDK.finance enables crypto assets to be managed within a ledger-based financial system with controlled withdrawals, validated deposits, policy-driven execution, and full operational and accounting oversight.
|
Feature |
Description |
|
Implemented omnibus sweeping for account-based assets. |
SDK.finance initiates sweeping of account-based assets from user-level vault accounts into the Treasury Vault Account. Sweeping is triggered after a successful deposit and moves the deposited amount from the user’s vault account to the treasury account used for consolidated storage. An additional parameter to show sweeping status added to the Transaction list API. |
Improvements
|
Feature |
Description |
|
Service users can create a bank account for the client by specifying BIC or SWIFT without a bank existing in the bank catalog. |
A bank account can be created either by specifying BIC or SWIFT or by choosing a bank from the bank catalog. |
|
Added ability to specify transaction category when executing bank topup via API |
When creating a bank top-up request, the service user can choose a category. |
|
Added ability to pass description and custom information for the exchange operation. |
When creating an in-system transfer in different currencies (exchange), the user is able to specify a payment reason. |
|
UI for currency exchange rates management were changed to make it smoother and more convenient. |
The main currency is removed, and source and destination currencies explicitly show the exchange direction. |
|
Notification description is added to the System settings → Notifications |
|
|
The following renaming is performed on UI:
|
|
Fixes
|
Amounts in the statement PDF are displayed in accordance with the currency scale defined for each currency. |
|
Removed hardcoded |
API changes
Updated |
|
User notifications settings were removed from the APIs
|
|
The new field Filtering works correctly via |
|
|
|
|
|
The new field
|
|
The existing request parameter The new optional parameter One of these parameters should be passed to the request. If both parameters are presented or absent in the request, then an error will be returned. |
|
The new optional parameter |
|
The new optional parameters |
|
Added filtering by |
|
|
|
In the response body property |
|
In the response body properties |
|
In the response body properties |
|
|
|
|
|
|
Added |
Deprecated/Deleted |
|
I18n properties changes
Added
|
|
|
|
|