Crassula Release Week 11

core v.25.03.5-25.03.6
client v.25.03.3-25.03.4

Improvements

Cards

Implemented OpenID Connect CIBA authentication for 3DS web authorization of payments made with Decta provider cards. Currently, this solution is available only in the Web Banking Interface.

Fees

Enhanced Charged fees reporting:

• Manually created fees are now recorded in logs (Admin Panel → Banking → Transactions, Transfer Type: Fee).

• Introduced a new "Manually created" filter in the Charged fees report, allowing users to filter manually created fees separately.

• Improved report generation to include both fees from price lists and manually created fees.

Mobile Banking Interface

• Introduced the Explore section in the interface, allowing users to manage their profiles and access essential account information.

• Removed the Local Worldwide section from the Make a payment screen, as its functionality has been fully integrated into other types of transfers. This improvement is also reflected in the Web Banking Interface.

• Added support for address tags in cryptocurrency transfers for XRP, XLM, and TON transactions.

Transfers

Added the allowed_manual_transfer_providers parameter in the configuration, enabling administrators to define available payment methods when creating payments from the Administrative Panel.

Fixes

API

• Restored the local field in the GET /api/clients/{clientId}/transfer/methods API method, resolving issues where users were unable to initiate transfers.

• Fixed validation for metadata parameters in the /api/clients/{clientId}/companies/{companyId} request, where values like "0" previously triggered a 422 error.

• Fixed an issue where the externalFilter parameter in GET /api/clients/{clientId}/issued-cards/{id}/external-transactions did not properly support filtering operators (eq, ne, gt, ge, lt, le) for trnTime. Filtering now functions correctly.

See Banking API for more detail.

Cards

Resolved an issue with incorrect Decta provider card balances in the UI, ensuring that Current and Available balances now match the values returned by the provider.

Fees

• Updated the fee processing logic for Reap provider cards, ensuring that fees are deducted in the card currency instead of the user’s default currency.

• Previously, users could activate only one "Display only fee" option per price list, restricting visibility. Now, multiple "Display only fees" options can be used and displayed in all interfaces and via API.

Transfers

• International transfer enhancements in the Web Banking Interface:

  • For GBP transactions, BIC is now displayed instead of Sort Code in International transfers.

  • For Faster Payments, Sort Code is displayed instead of Bank Code.

• Limited the maximum number of transactions per batch payment to 500 to improve processing stability and prevent possible transaction failures.

• Fixed an issue preventing IFX virtual account transactions from being displayed in the system. These transactions are now properly imported and shown.

Upcoming Updates

Improvements

API

To comply with PCI DSS 4.0 standards, the POST /api/clients/{clientId}/issued-cards/{id}/change-password API method will be updated with new password validation rules. Passwords must now have a minimum length of 12 characters (or 8 characters if the system does not support 12) and include both numeric and alphabetic characters.

Card issuing

• The logic for passing the legal address parameter when ordering a card from Company accounts will be updated. A new address type, CARDHOLDER_BILLING, will be introduced and sent to the Intercash service provider as Address1/2 (Billing Address) when ordering a card.

• In the Banking Web Interface, a new form for selecting an address and shipping method will be added to the virtual card ordering flow for the Intercash provider. This form will appear if the shipping_address_for_virtual_card configuration parameter is set to true.

Fixes

Transfers

Previously, when a transaction was created via the Administrative Panel, transactions in “Pending” status could be counted again in the limit calculation, leading to incorrect limit calculations. This issue will be resolved in an upcoming product update.