SabiPark onboards the park
We organise park access, operator review and marketplace publication. Assigned employees oversee trips, manifests and journey safety.
A SabiPark-managed marketplace for passengers, drivers and vehicle owners. Create trips at onboarded parks, reuse your setup and keep boarding moving.
Live Paystack ticket payments are working on SabiPark Park. Your account and park payment setup must be ready before you accept bookings.
Drivers operate journeys and sell verified tickets. Owners set vehicle agreements and monitor earnings. SabiPark connects trip publishing, bookings, passenger boarding and journey records.
SabiPark brings the digital operation together while each participant keeps their own responsibilities.
We organise park access, operator review and marketplace publication. Assigned employees oversee trips, manifests and journey safety.
Drivers create, price and manage trips against their approved vehicle agreement and park access. Owners set the agreement and monitor operations and their agreed earnings.
Published trips support remote booking and authorised driver sales. Verified tickets, manifests and dispatch checks keep the trip connected.
Park operational walkthrough
The owner sets the vehicle agreement. The driver publishes trips, sells tickets and boards passengers. Passengers book online and keep their tickets and journey details together.
Agrees terms and monitors operations
Creates the trip and serves passengers
Pays, receives a ticket and boards
Vehicle owner
Agree the owner amount or share and the vehicle owner’s refund responsibility. Your driver then handles the trip’s daily operations while you review the recorded activity.
Owner amount or share and refund responsibility
Creates the trip, sets the fare and boards passengers
Reviews the journey and recorded earnings
The owner sets and monitors the agreement; the driver manages the trip.
Illustrative role relationshipDriver
Create the trip, set the passenger fare and publish it when eligible. Serve online and walk-in passengers from the same trip inventory, then follow boarding, manifest and departure controls.
Use the approved vehicle and active agreement
Set the fare and manage shared passenger places
Unpaid reservations expire; confirmed tickets can be checked
The driver operates the trip; the owner monitors the agreed earnings and journey records.
Illustrative role relationshipPassenger
Choose a published Park trip for the current service day, review the fare and boarding point, and complete the passenger details. A travel ticket follows verified payment.
Check the fare, boarding point and service information
An unpaid reservation releases its place after the countdown
Verify the issued ticket and record boarding
View driver details and use available journey support tools
Park fill-and-go purchases are same-day. Scheduled Fleet advance bookings are a separate service.
Illustrative role relationshipTickets follow verified customer payment. Departure confirmation and provider-confirmed bank settlement are separate records. Payment access depends on the relevant verification and setup.
Built around the phone you already use, with the selected route visible when it matters.
Start the next trip from previous proposal details. Current park access, fare and vehicle checks still apply.
Your ticket-sales banner shows the trip you are selling. Remote and walk-in bookings use the same trip inventory.
Owner-operated, capped remittance and revenue-share agreements keep owner and driver allocations tied to agreed terms.
Your driver runs the trip. You retain visibility of the operating agreement, recorded fares and your share.
Record the owner amount or share, the driver’s responsibility and the vehicle owner’s refund obligations before operations begin.
Review trips and assigned routes. Drivers manage passenger sales, manifests, boarding and departure confirmation from their own workspace.
Follow your agreed allocations and payment records. Provider-confirmed payout evidence is separate from customer payment and departure confirmation.
Discover published routes and clear boarding details, with ticket and journey information in one place.
Choose your trip and traveller count before passenger details. Checkout becomes available when the trip’s approved payment setup is enabled.
See seat progress and advisory wait windows where available. Scheduled services show their configured departures.
Access private journey links and incident reporting where available. These tools do not promise continuously monitored emergency response.
SabiPark Fleet brings company-branded booking, branch teams, shared inventory, manifests and journey safety together.
Find answers for your role in the SabiPark marketplace.
Create an owner account and request access to an onboarded park and route. Your vehicle and operating information are reviewed before approved trips can be published.
The active vehicle agreement defines the owner amount or share and responsibilities, including refunds. The driver creates trips and sets passenger fares. Payment records show allocations; credited bank settlement requires provider confirmation and does not follow automatically from a ticket being paid.
Verified tickets, trip records and owner/driver allocations make recorded activity easier to review. The active agreement defines responsibilities and the owner’s share. These controls help identify discrepancies; they do not guarantee prevention of theft or cover cash collected outside the recorded workflow.
The trip records its approved route and assigned vehicle. Journey safety tools provide location updates where available, helping you compare reported progress with that route and report concerns. Location visibility depends on available updates and device connectivity; it is not continuous GPS tracking or an automatic guarantee that a vehicle stays on its route.
Create a driver account, complete verification, connect the required vehicle agreement and park access, then create a trip in Trips. Drivers set the passenger fare and manage the trip; the vehicle owner sets and monitors the commercial agreement. Only eligible current-day Park trips can be sold publicly.
No. Reuse your previous trip proposal details and update what has changed. The route is clearly shown on the trip and ticket-sales banner so you can check which departure you are selling.
Check in passengers with verified paid tickets, review the manifest, then confirm departure. Continue to journey location sharing from the trip dashboard.
The current driver workflow works through the responsive web dashboard on your phone. No proprietary SabiPark POS is required. Native app and contracted USSD rollout require separate readiness and activation.
Open the marketplace and choose a published service. Park fill-and-go public purchases are for the current service day; Scheduled Fleet services can accept advance bookings when the company opens them. Review the boarding location and terms, enter passenger details and complete the available Paystack checkout. Tickets follow verified payment.
No. Seat progress and available wait windows help you understand the trip’s progress, but fill-and-go estimates are advisory. Scheduled services show their configured departure information.
Cancellations, refunds and disruptions follow the booking policy shown before payment. Report a missing driver or refused booking from your journey page so the issue can be reviewed. Drivers arrange accepted replacements; approved refunds follow Paystack processing timelines.
SabiPark does not provide a passenger wallet or collect physical cash. Electronic payments depend on approved provider routing. Independent cash-to-transfer services, if available locally, operate outside SabiPark cash authority.
About us
SabiPark is a transport operations and passenger booking platform developed by SabiHQ Technologies Limited, a registered Nigerian company. We help motor parks, vehicle owners, drivers and fleet companies organise the work behind a passenger’s journey.
Our solution is made specifically for Nigeria: fill-and-go services alongside scheduled intercity departures, walk-in passengers alongside online bookings, branch teams, owner–driver agreements and passenger boarding. Fares are shown in naira, service-day controls use Nigeria time, and online payments use Paystack.
We bring those operational details into connected workflows: publish a trip, reserve a place, verify payment, issue a ticket, check the passenger in and keep the records needed to review the journey. Each role gets the controls that belong to its work.
Onboarding is open for Park drivers, vehicle owners and Fleet companies. Create your account to get started.