Fare collection
Manage payment and fare-collection flows for defined mobility services.
AFC
Bring fragmented field components together in one fare-collection architecture.
When validators, cards, terminals, top-up, subscriptions, monitoring and reporting are managed as separate systems, operations become complex. Galaksity brings these layers together in one central fare-collection architecture according to project requirements.

HOW WE BUILD IT
ONE SYSTEM ARCHITECTURE
Ten capabilities are designed not as isolated modules, but as one integrated fare-collection system sharing data, rules and operational flows.
Manage payment and fare-collection flows for defined mobility services.
Validate the card or relevant payment device according to its usage rules.
Manage balance loading, top-up tracking and the connection of multiple top-up channels with the central system.
Connect field terminals to the system as the physical transaction points of the fare-collection flow.
Manage card registration, status and usage processes centrally.
Bring field components, definitions and operational parameters together in one management layer.
Define subscription products, associate them with users or cards, and manage validity periods and usage rules.
Bring transaction and operational data together in traceable reports.
Connect the fare-collection system with other software and infrastructure components within the project scope.
Use central monitoring to track the operating status of field devices, transaction flows and system components.
FREQUENTLY ASKED QUESTIONS
A system that brings together fare collection, validation, card and terminal management, card top-up, subscription management, central monitoring, reporting and integration for mobility services.
Depending on the project scope, it can include fare collection, validation, terminals, card management, central management, reporting, integration, card top-up, subscription management and monitoring.
Top-up transactions and different top-up channels can be connected to the central system. Subscription products can be defined and linked to a card or user, with validity periods and usage rules managed centrally.
It tracks the operating status of field devices, transaction flows and system components, giving operations teams a common view.
The integration scope is defined after analysing existing devices, software, card structures, data flows and operational requirements.
Field scope, fare model, validation rules, terminal structure, top-up and subscription model, monitoring and reporting requirements can be configured around each project.
ELECTRONIC FARE COLLECTION