Site-specific rate structure
Set periods and user products around the way the facility actually operates.
Parking payment
Parking payment kiosks, integrated from end to end
Lexoh connects the kiosk, rates, access rights and transaction reporting in one coherent journey. We define how payment works at the site, install the field equipment and configure the platform used by the operating team.
Outdoor payment
Configurable rates
Transactions and receipts
Access validation
Turnkey installation
Operating design
Design the payment journey before selecting the kiosk
A kiosk is only one touchpoint. The project must settle when the driver pays, how the stay is identified, what validates the exit and how staff handle an exception. Those decisions determine the lane equipment, screens, reports and assistance procedure.
Payment tied to access
Associate the transaction with the ticket, plate, code or account used at the lane.
Guided interaction
Show the driver only the instructions needed to complete the transaction.
Transaction follow-up
Give staff the events needed to answer a customer question or reconcile activity.
Exception handling
Define lost-ticket, validation, cancellation and assistance cases before launch.
Outdoor deployment
Plan foundations, protection, power and communications for the kiosk location.
Decision path
From a configured rate to an authorized exit
The exact path varies by site, but each decision should remain understandable and traceable.
01 — Identify
Ticket, plate, code or account
02 — Calculate
Applicable rate rule
03 — Pay
Guided kiosk transaction
04 — Validate
Access right updated
05 — Exit
Decision sent to the lane
Lexoh field evidence
Kiosks in production
This workshop photo shows a batch of enclosures before final component integration. Screens, readers, payment hardware, communications and configuration are then adapted to the journey designed for each project.
What this changes in the project
Equipment placement, civil work, communications and operating procedures are validated together before commissioning.
Turnkey delivery
What turnkey payment delivery covers
We frame the project with the staff who will run it, then coordinate the field and software work that makes payment part of the wider parking system.
- 01Review rates and customer categories
- 02Define the entry–payment–exit journey
- 03Select and position the kiosk
- 04Connect barriers, readers and the platform
- 05Test transactions and exception scenarios
- 06Train staff and document the operation
Operating contexts
Different payment journeys for different facilities
Public parking
Self-service payment with visible instructions and rules staff can explain.
Tourism sites
Daily products, visitors and operating periods that change through the year.
Campuses and offices
A mix of subscribers, visitors and occasional validations.
Seasonal sites
Long-duration rights combined with occasional paid visits.
Before specifications
Questions to settle during design
Does payment happen before or after the stay?
This changes identification, exit control and lost-ticket handling.
How does a driver get help?
Intercom routing, visible instructions and after-hours procedures belong in the journey.
Where will the kiosk sit?
Traffic, accessibility, snow, drainage, bollards and connectivity all matter.
Which records must staff reconcile?
Agree on the required reports and ownership before configuration.
Questions asked before a project
Clear answers about scope, operation and integration.
Yes. Depending on the design, payment can update the right attached to a ticket, plate, code or account and allow the exit decision.
Multiple products and rules can be configured. Their presentation should still remain clear for the driver and is defined during project analysis.
The base, power, communications, drainage, impact protection, customer approach and service access all need to be reviewed.
No. The kiosk is an interaction point; rates, rights, transactions, devices and events are managed more effectively through a connected platform.
Define a payment journey that works in the field
Tell us about the facility, rates, users and operating constraints so we can map the complete architecture.
