Skip to main content
Skip table of contents

Crassula Release Week 10

core v.25.02.15-25.03.3
client v.25.03.1-25.03.2

Improvements

Administrative Panel

The “Get Requisites” button has been added to the Accounts section in the Admin Panel for providers that support the GET /api/clients/{clientId}/accounts/{accountId}/requisites method. These include Bitgo, IOHub, Iorys, Fireblocks, Crassula, VirtualClearJunction, CurrencyCloudReal, and Railsbank. The button appears only if there is at least one entry in the “Provider Account Numbers” section. Clicking the button fetches any missing account details from the provider via an API request but does not update existing requisites.

Agents

The eligibility criteria for agents issuing card products via API have been updated. Previously, agents could not issue card products, resulting in a 403 error when attempting to do so. The criteria are now correctly validated, allowing authorized agents to issue card products.

API

The pin parameter has been removed from the response of the following API methods:

  • POST /issued-cards/{id}/activate

  • POST /issued-cards/{id}/change-password

  • POST /issued-cards/{id}/change-pin

  • POST /issued-cards/{id}/reissue

Sensitive card data (PINs, card numbers, and CVC codes) will no longer be available in unencrypted form. The following methods, which previously allowed users to receive unencrypted responses, will now return only encrypted data:

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

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

See Banking API for additional details.

Currencies

USD has been added as a supported currency for the Railsr provider.

Verification

Additional validation has been introduced to prevent users from adding a phone number that is already in use by another user. Previously, if the person’s profile was not fully verified, the system returned a 500 error. This has been corrected to a 422 error with a detailed message.


Fixes

Fees

  • Fixed an issue where fees remained in the “Draft” status if the provider was included in the ignore_credit_transaction_in_internal_transfer_providers configuration. Now, when a fee is charged from a real account, a debit transaction is created, while the credit transaction is not created but imported from the provider. This issue and the fix apply to the IFX provider.

  • Fixed the display of zero-value fees in price lists. Previously, fees with a value of 0 were not displayed in the Admin Panel interface.

Transactions

  • Fixed an issue with recalls for the Centrolink provider. When processing a refund, an additional duplicate refund transaction was created, resulting in users receiving a double refund amount. This issue has now been resolved.

  • Fixed an issue where attempting to make a Bank Transfer via the Web Interface resulted in an infinite loading screen. The transfer process now functions as expected.

Upcoming Updates


Improvements

API

The validation and descriptions for the following API endpoints will be updated:

  • /api/clients/{clientId}/emails/{id}

  • /api/clients/{clientId}/phones/{id}

JavaScript errors detected

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

If this problem persists, please contact our support.