.png)
Crassula Release Week 47
core v.24.11.11-24.11.12
client v.24.11.5-24.11.5
Improvements
Mobile Banking Interface
Outgoing local transfers now include a confirmation check for the recipient’s information, ensuring that users can verify the validity of recipient details before confirming the transaction. This is implemented through Confirmation of Payee (CoP) functionality. The functionality covers UK Local and Dynamic UK Local transfers.
Added the Russian language localization to the Mobile Interface.
Payments
Implemented automatic Railsr SWIFT payments, replacing the previous manual process for such transactions.
Fixes
Administrative Panel
Addressed an issue where tags were not updating properly after modifications. Tag updates now save and reflect correctly.
Currency exchange
Resolved an issue where currency conversions involving the USDT-USDC cryptocurrency pair on the KuCoin provider returned a Decline status. Conversion functionality now operates as intended.
Payments
The character limit for the identifier input field (phone, username, email, IBAN, or account number) in Internal transfers was increased from 32 to 320 characters, resolving an issue that prevented some users from completing transfers.
Web Banking Interface
Added a confirmation dialog for deleting phone numbers and email addresses from account contact information, along with a success notification upon deletion.
Upcoming Updates
Improvements
API
The API method GET /api/clients/{clientId}/detect-transfer-type/{recipientNumber} will soon be marked as deprecated. A new API method will be introduced to determine whether a specific account supports SEPA payments based on the provided IBAN.
Administrative Panel
A feature toggle will be added to the system configuration to hide the "Synchronization" button in the Admin Panel. When enabled, the "Synchronization" button will no longer be displayed under Banking → Accounts → View.
Fixes
API
The API method
GET /api/clients/{clientId}/transactions/{transactionId}/payslipwill be updated to allow payslip downloads only when the following conditions are met: the transaction type is Transfer (4) and the transaction status is not “Draft”.Users face difficulties when requesting account opening with the Clear Junction provider. To resolve this issue, we will migrate to version 3 of the API for generating IBANs with Clear Junction. Previously optional parameters, such as
ibansGroup(for SEPA payments) andrequisiteGroup(for USD payments), will become required. For more details, refer to the corresponding Upgrade Note.
Co-Funded Opportunities
Migrating API docs to readme.com platform
We are excited to propose the migration of our API documentation to readme.com, a platform that enhances clarity, reduces support queries, and streamlines the developer experience. This upgrade will feature interactive examples, detailed endpoint guides, and multi-language code samples, all aimed at simplifying API integration and accelerating onboarding for development teams. By co-funding this initiative, you gain early access to the improved documentation and the opportunity to influence its features to better suit your needs. Contact your client manager to learn more about this initiative and how it can benefit your development processes. For more detail, see the corresponding article on this co-funded opportunity.