(02) The Context
The problem
- Merchants needed clear visibility into their own payment activity within the Alaje ecosystem, distinct from the operational view built for internal admins.
- The interface needed to accurately reflect transaction and operational data pulled from backend and third-party services.
- Designs needed to be translated into a functional, responsive application rather than static screens.
- Alaje integrates with backend and third-party services, so integration timelines occasionally affected the overall development process.
(03) My Role
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
(05) The Engineering
The Merchant platform was built by converting the provided designs into reusable React components and application pages, then integrating them with the backend services powering merchant payment activity. 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.
(07) Challenges & Decisions
The challenge
Since this was a payment-related product, the merchant platform needed to accurately reflect transaction and operational information sourced from backend and third-party services.
The decision
I tested features repeatedly to confirm that data was displayed correctly, that API integrations behaved as expected, and that user actions triggered the correct responses.
(08) Results
Impact
- Functional frontend implementation delivered for the Alaje Merchant platform
- Merchant-facing interface for managing payment activity within the Alaje ecosystem
- Merchant frontend integrated with the backend and third-party services powering the platform
(09) What I Learned
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.