Explore Release Notes

Release Version 4.35.0 (May 08, 2025)

08. 05. 2025

Pre-deployment steps

To be done before deployment

Check configuration changes and apply them in the application.yaml if the default configuration has been overridden there

Check if the release contains migrations. Migrations can affect deployment and downtime.

Use GET /i18n/export/{fileName} to download files with the current i18n properties. Check if the downloaded file is correct.

Post-deployment steps

To be done after deployment

Verify permission changes and assign or remove required permissions if they have been overridden

Add new properties from the I18n properties changes to the downloaded i18n properties file and add translation for them if needed.

Use POST /i18n/import to upload and apply a previously downloaded i18n file with added new properties.

Release migrations

Changes to notice

New functionality

Feature

Description

Benefits

Ability for service users to view, approve or decline account close requests

Service users can view, approve or decline account close requests

Additional option for users to close the account and transfer the remaining amount to an IBAN

Created a provider for Cybersource integration

Cybersource provider created for wallet top-up with the following

  • ability to specify access parameters at the application level

  • ability to enable/disable the provider

  • Cybersource provider will be returned in response to the API POST /v1/gate/methods/viewafter the configuration of the commission rule in the commission profile related to this provider.

  • If the Cybersource provider is disabled, it will be returned with the field "active": false

Cybersource integration will allow us to perform a wallet top-up from the payment card

Created Cybersource client for the following Cybersource APIs:

  • POST /bin/v1/binlookup

  • POST /risk/v1/authentication-setups/

  • POST /risk/v1/authentications/

  • POST /risk/v1/authentication-results

  • POST /pts/v2/payments/

If Cybersource integration is used, the project sdk5/api-client/cybersource will be provided together with this release.

This project produces the file cybersource-client-0.0.1.jar, which contains the generated API client and models.

This project should be assembled in the same way as sdk5/sdk5-openapi-generator project (execute the command mvn clean deploy in the project directory).

Cybersource client will be used for wallet top-up, and the source-code option can be used for any other purposes, depending on the requirements.

Improvements

Fixes

The contract cannot be changed for the same one.

API changes

Updated

Added

PUT /coin/close-requests/{id}?approve=true(false)

Deprecated/Deleted

I18n properties changes

Configuration changes

Added Arabic bundle web_bundle_ar.properties

The following configuration parameters are used for the CyberSource API client:

cybersource:
integration:
baseUrl: ${CYBERSOURCE_BASE_URL:https://apitest.cybersource.com}
requestTimeout: 10 # seconds
connectTimeout: 10 # seconds
merchantId: ${CYBERSOURCE_MERCHANT_ID:testMerchantId}
keyId: ${CYBERSOURCE_KEY_ID:testKeyId}
secretKey: ${CYBERSOURCE_SECRET_KEY:testSecretKey}

Database changes

Permission changes

New permission COIN_CLOSURE_REQUESTS_MANAGER was granted to the following roles:

  • ceo

  • antifraud_specialist

  • administrator

  • aml_specialist