College Bus Pass Application Android App with Online Payment and QR Pass

Getting a college bus pass still runs on paper in many colleges: a student collects a form from the transport office, fills it by hand, attaches photocopies of an ID and a photograph, queues again to submit it, and returns days later for the verdict — then pays at a separate counter and collects a printed pass that can be lost or forged. The College Bus Pass Application Android App with Online Payment and QR Pass replaces that chain with one phone flow: the student applies from the app, uploads the college ID, a passport photo and an address proof, and tracks the status live. The office approves or rejects with a reason, the student pays the semester fee through UPI in the app, and the app issues a QR pass the conductor scans at the bus door, logging every boarding. No counter visit is needed, and every pass is tied to a verified application and a recorded payment.

End to end, the app works as a four-stage loop between the student's phone, Firebase and the transport office, with the conductor's scan closing the circle. A student signs in with a phone number, fills in PRN, branch, route and boarding stop, and uploads the three documents; the application lands in the admin queue with the files attached. Transport-office staff verify the documents and approve or reject with a reason, and an approved student is prompted to pay the semester fee through the UPI intent flow in the app. Once the payment confirms, the app stores the UTR against the application and generates the QR pass, which the student can also download for offline use. On the bus the conductor scans the QR, the app checks validity, route and payment, and the scan is logged with pass ID and time for the transport office to review.

1. The student signs in with a phone number through Firebase Authentication and opens the new-pass application form.
2. The student enters PRN, branch, route and boarding stop, and uploads the college ID, a passport photo and an address proof (max 2 MB each).
3. The application is written to Cloud Firestore and appears in the transport office admin queue with the documents attached.
4. Admin staff verify the documents and approve or reject the application with a recorded reason; the student sees the status live.
5. An approved student pays the semester fee through the UPI intent flow (GPay, PhonePe, Paytm or BHIM); the UTR is stored with the application.
6. On payment confirmation the app generates the QR pass with pass ID, route, boarding stop and validity, available offline as a downloaded copy.
7. The conductor scans the QR at the bus door, the app checks validity, route and payment, and the scan is logged with pass ID, time and result.

Tech stack:

• Kotlin
• Android Studio
• Firebase Authentication (phone sign-in)
• Cloud Firestore (applications · passes · scan log)
• Firebase Cloud Storage (documents)
• UPI payment intent API
• ZXing QR code library
• Material Design 3 UI

The College Bus Pass Application Android App is built around four capabilities that work as one flow: new-pass application with document upload, online UPI payment, QR pass issue, and conductor scan verification. The application flow lets a first-time student apply from the phone with PRN, branch, route and boarding stop, uploading the college ID, a passport photo and an address proof, each file capped at 2 MB. Online UPI payment is implemented in the base build, not future scope: after approval the student pays through GPay, PhonePe, Paytm or BHIM, and the app stores the UTR against the application. The QR pass is generated only after payment confirms, carrying the pass ID, route, boarding stop and validity, and works offline from a downloaded copy. The conductor scan screen completes the loop, checking validity, route and payment at the door and logging every boarding with pass ID and time, so the office can see exactly who boarded which bus.

• [New-pass application with document upload] A first-time student applies from the phone with PRN, branch, route and boarding stop, uploading the college ID, a passport photo and an address proof, with each file capped at 2 MB (design target).
• [Online UPI payment in the base build] After approval the student pays the semester fee inside the app through GPay, PhonePe, Paytm or BHIM; the UTR is stored against the application and the QR pass is issued only after the payment confirms.
• [QR pass generation and display] The app generates a 25 × 25 module QR pass carrying the pass ID, student details, route, boarding stop and validity end date, and a downloaded copy keeps working offline.
• [Conductor scan and verification log] The conductor scans the QR at the door and gets an instant verdict — verified, expired, wrong route or already scanned — with every scan logged by pass ID, time and result.
• [Admin approval workflow] The transport office sees every application with its documents attached, approves or rejects with a recorded reason, and manages routes, boarding stops, seat capacity and the semester validity window.
• [Pass status tracking and renewal] The student tracks the application live — submitted, approved, paid, pass issued — and the app prompts for renewal before the semester validity ends.
• [Route and stop lookup] Students browse the 5 seeded routes with boarding stops and departure times before choosing a route, so the application carries the right stop from the start.

• Complete Android app source code in Kotlin (Android Studio project)
• Firebase setup guide: Authentication, Cloud Firestore collections and Cloud Storage rules
• Seeded demo dataset with 5 routes, boarding stops and sample applications
• Working demo build of the apply, payment, QR pass, admin and conductor screens
• Project report PDF (background, methodology, architecture, results)
• PPT presentation for final review
• Viva Q&A preparation document (Android, Firebase, UPI flow, QR verification)
• Setup and demo instructions