Parking payment
Parking pay station or pay by phone: choosing the right mix
A pay station and mobile payment are different ways to start or settle a parking session. The right mix depends on the people using the lot and the operating work behind each channel.
The decision
Define the parking model first
Decide whether drivers pay on arrival, during a stay or before leaving. Establish how the stay is identified: plate, ticket, code or account. That choice affects kiosk placement, signs and the exit decision.
A payment channel should fit this model. Installing both channels is useful only if the rules, session records and assistance process agree.
Lexoh can scope kiosk and payment workflows around the lot’s users and operating model.
When an on-site station helps
A station gives visitors a visible place to pay using the methods installed on that model. It can serve people who cannot or prefer not to use a phone. Confirm supported cards, receipt options and accessibility rather than assuming every kiosk accepts cash or includes an intercom.
Budget for the location as well as the cabinet: power, communications, drainage, protection, snow clearance and service access. Consumables and payment-terminal support remain operating responsibilities.
On a narrow screen, scroll the table horizontally to see every column.
| Question | Pay station | Phone |
|---|---|---|
| Visitor interaction | Installed terminal and available payment methods | Browser or app workflow selected for the project |
| Site work | Base, power, communications and service access | Signs, connectivity and payment instructions |
| Exceptions | Terminal, printing and transaction assistance | Account, plate-entry and payment assistance |
| Outage | Verify payment architecture and backup path | Verify network and service availability |
When phone payment helps
Mobile payment can reduce trips to a station and may allow a visitor to pay from the vehicle. Check the actual workflow: browser or application, account requirements, plate entry, confirmation and extension rules.
Make the location identifier and payment instructions unambiguous. A wrong zone or mistyped plate can create a dispute even when the payment itself succeeds. Specify how staff find and correct those cases.
Reconcile both channels against the same rules
Confirm how payments become valid parking sessions and how operators search transactions by site, time, source and status. Ask finance to review sample exports and the process for refunds and disputed transactions.
A payment recorded in the parking platform and a settlement in the merchant account are different stages. Assign responsibility for investigating discrepancies and for coordinating a refund with any change in access rights.
Check outages and total operating cost
Neither channel should be described as automatically working without connectivity. Document the payment provider’s supported behaviour, any backup connection and the assistance procedure. Local access for stored credentials does not establish offline payment acceptance.
Compare equipment, installation, recurring software, processing charges and support on the same basis.
Questions
Practical questions
Can drivers pay at one channel and extend at the other?
Only if the selected systems share the required session information and support that operation. Demonstrate it with the intended site rules before advertising it. Two payment options do not by themselves create one shared session.
What should an operator check before removing a pay station?
Review who currently uses it, the alternative for visitors without a usable phone, on-site connectivity, signs and assistance. Compare the ongoing service and transaction costs, then test the replacement journey with representative visitors before removing equipment.
Does pay by phone always require an app?
No. It depends on the provider and configured workflow. Verify the actual steps before writing signs or visitor instructions.
Should every lot offer both channels?
Not necessarily. Assess visitors, transaction volume, assistance needs and the cost of maintaining each channel.
References and further reading
- PayByPhone Help Centre: How does it work? and location codes
Provider-specific examples of app, mobile-web and location selection. These examples do not establish a Lexoh integration or the options available at a particular site.
- Parking payment kiosks
Lexoh product or project reference.
- Payments and transactions
Lexoh product or project reference.
Your project
Compare payment workflows for your lot
Lexoh can review the payment model, visitor needs and reconciliation requirements before defining equipment.
Discuss the project