Skip to content

Release 3.0.1

Release Date: 15-10-2025

Release Notes

📋 Overview

Release v3.0.1 focuses on improving system reliability and API consistency through targeted bug fixes and key feature enhancements. This update resolves several critical issues related to email OTP requests, product creation, card request flows, and public API responses. Additionally, enhancements have been made to transaction processing, consent handling, and eligibility checks, ensuring a smoother and more dependable experience across core services.

Summary

Features

  • Rain – Transaction Settlements and Adjustments Introduced improved settlement and adjustment mechanisms for Rain transactions.

  • Transaction Webhook Handling Enhanced webhook handling to support Completed, Incremental, Reversal, Refund, and Force Capture transaction events.

  • Consent and Eligibility APIs Updated consent and eligibility endpoints to deliver more reliable validation and consistent data structures.

Upgrade Notes

The sequence of steps to follow to upgrade are:

  1. Container images and configmaps
  2. DB migrations
  3. Swagger APIs

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.

Omnumi Frontend microservice

ConfigMap

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

configmap.yml
FLUTTER_CONFIG_VERSION: '3.0.1'

Omnumi card settelemnt microservice

ConfigMap

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

configmap.yml
CLIENT_AUTHORIZER_BASE_URL: '[replace with client authariser base URL]'

Card Issuer microservice

ConfigMap

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

configmap.yml
HEAP_LOGS: 'false'

DB migrations

Omnumi Core 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

Settlement Schema DB Migrations

Database backup

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

Download settelement_service_db_migrations_301.zip file available in Assets, unpack/unzip it in order to perform remaining instructions.

Create/update file in the following path [unzip-folder]/.env with credentials contents:

[unzip-folder]/.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]
DB_SCHEMA=settlement_service

Execute 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.3.0.1.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 Cards 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-3.0.1.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 Cards 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: omnumi-core-private-3.0.1.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.

Private: Card Issuer

Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select Private:Card Issuer and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: omnumi-card-issuer-private-3.0.1.json
Update settings
  1. Select Private:Card Issuer API.

  2. Open Settings tab and update:

  3. Web service URL = card-issuer microservice URL

  4. Save the changes.

Private: Omnumi Rule Engine

Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select Private:Rules Engine and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: omnumi-rule-engine-private-3.0.1.json
Update settings
  1. Select Private:Rules Engine API.

  2. Open Settings tab and update:

  3. Web service URL = rule-engine microservice URL

  4. Save the changes.

Image list

Microservice name Image tag
Omnumi Core Microservice omnumisandbox.azurecr.io/core:3.0.1-deliverable
Omnumi Rule-Engine Microservice omnumisandbox.azurecr.io/rule-engine:3.0.1-deliverable
Omnumi Card Resrvation Microservice omnumisandbox.azurecr.io/omnumi-card-reservation:3.0.1-deliverable
Omnumi Card Issuer Microservice omnumisandbox.azurecr.io/omnumi-card-issuer-service:3.0.1-deliverable
Omnumi Client Authorizer Microservice omnumisandbox.azurecr.io/omnumi-client-authorizer:3.0.1
Omnumi Card Settelement Microservice omnumisandbox.azurecr.io/omnumi-card-settlement:3.0.1-deliverable

Assets

Login into files portal