Crassula Release Week 45

core v.24.11.2-24.11.5
client v.24.11.1-24.11.2

New Features

New card provider

We are thrilled to announce the launch of the REAP card provider. Currently, only the issuance of virtual cards is supported, with no transaction functionality at this stage. Card balances are linked to existing accounts, allowing for issuance in any currency, including crypto and MCCY cards. For further details, please contact your client manager. Additional functionality for this integration will be introduced in upcoming product updates.

Improvements

Application forms

Removed the old functionality of Application forms from both API and Admin Panel.

Compliance

The Waiting for check stage now includes multiple checks to improve transaction validation:

• Compliance transaction check: Configurable via the transaction_check settings and executed by providers such as Huntli, Salv, and CA. This check is run when configured for specific payment types (e.g., Huntli for local payments).

• Account name check: Performed by the provider, the feature is implemented through CoP (Confirmation of Payee) checks.

Fixes

Administrative Panel

Resolved an issue with the middleName filter on the payments/data/identificationrequest/listpage, which was not functioning as expected. The filter now operates as intended.

API

• A 500 error occurred when invoking the POST /api/clients/{clientId}/phones/{id}/send method for an already verified person. This issue is now resolved.

• The unused 400 response code is removed from the POST /api/clients/{clientId}/issued-cards/{id}/top-up method. A 404 response is now issued instead.

See Banking API for details.

API documentation

• Improved the parameter descriptions from underscore_case to camelCase for the methods:

  • GET /api/clients/{clientId}/is-exceeded-client-limit

  • GET /api/clients/{clientId}/client-limits-exceeded

• Corrected documentation for the GET /api/clients/{clientId}/existing-recipients method by removing the unsupported type=self and adding missing recipient types for clearer guidance.

• Improved the documentation for the GET /api/clients/{clientId}/issued-cards/{id}/spent-details method by adding the response body and model to ensure comprehensive reference information.

See Banking API for details.

Limits

Previously, users experience issues when trying to edit existing thresholds. The approach to editing and deleting thresholds on the Banking → Limits page is revised: New thresholds are now validated to avoid duplicating values.

Web Interface

• Fixed an issue on the Currency Exchange page where, after switching currencies, the exchange rate label would update to the new currency name but retain the previous exchange rate temporarily, which could be misleading. Now, when users change the currency, the exchange rate field turns gray to indicate that a new rate is being calculated.

• Removed the Card accounts option from the Add funds dropdown menu in the Accounts section, as this option is not applicable to this feature.

Upcoming Updates

Fixes

API

We will be enhancing validation for the recipientIban field in the /api/clients/{clientId}/transfer/parameters endpoint. Previously, the validation pattern ^[A-Z0-9]+$ allowed special characters such as !,.[]-_^`, leading to potential errors with incorrect data. The updated validation pattern will ensure only valid characters are processed, improving data accuracy across multiple transfer methods.