Public Transportation Software

Account-Based Ticketing Explained: How Modern Transit Fare Systems Work and How to Evaluate Them

S
SaaSPodium Editorial TeamUpdated:
Account-Based Ticketing Explained: How Modern Transit Fare Systems Work and How to Evaluate Them - SaaSPodium

Advertisement

Account-based ticketing keeps a rider's fares, balance and trip history in a central back-end account, with a card, phone or bank card acting only as an identifier. This lets agencies change fare rules, apply caps and issue refunds centrally without reprogramming cards or devices.

Transit agencies are moving fare collection from cards and paper tickets to cloud accounts because riders expect to pay with the devices they already carry. The change affects procurement, security, accessibility and finance, not just the ticket machine.

This guide explains how account-based systems work, how they compare with other models, and how to evaluate vendors against integration, compliance and cost.

What Account-Based Ticketing Means

Account-based ticketing (ABT) stores a rider's fare entitlements, balance and travel history in a back-end account instead of on a card or ticket. The card, phone or bank card is only an identifier that points to that account.

This shifts fare logic from the device to the cloud. Agencies can change fare rules, apply caps and issue refunds centrally, and riders can use several payment methods against one account.

Fare systems also depend on consistent public data. Many agencies publish schedules in the GTFS format, but the ticketing back end must still agree with that data on routes, zones and fare rules; our guide to GTFS and transit data explains the schedule side.

Closed-Loop, Open-Loop and Mobile Ticketing

Closed-loop systems use agency-issued cards or tickets, open-loop systems accept riders' own contactless bank cards or phones, and mobile ticketing sells and validates tickets in an app. Most agencies run a mix.

Each model has trade-offs. Closed-loop gives full control over fare products and concessions but requires card distribution. Open-loop lowers friction for visitors and cuts cash handling, but concessions and fare capping need careful design. Mobile ticketing is fast to launch but needs reliable validation for riders with low connectivity.

  • Closed-loop: agency cards, tickets and passes; best for concessions and loyalty programmes.
  • Open-loop: contactless bank cards and phones; best for tourists and low-friction access.
  • Mobile: in-app purchase and visual or scanned validation; best for fast rollout and digital-first riders.

The Technical Architecture Behind Fare Systems

A modern fare platform has four layers: validators and ticket vending devices at the edge, a payment and account back office, fare-rule and product management, and reporting and settlement. APIs connect these layers to journey planners and customer apps.

Interoperability matters. Fare systems should connect with scheduling, real-time data, CRM or customer service tools, payment processors and identity services such as SSO for staff. Ask vendors how they handle offline validation, since vehicles lose connectivity in tunnels and rural stretches.

Payment security is not optional. Any system that handles card data should align with the PCI Security Standards Council requirements, and agencies should confirm who is responsible for each control in a shared responsibility matrix.

Vendors in the SaaSPodium Directory

SaaSPodium lists twelve public transportation software products, several of which touch fare payment and passenger information. Pricing is not published for these enterprise-oriented tools, so expect to request quotes.

Examples from the directory include Masabi (fare payments as a service), Bytemark (mobility and ticketing platform), INIT (IT solutions for public transport), Moovit (mobility as a service solutions) and Via (transit technology for smart cities). Also review Swiftly for real-time passenger data and TransLoc for campus transit.

Browse all products in the Public Transportation Software category and see how to run a structured evaluation in our guide to choosing public transit software.

How to Evaluate a Fare Platform

Evaluate a fare platform by modelling your real fare policy, testing accessibility, and proving the back office can reconcile revenue. Start with a written list of fare products, concessions, transfers and caps.

Request a demonstration using your own fare table, not a generic one. Test the rider app and web portal against the W3C Web Content Accessibility Guidelines because public agencies often have legal accessibility duties. Review data ownership, exit terms and how rider data is retained, using the principles on GDPR.eu if you serve EU riders.

Cost per validated trip = (Fare system operating cost + Payment fees) ÷ Number of validated trips

Operating cost includes licences, hosting, devices and support, while payment fees are processor charges. Compare this figure before and after a move to open-loop to see whether cash handling savings outweigh card fees. Vendors such as Masabi publish information on their fare payment approach that you can use to prepare demo questions.

Implementation Roadmap

Roll out fares in phases: pilot on one route, expand to a mode, then retire legacy media. Keep the old system running in parallel until reconciliation matches for at least one full billing cycle.

A typical plan includes fare policy definition, device and back-office integration, data migration of existing accounts, staff training, marketing to riders and a defined rollback path. Allow extra time for procurement and for integration with journey planning and customer support systems.

Frequently Asked Questions

How much does a transit fare payment system cost?
Public transportation software vendors in the SaaSPodium directory do not publish prices, so costs come from quotes. Expect pricing to depend on vehicle count, validators, transaction volume and whether the platform is delivered as a service or as an installed system.

How long does it take to migrate from card-based to account-based ticketing?
Plan roughly 12 to 24 months for a full agency migration including procurement, integration, testing and phased rollout. A mobile ticketing pilot can launch much sooner, often within a few months, while legacy media stays in service.

Should we choose open-loop or closed-loop fares?
Many agencies use both. Open-loop works well for visitors and low-friction access, while closed-loop remains valuable for concessions and agency-specific passes. Model your rider mix and fare policy before deciding, then pilot on one route.

Advertisement