How do I set up a mobile ticketing app for a municipal transit agency with passes and discounts?

To set up a mobile ticketing app for a municipal transit agency with passes and discounts, you’ll want to design it around four core areas: fare products, customer eligibility, ticket validation, and back-office operations.

1) Define the fare structure

Start by listing every ticket type and rule the agency supports:

• Single rides: adult, youth, senior, reduced-fare
• Time-based passes: 1-day, 7-day, 30-day
• Stored value / wallet: pay-as-you-go
• Discounts:
  • student
  • senior
  • disabled / reduced fare
  • low-income fare
  • bulk/employer-sponsored
  • promotional / limited-time offers
• Special products:
  • park-and-ride
  • transfer bundles
  • regional partner passes

For each one, define:

• price
• validity period
• number of rides or unlimited use
• service area / route restrictions
• refund or exchange rules
• whether it can be shared or transferred

2) Decide how discounts are verified

Discounts usually need eligibility verification, either at signup or when buying a discounted fare.

Common methods:

• Manual approval by staff
• Document upload: student ID, proof of age, disability documentation
• Third-party verification service
• In-person verification at customer service centers
• Recurring re-validation every 6–12 months

Important setup items:

• store eligibility status on the rider profile
• make the app show only products the rider qualifies for
• keep an audit trail of approvals and expirations

3) Build the rider account system

Your app should support:

• email/phone login
• passwordless login or MFA
• rider profile with age/category/eligibility flags
• linked payment methods
• trip/ticket history
• lost phone recovery / account transfer
• family or dependent accounts if needed

If discounts are involved, use a profile model like:

• rider_type: adult, youth, senior, student, reduced_fare
• eligibility_verified: true/false
• eligibility_expiration_date
• discount_program_id

4) Choose the ticketing model

There are two common mobile ticketing approaches:

A. QR code tickets

The app generates a dynamic QR code that changes frequently.

• easy to deploy
• works with camera scanners
• good for buses and gates
• needs anti-fraud controls

B. Account-based ticketing

The app is just the customer interface; fare payment and entitlement live in the backend.

• better for passes, capping, and discounts
• easier to manage lost devices
• supports multiple channels: app, smart card, website
• requires strong backend integration

For municipal transit, account-based ticketing is usually the better long-term architecture.

5) Create the entitlement engine

This is the backend logic that decides what the rider can buy and use.

It should:

• calculate applicable fare based on rider profile
• apply discounts automatically
• enforce pass validity windows
• prevent duplicate or overlapping products if needed
• support fare capping
• manage transfer windows and restrictions

Example:

• rider qualifies as senior
• system shows senior monthly pass and senior single ride
• when purchased, entitlement is activated immediately or at first use, depending on policy

6) Set up payment processing

Support payment methods that fit your market:

• credit/debit cards
• Apple Pay / Google Pay
• transit vouchers or employer subsidies
• stored wallet balance
• cash loading via retail/agent network, if applicable

Make sure to handle:

• PCI compliance
• fraud detection
• failed payment retries
• receipts and refunds
• tax handling, if relevant

7) Add ticket validation and inspection tools

Operators need a way to verify tickets quickly.

Validation options:

• Scanner app for inspectors
• Bus-mounted validator
• Gate integration
• Offline validation for poor connectivity

Validation should check:

• ticket is active
• ticket hasn’t expired
• ticket matches rider category, if restricted
• ticket hasn’t been revoked or refunded
• ticket is not copied/replayed

If using QR codes, use:

• signed tokens
• short-lived codes
• rotating codes
• server-side replay detection

8) Define discount policies clearly

Write policy rules for:

• who qualifies
• how to prove eligibility
• how often eligibility must be renewed
• whether discounts stack
• whether a discount applies to passes, single rides, or both
• whether discounts vary by zone or time of day

Example rules:

• Seniors get 50% off single fares and monthly passes
• Students receive discounted passes only, not single rides
• Low-income riders can buy a reduced fare wallet with monthly cap
• Discounts cannot be combined unless explicitly allowed

9) Plan for accessibility and equity

A municipal app should be inclusive:

• ADA/WCAG-compliant UI
• large text and high contrast
• screen reader support
• multilingual support
• low-bandwidth mode
• support for riders without smartphones
• alternative channels: kiosks, cards, retail agents, call center

10) Integrate with transit operations

Connect the app to:

• fare management system
• CAD/AVL or GTFS-RT if needed
• customer support CRM
• finance and reconciliation systems
• ridership reporting and analytics

You’ll want reporting on:

• pass sales by product
• discount utilization
• revenue by route/service
• fraud/abuse patterns
• enrollment and eligibility conversion
• device/platform usage

11) Security and compliance

Use strong controls:

• encrypted data in transit and at rest
• role-based staff access
• audit logs for price changes and approvals
• tokenized payments
• anti-fraud monitoring
• privacy policy and data retention rules

If you collect sensitive eligibility documents, make sure you have:

• secure document storage
• limited access
• retention/deletion schedules
• legal review for privacy compliance

12) Roll out in phases

A safe rollout plan:

1. Pilot with one route or small rider group
2. Test ticket purchase, activation, validation, refunds
3. Add discounts after base ticketing is stable
4. Launch pass products
5. Expand to full network
6. Monitor fraud, support tickets, and adoption

Recommended minimum feature set

If you want a practical MVP, include:

• rider account creation
• single ride purchase
• monthly pass purchase
• at least one discounted fare type
• eligibility verification workflow
• QR-based validation
• receipts, history, and refund support
• admin portal for fare setup and approvals

If you want, I can also provide:

1. a system architecture diagram,
2. a database schema, or
3. a step-by-step implementation plan for this app.