LPR enforcement that won’t ticket a paid parker.
Bring your own LPR cameras and push their reads into nfors. Every plate is matched against active permits — tolerant of camera misreads — and held through the legal grace window before any charge attaches, so automated enforcement stays accurate and defensible.
Automated reads, adjudicated the right way.
Bring your own cameras
nfors is camera-agnostic. Push reads from any LPR/ALPR system to a documented REST endpoint and receive HMAC-signed webhooks back — no hardware lock-in.
Permit match before any charge
Each read runs a three-tier match — exact, state-fallback, and confusable-character — against your live permits, so a camera never charges a driver who already paid.
Misread-tolerant by design
Common LPR confusions (O↔0, I↔1, B↔8, S↔5, Z↔2) are reconciled with a single-candidate safety guard, so the system never guesses between two real plates.
The grace gate applies to cameras too
An unmatched read is held in a time-released queue and can only become a charge after the state’s grace window has elapsed — measured against the parking duration.
Fix a misread, auto-void the charge
When a supervisor corrects a plate and it turns out to match a paid permit, the charge auto-voids and the void cascades to collections and the mailing partner.
Officers and cameras, one pipeline
LPR-captured and field-captured charges share the same workflow, compliance gates, payments, collections, and disputes — one audit trail, not two systems.
Reads in, decisions out.
Whether a fixed camera or an officer’s phone captured the plate, nfors reads it, matches it against live permit data aggregated from your providers, and surfaces only the vehicles that actually need enforcement.
- A confidence threshold routes uncertain reads to a human, not an automatic charge
- Permit data is aggregated from multiple providers into one match
- Every read and decision is stored for dispute and audit defensibility
Recent
Low confidence — confirm later
Common questions
Does nfors sell or operate LPR cameras?
No. nfors is camera-agnostic and bring-your-own-camera. Your LPR/ALPR system sends plate reads to the nfors API, and nfors ingests, matches, and adjudicates them. The differentiation is the permit-matching and compliance layer, not the camera hardware.
How does nfors avoid ticketing drivers who already paid?
Before any charge is issued, each read is matched against your live permits and whitelist with a three-tier, misread-tolerant match. A match returns no action. Charges are only created for unmatched plates, and only after the legal grace window has elapsed.
Is LPR enforcement real-time?
Reads you push to the API or that arrive via a provider webhook are adjudicated near-instantly. Permit data pulled from third-party providers on a polling cadence refreshes about every five minutes, so describe polled data as “near-real-time,” not instantaneous.
Which cameras and platforms are supported?
Any LPR system that can POST a plate read to a REST endpoint works. nfors also aggregates live permit data from multiple parking platforms (Level Parking, Parkmobile, and ParkLync are live today) so the safety check that protects paid parkers is well-informed.
Turn camera reads into defensible charges.
Free for 90 days, no credit card. Approval is usually same-day.