Account-Based Ticketing (ABT)

Account-Based Ticketing for Public Transport

Manage passenger accounts, fare rules and payment activity in a central back office. movinton connects account-based ticketing with automated fare collection, onboard validators and passenger applications for transport authorities and bus operators.

Passenger payments

A simple tap. A connected journey.

Bring cards, QR tickets and mobile payments together with onboard validation and a central fare collection platform.

  1. 1Passenger payment
  2. 2Onboard validation
  3. 3Central fare management

What is account-based ticketing?

Account-based ticketing (ABT) manages passenger balances and travel entitlements in a central system rather than relying on the physical card alone. A transit card or another supported payment medium identifies the journey, while the back office manages the account and applicable fare rules. This separates the passenger account from the device used to travel.

Account-Based Ticketing for Public Transport

Connect fare policies with passenger entitlements

Transport agencies need to manage more than a single adult fare. movinton connects passenger profiles with zone-based and distance-based tariffs, transfer rules and concessionary fares. Operators manage these policies centrally alongside account balances and transaction records, keeping fare administration within one operational environment.

Bring payment media into the same ticketing system

An ABT architecture can work with transit smart cards, QR tickets, contactless bank cards and mobile NFC payments, according to the deployment. movinton links payment acceptance with fare validators and centralized management, so the rider application, onboard equipment and operational back office work together. ABT and open-loop payment acceptance address different parts of this journey.

Follow fare activity from boarding to the back office

Each fare validation contributes to the operational view of the transport network. Teams can monitor transactions, review passenger account activity and connect fare information with fleet operations and passenger services. The Manisa deployment illustrates how validators, driver consoles and contactless payments fit within the wider movinton platform.

Frequently Asked Questions

How do ABT and AFC differ?

Automated fare collection (AFC) covers the wider process of accepting and validating fares. Account-based ticketing describes how passenger accounts, balances and entitlements are managed. ABT can be part of an AFC system.

Is ABT the same as open-loop payment?

No. ABT concerns where accounts and fare logic are managed. Open-loop payment allows passengers to use supported bank cards or mobile wallets. They can work together within the same transit payment solution.

Can account-based ticketing support bus networks?

Yes. Onboard bus fare validators connect passenger payment activity with the central ticketing platform. The appropriate media, fare rules and account workflows depend on the operator’s requirements.

LET’S MOVE FORWARD

Your city’s next chapter.

Let’s build a more connected public transport experience, together.

Let’s talk about your project