How do I choose between different fare collection systems for a transit agency procurement team?

Choosing a fare collection system is really a business-and-operations decision first, and a technology decision second. For a procurement team, the best approach is to compare systems against the agency’s service goals, rider needs, operating constraints, and long-term cost.

Here’s a practical framework.

1) Start with the agency’s goals

Before comparing vendors, define what the system must achieve. Common goals include:

• Reduce fare evasion
• Speed boarding and reduce dwell time
• Improve rider convenience
• Support mobile and contactless payments
• Serve unbanked riders and equity goals
• Simplify operations and reconciliation
• Integrate with regional partners
• Reduce cash handling costs
• Provide better data for planning and enforcement

If you don’t define priorities first, “best” will just mean “most features.”

2) Identify the main system types

Most procurement decisions fall among a few models:

Closed-loop smart card system

• Agency-issued card or media
• Stored value and/or passes
• Works well where the agency wants full control
• Often good for equity and offline use
• Can be less convenient for occasional riders

Open-loop contactless EMV system

• Riders tap bank cards, phones, or wearables
• Lower barrier for occasional riders and tourists
• Can speed adoption
• Usually needs strong back-office fare capping and settlement logic
• May not fully solve equity or unbanked access without supplements

Account-based ticketing / fare capping platform

• Fare rules are in the back office, not on the card
• Supports multiple media: cards, mobile, tokens, QR, etc.
• More flexible for policies and regional integration
• Can be more complex to design and govern

Mobile QR or app-based system

• Useful as a supplement or in low-infrastructure environments
• Can be low cost to launch
• Depends heavily on smartphone access and device reliability
• Usually not ideal as the only payment channel

Mixed or hybrid system

• Often the best real-world answer
• Example: open-loop + agency card + mobile + cash reload options
• Better for inclusion, resilience, and adoption
• More complex procurement and integration

3) Evaluate against key criteria

A good RFP evaluation matrix usually includes:

Rider access and equity

• Can unbanked riders pay easily?
• Is cash still supported where needed?
• Are there reload locations in underserved areas?
• Does the system work for seniors, visitors, and people without smartphones?

Fare policy flexibility

• Can it handle transfers, passes, discounts, zones, distance-based fares, free fare periods, and capping?
• Can the agency change fares without replacing hardware?
• Can it support complex regional agreements?

Total cost of ownership

Look beyond purchase price:

• Devices and validators
• Back-office software
• Communications/networking
• Maintenance and spare parts
• Clearing and settlement fees
• Customer service and dispute handling
• Card issuance or media distribution
• Upgrades, cybersecurity, and lifecycle replacement

Implementation risk

• How long will deployment take?
• How much cutover disruption is expected?
• Is the vendor’s solution proven at your agency size?
• How much customization is required?

Reliability and uptime

• Can validators work offline?
• What happens if the network fails?
• How does the system handle degraded modes?
• What are the SLA requirements?

Security and fraud control

• Payment security, encryption, key management
• Fare evasion prevention
• Chargeback handling for open-loop systems
• Protection against cloning, replay, and tampering

Data and reporting

• Can the agency access raw transaction data?
• Are dashboards and exports available?
• Who owns the data?
• Can data support planning, auditing, and enforcement?

Integration and interoperability

• Can it integrate with existing buses, rail gates, paratransit, parking, or regional systems?
• Does it support APIs?
• Can multiple operators participate?
• Can it link to customer accounts or CRM tools?

Customer experience

• Is tapping intuitive?
• Are error messages clear?
• Is the refund/dispute process manageable?
• Does it reduce friction for frequent and occasional riders?

4) Match the system to your operating environment

Different agencies have different “best fit” solutions.

Good fit for open-loop EMV

• High share of banked riders
• Strong contactless payment adoption
• Simple fare structure
• Desire for quick implementation and broad convenience

Good fit for closed-loop or account-based systems

• Equity concerns or high unbanked population
• Complex fares, discounts, or regional products
• Need for strong agency control and custom policies
• Desire to support cash reloads and non-bank media

Good fit for hybrid systems

• Most agencies
• Need to serve both frequent and occasional riders
• Need to preserve inclusion while modernizing payment options

5) Ask vendors the right questions

In procurement, the quality of the questions matters a lot. Ask:

• What fare structures are supported natively?
• What parts of the system are configurable versus custom-coded?
• How does the system support offline operation?
• What are the uptime and response-time commitments?
• What APIs and data exports are included?
• Who owns transaction and customer data?
• How are upgrades handled?
• What is the implementation timeline?
• What reference agencies use this system at similar scale?
• What cybersecurity certifications and practices are in place?
• What is the vendor’s roadmap and product lifecycle support?

6) Use a scoring model

Create a weighted scorecard with categories such as:

• Cost: 20%
• Equity/accessibility: 20%
• Fare flexibility: 15%
• Reliability: 15%
• Implementation risk: 10%
• Data/reporting: 10%
• Integration: 10%
• Vendor experience/support: 5%

Adjust weights based on your priorities. For example, if your agency is focused on equity, accessibility and cash reload options should weigh more heavily.

7) Think about governance and operating model

A fare collection system is not just a device purchase. Decide:

• Who will administer fare policy?
• Who manages settlement and reconciliation?
• Who owns customer support?
• Who handles bank/payment disputes?
• How will regional partners share revenue?
• Who maintains the media lifecycle and lost-card replacement process?

If these roles are unclear, even a good system can become difficult to run.

8) Pilot before full deployment

If possible, run a pilot with:

• A representative route or line
• A mix of rider types
• Real-world failure scenarios
• Staff training and customer feedback
• Performance tracking against success metrics

Measure:

• Boarding time
• Payment acceptance rates
• Fare evasion
• Customer complaints
• Transaction failures
• Operational workload

9) Common procurement mistakes to avoid

• Choosing based on headline features only
• Underestimating back-office complexity
• Ignoring unbanked riders
• Not defining fare policy before procurement
• Over-customizing the system
• Failing to plan for future expansion or regional integration
• Not budgeting for lifecycle support and replacement
• Skipping cybersecurity and data ownership terms

10) A simple rule of thumb

• If you want the fastest convenience for occasional riders, consider open-loop EMV
• If you need maximum control and inclusion, consider closed-loop or account-based
• If you want a durable solution for a broad transit market, hybrid account-based fare collection is often the strongest choice

If you want, I can also give you:

1. a sample RFP evaluation scorecard,
2. a requirements checklist, or
3. a decision matrix comparing open-loop, closed-loop, and account-based systems.