Crassula Release Week 28

core v.25.07.1-25.07.4
client v.25.07.1-25.07.6

Improvements

Cards

Updated the logic for retrieving delivery tracking numbers for Decta cards. Previously, all cards issued to the same cardholder had the same tracking number. Now, each card receives its own unique tracking number.

Verification

Secondary verification via the Skaleet provider is now supported. This applies only to persons and is mandatory for activating Skaleet accounts.

Web Interface

Introduced a new notification banner to inform users about the option to upgrade their profile to a higher Tier once their usage limits are reached. The feature is controlled through system configuration settings. See Tiers for details on the verification level functionality.

Fixes

API

Fixed an issue where the previous email or phone number retained the primary: true flag when a new primary contact was set. This caused multiple primary entries to appear in the API response. The flag is now updated correctly.

Cards

Fixed the display logic of action buttons in the Issued cards section of the Admin Panel. The Block, Decline, Recheck status, and Suspend buttons were previously not shown in certain cases. They are now displayed consistently.

Transactions

Fixed an issue with importing Decta transactions. Unnecessary warnings no longer appear during synchronization of Decta transactions in the Accounts section.

Web Interface

Corrected the login error message behavior. Previously, users received the message “Your session has expired. Please log in again” even when entering invalid credentials. The system now correctly shows “Invalid credentials” in these cases.

Upcoming Updates

Verification

The verification flow for Crassula, Sumsub, and Payall will be updated. Previously, if Sumsub rejected a client but Payall assigned a low-risk score during risk screening, the user's profile was activated based on Payall's assessment.

Sumsub will now act as the primary verification provider. If Sumsub rejects a client, the Crassula profile will remain inactive, regardless of the Payall score. Payall's risk assessment will no longer influence profile activation during onboarding.