Campus Parking Sticker Issuance Portal

Every academic year, campus security offices drown in parking sticker applications — paper forms, photocopied RCs and licences, manual fee receipts, and stickers handed out weeks later with no record of which vehicle belongs to whom. Verification is a desk pile: staff squint at documents, fee defaults go unnoticed, and at the gate nobody can quickly check whether a vehicle is authorised. This project is a parking sticker issuance portal that moves the whole workflow online. Students fill one application with vehicle and owner details, upload the registration certificate, driving licence and college ID, and pay the sticker fee plus refundable deposit online. The security office works through a verification queue showing each application's documents with per-document status, and approves, rejects or asks for resubmission with reasons. Approved applications move to sticker printing — a QR-coded sticker preview with the registration number, owner, vehicle type and allotted zone — and the student collects it against the application ID. A public status tracker and gate-side QR verification close the loop.

1. The student fills the application form, uploads RC, driving licence and college ID, and pays the fee plus deposit.
2. The application enters the verification queue with per-document status flags.
3. Security staff open each application, inspect the documents and approve, reject, or request resubmission with a reason.
4. On approval, the system generates the QR-coded sticker with registration number, owner, vehicle type and allotted zone.
5. The student tracks the four-stage timeline until the sticker is ready for collection at the security office.
6. At the gate, staff scan the sticker QR to verify the vehicle against the issued record.

Tech stack:

• PHP · Laravel (REST API + Blade views)
• MySQL (relational schema with seed data)
• HTML · CSS · JavaScript (responsive frontend)
• QR code generation (sticker + verification)
• File upload validation pipeline
• Razorpay payment integration (sandbox mode)
• Role-based access (student, security admin)
• Git

• [Online application] One form for applicant, vehicle and document details with a live sticker preview and transparent fee breakup.
• [Document upload & checks] RC, driving licence and ID uploads with format and size validation and per-document verification status.
• [Fee payment] Sticker fee plus refundable deposit collected online; the payment state gates verification.
• [Admin verification queue] Security staff see every application with documents, applicant history and one-click approve / reject / resubmit with reasons.
• [QR sticker generation] Approved applications produce a QR-coded sticker carrying the registration number, owner and zone for gate verification.
• [Status tracker] A four-stage timeline — submitted, documents verified, sticker printing, ready for collection — with expected dates.
• [Zone allotment] Vehicle type maps to a parking zone on approval, printed on the sticker and stored against the vehicle.

• Complete working web application (application, tracker, verification queue, sticker generation)
• Database schema with seed data (applications at every stage, fee records)
• QR sticker template and gate-verification lookup
• Razorpay sandbox integration wired to the fee payment
• Project report PDF (SRS, ER diagram, DFD, test cases, screenshots)
• PPT presentation for final review
• Viva Q&A preparation document (verification workflow, QR design, fee states)

• Document verification is a manual staff check; the system validates format and size only — OCR-based RC field extraction is future scope.
• Payments run in Razorpay sandbox in the demo; production needs the buyer's own keys and KYC.
• Physical sticker printing is outside the software; the portal produces the print-ready QR sticker layout.
• Gate QR scanning assumes a phone or scanner with network access to the portal.
• Applications, documents and fee figures in the demo are illustrative seed data.