ITKIT

Airport and road gates · 19 / 20

iToll

Free-flow highway tolling with a driver app

From the problem to how we solve it

iToll prototype screens

October 2026

Interactive prototype · synthetic data only

The problem

Stop. Queue. Pay.

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

Amounts are illustrative

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

Free flow on the M5

With iToll, the gantry reads the tag or the plate at full speed.

96

km/h

full speed

M5 gantry

Tag read

or plate read

ITKIT · iToll · Prototype screens, synthetic data

How it works

How it works · 2 of 5

Driver app

Alert within seconds

The driver app shows the charge within seconds, with the balance left.

Driver app screen: a charge alert shown seconds after the gantry, with the balance left

ITKIT · iToll · Prototype screens, synthetic data

How it works

How it works · 3 of 5

Every trip

Authenticated tag read

Every trip shows how it was read and that the tag transaction was authenticated.

Trip detail screen: how the trip was read, what was charged and the authenticated tag transaction

ITKIT · iToll · Prototype screens, synthetic data

How it works

How it works · 4 of 5

Human review

A person confirms unclear plates

If a plate is unclear, a person reads it. Nothing is billed until she confirms.

Operator back office: an unclear plate image waiting for a reviewer to read and confirm it

ITKIT · iToll · Prototype screens, synthetic data

How it works

How it works · 5 of 5

Disputes

Dispute from the app

Drivers dispute from the app and get a decision with a reason.

Dispute screens: a driver’s dispute in the app and the reviewer’s decision with a reason in the back office

ITKIT · iToll · Prototype screens, synthetic data

How it works

What it includes

7 screens and workflows in the prototype

Driver home

Drivers with an iToll account

Trip detail

Drivers checking a charge

Top up and pay

Drivers paying a trip or topping up

Vehicles and tags

Drivers and fleet owners

Dispute a charge

Drivers who think a charge is wrong

Operator back office

Plate reviewers, dispute reviewers and toll operations staff

Account and privacy

Drivers with an iToll account

ITKIT · iToll · Prototype screens, synthetic data

What it includes

Built to standards

International standards it is built to

StandardWhat it covers in iToll
ISO 17573-1:2019EFC reference model and roles
EN 15509:2023DSRC transaction security
EN ISO 14906:2023EFC 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.1Card payments in the app
ISO/IEC 27001:2022 and data-protection practiceRetention 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

What iToll works with

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

What iToll will never do

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

Start small, prove it, then scale and hand over

6–10 weeks

Assess

Map what already exists and decide, system by system: reuse, integrate, modernise or build.

4–6 months

Pilot

iToll at one authority, with real users and a measured outcome, on national infrastructure.

12–24 months

Scale

Roll out by region and service, sharing identity, integration and audit.

Agreed per contract

Operate and transfer

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

Walk through the iToll driver app and back office with synthetic trips.

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

F = full screen