Crassula Release Week 4

core v.25.01.6-25.01.9
client v.25.01.5-25.01.6

New features

Extended functionality of Unlimit

The Unlimit provider now supports Interledger transactions and currency exchanges, expanding its functionality and providing more flexibility for users.

Improvements

Administrative Panel

• Validation for supported currencies has been added when creating accounts in the Admin Panel. This ensures that only currencies supported by the selected provider can be used.

• The countryCode field, which is mandatory when creating a company, is now properly validated. Previously, companies could be created without a country code, which has now been corrected by introducing a NotBlank restriction in the CreateCompanyType form.

API

• The secretKey field in the documentation for the following API methods is now correctly marked as mandatory:

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

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

• A new stateReason field has been added to the response of the GET /api/clients/{{clientId}} method.

• The documentation for GET /api/clients/{clientId}/currency/rate has been updated, removing the request body, as it should not be included.

• RSA encryption has been introduced for API responses to enhance security. While the older functionality remains for compatibility, the following methods now support an optional secretKey parameter (public RSA key):

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

  • GET /api/clients/{ID}/issued-cards/{ID}/cardholder-data. If the secretKey is provided, the response is encrypted with RSA.

See Banking API for additional details.

Legal documents

Validation for the title field in Legal Documents and Legal Document Announcements has been added, with a maximum length of 55 characters. This prevents 500 errors previously caused by longer titles.

Notifications

The text alignment in the email notification templates for IBAN generation has been corrected to ensure a consistent layout.

Transactions

• The finalizedAt field is now supported for imported card transactions and vaults, improving transaction tracking and consistency.

• Confirmation of Payee (CoP) has been implemented for transactions processed via Railsr, enhancing payment verification.

Fixes

Accounts

Resolved an issue where attempts to top up an account with an unsupported currency resulted in a 403 error. The system now returns a 422 error with a detailed message, such as "Currency EUR is not supported by the account."

Limits

Fixed an issue where global limits were applied before user-specific limits, causing transactions to be declined if the user limit with a zero currency value was unable to override the global limit with a specific currency.

Upcoming Updates

Improvements

Card issuing

Card PINs will no longer be displayed after activation. This change, which previously applied to only some providers, will now apply universally. Users will still be able to request the PIN in the issued card details section on both web and mobile interfaces.

Card products

Consent functionality will be added for card products. Users will be required to consent to changes in card fees. This feature applies only to those using card products and includes the following:

• A listener will detect changes in card product fees, while a handler will process these messages and log the announcement in the LegalDocumentAnnouncement table.

• The following API methods will cover the new functionality:

  • GET /api/clients/{clientId}/issued-cards

  • GET /api/issued-card-products

  • GET /api/clients/{clientId}/privacy-announcement