Crassula Release Week 25

core v.24.06.9-25.06.11
client v.25.06.5-25.06.7

New Features

New SEPA payment method for ClearBank EU

We’re pleased to announce the introduction of a new SEPA payment method for the ClearBank EU provider. This enhancement expands SEPA transfer capabilities within the platform and allows for broader payment coverage.

Improvements

API

New mandatory parameters—purpose and categoryPurpose—were added to ClearJunction CHAPS batch payments. The parameters can be configured as mandatory via system settings and are optional by default. The following methods were updated:

• GET /api/clients/{clientId}/batch-transfers/template/accounts/{account}/methods/{transferMethod}/download

• GET /api/clients/{clientId}/batch-transfers/{batchTransferId}

• GET /api/clients/{clientId}/batch-transfers/{batchTransferId}/rows

• GET /api/clients/{clientId}/batch-transfers

• POST /api/clients/{clientId}/batch-transfers

• POST /api/clients/{clientId}/batch-transfers/{batchTransferId}/{action}

See Banking API for additional details.

Transfers

• Improved processing speed for incoming transactions. The speed improvement depends on the number of transactions processed simultaneously, but under average midday load, performance metrics show nearly a 4x acceleration.

• Introduced transaction import support for the Skaleet provider, enhancing account data synchronization.

Web Interface

Implemented consistent masking of phone numbers across all flows using two-factor authentication (2FA), including:

• Confirming, adding, or deleting 2FA methods

• Sending a PIN code during card activation

• Confirming phone numbers during verification

Fixes

Accounts

Removed the outdated ability to manually create accounts in the Admin Panel for the following card providers: Unlimit, Intercash, Decta, Swan, and Reap. These accounts are now automatically created during the card ordering process.

API

• Fixed an issue where the fromAccountIban field in API responses for incoming SEPA transfers displayed the sender’s IBAN instead of the beneficiary’s IBAN. The field now correctly shows the beneficiary’s IBAN in the Admin Panel and in the following methods:

  • GET /api/clients/{clientId}/transactions/{transactionId}

  • GET /api/clients/{clientId}/transactions

• Fixed missing masking of recipient phone numbers in the hint field of SMS requests for 2FA in the following API methods:

  • POST /tfa/confirmation-codes

  • POST /tfa/confirmation-codes-with-custom-phone

See Banking API for additional details.

Compliance

Improved masking of sensitive fields in API logs. The following fields are now fully masked (e.g., "password": "********"), not partially: password, salt, token, code, security, cvv, repeat, passphrase, currentPassword.

Currency exchange

Corrected the logic for crypto exchange orders involving the Kraken provider. Previously, some orders were stuck in the "New" status due to incorrect fund availability checks. The issue has been resolved, and the functionality now performs as expected.

Transfers

Resolved an issue where clients were unable to access the confirmation screen when attempting to initiate a cryptocurrency transaction.