TAXITUR.NO — Platform Assessment Report

Client requirements vs current system (roles, modules, GDPR, payments)
Environment audited: local codebase c:\laragon\www\txn + database txn · Live reference: www.taxitur.no
Report date: 1 August 2026 · Status legend: WORKING · PARTIAL · NOT WORKING · UNKNOWN / unverified live

Verdict on the client statement: The platform was built on a ready-made booking template and does not currently operate as a complete Norwegian online digital taxi marketplace (customer book → card pay → dispatch to nearby owners/drivers → complete → report → settle). Several screens exist, but critical marketplace, GDPR isolation, documentation, live tracking, and owner settlement pieces are missing or unsafe.
7
Working
16
Partial
10
Not working
1
Live Stripe unverified
“Customers should be able to submit a request, see the price and possibly book a trip, pay by card, and the trips are then posted… to registered car owners/drivers. (It does not work like that).” — Client message

Assessment: request + price + book UI exist, but pricing logic is unreliable, dispatch radius is 5 km (not ~100 km), category/first-wins matching is incomplete, GDPR leaks are confirmed in code, and Stripe return path has debug exits. Overall marketplace goal = NOT WORKING as a product.

1. Role overview — what works / what does not

1.1 Public Customer (online booking)

Client needStatusFinding
Submit trip requestWORKINGHome/online booking form collects pickup, drop-off, datetime, passengers.
See price before bookingPARTIALQuote UI calls bookingsystem/getVechicles, but threshold_km is omitted from SELECT → wrong fares (often day-rate).
Book a tripWORKINGBooking is inserted into vbs_bookings after passenger/payment step.
Pay by card (Stripe)PARTIALStripe Charge path exists in code; stripe_return() still has print_r/exit and writes invalid status confirmed (DB allows confirm). Live production success unverified.
Trip posted to owners/driversPARTIALNearby poll exists, but radius hardcoded to 5 km (client asks ~100 km); no reliable category match / first-confirm lock.
Live track car on map (start→end)NOT WORKINGMaps used for route preview / operator nearby map only. No customer live tracking of assigned vehicle.

1.2 Administrator

Client needStatusFinding
Enter trips manuallyWORKINGBookings::add_booking supports admin-created trips.
Manage users / vehicles / settingsWORKINGAdmin modules for customers, drivers, companies/car owners, vehicles, categories, coupons, CMS, settings.
Customers editNOT WORKINGCreate/list/delete/status exist; no edit customer.
Pay owners after completed trips (bank)NOT WORKINGNo settlement/payout workflow; bank fields exist on users table but no admin payout module.
Dispatch rules (100 km, category, first wins)NOT WORKINGNot implemented to client spec (see §2B).

1.3 Car Owner

Client needStatusFinding
Self-register as car ownerNOT WORKINGPublic register supports customer/driver only. Owner accounts created by admin.
Company info + docs (certificate, insurance, many licenses, bank)NOT WORKINGDB columns exist (company_certificate, insurance_liability, permit_*, account_number, IBAN/SWIFT…), but UI/forms do not collect or upload them.
Upload cars with photo + visible reg. numberPARTIALVehicle text fields / plate exist; owner “add car” UI incomplete; no enforced photo-of-plate requirement.
Add drivers under ownerWORKINGOwner can add drivers; ownership link (created_by) not consistently set → weak isolation.
See only own fleet trips + pricesNOT WORKINGPayment/trip listing can expose broader booking data (insufficient owner filter).
Download reports anytimeNOT WORKINGReports module is admin-only; no owner report export.
Portal navigation / dashboardNOT WORKINGJS calls missing methods (get_bookings, verify_booking); profile POST target missing; salary AJAX joins nonexistent drivers table.

1.4 Driver

Client needStatusFinding
Profile (name, phone, email, photo)PARTIALPresent; address not properly supported.
Docs: license both sides, YSK, driver’s pass both sides, port/airport accessNOT WORKINGDB has fields (license_front/back, driver_ticket_*, driver_card_*, avinor_card, isps_course…), but forms do not expose full document pack. Client assumed “most in place” — schema yes, product no.
See nearby jobs (~100 km), correct category, first confirm winsPARTIALNearby jobs exist at 5 km; no category gate; no atomic first-wins lock.
Start/stop trip by phoneWORKINGWeb portal status flow: accept → on_the_way → trip_started → completed (browser on phone).
Own trip history + prices onlyNOT WORKINGHistory AJAX filters wrong field; nearby feed exposes prices of others’ trips.
GDPR: must NOT see all trips/prices/cars/driversNOT WORKINGConfirmed defect. Driver dashboard loads all today’s bookings; lists can expose all drivers/vehicles. Matches client report from drivers.
Driver menu / navigationNOT WORKINGSidebar links to dead routes (settings/bookings, executive).
ReportsPARTIALOnly ad-hoc Excel from DataTables; no proper report module.

1.5 Corporate / professional business customer (hotel, cruise, airline)

Client needStatusFinding
Company login + company name, address, invoice address/email, contact person, phone, emailPARTIALRegister has company name, physical/invoice address, invoice email, phone, email, org. number. Dedicated contact-person field missing (minimum not fully met).
Full overview of booked trips incl. pricesPARTIALBookings list exists (scoped); prices mainly on detail, not full list overview.
Export reports anytimePARTIALCSV invoice export exists but omits price columns.
BranchesPARTIALAdd/delete branches; no edit/update.

2. Full requirements matrix (client message → system)

A. Online digital booking platform

