Back to work

2024-2026 · Bank payment operations

Merchant Pro

Every payment needs a record bank teams can act on.

Used in-house by: Zenith Bank Gambia · Zenith Bank Sierra Leone

Merchant Pro · Payment collection dashboard · Click to enlarge

The operational side of a payment

I designed the internal payment-management experience behind Merchant Pro, used by Zenith Bank in Sierra Leone and The Gambia. In 2025, the product handled tens of millions of leones and tens of millions of dalasi in payment value, bringing collection status, transaction records and SmartKorpor-related payments into one bank-facing workspace.

Project-reported 2025 payment values, shown separately in each market’s currency.

Tens of millions of leones
2025 payment value in Sierra Leone
Tens of millions of dalasi
2025 payment value in The Gambia
2 markets
Used in-house by Zenith Bank
Inside this case study

Payment value in live use

Project-reported figures for 2025 put payment value processed through Merchant Pro at tens of millions of leones in Sierra Leone and tens of millions of dalasi in The Gambia. These are local-currency payment values for the two markets, reported separately, rather than a transaction count or a combined converted total. My contribution was the internal product design that helps staff review collection status, administration and transaction evidence.

The product and its users

Merchant Pro is a payment merchant application for internal bank and company teams. The Zenith Bank implementation is live and used in-house in Gambia and Sierra Leone. Its purpose is to give staff a clear view of payment collection activity and the administrative setup behind it.

My contribution at IETECH

I worked on Merchant Pro as a Product Designer at IETECH. The work presented here covers the bank-branded login, payment collection dashboard, sidebar navigation, reusable input states, transaction receipt and support access.

Making payment activity easier to read

The collection dashboard separates successful, failed, pending and cancelled payments, with a transaction history entry point and a month-by-month activity chart. The design gives staff a starting point for understanding payment activity before reviewing individual records. The numbers in these supplied design screens are illustrative UI content, not reported bank performance.

SmartKorpor: public-service payments in Sierra Leone

My Merchant Pro work also included SmartKorpor-related payments. SmartKorpor is a payment and settlement platform used for public and private services in Sierra Leone. Its public portals cover services such as vehicle and driver licensing, fines and government-service payments, with multiple payment channels and digital receipts. This is the wider payment context behind that part of my work. My contribution sits within the bank-facing Merchant Pro experience; the public portals illustrate the services involved rather than interfaces I claim to have designed in their entirety.

Organising a complex administration space

I grouped the application into Dashboard, Admin, Operation and Report. The Admin structure brings together client profiles, account types, branches, branch till accounts, currencies, merchant setup, charges, settlement accounts, charge concessions and role levels. Active and expanded states help users keep their place; the navigation search is intended to help them find a module without repeatedly opening each group.

Administration groups, expanded navigation and an active location within the application · Click to enlarge

Designing states, not just populated screens

I worked on a component-based design system for Merchant Pro, defining reusable form controls, navigation patterns and their interaction states. Empty, selected, disabled and permission-restricted fields follow consistent rules, including explanations when staff cannot edit a value. That consistency makes repeated administrative tasks easier to understand and gives engineering a clear reference for behaviour across modules.

Reusable controls with empty, selected, disabled and permission-restricted states · Click to enlarge

Keeping transaction evidence close to the work

The receipt design brings the amount, payer, bank reference, payment identifiers, date, payment method and remark into one view, with share and download actions. A nearby support entry point offers a way to ask for help when an issue prevents staff from completing their work.

A payment record with references, receipt actions and support access · Click to enlarge

Live use

Merchant Pro is currently in use inside Zenith Bank Gambia and Zenith Bank Sierra Leone. The screens shown here document the interface and its component decisions; they do not represent live customer transactions or measured business results.

My design contribution at IETECH

  • Organised payment collection around transaction status and activity trends, giving bank staff a clear starting point for reviewing operational data.
  • Defined the information architecture across administration, operations and reporting, with navigation states that preserve context in a complex application.
  • Documented reusable form behaviours, including disabled and permission-restricted states, so the interface explains what staff can do and why.
  • Brought payment references, payer details and receipt actions into one transaction view to support traceability and follow-up.
  • Applied Zenith Bank’s identity to the authentication experience and kept support access close to the operational workflow.
  • Worked on SmartKorpor-related payments as part of the Merchant Pro application.
Bank-branded authentication for internal users · Click to enlarge

SmartKorpor product context