What Is a Validator? A Bus Validator Selection Guide
Last updated: 08.08.2026 · Technical content: SoleAkbil Engineering Team
A validator is the in-vehicle payment terminal that verifies a passenger's right to travel and collects the fare when they tap a card, phone or ticket. It is the field-facing part of an automated fare collection (AFC) system: it reads the card, charges the fare according to the tariff, records the transaction and forwards it to the central software.
What Does a Validator Do?
The word "validate" says it all — that is the validator's core job. When a passenger taps, the device performs the following in sequence:
- Reads the identity. It detects a Mifare card, NFC phone, QR ticket or EMV credit card.
- Validates the right to travel. Card type, balance, pass / ride credits and blacklist status are checked.
- Calculates the fare. The amount is determined by card type and current tariff; transfer and special-day discounts are evaluated.
- Charges and records. The balance is deducted and the transaction is written to an immutable ledger.
- Gives feedback. Voice announcement, coloured LED and screen inform driver and passenger; a door/turnstile relay is triggered where needed.
This whole chain must complete in under a second — otherwise queues build up at stops.
Smart Validator vs. Simple Card Reader
| Simple card reader | Smart validator |
|---|---|
| Reads only the card UID | Evaluates card type, tariff, pass limits and discount rules |
| Depends on the server | Processes without connectivity, then syncs |
| Single access method | Card + NFC phone + QR ticket + EMV credit card |
| No or limited screen/audio | Touchscreen, voice announcement, LED, multi-language |
| Cannot be managed remotely | Remote tariff/settings sync, device health monitoring |
| No security layer | Card-key isolation, PIN-protected driver login, kiosk lock |
What to Look For When Choosing a Validator
1. What happens when the internet drops?
This is the critical question. On server-dependent devices, collection stops as soon as the signal goes. On the Sole Akbil validator, physical Mifare card taps run fully offline: the transaction is queued and synced automatically once connectivity returns.
2. How many access methods are supported?
Passenger profiles are not uniform. The Sole Akbil validator brings four methods together in one device: Mifare card, NFC phone (HCE), QR ticket and EMV credit card. That removes the need to buy separate devices.
3. How is card security handled?
Card cloning is the best-known weakness of city card systems. In Sole Akbil each operator has its own encrypted card key; a card obtained from another source cannot work cryptographically. In addition, the Clone Suspicion Report (R16) automatically catches the same card being used on different devices within 120 seconds.
4. Where is the fare calculated?
A fare calculated on the device can be manipulated. In Sole Akbil the amount written to the ledger is always the amount the server calculated; even if the application is reverse-engineered, no fake transaction can be produced.
5. What is the driver and passenger experience like?
Automatic card detection (continuous listening, no button press), quick fare buttons, a large accessible screen, coloured LED strip, voice announcements and birthday greeting messages — these determine acceptance in the field.
6. Can you manage the fleet remotely?
You do not want to visit every vehicle for a tariff change. Prices and settings are distributed to the whole fleet remotely from the central panel; a device that sends no data for 5 minutes is automatically flagged "offline".
Technical Framework of the Sole Akbil Validator
| Operating system | Android-based dedicated POS operating system |
|---|---|
| Connectivity | SIM card (4G), WiFi or Ethernet |
| Access methods | Mifare Card, NFC Phone, QR Ticket, EMV Credit Card |
| Card technology | Mifare Classic (DESFire supported in the infrastructure) |
| Operating mode | Offline-first; card taps work without connectivity |
| Security | Operator-specific encrypted card key, PIN-protected driver login, kiosk lock, hardware-backed encrypted device secret |
| Interface | Touchscreen, voice announcement (TTS), coloured LED strip, door/turnstile relay |
| Languages | Turkish, English, French (including screens, announcements and error messages) |
| Management | Remote settings/tariff sync, device health and last-seen tracking |
Hardware options and module configuration (EMV module, external reader, mounting type) are determined by project scope. For model details see Sole Akbil T20 and Sole Akbil T10.
Which Operator Should Choose Which Validator?
- District municipality / rural route — offline operation and voice announcements come first.
- Minibus and shared-taxi cooperative — compact mounting, quick fare buttons and driver shift tracking come first.
- Private bus operator — per-plate revenue reporting and the daily Z report come first.
- Tourism and campus transport — multi-language interface, QR ticketing and EMV credit card come first.
Continue reading: what is an AFC system? · city card system · validator software
Frequently Asked Questions
What is a validator and what is it for?
A validator is the in-vehicle payment terminal that verifies a passenger's right to travel and collects the fare when they tap a card, phone or ticket. It reads the card, charges the fare according to the tariff, records the transaction and forwards it to the central software.
Does a bus validator work without internet?
On the Sole Akbil validator, physical Mifare card taps run fully offline; the balance is deducted locally and instantly, the transaction is queued and synced automatically once connectivity returns. NFC phone and QR ticket taps run online because they require server validation.
Which payment methods does the validator accept?
The Sole Akbil validator brings four methods together in one device: Mifare card (physical city card), NFC phone (HCE), single-use QR ticket and contactless EMV credit card.
Is there a card cloning risk on the validator?
Because each operator has its own encrypted card key, a card obtained from another source cannot work cryptographically. In addition, the Clone Suspicion Report (R16) automatically catches the same card being used on different devices within 120 seconds.
Do I have to visit every vehicle for a tariff change?
No. Price and settings changes are distributed to the whole fleet remotely from the central management panel. Devices sync over SIM internet.
How many languages does the validator support?
Turkish, English and French are supported, including all on-device screens, voice announcements and error messages.
Let's Choose the Right Validator Together
Tell us your fleet size and route structure and we will recommend the right model.