Request, negotiate, accept, and ride with one clear flow.
Waka is built so the fare decision happens before the ride becomes a match. The marketplace is for agreement; the matched ride is for pickup, progress, and completion.
Passenger flow
- Open Passenger, sign in or create an account, and prepare your ride request.
- Enter pickup, destination, optional stops, timing, vehicle preference, and the fare you are willing to offer.
- Publish the request so active nearby riders can review it.
- Compare rider proposals, counter when needed, or accept the rider offer that works.
- After acceptance, follow the matched ride with trip status, communication, and support in one place.
Rider flow
- Open Rider, sign in or apply to drive with Waka.
- Complete the profile and eligibility steps required before receiving ride requests.
- Go active only when ready to review requests. Availability controls whether marketplace requests appear.
- Review nearby requests, make a proposal, accept a passenger offer, or leave a negotiation that does not work.
- After match, follow navigation, mark arrival, mark pickup, continue through stops, and complete the ride at drop-off.
What happens when a fare is accepted
Acceptance is the handoff from marketplace to matched ride. Whether the passenger accepts a rider proposal or the rider accepts the passenger fare, Waka closes the fare conversation for that request, removes it from the open marketplace for other riders, and takes both matched users into the active ride flow.
Why that matters
Busy days become easier when each screen has one job. Before acceptance, the screen is about deciding whether the fare works. After acceptance, the screen is about pickup, progress, communication, completion, and support.
What Waka protects
Waka is designed to protect the clarity of the agreement. Before match, the important question is whether the fare and ride make sense. After match, the important question is how to complete the trip smoothly.