Skip to main content
Skip table of contents

Crassula Release Week 50

core v.24.12.2-24.12.6
client v.24.12.3-24.12.5

New Features

Card Tracking Details

Delivery details, including the delivery address, are now displayed for all cards. Additionally, Decta cards include tracking numbers to provide more precise delivery updates. This feature enhances transparency and ensures users have all the necessary information about their card shipments.

Referral program

The Referral Program feature has been introduced, allowing clients to earn bonuses for inviting friends. Both referrers and referrals can now receive a percentage of currency exchange fees, with simplified configuration options in the Price Lists and automatic referral code generation. See Referral program for additional details on the solution.


Improvements

Administrative Panel

  • A new feature flag has been added for transaction states. When enabled, the State field is hidden during transaction editing, limiting manual state changes for transactions. Contact your manager for configuration details.

  • Two-factor authentication (2FA) processes for administrators are now logged in the Authentication Logs section of the Admin Panel, providing better tracking and audit capabilities.

API

  • The GET /api/clients/{clientId}/transactions/{transactionId}/payslip method has been updated. Payslips can now only be downloaded for transactions with a type of Transfer (4) and a status other than Draft.

  • Descriptions for the POST /api/clients/{clientId}/accounts/{number}/top-up and POST /api/clients/{clientId}/accounts/{number}/wallet-top-up methods have been improved in the API documentation.

  • The GET /api/clients/{clientId}/transfer/methods API response now includes a methodDescription field, providing detailed explanations for each transfer method. These descriptions are also displayed in the mobile and web interfaces.

See Banking API for additional details.

Issued cards

Two new email notifications have been introduced for improved user communication:

  • Card Status Change: Users will now receive an email notification whenever the status of their card changes. For example, if a card is frozen, an email will be sent to notify the user.

  • Card Expiration Reminder: Notifications will be sent to users as their card approaches its expiration date. The notification period is defined in the system configs.

This functionality can be enabled for REAP cards. If you would like to enable the notifications for cards issued by other providers, contact your manager for assistance.

Payments

  • Transfer fees are now automatically collected from the Hot Wallet into a separate Fee Wallet using a Fee Collector. This allows WLs to separate client funds from charged fees. The functionality is disabled by default.

  • A feature toggle has been added to hide the Decline button in transaction details. This prevents transactions from being canceled within Crassula, ensuring stricter transaction management. The Decline button available in Transactions (pre-approval) remains, and the preapproval flow is not affected.

Web Interface

  • The payslip in transaction details now includes a UTC timezone suffix.

  • Users can now save templates when creating Bank Transfers (previously called Dynamic Payments)


Fixes

API

The response fields for the GET /api/clients/{ID}/existing-recipients method have been updated to follow the camelCase formatting in the API documentation.

Upcoming Updates


Improvements

API

A new secretKey parameter will be introduced for the following API methods:

  • GET /api/clients/{clientId}/issued-cards/{id}/pin-code

  • GET /api/clients/{clientId}/issued-cards/{id}/cardholder-data

When the secretKey parameter is used, the API will return encrypted data, including the PIN code, card number, and CVC code. This enhancement improves security and ensures sensitive data is properly protected.

Contact details

New phone numbers and email addresses will automatically be set as default, while old contact details will be moved to additional contacts. This improvement eliminates the need for multiple confirmations when updating contact details. Users will still be able to manually change default contact details.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.