Alaje Admin — Building the frontend for a payment platform
A React-based Admin platform designed to support payment operations, platform management, and merchant oversight.
I worked as the Frontend Engineer responsible for building the Alaje Admin platform — the operational side of a payment gateway that gives internal users visibility and control over the wider payment ecosystem. My work involved translating product designs into responsive, functional interfaces and integrating them with the required backend and third-party services.
- Frontend Engineer
- React · TypeScript
- Payment Channel Monitoring · Merchant & User Management · Settlements & Reconciliation · Reports & Audit Logs
The challenge
- Internal teams needed a single place to monitor activity across the wider payment ecosystem.
- The admin platform brought together many distinct operational areas — merchants, users and roles, MDA accounts, transactions, settlements, reconciliations, tickets, audit logs and reports — that all needed to live in one coherent interface.
- Large amounts of operational information had to be presented clearly rather than overwhelming administrators.
- Alaje integrates with backend and third-party services, so integration timelines occasionally affected the overall development process.
My contribution
- Converted product designs into functional interfaces
- Built the frontend application in React
- Created reusable and maintainable UI components
- Implemented responsive user interfaces
- Integrated frontend features with backend APIs
- Integrated with external and third-party APIs where required
- Tested features extensively to ensure they worked as expected
The Admin platform was built by converting the provided designs into reusable React components and application pages — dashboard layouts, navigation, data displays, tables, forms and status indicators. Once the interfaces were in place, I integrated them with the backend services powering the platform. Because some features depended on external and third-party services, development required continuous testing and coordination to confirm each feature worked correctly once its required integration became available.
A member journey
Because this was a payment-related product spanning many operational areas, data displayed in the admin dashboard needed to be accurate and reliably kept in sync with backend and third-party services.
I tested features repeatedly to confirm that data was displayed correctly, that API integrations behaved as expected, and that transaction and operational information was accurately reflected in the interface.
Since some integrations weren't always ready at the same time as the frontend, rigorous, repeated testing was the way to catch mismatches before they reached administrators relying on the dashboard for operational decisions.
Impact
- Functional frontend implementation delivered for the Alaje Admin platform
- Centralised dashboard covering payment channels, merchants, users, MDA accounts, transactions, settlements, reconciliations, tickets, audit logs, reports and platform configuration
- Admin frontend integrated with the backend and third-party services powering the platform
Building the interface was only one part of delivering a working product — dependencies on backend and third-party services could significantly influence timelines. That reinforced the need for continuous testing and coordination so features worked correctly once the required integrations became available.
Evidence & recognition — coming soon.