Crassula Release Week 13
core v.25.03.18-25.03.19
client v.25.03.7-25.03.8

Improvements
Administrative Panel
Improved filtering in the Reports → Agent Fee section to include users linked to both agents and clients. The enhanced filter works with any filter option and shows all relevant records for agents and non-agents alike.
Card issuing
Updated the logic for passing the legal address parameter when ordering a card from Company accounts. A new address type, CARDHOLDER_BILLING
, is introduced and sent to the Intercash service provider as Address1/2 (Billing Address) when ordering a card.
Transactions
Implemented synchronization of account balances and transactions for accounts managed by the CurrencyCloud provider. Additionally, the currency is now displayed in the synchronization message for transactions with the "skipped" status.
Outgoing UK Local transfers now include a confirmation check for the recipient’s information on the Web Interface, ensuring that users can verify the validity of recipient details before confirming the transaction. This is implemented through Confirmation of Payee (CoP) functionality.
Fixes
API Documentation
Added missing information on creating draft payments for SEPA, Internal, SWIFT, Local, and Crypto transactions via the new API endpoint POST /api/clients/{clientId}/drafts/{type}
.
See Banking API for more detail.
Transactions
Fixed an issue where hold amounts for Decta provider cards did not correctly account for external fees, resulting in inaccurate balance displays. The external fee is now added to the transaction amount, and the balance calculations are correct.
Resolved an issue with Reap provider card transactions where the decline reason for hold transactions was not being saved or displayed properly.
Upcoming Updates
Improvements
Notifications
Cooldown logic for SMS verification codes will be updated to apply different waiting periods for verified and unverified users. The corresponding API methods will also return updated headers, including MessageCooldown
, X-Next-Attempt-After
, and Retry-After
, to reflect the cooldown status accurately. Refer to upcoming product updates for more details.
Authentication
OAuth 2.0 authentication will be introduced in Web and Mobile Interfaces using Okta Identity as the provider. This change ensures a more secure and streamlined login experience by replacing the traditional email-password login method with OAuth-based authentication. Please note that this is just the initial implementation of the functionality.