Release Version 4.38.0 (June 22, 2025)
- Pre-deployment steps
- Post-deployment steps
- Release migrations
- Changes to notice
- New functionality
- Improvements
- Fixes
- API changes
- I18n properties changes
- Configuration changes
- Database changes
- Permission changes
Pre-deployment steps
|
To be done before deployment |
|---|
|
Check configuration changes and apply them in the |
|
Check if the release contains migrations. Migrations can affect deployment and downtime. |
|
Use |
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 translations for them if needed. Use |
Release migrations
–
Changes to notice
|
Changes to notice |
|---|
|
|
New functionality
Improvements
|
Feature |
Description |
|
If OTP confirmation is required for the account closure, it is specified in the API response |
|
|
|
– |
|
Ability to filter the list of contracts on UI based on whether they are default or not, and show default status in the Contracts list |
New filter and field “Is default” added to the CRO → Contracts |
|
According to ISO 3166
|
|
Fixes
–
API changes
Updated |
|
For endpoints:
for request object also in request object request example:
Also in responses on create, update and view added new field response example:
|
|
The response was changed to:
confirmationRequired = true if confirmation required, otherwise – false |
|
|
|
|
|
|
Added |
|
|
Deprecated/Deleted |
|
– |
I18n properties changes
–
Configuration changes
The following parameters were added to application.yaml file:
token:
access:
...
login-changer-ttl: 60 # in minutes
payment-executor-ttl: 30 # in minutes
...
Database changes
–
Permission changes
The new technical role payment_executor was created, and the new permission PAYMENT_EXECUTOR was assigned to this role. PAYMENT_EXECUTOR permission allows calling the following API operations:
-
POST /merchant-payments/{identifier}/execute -
POST /gate/transactions/{tx}/submit