UI/UX Designs

The brief from stakeholders was clear: the existing online banking interface was outdated and generic, the kind of flat, bordered design that every Nigerian bank had at the time. They wanted something modern, distinctive, and premium-feeling, the kind of interface that signals trust and quality the moment a customer logs in.

I proposed applying Apple's Liquid Glass visual language, translucent layered panels, soft blur effects, depth created through frosted surfaces, and light that feels like it passes through the interface rather than sitting on top of it. For a banking product, this was a deliberate choice: glass conveys clarity, precision, and transparency, values that matter in financial services and that the existing design completely failed to communicate.

The full dashboard covered account overview, real-time transaction history, domestic and international transfer flows, and loan management. The translucent panel system meant that content hierarchy could be communicated through depth and blur intensity rather than hard borders, a far more sophisticated approach than the flat, table-heavy designs common across the sector. Every state, from loading to empty to error, was designed within the same glass vocabulary to keep the experience consistent throughout.

Cooperative societies across Nigeria are largely managed on spreadsheets or through fragile legacy tools that weren't designed for the job. The brief was to design a proper administrative interface, one that could handle the full lifecycle of a member's financial relationship with the cooperative, from their first contribution to loan repayment and eventual withdrawal.

The core workflows driving the design were: tracking member contributions (both recurring and lump-sum), processing loan applications and managing the approval queue, handling withdrawal requests, and monitoring repayment schedules against outstanding loan balances. Each of these domains has its own data model and user intent, so the design needed clear separation between them without creating a navigation maze that overwhelmed a single cooperative officer managing everything.

I designed around a permission-layered admin view where the primary role, the cooperative officer, lands on a health dashboard showing pending approvals, overdue repayments, total pooled funds, and recent member activity at a glance. Every approval action required a confirmation state and an audit note, building a paper trail into the design rather than treating it as an afterthought. The result was an interface that gave small financial institutions the kind of operational clarity that previously only large banks could afford.

Paysure Core is a fintech infrastructure layer, the kind of product that sits underneath consumer and business applications and handles the routing, processing, and orchestration that makes financial products work. The dashboard needed to give administrators full control over everything: the APIs exposed to partners, the service providers (payment processors, telcos, data aggregators) integrated into the stack, and the products built on top of that infrastructure.

The design challenge was scale and operational risk. A single admin view spans multiple business domains simultaneously, and any mistake in this interface, a misconfigured API endpoint, a disabled service provider, a mispriced product, can cascade into failures for every downstream user and client. Every design decision had to balance information density against cognitive clarity, making the interface powerful without being overwhelming.

I designed around three primary navigation pillars: Products, Providers, and APIs. The homepage surfaced system health at a glance, uptime indicators, request volumes, error rates, and provider status, so administrators could assess the state of the entire platform in seconds. Configuration flows were deliberately step-by-step with explicit confirmation gates, diff previews before applying changes, and a full audit log accessible from every entity. The design system used a dark, high-density visual language consistent with infrastructure tooling, prioritising information over decoration.

Most children grow up with no real experience of money until they're expected to manage it independently. CoolPay Kids was designed to bridge that gap, a GoHenry-style product built for the Nigerian and broader African market, where financial literacy is rarely taught systematically at home or in schools. The proposition is simple: parents set tasks with monetary rewards, children complete them, earn their allowance, and learn to manage what they've earned.

The app has two entirely distinct interfaces sharing the same product. The parent view is structured and controlled, task creation, reward amounts, spending approvals, savings goals, and a full view of the child's account activity. The child view is built to be opened willingly, with playful illustrations, animated celebrations for task completion, a balance display that feels more like a game score than a bank statement, and a savings jar that visually fills as goals get closer. Designing both within a single coherent product without either feeling like a compromise was the central design challenge.

The child interface required the most iteration. It needed to feel like an app kids actually want to open, not a financial product dressed up with cartoon characters. I used a bold, high-contrast colour palette anchored in warm amber and coral tones, oversized typography for all monetary amounts, and micro-interactions that reward completion with satisfying animations. Every screen was tested against a simple question: would a ten-year-old understand this without help? The adult logic, interest, budgeting categories, spending limits, is present in the parent layer only, surfacing to children only as the simple fact of what they've earned and what they're saving for.