Crassula Release Week 44

core v.24.10.15-24.10.21
client v.24.10.9-24.10.11

Improvements

Accounts

ClearJunction has introduced a new API for closing virtual IBANs. It is now possible to close ClearJunction Virtual accounts directly through the Crassula system via the Admin Panel or API. The actual process remains unchanged, and no additional action is required.

API

Enhanced documentation for the following API endpoints:

• POST /api/clients/{clientId}/identification-requests

• GET /api/clients/{clientId}/accounts

• GET /api/clients/{clientId}/accounts/{accountId}/iban/{iban}/balances

• POST /api/clients/{clientId}/account/{accountId}/metadata

• GET /api/clients/{clientId}/account/{accountId}/metadata

See Banking API for additional details.

Documentation

A new Upgrade Notes page has been created to provide clients with pre-deployment guidance on upcoming changes in Crassula’s platform. This page ensures that users can prepare for significant updates before they are officially released, minimizing potential disruptions. Checking this page between releases will keep you informed about important updates that may require action. See Upgrade Notes for details.

Payments

• A redirection mechanism has been added for Clearbank real and virtual accounts, redirecting payments to internal transfers if the recipient account specified in SWIFT is found within the Crassula’s or service provider's system.

• Now, the recipient bank's country is resolved directly from IBANs. The functionality is supported by BoL and ClearJunction accounts.

• The Unlimit provider has been added for dynamic payments.

• Following B4B's requirements, transactions marked with an error will now be accepted, awaiting a webhook for further confirmation. Previously, such transactions were declined, but now they are approved until a reversal transaction is received. The improvement covers only approved (200) transactions with the Declined status and ERROR.

Web Interface

The validation message for exceeding exchange limits has been updated from “You’ve reached exchange transactions amount limit this period” to "Please reduce the amount to complete currency exchange”.

Fixes

Currency exchange

• Fixed an issue with Clearbank where exchange fees were not displayed for exchange rates, even if they were applied. The functionality is fixed and works as intended.

• Fixed an issue with rate retrieval for Clearbank, ensuring that rates are displayed correctly when the exchange amount in a request is less than the minimum limit.

Mobile Interface

Fixed an issue that prevented file uploads for batch payments in the Android app.

Payments

Resolved a case where completing a parent transaction also completed child transactions, causing commission transactions with a WAITING_FOR_FUNDS status to move to complete and leading to negative balance. The issue stemmed from Iorys/ioHub using an outdated flow that forced child transactions to complete once the parent was completed, regardless of available funds. This behavior has been corrected, and such transactions will remain in WAITING_FOR_FUNDS status.

Upcoming Updates

Improvements

API

• An API method for importing incoming payments for IFX real accounts will be implemented.

• The failure webhook for ClearBank payments will be updated to report all observed failure reasons instead of just one.

• New FX functionality will be introduced after integrating Railsr FX, enabling currency exchange for GBP and EUR.

• Automatic Railsr SWIFT payments will be added, replacing the manual scheme for such transactions.

• The new API method /api/clients/{{clientId}}/transfer/account-name-check will verify payment details when transferMethod=faster_payments or chaps are used on CJ accounts. For other payment methods and providers, the response will return NOT_ENROLLED.

• The use of manually created referral codes will no longer be supported (referral_code: false). Once this update is live, all existing referral codes will be deleted. The functionality will be replaced with a new improved workflow. See Upgrade Notes Week 44 for additional instructions.

Compliance

The Waiting for Check stage will include multiple checks to improve transaction validation:

• Compliance Transaction Check: Configurable via the transaction_check settings and executed by providers such as GFS, Salv, and CA. This check will run when configured for specific payment types (e.g., GFS for local payments).

• Account Name Check: Performed by the provider, will be implemented through CoP (Confirmation of Payee) checks.

Limits

The approach to editing and deleting thresholds on the Banking → Limits page will be revised. It will be possible to edit existing thresholds. New thresholds will be validated to avoid duplicating values.