Crassula Release Week 24

core v.25.06.5-25.06.6
client v.25.06.3-25.06.4

Improvements

API

• A new GET /api/clients/{clientId}/issued-cards/{cardId}/external-holds endpoint is now available to retrieve hold data from the provider. Currently, this is supported for Decta only.

• Phone numbers in 2FA fields are now masked in API responses. The recipient field now includes a hint instead of the full number, while the value for TOTP is returned as an empty string.

• The masking logic for the POST /api/clients/{clientId}/issued-cards method, visible in the API Request Log section of the Admin Panel, is now configurable. Sensitive fields in the response can be shown or hidden based on a configuration managed by technical support. Additionally, the masking behavior is adjusted dynamically depending on the length of the field value.

• Field names in the GET /api/clients/{clientId}/transactions/{transactionId}/flat response have been renamed:

  • bankCode → recipientBankCode

  • correspondentBankName → correspondentName

  • correspondentBankAccountNumber → correspondentAccount

  • correspondentBankCode → correspondentSwift

• Improved the documentation and response schemas for the following API methods:

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

  • POST /api/clients/{clientId}/accounts

  • PUT /api/clients/{clientId}/accounts/{accountId}/close

  • PATCH /api/clients/{clientId}/accounts/{number}

  • POST /api/clients/{clientId}/accounts/full

See Banking API for additional details.

Cards

Service fee charges are now deferred for cards in the SUSPENDED status. If a card was in the ACTIVE status during any part of the billing period, the fee is accrued and applied after reactivation. No fee is charged if the card remains suspended for the entire period.

Communication

Transaction email notifications are now also sent for accounts opened by providers of the None category.

Reports

Decimal precision for Fee reports has been updated. Previously, all values were rounded to two decimal places, including crypto fees. Now, full precision is preserved where applicable.

Service Providers

• The Unnax provider has been removed.

• The Skaleet banking provider has been integrated and now supports transaction processing.

• ClearBank has been added as a Confirmation of Payee provider in Crassula for the requester role.

Transactions

• Improved processing speed for transactions that required approval. These transactions are now less likely to get stuck in the PENDING state.

• Refunds no longer include associated fees. In line with Crassula standards, only the original amount is refunded. Fees must be returned manually if required.

Web Interface

• For ClearBank CHAPS v5 batch payments, the fields “Purpose” and “Category Purpose” are now displayed. The “Account” field has also been renamed to "Account number/IBAN".

• A new search feature has been added to the “Transaction history” page. The “Search” field now includes input validation, error handling, and a reset filter button.

Fixes

Administrative Panel

Resolved an issue where the "Publish" button was missing from the price list screen for some users

Statements

Fixed incorrect decimal formatting in balance reports. Previously, fiat values displayed an excessive number of decimal places (up to 16).

Verification

• Fixed an issue where user data was not properly processed by ComplyAdvantage when the crypto_extended_beneficiary_info setting was set to false.

• Corrected account blocking behavior for users rejected by Unlimit. User profiles are now only blocked if the rejection comes from the main provider (e.g., Sumsub). Rejections from secondary providers no longer trigger blocking.

Web Interface

Fixed an issue with the "Your total" and "Transfer fee" values in the payment window. These values are now updated correctly.

Upcoming Updates

Improvements

API

• The following API responses will include a new cardHolderId field:

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

  • GET /api/clients/{clientId}/issued-cards

  • GET /api/clients/{clientId}/issued-cards/{id}

• New mandatory parameters—purpose and categoryPurpose—will be added to ClearJunction CHAPS batch payments. The parameters can be configured as mandatory via system settings and are optional by default. The following methods will be 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}