Release Version 4.54.0 (March 23, 2026)
- Pre-deployment steps
- Post-deployment steps
- Release migations
- Changes to notice
- 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 |
|---|
|
New record added to the |
|
Extended the |
|
Added column |
Changes to notice
|
Changes to notice |
|---|
|
All enum values on the OpenAPI side were changed to lower snake case. This change affects all API requests and responses where any enum is used. For a detailed description, contact our support. |
New functionality
|
Feature |
Description |
Benefits |
|---|---|---|
|
Ability to get deposit address for the account in a Fireblocks-enabled asset. |
When a client requests a deposit address for a Fireblocks-enabled asset, SDK.finance checks whether a deposit address is already linked to the internal account. If not, it generates the address using the corresponding use case flow, links it to the account, and returns it in the API response. The mobile app shows the deposit address on the Add money screen for Fireblocks-enabled assets. |
Enables clients to receive crypto deposits directly into their Fireblocks-managed wallet accounts without manual address provisioning. |
|
Ability for manual withdrawal finalisation for withdrawal from the account in a Fireblocks-enabled asset. |
The administrator verifies the status of a pending withdrawal externally (e.g. via Fireblocks Console) and finalises it by selecting a final status — success or failed. SDK.finance either confirms the held amount and completes the withdrawal, or cancels the withdrawal and releases the held funds back to the user account. |
Gives administrators full control to resolve stuck or unresponsive Fireblocks withdrawal transactions and restore account balances. |
|
Ability to re-send pending withdrawal to Fireblocks. |
The administrator re-sends a pending withdrawal transaction to Fireblocks in cases where the withdrawal was originally initiated via Fireblocks but was not executed on the Fireblocks side. SDK.finance re-initiates the withdrawal via the Fireblocks API and continues processing based on the result returned by Fireblocks. |
Enables recovery from failed Fireblocks withdrawal submissions without requiring manual database intervention. |
|
New format for user action history. |
The administrator can view a log of user sessions and actions. Sessions can be filtered by period, session ID, location, suspicious activity, and session status. Session details include IP address, device type, browser, location, duration, and action count. Actions are classified as transactions or client actions, and include the action type, related object ID, and before/after values for tracked changes. |
Provides compliance and audit capabilities for monitoring user behaviour, detecting suspicious activity, and supporting incident investigations. |
|
Ability to enable two-factor authorisation using an authenticator application for service users. |
A service user with the appropriate permission can enable or disable TOTP for another service user. When TOTP is enabled for a user by an administrator and the authenticator is not yet connected, the user is prompted to complete the TOTP setup on their next login by scanning a QR code. |
Allows administrators to enforce a two-factor authentication policy across all service users without requiring each user to self-enrol. |
|
Ability to mark contract as hidden for business users. |
Service users can mark a contract as hidden so that business users cannot view it in the list of available contracts or assign it to themselves. Service users retain the ability to view and assign hidden contracts regardless of visibility settings. |
Provides flexible contract management — promotional, internal, or restricted contracts can be kept invisible to clients while remaining available to administrators. |
|
Ability for the administrator to specify a list of available locales. |
The administrator can add or remove locales available in the system directly from the UI. When a language is added, all necessary steps are performed automatically to allow uploading a localisation file. English cannot be removed as it is used by default. |
Simplifies localisation management by eliminating the need for configuration file changes when adding or removing supported languages. |
|
Ability for the administrator to specify the initial KYC status for new users. |
The administrator can configure the default KYC/KYB status for newly created Individuals, Merchants, and Companies (including shareholders) — either None (KYC required) or Approved (KYC not required). When a Company is marked as KYC not required, its shareholders are also created in approved status. |
Enables flexible onboarding flows, allowing operators to skip KYC for trusted client segments or specific organisation types. |
|
Ability for service users to upload documents on behalf of Individual. |
API |
Enables flexible onboarding flows, allowing operators to upload documents on behalf of the users. |
|
Ability to manage transaction categories on UI |
The administrator can manage transaction categories and set the default category for each transaction type from the CFO section → Categories & TXN types. Two tabs are available: Categories and Transaction types. |
Simplifies system configuration. |
Fixes
|
Sorting option removed from UI except where backed by API. |
|
The main currency definition is removed from the Currency list. |
Improvements
|
Feature |
Description |
|---|---|
|
UI exception filter for expired tokens |
Exceptions related to expired tokens are now filtered out on the UI to prevent unnecessary error notifications from being shown to users when their session naturally expires. |
API changes
|
Updated |
|
All enum values on the OpenAPI side were changed to lower snake case. This change affects all API requests and responses where any enum is used. |
|
|
|
API is now available for unauthorised users. New required property |
|
New action New property |
|
New request type |
|
Property |
|
Property
|
|
Three new actions added:
|
|
Added |
|
Returns the primary active deposit address for the given coin, or creates a new one if no address is linked yet. Required permission: |
|
|
|
Returns current initial KYC status for supported organisation types. Required permission: |
|
Updates initial KYC status for one or more organisation types (partial update supported). Required permission: |
|
Creates a new supported locale. Required permission: |
|
Deletes an existing supported locale. Delete a locale from the supported locale list without removing its localization data. Required permission: |
|
Deprecated/Deleted |
|
— |
I18n properties changes
|
Added |
|---|
|
|
|
|
Configuration changes
|
Added |
|---|
|
|
Database changes
|
New record added to the |
|
Extended the |
Permission changes
|
New permission |
|
New permission |
|
New permission |
|
New permission
|
|
New permission USER_ACTION_VIEWER added and granted to the following roles:
|
|
Permission
|