Home › Release Notes › Release Version 4.33.0 (April 16, 2025)
Explore Release Notes

Release Version 4.33.0 (April 16, 2025)

16. 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.

If Kafka is enabled and the property to use Kafka for gate transactions confirmation is enabled, Kafka topic and consumer group should be created and defined in the configuration. Check configuration changes for more details.

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

Changes to notice

API POST /tickets/view marked as deprecated

API POST conversations​/view should be used to view chats

New functionality

Feature

Description

Benefits

Ability for users to specify where OTP for confirmation will be sent

The business user or service user is able to specify where confirmation OTP should be sent – to the email, phone, or both email and phone registered as login credentials.

If user OTP confirmation is required but no settings were specified by the user:

  • if the phone number is specified for login, OTP will be sent to the phone

  • if the phone is not specified for login, OTP will be sent to the email

Enhances user experience by providing more flexibility

OTP confirmation – OTP confirmation for account closing

When OTP confirmation for account closing 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.

OTP confirmation functionality works only with enabled Kafka

OTP confirmation – OTP confirmation for invoice payment

When OTP confirmation for invoice payment 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.

OTP confirmation – OTP confirmation for gate transactions, top-up, withdrawal, purchase, and card issuing via provider

When OTP confirmation for gate transactions is enabled at the system level and for the user, the gate transaction (gate_tx) will be created in the new waiting_for_approval status.

Upon successful OTP verification, the gate transaction status will update to provider_assigned.

After OTP confirmation, the front end should immediately invoke the following API calls to finalise the transaction:

GET /gate/transactions/{{gateTransactionId}}/payer-fields

POST /gate/transactions/{{gateTransactionId}}/submit

gateTransactionId corresponds to the confirmationEntityId provided in the OTP confirmation response.

OTP confirmation – OTP confirmation to deactivate/activate the account

When OTP confirmation to deactivate/activate the account 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.

OTP confirmation – OTP confirmation to change the status for the in-system card

When OTP confirmation to change the status for the in-system card 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.

Ability for business users to close the profile if all accounts are closed

Business users can close the profile if all accounts are closed

Enhances user experience

API changes

Updated

New notificationEventType SENSITIVE_OPERATION_CONFIRMATION was added to APIs

PATCH /profiles/my/security-settings

PATCH /profiles/{userID}/security-settings

Added

PATCH /v1/profiles/close

Deprecated/Deleted

POST /tickets/view

API POST conversations​/view should be used to view chats

I18n properties changes

–

Configuration changes

Added new property file: gate-tx-messaging to allow OTP confirmation via Kafka

gate-tx-messaging:
 enabled: ${GATE_TX_MESSAGING:false}
 kafka:
 topic: ${GATE_TX_TOPIC:tx-topic-dev}
 consumers:
 status-change:
 id : ${GATE_TX_STATUS_CHANGE_CONSUMER_GROUP_ID:tx_status-change-consumers}

The following properties are used for OTP confirmation for gate operations (purchase, top-up, withdrawal, and card issuing):

Property

Type

Default Value

Description

gate-tx-messaging.enabled

boolean

false

Feature flag. Enables or disables the Gate Transaction Messaging mechanism. If false, Kafka producers and consumers will not be initialised. Controlled by the environment variable ${GATE_TX_MESSAGING}.

gate-tx-messaging.kafka.topic

string

tx-topic-dev

Kafka topic name is used for transaction messaging. Controlled by the environment variable ${GATE_TX_TOPIC}.

gate-tx-messaging.kafka.consumers.status-change.id

string

tx_status-change-consumers

Kafka Consumer Group ID is used to consume transaction status change events. Controlled by the environment variable ${GATE_TX_STATUS_CHANGE_CONSUMER_GROUP_ID}.

Permission changes

The following permissions were granted to the AML specialist role by default:

  • BUSINESS_ROLES_VIEWER

  • BANK_PROCESS_VIEWER

  • BUSINESS_REQUEST_VIEWER

The following permissions were granted to the Administrator and CEO roles by default:

  • CHANGE_LOGIN_REQUEST_VIEWER

  • CHANGE_LOGIN_REQUEST_MANAGER

  • BANK_PROCESS_VIEWER

  • BUSINESS_REQUEST_MANAGER

The following permissions were granted to the CEO role by default

  • GLOBAL_CONFIRMATION_SETTINGS_MANAGER

  • GLOBAL_CONFIRMATION_SETTINGS_VIEWER

The following permission was granted to the Individual and Corporate roles by default

  • GLOBAL_CONFIRMATION_SETTINGS_VIEWER

The following permissions were granted to the CEO, Customer Success Specialist, Customer Support, and Customer Support Manager roles by default

  • USER_CONFIRMATION_SETTINGS_VIEWER

  • USER_CONFIRMATION_SETTINGS_MANAGER

The following permission was granted to the Merchant and Corporate roles by default:

  • OPERATION_CONFIRMER

New permission created: PROFILE_TERMINATOR_OWNER

Permission granted to the Individual, Merchant, and Corporate roles by default.

Permission MEDIA_FILE_OWNER was granted to the Customer support and Customer support manager roles by default