Release Version 4.34.0 (April 29, 2025)

29. 04. 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.
Set variable `VUE_APP_BACK_OFFICE_CLIENTS_CHAT_PAGE_VISIBLE` to `true` to enable chat functionality on the UI.

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.
The following SQL query should be executed `UPDATE confirmation_request SET params_data = jsonb_set(params_data, '{type}', '"coin_transfer"') WHERE NOT (params_data ? 'type') RETURNING *;`

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.

The following SQL query should be executed

UPDATE confirmation_request

SET params_data = jsonb_set(params_data, '{type}', '"coin_transfer"')

WHERE NOT (params_data ? 'type')

RETURNING *;

Release migrations

–

Changes to notice

Changes to notice
`PUT /v1/close/coin/{serial}` Added mandatory fields `transferType` to determine which transfer mode is processed (allowed values `coin_transfer` \| `iban_transfer`) Wallet transfer example: `curl --location --request PUT '{{host}}/api/v1/close/coin/{{serial}}' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer eyJhbGciO_AnTJoUF_w' \ --data-raw '{ "transferType": "coin_transfer", "transferToCoinSerial": "20076743" }'` Backward Compatibility: Existing wallet transfer integrations will continue to function as before till version 4.35.0. IBAN transfer example: `curl --location --request PUT '{{host}}/api/v1//close/coin/{{serial}}' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer eyJhbGciO9F-2__AnTJoUF_w' \ --data-raw '{ "transferType": "iban_transfer", "iban": "UA213223130000026007233566001", "swift": "PBANUA2XHAF", "recipientFullName": "Maksym Oliinyk" }'`

Changes to notice

PUT /v1/close/coin/{serial}

Added mandatory fields transferType to determine which transfer mode is processed (allowed values coin_transfer | iban_transfer)

Wallet transfer example:

curl --location --request PUT '{{host}}/api/v1/close/coin/{{serial}}' \

--header 'Content-Type: application/json' \

--header 'Authorization: Bearer eyJhbGciO_AnTJoUF_w' \

--data-raw '{

    "transferType": "coin_transfer",

    "transferToCoinSerial": "20076743"

}'

Backward Compatibility: Existing wallet transfer integrations will continue to function as before till version 4.35.0.

IBAN transfer example:

curl --location --request PUT '{{host}}/api/v1//close/coin/{{serial}}' \

--header 'Content-Type: application/json' \

--header 'Authorization: Bearer eyJhbGciO9F-2__AnTJoUF_w' \

--data-raw '{

    "transferType": "iban_transfer",

    "iban": "UA213223130000026007233566001",

    "swift": "PBANUA2XHAF",

    "recipientFullName": "Maksym Oliinyk"

}'

New functionality

Feature	Description	Benefits
Ability for cashiers to reject cash management requests initiated by the Accountant	Cashiers can reject cash management requests initiated by the Accountant, so the rejected request will be available in the operation history. Business requests related to cash input, cash collect and cash investment operations can be declined via the existing API operation `POST /v1/business-requests/{requestIdentifier}/decline` This functionality is currently available in the APIs and will be incorporated into the UI in future versions.	Enables more efficient and controlled cash management
OTP confirmation – OTP confirmation to change the status for a card issued via the provider	When OTP confirmation for change status for a card issued via the provider is enabled at the system level and for the user, the system will send OTP to the user’s verified mobile phone number or verified email, according to the user’s settings.	Enhances security for users by verifying their identity.
Ability for business users to create an account close request with the transfer of the remaining balance to the specified IBAN	Business users can create an account close request with the transfer of the remaining balance to the specified IBAN This will be available on UI in the SDK.finance mobile application	Enables flexible and streamlined account closure with balance transfer.
Notification for the user when the account is closed	When the account is closed, the system creates a notification for the user. Default notification settings: in-system – enabled email – disabled SMS – disabled This will be available on UI in the SDK.finance mobile application	Ensures user awareness through notifications
Ability for service users to specify three selling points for the contract	Service users can specify three selling points for the contract	Enables flexible promotion of services by defining key selling points in contracts.
Ability for business users to see the list of contracts with monthly fee value and selling points, and with the current contract marked	Business users can see the list of contracts with monthly fee value and selling points, and with the current contract marked This will be available on UI in the SDK.finance mobile application	Enables easy contract comparison with key details and the current contract highlighted.
Ability for business users to see contract details with all commissions and monthly fee	Business users can see contract details with all commissions and a monthly fee This will be available on UI in the SDK.finance mobile application
Ability for business users to change the contract for themselves	Business users can change the contract for themselves This will be available on UI in the SDK.finance mobile application	Gives business users flexibility to choose and change their contract.

Improvements

–

Fixes

cashback_payer wallet is not used and is not created anymore

API changes

Updated

PUT /v1/close/coin/{serial}

Added mandatory fields transferType to determine which transfer mode is processed (allowed values coin_transfer | iban_transfer)

sellingPoints node added to responses for the following APIs

POST /contracts/for-update

POST /contracts/view

PATCH /contracts/{contractId}

POST /contracts/{contractId}/copy

added sellingPoints node to the request

GET /v1/profiles/my

contractId added to the response

monthlyFee section was added to the response of APIs

POST /v1/contracts/view
POST /v1/contracts/for-update

Added

GET /coin/close-requests

PUT /contracts/{contractId}/selling-points

Deprecated/Deleted

–

I18n properties changes

–

Configuration changes

Added the following configuration parameters to the application.yaml:

spring:

  jpa:

    properties:

      hibernate:

        order_inserts: true

        order_updates: true

        jdbc:

          batch_size: 50

The following keys and values were added for configuration text and subject of notification messages:

notification.account_closed.sms=Your account '${coinSerial}' has been successfully closed.

notification.account_closed.email_text=Your account '${coinSerial}' has been successfully closed.

notification.account_closed.email_subject=Account closed

notification.account_closed.push_text=Your account '${coinSerial}' has been successfully closed.

notification.account_closed.push_subject=Account closed

Database changes

Added the following indexes:

create index concurrently idx_account_balance_modification_serial on account_balance_modification(serial,created_at);

create index concurrently idx_account_def_non_deleted_account_id on account_def(account_id,id) where NOT is_deleted AND deleteaction_id IS NULL;

Permission changes

The following permissions were granted to cashier role:

BUSINESS_REQUEST_CASH_DESK_COLLECT
BUSINESS_REQUEST_CASH_DESK_INPUT
BUSINESS_REQUEST_CASH_DESK_INVESTMENT

Permission COIN_CLOSURE_REQUESTS_VIEWER was granted to the following roles

administrator
ceo
aml_specialist
antifraud_specialis

Permission COMMISSION_VIEWER was granted to the following roles:

administrator
ceo
cro
revenue_analyst
revenue_specialist
individual
merchant
corporate

Permission MONTHLY_FEE_VIEWER was granted to the following roles:

individual
merchant
corporate

Permission ORGANIZATION_CONTRACT_OWNER was added to the following roles:

individual
merchant
corporate