Crassula Release Week 27

core v.25.06.18-25.07.1
client v.25.07.1-25.07.2

Improvements

Card Fees

Introduced configurable service charge conditions that apply only if a card is older than one billing period and has recent financial activity. Available for both virtual and plastic cards (initially for Decta), this logic can be enabled via the Operational Logic field in Card Product settings.

Mobile Banking Interface

A new verification logic is now supported in the Mobile Banking Interface. Users can access crypto services with minimal verification if their incoming volume stays below a defined threshold. If limits are exceeded, the app notifies users and prompts them to upgrade their verification level.
Added support for internal cryptocurrency transfers between users on the same platform. These transfers are processed instantly and without fees, as they don’t involve blockchain activity. This functionality is available for Web and Mobile Banking Interfaces and can be enabled via system configuration.

Transfers

Implemented transaction reconciliation logic using clearing files from the Decta provider. Any missing transactions found during comparison are now automatically added to Crassula’s records.

Verification

Added a beneficiary existence check for bank transfers using the Equals Money provider. This check is mandatory and requires 2FA confirmation for security.

Fixes

Administrative Panel

Re-enabled the “Mark as primary” button in the Banking → Accounts → Show section for active accounts. Visibility of this button can be controlled via Administration → Access Role as before.

API

Resolved a server error in the PATCH /api/clients/{clientId}/person-password endpoint when using a master key.

See Banking API for more detail.

Transfers

Updated the timestamp logic for imported transactions from the Skaleet provider. Previously, the creation time defaulted to 00:00:00, which now reflects the actual transaction time as expected.
Fixed a validation issue where the bankCountryCode was incorrectly compared against the IBAN country code. The validation now correctly uses the country associated with the BIC.

Upcoming Updates

Improvements

Accounts

We will be adding provider-related context to account details in the system. This improvement will display which service provider an account is associated with, and will be available via Web and Mobile Banking Interfaces.

Transfers

A mandatory "Purpose" field will be introduced for SWIFT transfers to the UAE for users of the Railsr provider. This requirement will apply to transfers created via both Bank transfers and Batch payments using the following API methods:

POST /api/clients/{clientId}/transfer/dynamic/swift
POST /api/clients/{clientId}/batch-transfers

More information will be provided in the upcoming product updates. See the upgrade note for details.