Skip to main content
Skip table of contents

Crassula Release Week 15

core v.25.04.8-25.04.9
client v.25.04.3-25.04.4

New Features

Bank transfer templates

We are excited to announce the introduction of Bank transfer templates. Previously, separate templates were available for European, Local, and International transfers. With this update, they are now replaced by a single, streamlined template that supports the full functionality of all transfer types. This enhancement greatly simplifies the user experience and ensures consistent behavior across all types of transfers.


Improvements

API Documentation

Refactored the Crassula Banking API documentation to support the OpenAPI Specification 3.0 standard. Additionally, the grouping of API methods has been improved to enhance usability.

Card fees

Enhanced transaction logic for card order fees. Now, status checks from third-party services determine whether a fee transaction proceeds. If the card is successfully issued, the fee is processed; if an error occurs, the transaction is marked as DECLINED.

Currency exchange

Significantly improved the functionality for creating and using Interledgers. Interledgers are now created earlier in the process—as soon as a transaction enters the WAITING_FOR_PROCESS status—making the currency exchange flow faster and more streamlined.

Transfers

  • Added validation to prevent creation or updates of transfer templates with duplicate names. If a template with the same name exists, a number is appended to the new name (e.g., test → test 1). This improvement is implemented in both the Web and Mobile Banking Interfaces, and users will see a message: “Template with the same name already exists.”

  • In the Web Interface → Batch Payments section, introduced a notification informing users that a maximum of 500 transactions is allowed per batch payment.

  • Improved transaction status handling for Railsr-issued cards. If a transaction previously marked as COMPLETED receives a webhook with a DECLINED status, the system updates the transaction to DECLINED (fees remain unchanged). Please note that this change is one-directional: transactions already marked as DECLINED will not be updated if a COMPLETED status is received later.


Fixes

Administrative Panel

Resolved an issue where changes to card products in the Activity Logs did not log the Client Eligibility Criteria. This parameter is now correctly logged.

Transfers

Fixed an issue that occurred during BIC resolution when the associated address was not provided. The functionality now works as expected.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.