Resources — Explainer

What is account-based ticketing?

Account-based ticketing is a fare model where the account is in the back office — not on the card. Riders tap any token to board and the platform works out the right fare automatically.

Back to resources

Definition

ABT in plain language

Account-based ticketing (ABT) is a fare collection model where fare calculation happens in the back office after each tap — rather than on the card or device at the time of boarding. The rider registers a token (smart card, phone, or wearable), taps to travel, and the platform automatically applies the right fare, discount, or cap to their account. No pre-selection of ticket type is required.

How it works

Tap, travel, done

  1. Register a token

    Rider registers a smart card, phone, or wearable to their account — once, not per journey

  2. Tap to board

    Token is validated at the gate or onboard — the back office records the tap

  3. Best fare applied

    The platform calculates the right fare — product, discount, or daily/weekly cap — and charges the account

ABT vs stored value

What makes ABT different from a smart card?

Traditional stored-value smart card

  • Value stored on the card itself — lost card = lost value
  • Rider must select the right ticket before boarding
  • Card reader does the calculation at the gate
  • Single token type only
  • Proprietary infrastructure required

Account-based ticketing

  • Account in the back office — token is just an identifier
  • Platform automatically finds the best fare
  • Back office does the calculation after boarding
  • Any token — smart card, phone, wearable, bank card
  • Open APIs — works with any hardware

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.