Full-Stack Developer – Custom Booking System with Instant M-Pesa Agent Payouts (Kenya)
Project description
Job Description I need an experienced full-stack developer to design and build a web application that integrates with M-Pesa for payments, using React on the front end, Node.js on the back end, and PostgreSQL as the database. Project overview The system should let users initiate and complete M-Pesa payments (STK Push / C2B), record transaction status in real time via callbacks, and manage related data (users, transactions, and core records) through a clean React interface and a well-structured Node.js API. Exact feature scope will be refined in the first week once we align on priorities. The foundation needs to be solid, secure, and maintainable. Technical requirements
- React (modern functional components and hooks)
- Node.js with a structured API (Express or equivalent)
- PostgreSQL (schema design, migrations, and queries)
- M-Pesa Daraja API integration (authentication, STK Push, callbacks, and transaction status handling)
- Proper error handling, logging, and basic security practices
- Environment-based configuration (dev / staging / production)
What I’m looking for
- Proven experience with the stack above, especially real M-Pesa integrations
- Ability to work independently on an hourly basis with clear weekly progress updates
- Willingness to discuss architecture choices and document key decisions
- Clean, readable code and a practical approach to deployment
Timeline and availability Estimated 3–6 months on an hourly basis. Medium skill level is appropriate; reliability and clear communication matter more than the lowest rate. This is a multi-month engagement. Please review your calendar carefully and disclose in your proposal any holidays or planned periods of limited availability in the next 3–6 months. Short, advance-communicated breaks are acceptable; I will hold you to the availability you state. Please also include:
- 1–2 examples of previous M-Pesa or similar payment-gateway work
- A short note on how you would structure the initial API and database schema
- Your typical weekly availability
I’m ready to start soon and will provide more detailed requirements once we connect.