Ecobank Business App and Mobile 5 Admin

Admin and configuration systems for onboarding, requests, audit trails, campaigns, documents, feature controls, and maker-checker approvals across Ecobank digital banking channels.

Metrics

30+ affiliates

Maker-checker approvals

Audit-backed controls

Ecobank Business App and Mobile 5 Admin screenshot

Problem

The work started here.

Regional banking teams needed centralized control over onboarding, configuration, approvals, and operational changes without weakening security or auditability.

Research

Mapped onboarding, request, campaign, and document configuration flows with product and operations stakeholders.
Reviewed approval paths for sensitive banking operations that required maker-checker enforcement.
Identified the feature controls that needed dynamic enable and disable behavior across regions.

Planning

Grouped workflows into role-aware modules for onboarding, request management, audit trails, campaigns, and document configuration.
Defined configurable service controls for onboarding, transfers, payments, cards, and settings.
Planned approval states so sensitive updates could be submitted, reviewed, approved, rejected, and audited.

Architecture Highlights

Frontend modules used Angular, React, and Next.js surfaces depending on the platform context.
Spring Boot services exposed structured workflow APIs aligned with business domains.
SSO and RBAC guarded routes, actions, and data visibility across operational roles.

System Design

Maker-checker records preserve submitter, reviewer, decision, justification, and timestamps.
Feature-control changes require audit-backed justification before taking effect.
Role permissions separate configuration, review, approval, and reporting responsibilities.

Challenges

The same platform needed to support many affiliates with different operational needs.
Sensitive actions required strong controls without making daily admin work slow.
Audit data had to stay clear enough for governance and compliance reviews.

Solutions

Built reusable workflow patterns for requests, approvals, comments, and audit trails.
Added dynamic feature toggles with required justification for risky service changes.
Structured admin pages around clear task states and permission-aware actions.

Performance

Kept data-heavy admin views organized with modular screens and scoped fetching.
Reduced repeated implementation work by reusing approval and audit UI patterns.
Improved operational response with real-time notification flows.

Tech Stack

Angular

React

Next.js

Java

Spring Boot

SSO

RBAC

Code Snippet

const request = await submitForApproval({
  service: "transfers",
  action: "disable",
  reason,
  makerId: user.id,
});

Gallery & Animations

The final product uses subtle hover tilt, reveal choreography, and responsive image transitions to make the case study feel alive without turning the page into a heavy demo reel.

Ecobank Business App and Mobile 5 Admin gallery image 1

Ecobank Business App and Mobile 5 Admin gallery image 2

Lessons Learned

Banking admin tools work best when governance is built into the workflow, not added after launch.
Configurable controls need visible reasoning so teams can trust each change.
Role design is part of product design when every action carries operational risk.

Research

Mapped onboarding, request, campaign, and document configuration flows with product and operations stakeholders.

Reviewed approval paths for sensitive banking operations that required maker-checker enforcement.

Identified the feature controls that needed dynamic enable and disable behavior across regions.

Planning

Grouped workflows into role-aware modules for onboarding, request management, audit trails, campaigns, and document configuration.

Defined configurable service controls for onboarding, transfers, payments, cards, and settings.

Planned approval states so sensitive updates could be submitted, reviewed, approved, rejected, and audited.