Crassula Release Week 31

core v.24.07.14-24.07.16
client v.24.07.10-24.08.1

Improvements

Administrative Panel

Added new columns to Reports → Banking → Accounting:

• Outgoing Pending: This new column displays the outgoing pending transactions.

• Incoming Pending: This new column shows incoming pending transactions.

• Actual Balance: Calculated as closing balance - outgoing pending. This column provides a real-time view of the available balance after accounting for pending outgoings

API

Added a new setting, white_label_footer, for configuring footer text. The API method GET /api/public/settings now includes a new parameter, whiteLabelFooter, which returns the footer text. The footer text can be changed either through the configuration file or via the Administrative Panel. We recommend creating the footer text through the Administrative Panel to avoid formatting issues.

Card issuing

Introduced the ability to configure certain parameters as mandatory or optional. When the configuration parameters shipping.address, holder.phoneCountryCode, and holder.phoneNumber are enabled, these fields become mandatory. If these parameters are disabled in the configuration, they will be automatically filled with data from the person database.

Web and Mobile Interfaces

Updated the flow for selecting card currency during issuance. Previously, the Card Details window (where users could select the card currency) was skipped if the user only had one card option available in one currency. Now, regardless of how many and which card options are available, users will always see the Select Card Currency option when ordering a card. This change is reflected in both the Web and Mobile Interfaces.

Fixes

Administrative Panel

Fixed an issue in the Admin -> Reports -> Banking -> Accounting section where the actual_balance field displayed null (which showed the balance as 0) if there were no outgoing pending transactions. The actual balance field now correctly reflects the balance.

Reports

Corrected an issue where the provider number of the financial account was always displayed in the report, regardless of the specified fromAccountIban.

Transfers

Added validation for the Details field in dynamic (Bank transfer) Local and Batch Local payments for the Railsr provider, with a maximum length of 18 symbols.

Web Interface

Fixed an issue where the date of birth was displayed as one day less than the date entered during the registration of a new person.

Upcoming Updates

Improvements

API

• Validation will be added to prevent sending payments and conducting currency exchanges from interledger accounts. This change will affect the POST /api/account-transaction and POST /api/fee-transaction methods and will be reflected in the Administrative Panel. Attempts to create transactions or currency exchanges from interledger accounts will result in the error message: “Transactions from interledger accounts are not allowed.”

• We will introduce the ability to group bank transfer parameters dynamically, based on the method group. A new attribute, group, will be added to the parameters for dynamic payments in the GET /api/clients/{clientId}/transfer/parameters method.

• Validation of the Amount parameter will be added when sending payments in Bank Transfers. This change will be implemented in the /api/clients/{clientId}/transfer/methods endpoint.

Card fees

We will enhance the logic for card fees. If a user's default currency differs from the service provider's default currency, the user's default currency will be used for card fees.

Fixes

API documentation

We will improve the documentation for the GET /api/clients/{clientId}/transfer/parameters method by adding the currently missing parameters:

• account

• transferMethod

• countryCode

• currency