IDRequirementStatusEvidence / note
A1Customer submits requestWORKINGWelcome booking funnel
A2See pricePARTIALBroken threshold pricing in getVechicles
A3Book tripWORKINGInserts booking
A4Pay by cardPARTIALStripe code present; return path broken; live unknown
A5Posted to owners/driversPARTIALNearby poll only; not full marketplace
A6Customer live map trackingNOT WORKINGMissing feature

B. Dispatch (100 km / first confirm / phone)

IDRequirementStatusEvidence / note
B1~100 km visibility from pickupNOT WORKINGHardcoded HAVING distance < 5 (5 km)
B2First confirm + correct categoryPARTIALAccept exists; no category filter; no race-safe first-wins
B3Start/stop by phoneWORKINGMobile web portal status changes

C–E. Owner / Driver / Corporate (summary)

AreaWorkingPartialNot working
Car Owner Add drivers Cars (text only) Self-signup, docs pack, plate photo rule, scoped trips, reports, portal bugs
Driver Start/stop trip Basic profile, nearby jobs (wrong radius) Full docs UI, GDPR isolation, correct history, nav, proper reports
Corporate Register + login + scoped bookings Company fields, trip overview, CSV export, branches Contact person field; priced full reports

G. Security / GDPR (Norwegian Data Protection Act)

Critical legal risk: Client report that drivers see all trips, prices, other cars and drivers is confirmed in code. This must be fixed before any further driver onboarding in Norway.
IDRequirementStatusFinding
G1Driver must not see all trips/prices/cars/driversNOT WORKINGDashboard loads all today’s bookings; driver/vehicle lists insufficiently scoped
G2Data isolation by role/companyPARTIALCorporate scoping better; owner/driver isolation weak

H. Payments

IDRequirementStatusFinding
H1Stripe functional end-to-endPARTIAL / UNKNOWN liveCharge path exists; stripe_return debug exits + bad enum; SCA/modern PaymentIntents incomplete
H2PayPal / PayUPARTIALCode present; not validated as production-ready for Norway card flow
H3Owner bank settlement after tripsNOT WORKINGNo payout module

3. Prioritised issues list (for delivery / client)

PrioIDIssueRoles hitWhy it matters
P0GDPR-1Drivers can see all trips / prices / cars / driversDriver, Admin, LegalViolates GDPR / Norwegian Data Protection Act; stop driver access until fixed
P0DISP-1Nearby radius 5 km instead of ~100 km; no category + first-wins lockCustomer, Driver, Owner, AdminMarketplace dispatch does not match business rules
P0BOOK-1Wrong online price quotes (threshold_km bug)CustomerCannot trust “see price then book”
P0PAY-1Stripe return broken (debug exit + invalid status)CustomerCard payment completion unreliable
P1OWN-1Car owner portal broken (missing methods, salary SQL)Car OwnerOwner cannot operate fleet in portal
P1OWN-2No owner self-onboarding + document/bank pack UICar Owner, AdminClient minimum for owners not met (despite DB columns)
P1DRV-1Driver nav dead links; history uses wrong filterDriverPortal unusable / wrong data
P1DRV-2Full driver document pack UI missingDriverCompliance docs not collectable in product
P1TRACK-1No customer live trip tracking on mapCustomerExplicit client requirement missing
P1RPT-1No owner/driver/corporate priced report exportsOwner, Driver, Corporate“Take out reports as often as they want” not met
P2CORP-1Contact person field + list prices + export pricesCorporateMinimum company customer profile incomplete
P2ADM-1Customer edit missing; airport settings tables missingAdminAdmin ops gaps
P2SETL-1No payout/settlement to owner bank accountsAdmin, OwnerCannot pay owners after completed trips
P3UX-1Hardcoded production CDN assets; backup controllersAllStability / maintainability

4. Recommended work flow (delivery plan)

Order is intentional: fix legal/data leaks first, then money path, then marketplace rules, then role onboarding & reports. Do not onboard more drivers until P0 GDPR is closed.
  1. Phase 0 — Freeze & protect (1–3 days)
  2. Phase 1 — Make online booking trustworthy (3–7 days)
  3. Phase 2 — Marketplace dispatch (1–2 weeks)
  4. Phase 3 — Role portals (1–2 weeks)
  5. Phase 4 — Tracking & reports (1–2 weeks)
  6. Phase 5 — Acceptance on taxitur.no

5. Acceptance checklist (role-based)

RoleMust pass before “done”
CustomerQuote correct → book → card pay → confirmation → later live track assigned car
DriverSees only eligible nearby jobs + own history; cannot see others’ prices/cars/drivers; can accept/start/stop; uploads required docs
Car OwnerRegisters with company + docs + bank; uploads cars (photo+plate); adds drivers; sees only own fleet trips; exports reports
CorporateCompany profile complete (incl. contact person); books/views trips with prices; exports reports
AdminCreates trips; manages users; GDPR-safe views; can settle owners

6. Direct answers to client points

Client statementAssessment
“Cannot be used as an online digital booking platform”Partially true — UI exists, but pricing, dispatch, GDPR, tracking, owner ops, and reliable card completion are not product-ready.
“Trips posted to car owners/drivers — does not work like that”Confirmed. Nearby 5 km poll ≠ 100 km marketplace with category + first-wins.
“Ready-made template, built on this”Confirmed (DVBS / Codecanyon-style template architecture).
Drivers saw all trips/prices/cars/driversConfirmed in code — critical GDPR defect.
Driver docs “most in place”DB columns largely exist; product UI does not collect the full pack.
Stripe “don’t think anything functional”Some code exists; completion path broken / not proven live.
WhatsApp is not a communication/contract toolProcess recommendation: use in-app + email/SMS with audit trail only — not WhatsApp as contract/confirmation channel.