ITKIT
Airport and road gates · 19 / 20
Free-flow highway tolling with a driver app
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
1
Toll plazas make every car and truck stop and queue.
2
Drivers learn about charges, low balances and fines too late.
3
A misread plate becomes a fine with no simple way to dispute it.
Stop · Queue · Pay · Drive through
ITKIT · iToll · Prototype screens, synthetic data
The problem
Our answer
Gantries read a tag or plate at full speed, and the driver app shows the charge within seconds. Unread plates and disputes go to a person; amounts here are illustrative because real tariffs are not set.
How it works · 1 of 5
iToll
With iToll, the gantry reads the tag or the plate at full speed.
96
full speed
ITKIT · iToll · Prototype screens, synthetic data
How it works
How it works · 2 of 5
Driver app
The driver app shows the charge within seconds, with the balance left.
ITKIT · iToll · Prototype screens, synthetic data
How it works
How it works · 3 of 5
Every trip
Every trip shows how it was read and that the tag transaction was authenticated.
ITKIT · iToll · Prototype screens, synthetic data
How it works
How it works · 4 of 5
Human review
If a plate is unclear, a person reads it. Nothing is billed until she confirms.
ITKIT · iToll · Prototype screens, synthetic data
How it works
How it works · 5 of 5
Disputes
Drivers dispute from the app and get a decision with a reason.
ITKIT · iToll · Prototype screens, synthetic data
How it works
What it includes
Drivers with an iToll account
Drivers checking a charge
Drivers paying a trip or topping up
Drivers and fleet owners
Drivers who think a charge is wrong
Plate reviewers, dispute reviewers and toll operations staff
Drivers with an iToll account
ITKIT · iToll · Prototype screens, synthetic data
What it includes
Built to standards
| Standard | What it covers in iToll |
|---|---|
| ISO 17573-1:2019 | EFC reference model and roles |
| EN 15509:2023 | DSRC transaction security |
| EN ISO 14906:2023 | EFC application interface (vehicle data) |
| Leading practice (ANPR enforcement) | Human review of unclear plates |
| Leading practice (disputes) | Disputes with evidence and a reasoned decision |
| PCI DSS v4.0.1 | Card payments in the app |
| ISO/IEC 27001:2022 and data-protection practice | Retention and access transparency |
| WCAG 2.2 SC 3.3.8 Accessible Authentication (Minimum) | Sign-in without a memory test |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · iToll · Prototype screens, synthetic data
What it includes
Connects to
Licensing registry (plate and owner check)
Payment gateway and wallets
Fines authority
Tag issuer and distribution
OneID (driver account sign-in)
ITKIT · iToll · Prototype screens, synthetic data
What it includes
Safeguards
Real tariffs and fine amounts are not set; every SYP amount shown is illustrative.
iToll does not issue fines; the fines authority does.
Nothing is billed from a plate read until a person confirms it.
ITKIT · iToll · Prototype screens, synthetic data
Delivery
How delivery works
6–10 weeks
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
iToll at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
We run it with your team, train them, then hand over operations, code escrow and keys.
Durations are typical ranges, fixed per contract
ITKIT · iToll · Prototype screens, synthetic data
Delivery
Next step
Drivers see what data is held and who looked at it. iToll is a working name and every amount is illustrative. Ask us for a walkthrough.
1 · Demo
A guided session on the iToll prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you