Release Version 4.45.0 (October 29, 2025)
- Pre-deployment steps
- Post-deployment steps
- Changes to notice
- New functionality
- Improvements
- API 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  | 
Changes to notice
| Changes to notice | 
|---|
| API  | 
New functionality
We’ve started developing Business Account functionality.
This release introduces several 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 upload documents of company shareholders. | Users can upload documents of company shareholders for compliance review. | 
| Ability for users to mark the Company as Ready for review when all required information is specified and all required documents are uploaded. | Users can mark the Company as Ready for review when all required information is specified and all required documents are uploaded. When the company is marked as Ready for review any changes in the company information or documents are forbidden. | 
| Ability for Compliance to approve/decline documents of company shareholders. | Compliance can approve/decline documents of company shareholders. | 
Improvements
| Feature | Description | 
| Ability to pay for merchant payment using another method if the payment was not finished successfully (payment failed, OTP is not correct, or not specified). | Users can repeat failed payment using the same or another payment method if the payment was not finished successfully. Users will see each payment attempt in the transactions list. | 
| Ability to pay for invoice using another wallet if the payment was not finished successfully (payment failed, OTP is not correct, or not specified). | Users can repeat invoice payment using the same or another wallet if the payment was not finished successfully. Users will see each payment attempt in the transactions list. | 
| Ability for users to create a bank account by specifying BIC/SWIFT instead of the internal bank ID and account details. | Users can create a bank account by specifying BIC/SWIFT instead of the internal bank ID and account details. Bank with the specified BIC/SWIFT must exist in the system. | 
| Added API to get the list of transaction type names in the specified locale. | API  | 
| Organisation ID is added to the authorisation token. | Organisation ID from the authorisation token can be used by the front-end instead of storing it on their side. | 
API changes
| Updated | 
| 
 The new optional parameter  | 
| 
 The new field “ “ | 
| 
 The query parameter “ | 
| Added | 
| 
 | 
| 
 | 
| 
 | 
| Deprecated/Deleted | 
| 
 | 
