Skip to content

Collaboration Platform

ZoomPass

A transport fare-payment collaboration completed after Mfidie Solutions took on the remaining backend work and deployment.

The ZoomPass home page: the heading "Get paid faster. Go cashless with ZoomPass." and a panel showing the USSD code a passenger dials to pay a driver.
The ZoomPass site's reasons drivers use it, including SMS confirmations, exportable reports and working on any phone, above its per-transaction price.

How it fits together

People reach it through

  • Web

Laravel · MySQL

  • GTBank

Connected to

Context

ZoomPass was developed for a transport-related client that wanted passengers to pay fares in a way that reduced the difficulties drivers face collecting their money. The project began with another development team, which built the first phase of the backend. Mfidie Solutions joined as a collaborator to complete the remaining application work and manage rollout and deployment. The resulting system was successfully deployed using Laravel and MySQL.

The problem

For a transport business, collecting fares is not only about the passenger making a payment. Drivers also need a dependable way to receive the money associated with their work. The client wanted a digital process to address problems around collecting and receiving fares. By the time Mfidie Solutions became involved, an initial backend already existed. The task was therefore different from starting with an empty project: the team had to continue development from another team’s work, finish the outstanding pieces and prepare the application for real deployment. The payment integration introduced an additional dependency on a financial institution with its own process and requirements.

Our contribution

The first development team built the initial backend. Mfidie Solutions completed the remaining backend and application development, coordinated the GTBank payment integration, rolled out the product and deployed it. This was a collaboration, not a claim that Mfidie Solutions authored every part of the original codebase.

Approach

We worked from the existing Laravel and MySQL application instead of rebuilding the early work unnecessarily. The remaining development was completed around the client’s fare-payment objective. Deployment formed part of our responsibility, so the engagement extended beyond writing features to getting the application into operation. The integration work required direct coordination with GTBank, a payment provider the team had not previously worked with.

Challenges

  • GTBank was a new payment integration partner for the team. Its process involved considerable back-and-forth, so coordination and resolving integration requirements took longer than a familiar provider would have.
  • Taking over a backend begun by another team required continuing from the existing implementation while completing and deploying the remaining work.

Outcomes

The team completed and successfully deployed ZoomPass. The client received a working transport-payment application rather than an unfinished backend.

Technology

  • Laravel
  • MySQL
  • GTBank

Links

Services involved

Have something similar in mind?

Book a Free Consultation