Skip to main content
Skip table of contents

Crassula Release Week 35

core v.25.08.8-25.08.9
client v.25.08.6-25.08.8

Improvements

API

  • Added the paymentPurpose field to the response of the api/clients/{clientId}/transactions/{transactionId}/flat endpoint.

  • The beneficiaryCountryCode and bankCountryCode fields were added to the /transfer/account-name-check request. These fields are now required for the Equals Money provider.

See Banking API for details.

Mobile Interface

Improved the error message shown when attempting to issue a card without a payment account to cover issuance or delivery costs. The message now clearly states the cause of the failure.


Fixes

Crypto

Fixed an error that occurred when exchanging SOL to USDT. The operation now completes successfully.

Payments

  • Resolved an issue where recall transactions with Centrolink remained pending. These recalls are now processed correctly.

  • Fixed a bug that caused the “Payment Purpose Code” field to be lost when saving a draft transfer for Railsbank (UAE). The field is now retained and visible when using a draft.

Reports

Fixed an error that occurred when generating Accounting and Historical Accounting reports with multiple account status filters.

Web and Mobile Interfaces

Fixed alignment issues on the Settings → Fees page in the Web version for mobile devices. Previously, long text strings could overflow the content block. The layout now adjusts correctly.

Upcoming Updates


Improvements

API

Validation rules will be updated for Bank transfers by the IFX provider:

  • recipientIban: Will become a required field.

  • beneficiaryAddress: Maximum length will be increased from 70 to 200 characters.

  • recipientName:

    • Expression requirements will change from ^[a-zA-Z.' ]+$ to ^[a-zA-Z0-9\/\-?:().,'+\s#=!"%&*<>;{@\r\n]*$

    • Maximum length will increase from 35 to 140 characters.

  • details: A maximum length of 35 characters will be enforced.

  • recipientAccount: Will become required for SWIFT transfers.

If you're using IFX-related endpoints, make sure to update your requests to comply with the new validations. Otherwise, validation errors will be returned. See Upgrade Notes Week 35 for details.

JavaScript errors detected

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

If this problem persists, please contact our support.