By Janet Abigail

….The rapid expansion of digital financial services changed the rhythm of everyday commerce in Lagos. Bank customers increasingly expected transfers, payments, account services and other transactions to happen almost instantly, while businesses sought faster ways to connect their operations to financial institutions. Mobile applications, virtual accounts, payment platforms and fintech services became increasingly embedded in the city’s commercial environment. What customers experienced as a simple transaction, however, depended on a considerably more complex technological ecosystem.

Behind many digital banking services were core banking applications, databases, authentication systems, integration platforms and application programming interfaces, commonly known as APIs. These technologies allowed different systems to exchange information and execute transactions while shielding customers from much of the complexity occurring behind the screen. For technology professionals working within Lagos’s banking ecosystem, this created a significant challenge: financial institutions needed to introduce new digital capabilities without disrupting established systems already processing critical banking operations.

Racheal Kikachukwu Ogan’s work in enterprise application support, implementation and API integration provides an example of the engineering activity behind this transformation. Her responsibilities within Stanbic IBTC included supporting business-critical banking applications before progressing into enterprise integration and API-platform implementation. 

As digital banking expanded, financial institutions increasingly needed their internal systems to communicate efficiently with external applications and business platforms. APIs provided controlled interfaces through which these interactions could occur. Their importance was particularly evident in an environment where established banking applications operated alongside newer digital platforms. Modernisation did not necessarily mean replacing every existing system. Instead, integration technologies provided a practical bridge between established infrastructure and emerging digital services.

Ogan worked within this intersection. Her responsibilities included implementing API-driven solutions across user-acceptance-testing and production environments and addressing integration challenges involving established and newer technology platforms. The work reflected a wider transformation within financial technology. Banking capabilities that had traditionally remained within institutional systems could increasingly be made available as controlled, reusable digital services supporting different applications and commercial requirements.

As API portfolios expanded, managing them effectively became equally important. Creating an API was only one component of the process. Interfaces needed appropriate testing, documentation, security controls, version management and deployment processes. Developers and approved consumers also required mechanisms through which they could discover and understand available services.

During her work in enterprise integration, Ogan deployed and managed more than 20 Open APIs across more than 10 products in a sandbox environment and more than 13 Open APIs across over six products in production, using IBM API Connect and Red Hat Linux. The distinction between sandbox and production environments was important. Sandbox environments provided controlled spaces for developers and API consumers to test integrations, while production environments required greater operational discipline because failures could directly affect live services, transactions and customers.

Ogan also managed the community surrounding the Stanbic IBTC Developer Portal, an API marketplace through which API products could be presented to developers and other consumers. Such an environment represented more than a technical catalogue. It provided an organised mechanism for making banking capabilities discoverable and reusable while maintaining institutional oversight.

One of the more difficult aspects of digital transformation in financial services was maintaining interoperability between technologies developed at different times. Banking institutions depended on established applications that could not simply be discarded whenever newer technologies emerged. These systems contained important data, processes and business logic. New digital services therefore had to communicate with existing infrastructure without compromising reliability.

Ogan’s earlier application-support responsibilities included maintaining Oracle and SQL/PL-SQL-based banking applications, conducting root-cause investigations and supporting production systems while maintaining 98.8% SLA compliance. Her subsequent integration responsibilities placed her at another point in that technological relationship: implementing new services and resolving integration issues across enterprise environments. This progression demonstrates how the growth of digital banking depended not only on customer-facing applications but also on professionals capable of understanding and connecting the systems operating behind them.

The significance of this work became particularly apparent when technical performance was connected to commercial outcomes. One of Ogan’s projects involved streamlining power vending and automating account crediting using Java and SQL. The solution addressed an operational weakness that had exposed the client to substantial recurring financial losses. By automating the account-crediting process and improving transaction handling, the implementation demonstrated how integration engineering could produce measurable value beyond the technology function. 

She was also involved in the architectural design, onboarding and deployment of a Fundable Virtual Account Service, implemented for 16 clients in user-acceptance testing and nine clients in production using REST APIs, SQL, JSON and Red Hat Linux. These examples demonstrate the economic significance of infrastructure that customers rarely encounter directly. When account crediting, virtual accounts and system integrations operate reliably, technology becomes part of the underlying machinery supporting commercial activity.

For customers moving through Lagos’s increasingly digital economy, banking technology was generally experienced through visible outcomes: a successful transfer, an account credited correctly, a payment completed or a digital service responding when required. Behind those outcomes were databases, enterprise applications, APIs, Linux environments, integration services and technical teams responsible for maintaining their interoperability.

Ogan’s progression from supporting enterprise banking applications to implementing APIs and integration platforms reflects this less visible dimension of financial technology. Her experience demonstrates how technical work occurring behind customer interfaces can influence service reliability, business efficiency and the ability of financial institutions to extend digital capabilities to businesses and other technology platforms.

In a commercial centre such as Lagos, where financial institutions, businesses, technology companies and consumers were becoming increasingly interconnected, APIs represented more than communication mechanisms between software applications. They provided essential bridges between established banking infrastructure and an expanding digital economy.

The most effective infrastructure rarely announces itself to the customer. When APIs, applications and integration layers operate correctly, the technical complexity largely disappears. A transaction simply completes, information reaches the appropriate system, and the customer continues with their day. It is this largely invisible combination of integration, reliability and engineering that helped make increasingly sophisticated digital banking experiences appear remarkably simple.