.png)
Crassula Release Week 39
core v.24.09.6-24.09.7
client v.24.09.6-24.09.9
New Features
Automatic Account Creation on Top-Up
Automatic account creation has been introduced for card top-ups involving currency conversion. This enhancement ensures that when a card is topped up in a different currency (e.g., topping up a euro card from a GBP account), an account in the target currency is automatically created, the top-up sum is converted and then transferred to the card account. The functionality is enabled in system configs. Contact your manager for configuration details.
Card Products
The Card product functionality has been added to the web interface, allowing users to:
Select card products during the card order process.
View card product fees during and after ordering a card.
This feature is currently available for Decta, with plans to roll it out to other providers in the future. The functionality is enabled in system configs. See Card product for additional information and contact your manager for configuration details.
Card Withdrawal
The Card Withdrawal feature has been introduced, allowing users to transfer funds from a card account to another client account. This feature is the opposite of a top-up and is recommended for use with Decta cards. The functionality is enabled in system configs. Contact your manager for configuration details.
Improvements
Accounts
Interledger accounts can now be separated, allowing different interledger setups for currency exchange and internal operations. This enhancement applies to any provider integration that supports interledgers.
Administrative Panel
A new "Account restriction" section has been added to the Reports menu. It will display provider-specific restriction instructions in the future once the development is finished. Currently, the new section is available as a placeholder for the upcoming account restriction functionality.
An additional confirmation has been added when releasing transactions from hold, requiring administrators to confirm the reset of
ProviderEndToEndId. Admin actions will be logged in Activity Logs.The restriction on setting card fees as both a percentage and a fixed value has been removed.
API
Improvements have been made to the API to support the Card Product concept. A new API method,
GET /api/clients/{{clientId}}/issued-card-products/{productId}, has been introduced to retrieve card product data.A new header,
X-TFA-User, is required when using an API key for actions protected by two-factor authentication (2FA). If the header is not provided, a 422 error will be returned with the message: "Unable to find the confirmation code owner. Use the 'X-TFA-User' header."
See Banking API for details.
Communication
Support for multiple SMS providers has been added, with prioritization settings allowing administrators to specify which providers are excluded from specific countries. The system will cycle through the configured providers (e.g., Provider 1, Provider 2, Provider 3) in the specified order.
Compliance and 2FA
The list of fields sent to ComplyAdvantage has been extended.
A cooldown timer for 2FA code requests has been added, improving the functionality to prevent multiple attempts.
Payments and transactions
Support for receiving CHAPS payments from Railsr has been added. Outgoing CHAPS payments are not supported.
Bank transfers (dynamic payments) have been implemented for Clearbank UK. The functionality is not supported yet by Clearbank EU.
Web Interface
The currency dropdown has been removed when withdrawing from single-currency saving accounts (vaults). A fixed currency is now displayed.
The naming convention for issued cards has been revised. The new card name format is the following:
Virtual cards:
{currency_name} Virtual *{last 4 digits of the card}.Plastic cards:
{currency_name} Plastic *{last 4 digits of the card}.
Fixes
Administrative Panel
Fixed an issue where filtering in the Banking → Accounting → Filter section resulted in an error related to an incorrect postal code.
API
Fixed an issue where the periodStart date filter was ignored, affecting the generation of reports via POST /api/reports/banking/accounting/export-requests/{format}.
Transactions
Resolved an issue when processing USDT.t transactions where fees could not be applied correctly.
Fixed an issue where cooldowns were blocking transfer creation if a Client API Key was being used, which allowed bypassing 2FA.
Web Interface
Corrected an issue preventing the display of accurate account details for CurrencyCloud mono-currency accounts.
Upcoming Updates
Improvements
API
Railsr is transitioning to a new KYC API standard. The person V2 API and company V2 API have been released. We are in the process of updating the person V2 API as a part of our ongoing improvements to the KYC process, following the release of the V2 API for individuals. This change aims to enhance regulatory compliance and service efficiency. The company V2 API was released on August 12, 2024, and will be addressed in later updates. Refer to the Railsr documentation for additional details on the update.