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.
Background & Context
taxi-app is a multi-package booking and operations platform. The domain API lives in backend/ (ASP.NET Core 8 + EF Core + SQL Server)—not NestJS/Prisma. Operators use React admin in frontend/ (TailAdmin). Riders book via website/ (CRA multi-step), taxi-nextjs/ (Next.js 15), and cab-website/ (Next.js 16 marketing/cab.uk quote→book→payment). Root api/ is an unused WeatherForecast template. There is no driver mobile app in-repo; NotificationService logs only (email/SMS/push not wired).
Search demand around multi-package uk transfer booking platform and Taxi App Platform keeps rising as operators look for proof—not slide decks—before they hire a build partner.
Tekvers framed Taxi App Platform as a multi-package uk transfer booking platform engagement with clear module boundaries, measurable outcomes, and a stack centered on ASP.NET Core 8, EF Core, SQL Server, JWT, React 18.
Delivery covered software development, cloud devops, digital marketing, with SEO-ready surfaces and internal linking so the public story reinforces the product work.
This case study page targets buyers researching multi-package uk transfer booking platform architecture, vendor evaluation, and implementation risk—paired with related Tekvers blogs and guides on the same niche.
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.
Our 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.
What We Delivered
- 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 & Impact
- 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/`
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.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.