Crassula Release Week 23

core v.25.06.1-25.06.2
client v.25.06.1-25.06.2

Improvements

API

• The following deprecated API methods are permanently removed from the system:

  • GET /api/clients/{clientId}/statement (please use GET /api/clients/{clientId}/statement.{_format} instead)

  • GET /api/transfer/requisites/{provider} (please use GET /api/clients/{clientId}/account/{accountId}/requisites instead)

• Introduced a new API endpoint for managing unsuccessful PIN entry attempts:

  • GET /api/clients/{clientId}/issued-cards/{id}/pin-try-counter: returns the current attempt count.

  • POST /api/clients/{clientId}/issued-cards/{id}/pin-try-counter: resets the attempt count to 0.

• Implemented transaction search by the details field via GET /api/clients/{clientId}/transactions, supporting SQL LIKE search, length validation (3–100 characters), regex filtering, and date filters.

• Moved all deprecated methods in the Crassula Banking API documentation to a separate "Deprecated" section.

See the Banking API and the corresponding upgrade note for more details.

Mobile Banking Interface

• Added a new screen for confirming account top-ups. The screen displays key transaction details including “From Account,” “To,” “Top-up Fee,” and additional information for greater transparency.

• Introduced a Reissue button in the Mobile Banking Interface for Decta cards that are blocked or nearing expiration, improving the card lifecycle management process.

• Implemented transaction search filtering to allow more precise queries within transaction history.

Transfers

• Enabled support for using accounts with the None provider for bank transfers.

• Updated the card top-up process: Funds are now first routed to a reconciliation account before initiating the top-up request to Decta, ensuring greater control and accuracy.

Fixes

Card issuing

Fixed an issue where the shipping address in the card issuance process was not updated after changes were made to the legal address.

Transfers

• Improved validation for CHAPS transfer drafts: Required fields beneficiaryCity, beneficiaryCountryCode, and beneficiaryAddress are now enforced for relevant account types.

• Resolved an issue with SWIFT transfers to the UAE by ensuring the iso_purpose_code: "FIS" is included in requests sent via the Railsr provider.

Verification

Fixed an issue where KYC data could not be passed to the Unlimit provider for account activation. The functionality now operates correctly.