Omni-Core Monitoring Platform

Overview

GAIA and Omnicore are internal operational platforms used by PalmPay teams to manage the configuration data that supports payment and telecommunications services.

The systems provide authorised users with centralised access to institution records, channels, transaction types, inventories, routing configurations, validation rules, and operational logs.

My Role

My contribution focused particularly on the Channel Inventory Management experience and related administrative workflows.

The Challenge

Operations teams needed to manage a large amount of payment-channel configuration data without relying on direct database access or repeated engineering support.

The platform needed to support:

• Institution and payment-channel configuration.
• Inventory creation and maintenance.
• Filtering across large operational datasets.
• Activation and deactivation of individual records.
• Bulk data creation.
• Modification and deletion of existing configurations.
• Audit-log access for tracking administrative activity.
• Clear handling of API responses, loading states and system errors.

Because changes could affect live payment or telecommunications services, the interface also needed to make operational actions clear and reduce the possibility of configuration mistakes.

The Solution

I contributed to the development of reusable, API-driven administration screens that allowed authorised users to search, create and manage operational records from one interface.

For Institution Management, the platform allows users to:

• Filter institutions by business type, country code and institution.
• View institution names, standard codes and supported transaction types.
• Create individual institution records or perform bulk creation.
• Modify configurations and review activity logs.

For Channel Inventory Management, I implemented interfaces that allow operations teams to:

• Search by channel, transaction type, inventory ID and inventory name.
• View inventory volume, measurement units and channel inventory identifiers.
• Create and update inventory configurations.
• Enable or disable inventory records using status controls.
• Delete records and review change logs.
• Manage data-bundle and other service inventories from a structured table.

The screens were designed around reusable form controls, filters, tables and action components to maintain consistency across the broader platform.

Key Contributions

• Built and maintained complex administrative data tables.
• Implemented multi-parameter filtering and query workflows.
• Integrated frontend screens with backend configuration APIs.
• Developed create, edit, delete and enable/disable actions.
• Added operational feedback for loading, successful actions and system errors.
• Supported auditability through record-level log access.
• Improved the presentation of complex payment-channel data for non-engineering users.

Outcome

The platform gave operations teams a central and more efficient way to manage payment-channel configurations without depending on direct database updates.

It improved visibility into institutions and inventory records, simplified recurring configuration tasks, supported audit tracking, and provided a scalable interface for managing the operational data behind PalmPay’s payment services.

**

Portfolio note:** Before publishing the screenshots, blur the internal URL, username, institution names, inventory identifiers and any production-related data.