See it on your volume
Type how tickets reach the municipal office and how many you process. Set-fine and clerk time are yours to edit.
Participating private properties can receive a proposed share of the municipal ticket book — a cost-sharing principle that can offset their enforcement cost. The municipality decides; ParkWare cannot enforce the transfer.
| Today | With By-Law Enforcer | |
|---|---|---|
| Intake path | ||
| Clerk time on intake | ||
| Typical time until payable | ||
| Municipal platform fee | — | $0 (free tier) |
| Motorist pay (ESP-issued tickets) | ||
| Face value of that book | ||
| Municipality keeps | ||
| Proposed property share |
The bottleneck
Your by-law office is accountable for tickets issued on private property — condos, apartments, plazas, and commercial sites — but intake is often still:
- Paper ticket books and physical copies delivered to city hall
- Clerk re-keying before a ticket is payable online
- 24–48+ hours (or longer) before motorists can pay on the municipal portal
You should not have to buy a new municipal software stack to fix that.
Municipal partner — what it means
Your municipality certifies Enforcement Service Providers (ESPs) — private security companies or police, under your by-law — to issue municipal parking tickets on private property.
On the free tier, the municipality pays nothing for the software seat. Authorized ESPs fund per-property access. You get ticket management and export into your back-end — plus, on the same free layer, PayTick.ca for ticket pay and ParknPay.ca for paid municipal parking. The platform earns a processing fee on those payment lanes, not a municipal licence bill.
An issuance layer — not a second city hall
Municipal staff keep the parking system they already use. Authorized private ESPs issue from this front end. Configure your ticket codes, push that book to those officers, and the structured record still files to your back-end.
If you want those tickets payable the same day they are written — before a clerk re-keys them — the notice can point to PayTick.ca. Connect your own payment account, or ask the platform to operate it and settle to you. One pay address on the notice; a payment marks the file on your side.
PayTick is the public pay face for platform-issued tickets. It does not replace your office system.
Paid parking on the same free layer
Any municipality on this free layer can offer paid parking through ParknPay.ca — on-street, surface lots, garages, and other municipal paid spaces. Same rule as tickets: you do not buy a new stack. Motorists pay; the city keeps the parking revenue; the platform takes a processing fee (as it does on PayTick.ca).
Connect your own payment account, or ask the platform to operate it and settle to you.
ParknPay.ca is the paid-parking lane on this free municipal layer (product path). It is not a replacement for your existing office system.
How tickets reach you
Field officers may still use handwritten municipal ticket books for the motorist. What changes is the digital record — and, if you choose, a same-day pay page:
- Officer captures each issuance in Enforcer.mobi (plate, infraction, photos, penalty notice number).
- End of shift, the platform builds a structured package — spreadsheet manifest plus photo evidence per ticket.
- Your parking office receives data via email submission, or — when you adopt it — a daily export from the municipal portal in your import format.
This is not “scan paper at the counter.” Packages are built from the ESP’s platform records.
Which situation sounds like yours?
Start with digital shift-end packages
Your ESPs can submit structured manifests and photos each shift — so clerks stop re-keying from paper. No municipal software fee.
Add municipal portal export
Municipal staff pull one daily batch when you are ready — consolidated view, custom export format available.
Keep the system you already run — or export to it
Municipal staff keep their current process. Private ESPs issue on this front end; the record still exports to you. No forced rip-and-replace.
Authorize providers on one platform
Especially practical for smaller municipalities — contract enforcement capacity without hiring a full by-law team for private-property sites.
Free tier vs paid (when you are ready)
| Tier | What you get | Municipality pays |
|---|---|---|
| Free | Private-property municipal tickets · submit or export to your back-end · PayTick.ca ticket pay · ParknPay.ca paid street / lot / garage parking | No software seat — ESPs fund access; platform earns a processing fee on PayTick and ParknPay |
| Paid | Municipal-direct ticketing on your streets and lots · exemption registry | Subscription — only when you choose to expand issuance beyond the ESP layer |
ParknPay and PayTick sit on the free municipal layer. The paid tier is extra issuance capability, not a requirement to collect parking or ticket payments.
15-minute intake conversation
Tell us how tickets reach your parking office today — paper, email, or your current system. We will map the lowest-friction path for your import workflow.
municipal@parkware.caMunicipal partner inquiries · Enforcement Solutions Corp. (ParkWare)