Case study

Wamido Learning Platform
Full Stack Web Developer & Platform Lead
Wamido is a Moodle 4.5 learning platform for youth mentorship and Rich Kids School courses, running 19 custom plugins. I built it with PHP plugins forked from the KBM platform, Flutterwave checkout in NGN and USD with geo-based currency selection, live event sign-ups, a knowledge base, and 32 Bash scripts for deployment and course migration.
How it’s built
Wamido Learning Platform · Moodle 4.5 tenant for Wamido training with NGN/USD Flutterwave checkout
Wamido Learning Platform (training.wamido.org) is a Moodle 4.5 site for Wamido's mentorship and Rich Kids courses. I forked the KBM plugin set onto it, rebranded the theme, and added NGN and USD pricing with Flutterwave checkout, geo-based currency selection, live event sign-ups and a knowledge base. It runs 19 custom plugins, and 32 shell scripts handle deployment and course migration.
- custom Moodle plugins
- 19
- checkout currencies (NGN, USD)
- 2
- commits, all mine
- 44
- deployment and migration shell scripts
- 32
- theme Mustache templates
- 46
Technology and what it does here
- Moodle 4.5 (PHP 8.3)
- Base LMS, 4.5.10+; php83-switch.sh migrates the FPM pool
- Flutterwave
- Hosted checkout; flutterwave_verify.php re-verifies transaction id, tx_ref, status, amount and currency
- Geo-IP lookup
- Kbm_geo_country() picks NGN or USD by country unless the user chose a currency
- Mustache + SCSS
- Theme_kbm rebranded for Wamido: shell, checkout, Rich Kids and mentorship landing pages
- H5P / Content Bank
- Scripts install H5P types and migrate RKS course content into the content bank
- Bash + npm scripts
- Deploy, db/file sync, prod install, health checks, course migrations
- Nginx + MariaDB + Redis
- Production stack from prod-install.sh, shared with the KBM tooling
Implementation details
- Flutterwave verification compares the charged amount to the price authored for the charged currency, not a converted Naira price, so a buyer cannot pay the cheaper converted figure.
- The tx_ref encodes course and user id, and the callback rejects a reference that does not match the logged-in user before enrolling via self or manual enrolment.
- Currency is resolved from an explicit cookie/user preference first, then geo-IP, then default.
- local_live serves event cover images only to managers while an event is hidden, so unpublished artwork does not leak via a guessable URL.
System architecture
The Wamido Moodle deployment uses Flutterwave for checkout in NGN and USD. Moodle grants access after the server validates the transaction.
Project screenshots
Open full-size screenshot in a new tabResults and testing
Wamido’s course-tracks view
The screenshot below shows the learner-facing course catalogue in the Wamido theme.
Payment verification in the checkout code
The Wamido codebase traces the purchase from Flutterwave verification through currency and amount checks to the Moodle enrolment call.
Course Discovery and Checkout
Wamido ran as a separate Moodle deployment with its own brand and payment provider. I adapted the course discovery and checkout workflow to that setup.
Read catalogue fields from Moodle
I adapted the catalogue to the Wamido theme and used Moodle custom fields for course prices, duration, and curriculum. The catalogue and checkout read from the same course records.
Verify both payment currencies before enrolment
I added Flutterwave checkout in NGN and USD. The server verifies the payment with Flutterwave, then compares the returned currency and amount with the expected values before calling Moodle’s enrolment API.
Deployment and Platform Operations
I maintained the deployment scripts for Wamido’s Moodle installation alongside work on learner-facing features.
Update the deployment scripts for PHP 8.3
I updated the scripts for PHP 8.3, Redis, and Moodle cron, including restarting the correct PHP worker service after a release.
Technologies
- Moodle
- PHP 8.3
- JavaScript
- Flutterwave
- Redis
- Bash
