What are the best free fare collection systems for a small transit fare modernization pilot?

For a small transit fare modernization pilot, the “best free” fare collection options usually means open-source / low-cost-to-start tools rather than fully free commercial platforms. The right choice depends on whether you need mobile ticketing, contactless cards, QR codes, cash handling, or simply a proof-of-concept.

Best free / open-source options to consider

1. OpenTripPlanner + GTFS + simple payment/ticket layer

Best for: agencies piloting digital fares with minimal infrastructure

• Open-source trip planning and routing
• Can be paired with a lightweight web app for fare purchase/validation
• Good if you want a prototype that links trip info + ticketing
• Not a complete fare collection system by itself, but a strong foundation

Pros: free, mature, widely used
Cons: you still need to build or integrate payment and validation logic

---

2. MOBY or similar open-source mobile ticketing components

Best for: QR-based mobile tickets in a small pilot

• Some open-source transit ticketing projects exist, but quality and maintenance vary
• Useful for a pilot where riders buy a pass in a web app and show a QR code
• Can be validated with low-cost Android devices

Pros: low hardware cost, easy rider experience
Cons: fragmented ecosystem; verify current maintenance before choosing

---

3. Open-source fare validators + custom backend

Best for: pilots using smartphones or low-cost Android devices as validators

• Use Android tablets/phones with a custom validation app
• Backend can be built with open-source tools like PostgreSQL, Node.js/Python, and a payment API
• Works for QR tickets, employee passes, or limited account-based systems

Pros: very flexible, inexpensive
Cons: requires some software development

---

4. Transit fare account-based systems built on open-source infrastructure

Best for: agencies wanting account-based fares without proprietary lock-in

• Store rider accounts centrally
• Issue QR or NFC media linked to accounts
• Can later expand to smart cards or bank card-based open loop

Pros: scalable, modern architecture
Cons: more complex; usually needs custom integration

---

5. Generic open-source payment tools + fare logic

Best for: token-based, pass-based, or pay-as-you-go pilot
Use:

• Stripe or similar for payment processing
• Open-source web app for fare purchase and rider accounts
• QR code libraries for ticket issuance
• Open-source validators on Android devices

Pros: fast to launch, low upfront software cost
Cons: payment processing itself is not free, even if software is

---

If you want truly minimal-cost pilot setups

Option A: QR code mobile pass pilot

• Rider pays online
• Receives QR code on phone
• Driver or inspector scans it with Android device
• Best for: small fixed-route pilot

Option B: Stored-value / pass account pilot

• Riders create accounts
• Fare deducted or pass activated digitally
• Good for: workforce shuttles, university routes, small urban networks

Option C: Smartphone validator pilot

• No dedicated hardware beyond Android phones/tablets
• Best for: proof-of-concept and low-budget deployment

---

What to avoid for a small pilot

• Full smart card systems unless you already have hardware and support
• Closed proprietary fare suites with high setup fees
• Open-loop bank card payment if your ridership is small and you want low complexity; it’s often overkill for a pilot
• Custom hardware-heavy systems unless you have IT and operations support

---

My practical recommendation

For a small modernization pilot, the most cost-effective path is usually:

1. QR code-based mobile tickets
2. Android phone/tablet validation
3. Open-source backend for rider accounts and ticket verification
4. Commercial payment processor for transactions

This gives you a modern customer experience without expensive farebox or smart card infrastructure.

---

To narrow it down

If you want, I can give you:

• a shortlist of specific open-source projects
• a recommended architecture for a pilot
• or a comparison table for QR, NFC, smart card, and open-loop payment options

If you tell me your pilot size, mode, and whether you want bus-only, rail, or multimodal, I can suggest the best fit.