Crassula Release Week 9

core v.25.02.14-25.02.16
client v.25.02.7-25.02.8

Improvements

Reports

The Account Statement now displays the Finalized At date instead of the Updated At date.

Web and Mobile Interface

Improved wording in fraud prevention notifications across both Web and Mobile Interfaces.
Updated the text in the Transfer request accepted dialog in the Web Interface. The new message reads: "Recipient will get the transfer shortly."
In the Web Interface, added support for address tags in cryptocurrency transfers for XRP, XLM, and TON transactions.
E-commerce-related functionality is removed from the Web Interface following the deprecation of E-commerce services. The removed features include:
- Saved client cards (previously used for account top-ups).
- Account top-up with a card.
- Account top-up with other payment methods.
- Transit payments.
- Transit payouts.

Also, as part of this deprecation, all E-commerce-related API endpoints are now marked as deprecated in the API documentation. See the Upgrade Note for more details.

Fixes

Price lists

The Shipping Method field was previously not marked as mandatory, causing issues when editing shipping details. This has been corrected, and the functionality now works as expected.

Quotas and limits

Enhanced stability in the Sign-up process by introducing a timer that limits how frequently users can request an SMS verification code. Additionally, the API request for phone verification (phone-verification/request) now includes the X-Next-Attempt-After header.

Verification

Fixed an issue with document uploads via SumSub, where the document type for front and back side of ID cards was displayed as undefined. The correct labels (front and back) are now shown.

Upcoming Updates

Fixes

Batch payment transaction limit update

The maximum number of transactions allowed in a single batch payment will be limited to 500. Previously, larger batch payments could cause processing issues, and this adjustment ensures smoother and more reliable transaction handling.