Crassula Release Week 20

core v.26.05.7-26.05.8
client v.26.05.3-26.05.4

Improvements

Administrative Panel

Optimized the Logs tab in the Issued Card section. Added log pagination, support for the logs_page parameter in the URL, preservation of the active Logs tab state, and disabled excessive logging for the SWAN getTransactions operation, which previously caused page instability.

Fixes

Administrative Panel

Fixed discrepancies between balances displayed in the Administrative Panel and in Statements. The issue was caused by different rounding approaches for fractional values.

Compliance

Fixed an issue in the Huntli service where UpdateTransactionStatus requests were repeatedly sent after a transaction had already reached a final status, causing 422 errors and incorrect transitions to Declined or Failed. Additionally, the maximum supported IBAN length has been increased from 30 to 34 characters to support valid IBANs.
Fixed an issue where the system could incorrectly interpret successful responses from Sumsub as failed requests and attempt to create duplicate transactions, resulting in duplicate errors.

Transfers

Corrected settlement date calculation for SEPA Instant (INST) transfers. Settlement dates are now determined using UTC instead of UTC+2, while SEPA Credit (SCT) logic remains unchanged.
Significantly improved handling of incoming Instant transfers to closed or disabled IBAN accounts. Previously, SEPA Instant transfers could remain pending and eventually fail due to Litas timeout processing. The system now immediately detects unavailable IBANs and returns the correct rejection code (AC04), allowing senders to receive a clear error response without waiting for a timeout.
Improved transaction search logic for the Centrolink provider to prevent cases where incoming recalls referenced incorrect original transactions.
Improved payment execution logic for the Zand provider. If the purpose parameter is not specified, the system now automatically sends the PaymentPurposeCode value as the FIS string.
Added support for transmitting and processing the Beneficiary State or Province and Beneficiary Postal Code parameters for SWIFT payments via the Currencycloud provider. Previously, the absence of these parameters could lead to payment processing errors.