Multi-package UK transfer booking platform
Taxi App Platform
ASP.NET Core 8 + SQL Server booking API with layered GBP fare engine, React ops admin, and parallel React/Next.js rider sites—Stripe and PayPal payment initiation.
The challenge
A UK transfer operator needed online booking, fleet/pricing configuration, composite fares, and payment initiation across admin and multiple rider UIs—without claiming live notification delivery or a driver app the repo does not contain.
The solution
Taxi App Platform: ASP.NET Core 8 + SQL Server booking API with layered GBP fare engine, React ops admin, and parallel React/Next.js rider sites—Stripe and PayPal payment initiation. Multi-package UK transfer booking and dispatch foundation. Tekvers delivered a maintainable multi-package uk transfer booking platform system for Taxi App Platform using ASP.NET Core 8, EF Core, SQL Server, JWT, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Approach
API as the operational brain
Admin and rider packages consume the ASP.NET controllers; Swagger and Postman document auth, customers, direct bookings, drivers, vehicles, payments, and fixed fares.
Layered fare engine
`FareCalculationService` composes configurable pricing rules so ops can tune GBP airport/port economics without rewriting UIs.
Parallel rider surfaces
CRA and Next.js flows share the booking narrative (journey → vehicle → auth → info → payment → confirmation) while `cab-website` adds marketing quote APIs for locations/route estimates.
Deliverables
- ▸ASP.NET Core 8 booking/fleet/pricing/payments API on SQL Server
- ▸React 18 TailAdmin ops dashboard (bookings, customers, drivers, vehicles, zones, pricing, RBAC UI screens)
- ▸Rider booking SPAs: React CRA + Next.js 15 multi-step
- ▸Next.js 16 marketing/quote site (`cab-website`)
- ▸Stripe PaymentIntent + PayPal Checkout SDK integration paths
- ▸Booking workflow statistics and direct-booking search/assign/pay actions
- ▸Postman collection for major HTTP flows
Outcomes
- ▸Multi-package UK transfer booking and dispatch foundation
- ▸Composite fare calculation with documented rule order
- ▸Admin fleet and pricing configuration without a separate microservices mesh
- ▸Explicit non-features: no driver app, notifications log-only, unused WeatherForecast `api/`
Impact
Operators manage jobs, fleet, and fares from one ASP.NET brain while riders book on parallel web UIs—Tekvers corrected stack mythology (ASP.NET, not Nest) and kept AI/marketing service tags from the portfolio metadata without inventing ML features absent from taxi-app docs.
Tech stack
Want something similar?
I build production systems like Taxi App Platform—from architecture through launch. Tell me what you need.
Contact me →