Skip to content

Release 2.9.0

Release Date: 25-09-2025

Release Notes

📋 Overview

  • Release v2.9.0 delivers major improvements in compliance and badge management, with automation, exception handling, and refined risk checks. Tenant onboarding is now more flexible with the option to proceed without KYC, while businesses gain support for multiple wallets. The console experience has also been enhanced for better usability.

  • A key bug fix addressed disbursement wallet transfers, while a few non-blocking issues remain open and will be tracked in future releases.

Features & Enhancements

  • Compliance Officers can now change ID badge assignments, Info badge assignments, and KYC details.
  • Automated badge assignment based on customer detail updates.
  • Badge Management extended with Proof of Address refinements and support for adverse media checks.
  • Tenant onboarding enabled without KYC requirements.
  • Businesses can now hold multiple wallets.
  • Console enhancements, including toolbar updates and quarterly maintenance improvements.
  • Exception management updates for Compliance Officers.

Bugs

  • Fixed issue preventing transfers from disbursement wallet to a single recipient.
  • Known issue: Updating account_status in customer_accounts (reflected as KYC Status in Console) remains open.
  • Known issue: Dependency bug linked to account_status update remains open.
  • Known issue: Badge Management enhancement (OR operator in Rule Engine) blocked by dependency bug.

Upgrade Notes

The sequence of steps to follow to upgrade are:

  1. Container images and configmaps
  2. DB migrations
  3. Swagger APIs
  4. Post Release Scripts

Container images and configmaps

All provided images, available in the Image List section should be downloaded and built to be LGPL compliant.

All new images tags will be used to update Kubernetes manifests.

Core microservice

ConfigMap

Add/replace the following values in Core microservice's ConfigMap:

configmap.yml
TENANT_COMPLIANCE_CHECK: 'true'

DB migrations

Download DB migrations ZIP file available in Assets, unpack/unzip it in order to perform remaining instructions.

DB backup

Before proceeding with remaining steps, it's strongly advised to take a database backup before proceeding.

Update credentials

Edit/create a file named development.env inside db-migrations/src/common/envs folder

db-migrations/src/common/envs/development.env
DB_HOST=[replace with db host url]
DB_USER=[replace with db user]
DB_PWD=[replace with db user password]
DB_NAME=[replace with db name]

AZURE_TENANT_ID=[replace with azure tenant id]
AZURE_CLIENT_ID=[replace with azure client id]
AZURE_CLIENT_SECRET=[replace with azure client secret]
AZURE_KEYVAULT_NAME=[replace with azure keyvault name]
DEFAULT_TENANT=[replace with default tenant name]

Execute DB migrations

Execute the remaining commands located inside the extracted content folder (e.g.: db-migrations):

Execute migrations
$ npm install
$ npm run migrate

Swagger APIs

Download Swagger APIs tarball file available in Assets, unpack/unzip it in order to perform remaining instructions.

Update API

Public (v2)

Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select public and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: Public.2.9.0.open-api.json
Update settings
  1. Select Public API.

  2. Open Settings tab and update:

  3. Web service URL = core microservice URL

  4. Save the changes.

Update methods ChainCore
  1. Open Chain tab and enable Group by tag.
  2. Expand ChainCore and update the Backend – HTTP(s) endpoint with chain-core microservice URL.
  3. Repeat operation for all listed API methods under ChainCore.
Update methods Auth
  1. Open Auth tab and enable Group by tag.
  2. Expand Auth and update the Backend – HTTP(s) endpoint with auth service microservice URL.
  3. Repeat operation for all listed API methods under Auth.
Update methods Card Issuer
  1. Open Card tab and enable Group by tag.
  2. Expand Card and update the Backend – HTTP(s) endpoint with card issuer service microservice URL.
  3. Repeat operation for all listed API methods under Card.

Partner (v2)

Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select partner and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: partner-2.9.0.open-api.json
Update settings
  1. Select Partner API.

  2. Open Settings tab and update:

  3. Web service URL = core microservice URL

  4. Save the changes.

Update methods ChainCore
  1. Open Chain tab and enable Group by tag.
  2. Expand ChainCore and update the Backend – HTTP(s) endpoint with chain-core microservice URL.
  3. Repeat operation for all listed API methods under ChainCore.
Update methods Card Issuer
  1. Open Card tab and enable Group by tag.
  2. Expand Card and update the Backend – HTTP(s) endpoint with card issuer service microservice URL.
  3. Repeat operation for all listed API methods under Card.

Private: Omnumi Core

Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select Private:core and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: private-core.2.9.0.open-api.json
Update settings
  1. Select Private:core API.

  2. Open Settings tab and update:

  3. Web service URL = core microservice URL

  4. Save the changes.

Image list

Microservice name Image tag
Core Microservice omnumisandbox.azurecr.io/core:2.9.0-deliverable
Rule-Engine Microservice omnumisandbox.azurecr.io/rule-engine:2.9.0-deliverable
Card Settelement Microservice omnumisandbox.azurecr.io/omnumi-card-settlement:2.9.0-deliverable
Frontend Microservice omnumisandbox.azurecr.io/frontend:2.9.0
Listener Microservice omnumisandbox.azurecr.io/listener:2.9.0-deliverable

post-release-scripts

Download Post Release Script file available in Assets, with (post-release-scripts-290.pdf)

Assets

Login into files portal