Resources
Side-by-side comparison
Account-Based Ticketing (ABT)
The account — not the card or device — is the ticket. Riders touch in and out; the back office calculates the optimal fare and charges the registered payment method. Supports fare capping, multi-modal journeys, and contactless bank cards.
- Real-time account management
- Fare capping built in
- Works with any contactless card or device
Traditional AFC
Automatic Fare Collection is the broad category. Traditional AFC uses stored-value smart cards or paper tickets where value or validity is encoded on the medium itself — not in a central account. Includes legacy contactless smart cards like Oyster, ORCA, and Charlie Card.
- Card must be present to travel
- Value stored on medium, not account
- Hardware-dependent infrastructure
Common misconception
“ABT and AFC mean the same thing.” They don’t. AFC is the category; ABT is a specific and more modern architecture within it. All ABT systems are AFC systems, but not all AFC systems are ABT.
Common questions
ABT FAQ
Not necessarily. Justride's open Validation SDK means ABT can work with your existing hardware. If your validators can read the token type you want to support, they can work with ABT.
ABT works with smart cards, wearables, and contactless bank cards — not just smartphones. Riders don't need to use an app to benefit from account-based ticketing.
The back office looks at the rider's account, their travel history for the day or week, and the fare rules configured by the agency — and automatically applies whichever product gives the rider the lowest fare for their journeys.
Masabi has delivered full ABT deployments in 11 months from contract signature to go-live. The configure-not-build approach removes the main sources of delay in traditional transit technology projects.