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.
“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 need | Status | Finding |
| Submit trip request | WORKING | Home/online booking form collects pickup, drop-off, datetime, passengers. |
| See price before booking | PARTIAL | Quote UI calls bookingsystem/getVechicles, but threshold_km is omitted from SELECT → wrong fares (often day-rate). |
| Book a trip | WORKING | Booking is inserted into vbs_bookings after passenger/payment step. |
| Pay by card (Stripe) | PARTIAL | Stripe 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/drivers | PARTIAL | Nearby 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 WORKING | Maps used for route preview / operator nearby map only. No customer live tracking of assigned vehicle. |
1.2 Administrator
| Client need | Status | Finding |
| Enter trips manually | WORKING | Bookings::add_booking supports admin-created trips. |
| Manage users / vehicles / settings | WORKING | Admin modules for customers, drivers, companies/car owners, vehicles, categories, coupons, CMS, settings. |
| Customers edit | NOT WORKING | Create/list/delete/status exist; no edit customer. |
| Pay owners after completed trips (bank) | NOT WORKING | No settlement/payout workflow; bank fields exist on users table but no admin payout module. |
| Dispatch rules (100 km, category, first wins) | NOT WORKING | Not implemented to client spec (see §2B). |
1.3 Car Owner
| Client need | Status | Finding |
| Self-register as car owner | NOT WORKING | Public register supports customer/driver only. Owner accounts created by admin. |
| Company info + docs (certificate, insurance, many licenses, bank) | NOT WORKING | DB 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. number | PARTIAL | Vehicle text fields / plate exist; owner “add car” UI incomplete; no enforced photo-of-plate requirement. |
| Add drivers under owner | WORKING | Owner can add drivers; ownership link (created_by) not consistently set → weak isolation. |
| See only own fleet trips + prices | NOT WORKING | Payment/trip listing can expose broader booking data (insufficient owner filter). |
| Download reports anytime | NOT WORKING | Reports module is admin-only; no owner report export. |
| Portal navigation / dashboard | NOT WORKING | JS calls missing methods (get_bookings, verify_booking); profile POST target missing; salary AJAX joins nonexistent drivers table. |
1.4 Driver
| Client need | Status | Finding |
| Profile (name, phone, email, photo) | PARTIAL | Present; address not properly supported. |
| Docs: license both sides, YSK, driver’s pass both sides, port/airport access | NOT WORKING | DB 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 wins | PARTIAL | Nearby jobs exist at 5 km; no category gate; no atomic first-wins lock. |
| Start/stop trip by phone | WORKING | Web portal status flow: accept → on_the_way → trip_started → completed (browser on phone). |
| Own trip history + prices only | NOT WORKING | History AJAX filters wrong field; nearby feed exposes prices of others’ trips. |
| GDPR: must NOT see all trips/prices/cars/drivers | NOT WORKING | Confirmed defect. Driver dashboard loads all today’s bookings; lists can expose all drivers/vehicles. Matches client report from drivers. |
| Driver menu / navigation | NOT WORKING | Sidebar links to dead routes (settings/bookings, executive). |
| Reports | PARTIAL | Only ad-hoc Excel from DataTables; no proper report module. |
1.5 Corporate / professional business customer (hotel, cruise, airline)
| Client need | Status | Finding |
| Company login + company name, address, invoice address/email, contact person, phone, email | PARTIAL | Register 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. prices | PARTIAL | Bookings list exists (scoped); prices mainly on detail, not full list overview. |
| Export reports anytime | PARTIAL | CSV invoice export exists but omits price columns. |
| Branches | PARTIAL | Add/delete branches; no edit/update. |
2. Full requirements matrix (client message → system)
A. Online digital booking platform
| ID | Requirement | Status | Evidence / note |
| A1 | Customer submits request | WORKING | Welcome booking funnel |
| A2 | See price | PARTIAL | Broken threshold pricing in getVechicles |
| A3 | Book trip | WORKING | Inserts booking |
| A4 | Pay by card | PARTIAL | Stripe code present; return path broken; live unknown |
| A5 | Posted to owners/drivers | PARTIAL | Nearby poll only; not full marketplace |
| A6 | Customer live map tracking | NOT WORKING | Missing feature |
B. Dispatch (100 km / first confirm / phone)
| ID | Requirement | Status | Evidence / note |
| B1 | ~100 km visibility from pickup | NOT WORKING | Hardcoded HAVING distance < 5 (5 km) |
| B2 | First confirm + correct category | PARTIAL | Accept exists; no category filter; no race-safe first-wins |
| B3 | Start/stop by phone | WORKING | Mobile web portal status changes |
C–E. Owner / Driver / Corporate (summary)
| Area | Working | Partial | Not 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.
| ID | Requirement | Status | Finding |
| G1 | Driver must not see all trips/prices/cars/drivers | NOT WORKING | Dashboard loads all today’s bookings; driver/vehicle lists insufficiently scoped |
| G2 | Data isolation by role/company | PARTIAL | Corporate scoping better; owner/driver isolation weak |
H. Payments
| ID | Requirement | Status | Finding |
| H1 | Stripe functional end-to-end | PARTIAL / UNKNOWN live | Charge path exists; stripe_return debug exits + bad enum; SCA/modern PaymentIntents incomplete |
| H2 | PayPal / PayU | PARTIAL | Code present; not validated as production-ready for Norway card flow |
| H3 | Owner bank settlement after trips | NOT WORKING | No payout module |
3. Prioritised issues list (for delivery / client)
| Prio | ID | Issue | Roles hit | Why it matters |
| P0 | GDPR-1 | Drivers can see all trips / prices / cars / drivers | Driver, Admin, Legal | Violates GDPR / Norwegian Data Protection Act; stop driver access until fixed |
| P0 | DISP-1 | Nearby radius 5 km instead of ~100 km; no category + first-wins lock | Customer, Driver, Owner, Admin | Marketplace dispatch does not match business rules |
| P0 | BOOK-1 | Wrong online price quotes (threshold_km bug) | Customer | Cannot trust “see price then book” |
| P0 | PAY-1 | Stripe return broken (debug exit + invalid status) | Customer | Card payment completion unreliable |
| P1 | OWN-1 | Car owner portal broken (missing methods, salary SQL) | Car Owner | Owner cannot operate fleet in portal |
| P1 | OWN-2 | No owner self-onboarding + document/bank pack UI | Car Owner, Admin | Client minimum for owners not met (despite DB columns) |
| P1 | DRV-1 | Driver nav dead links; history uses wrong filter | Driver | Portal unusable / wrong data |
| P1 | DRV-2 | Full driver document pack UI missing | Driver | Compliance docs not collectable in product |
| P1 | TRACK-1 | No customer live trip tracking on map | Customer | Explicit client requirement missing |
| P1 | RPT-1 | No owner/driver/corporate priced report exports | Owner, Driver, Corporate | “Take out reports as often as they want” not met |
| P2 | CORP-1 | Contact person field + list prices + export prices | Corporate | Minimum company customer profile incomplete |
| P2 | ADM-1 | Customer edit missing; airport settings tables missing | Admin | Admin ops gaps |
| P2 | SETL-1 | No payout/settlement to owner bank accounts | Admin, Owner | Cannot pay owners after completed trips |
| P3 | UX-1 | Hardcoded production CDN assets; backup controllers | All | Stability / 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.
-
Phase 0 — Freeze & protect (1–3 days)
- Restrict driver list/dashboard queries to assigned / nearby eligible jobs only (no all-trips, no all-vehicles, no all-drivers).
- Audit logs: who can see what (role matrix).
- Communicate temporary limitation to existing driver accounts.
-
Phase 1 — Make online booking trustworthy (3–7 days)
- Fix
getVechicles pricing (threshold_km + null-coalesce).
- Repair Stripe return (remove debug exit; write valid
confirm status; test card success/fail).
- Smoke-test: request → quote → book → pay → booking row created.
-
Phase 2 — Marketplace dispatch (1–2 weeks)
- Configurable radius (default 100 km).
- Filter by booked vehicle category vs driver/owner fleet category.
- Atomic accept: first confirm wins; others see “already taken”.
- Push/notify eligible drivers/owners (email/SMS — not WhatsApp as contract channel).
-
Phase 3 — Role portals (1–2 weeks)
- Driver: fix nav, own history by
driver_id, start/stop statuses, document upload UI wired to existing DB columns.
- Car owner: fix portal APIs; self-registration; docs + bank fields UI; cars with plate photo; scoped trips only.
- Corporate: contact person field; trip list with prices; CSV with prices.
-
Phase 4 — Tracking & reports (1–2 weeks)
- Customer live map from trip_started → completed (driver location stream).
- Owner / driver / corporate report downloads (date range, prices, vouchers).
- Admin settlement queue (mark paid to owner bank account).
-
Phase 5 — Acceptance on taxitur.no
- Login as: admin, corporate, car owner, driver, public customer.
- Run checklist in §5; sign off each role.
- GDPR review with Norwegian counsel if required.
5. Acceptance checklist (role-based)
| Role | Must pass before “done” |
| Customer | Quote correct → book → card pay → confirmation → later live track assigned car |
| Driver | Sees only eligible nearby jobs + own history; cannot see others’ prices/cars/drivers; can accept/start/stop; uploads required docs |
| Car Owner | Registers with company + docs + bank; uploads cars (photo+plate); adds drivers; sees only own fleet trips; exports reports |
| Corporate | Company profile complete (incl. contact person); books/views trips with prices; exports reports |
| Admin | Creates trips; manages users; GDPR-safe views; can settle owners |
6. Direct answers to client points
| Client statement | Assessment |
| “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/drivers | Confirmed 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 tool | Process recommendation: use in-app + email/SMS with audit trail only — not WhatsApp as contract/confirmation channel. |