Smart Parking Management System

Three Role Surfaces, One Codebase

The web app delivers three distinct UX surfaces: Admin (operations center, dashboard, transactions, pricing, system health, realtime monitor), Staff (card-management console — issue, top-up, leave, lost), and Customer (no-login balance check + card-tap leave). Each surface authenticates differently and only sees what it should.

RFID Card Lifecycle

Cards are the unit of customer identity. Each has a unique card number, an optional unique vehicle plate, a car size (small / medium / large), an assigned pricing profile, a current balance, and an optional linked customer. Full lifecycle: issue, top-up, transfer balance, mark lost + replace, deactivate.

Flexible Pricing Profiles

Pricing is built around per-customer pricing profiles. Each profile uses one of two models — a fixed fee at exit (a flat charge per car size) or a duration-based charge calculated from the time parked — and a simple flat-rate plan is available alongside for operators who want it. New cards are issued against a pricing profile. At the exit gate the kiosk reads the profile, calculates the right fee for that card, and proceeds.

Each pricing profile uses one of two models — a fixed fee at exit per car size, or a duration-based charge from the time parked. Cards are assigned to a profile; the kiosk applies the right model and fee automatically at exit.

• Two models per profile — fixed fee at exit or duration-based
• Multiple pricing profiles (per customer segment, per zone, per time window)
• A simple flat-rate plan is available alongside
• Profile assignment can change per card without re-issuing it; pricing changes are immediate and audit-logged

Transaction Ledger (Append-Only, Auditable)

Every balance change creates a transaction record — top-up, parking fee, refund, or balance transfer — with the post-transaction balance snapshot. The ledger reconstructs the balance independently of the cached column, so discrepancies are detectable and reportable.

Parking-Session Audit Trail

Every leave creates a parking-session record capturing the fee charged and the pricing model used. Sessions are auditable by card, by date range, by staff member who processed the leave, and by the kiosk that handled the gate.

Customer Self-Service Portal (No Login)

The public customer portal lets a customer enter their card number and see balance, recent activity, and a card-tap leave shortcut. By design, the customer's identity is the card — no username, no password, no credential-theft surface. Reduces support volume dramatically.

Real-Time Monitoring Service

A standalone monitoring service fans out live activity (each card action), real-time stats, recent transactions, recent cards, running totals, and parking alerts to the admin's Realtime Monitor. Events are emitted from the API on every balance change.

Android Kiosk Fleet with Device Approval

Each Android kiosk has a unique device identity. On first boot it self-registers with the operations center. An admin reviews the request and approves (or rejects) it. Only approved devices are allowed to run kiosk-only operations. Every kiosk request carries its identity and updates its last-seen timestamp.

Kiosk Drives the Hardware Directly

The kiosk drives the RFID card reader and the barrier gate directly — there is no third-party middleware in the loop. It also feeds a hardware watchdog at fixed intervals, so a hung kiosk recovers itself automatically without an on-site visit.

Offline-Validated Licensing

Each deployment is governed by an offline-validated licence tied to the operator's own server. The licence validates entirely on-premise — no phone-home, no SaaS dependency, no internet connection required. If the licence is invalid or expired, the application fails closed, locking down with a branded notice instead of serving the page.