- 09:00Operator console
StreetPortland Crescent · Manchester
TariffGBP 2.00 / hour · max 4 h
- 14:30
Vehicle
Session
- 14:30
Payment
Status
- 14:48
Check
- 15:20
Extension
- 18:00
Report
Platform
One record
behind every parking stay.
IPark is built around a single parking record that every app reads and writes. Rules, payments, checks and reports stay in step, across streets, operators and countries.
One shared parking record
Every team, every app,
working from the same record.
A parking stay is a single record in IPark. The operator’s rules, the driver’s payment, the inspector’s check and the evening report all read and write the same one, so nobody works from an outdated copy.
Follow one stay through the day
- 3connected apps on one record
- 5languages, right-to-left included
- 4import formats for existing street data
- 1set of rules per country: currency, VAT, grace period
What each team gets
Streets, zones and tariffs
Map the streets you manage and attach the rules drivers pay by.
- Routes or areas with automatic road correction
- Tariff and maximum stay per zone or street
- Import from CSV, Excel, XML or GeoJSON
Park, pay and extend
A clear price before paying and a reminder before the time runs out.
- Street detected by GPS or found by search
- Extend remotely, up to the maximum stay
- Garage shared by QR, EV chargers nearby
Plate checks with evidence
The answer first, then the paperwork, recorded on the spot.
- Camera plate recognition or manual entry
- Photos stamped with time and GPS position
- Fines and appeals followed to a decision
Payments by country
Drivers only see the payment methods offered where they park.
- Cards, Apple Pay and Google Pay through Stripe
- Local gateways and wallets where enabled
- Currency, VAT and payouts per operator
Roles and geographic scope
Each person works only where they are responsible.
- Platform, client, inspector and custom roles
- Access limited to a country, operator or zone
- Messaging and an audit log of every change
Reports you can trust
Activity and revenue that always lead back to the source records.
- Sessions, revenue and fines by zone
- From any figure to the record behind it
- Exports for finance and planning
Illustrative day using the demo data from the previews above.
Fine alerts
A fine reaches the owner,
not everyone with the plate.
Anyone can type a plate into an app. So IPark only sends a fine alert to the person who has proved the car is theirs, and to the people they choose to tell.
How a driver becomes the verified owner
- Add the car
The driver adds the plate to their garage in the app, as they do today.
- Prove it once
They send a photo of the registration certificate with its number and the keeper’s name.
- Staff check it
The operator compares the certificate with the plate in the console, then approves it or says what is missing.
- Share if they want
The owner can pass on fine alerts by QR code to family or other drivers of the car, up to ten people.
Who hears about a fine on this car
- The verified ownerAn alert in the app. They can pay or dispute the fine.
- People the owner shares withAn alert in the app. They can view the fine, not pay or dispute it.
- Anyone else who saved this plateNothing. They are not told and cannot see the fine.
- A car with no verified ownerThe paper notice left on the car, as always.
Example plate.
Private by design
- The certificate is seen only by the staff who review it.
- People who get shared alerts see the owner’s first name, never the document.
- Each plate has one verified owner. When a car is sold, approving the new owner ends the old one.
- The owner can remove anyone, and anyone can stop their alerts, at any time.
In the operator console
A review queue shows each certificate next to the plate, the name on the account and the car’s earlier owners. Every approval, rejection and revocation is kept in the audit log, and each fine shows who was alerted.
Built for real operations
Ready for many streets,
operators and countries.
Many countries
Each country has its own currency, tax, grace periods and payment providers.
Many operators
Operators share one platform, and each works only with its own zones and teams.
Roles and scopes
Platform admins, operator staff and inspectors get the access their role needs, in the areas they manage.
Payments confirmed first
A session starts only after the payment provider has confirmed the payment on the server.
Private by design
Registration certificates are seen only by the staff who review them, and fine alerts reach verified owners only.
An audit log
Sensitive actions such as approvals and revocations are recorded with who did them and when.
Questions & answers
Common questions
about this part of IPark.
Getting to know IPark? Start here.
All questionsDoes IPark work across several cities or countries?
Yes. One platform can serve several countries, operators and zones, each with its own currency, tax and parking rules. Roles and geographic scopes keep every team member focused on the areas they manage.
Which payment methods are supported?
Payment providers are enabled per country: Stripe for cards and wallets such as Apple Pay and Google Pay, alongside local gateways, mobile wallets, bank transfer or cash where the operator offers them. Drivers only see the methods available where they park.
Who is told when a car gets a fine?
Only the car’s verified owner, plus anyone they chose to share fine alerts with, gets an alert in the app. Saving a plate in a garage is not enough. If nobody has proved they own the car, the driver finds out from the paper notice left on it.
How does a driver prove they own a car?
From the car in their garage, they send a photo of the registration certificate with its number and the keeper’s name. Operator staff check it in the console and approve it or explain what is missing. Each plate can have only one verified owner.
Make your parking network work together.
See the platform with your zones, teams and operating requirements in mind.