Built to survive a dispute — and an audit.
Private enforcement is a category dogged by illegal-ticket headlines and license-plate-misread complaints. nfors is built so every charge is defensible by construction — gated, evidenced, and on the record from the moment it’s issued.
One engine, every jurisdiction — not hardcoded to one state.
Every zone carries a state. Grace minutes, late-fee floors, dispute and appeal windows, signage requirements, statute citations, and booting legality are all read per zone from a researched policy table covering all 50 states and DC — so a Florida lot and an Alabama lot each enforce their own rules, automatically.
- Grace minutes, late-fee floors, appeal & response windows — per state
- Signage requirements and statute citations rendered from the policy row
- Policies are researched, then upgraded to counsel-validated state by state
- Grace period
- 60 min
- Statute
- §715.075
- Appeal window
- 10 days
- Booting
- Restricted
Every charge, gated and on the record.
A hard grace gate on every charge
Issuance is blocked until the legal grace window elapses — computed as the longer of your grace and the state’s — with a server-verified clock and an immutable, statute-citing attestation (or a timed queue link) on every charge.
Signage attestation gating
A zone cannot issue a charge without a current signage attestation. Edit a state’s signage requirements and the version bumps, invalidating stale attestations after a grace window so enforcement re-attests.
Court-ready evidence packets
Any charge produces an operator-branded, compliance-redacted PDF — charge identity, vehicle, GPS/zone, the entry/exit window, statute citation, appeal terms, the full chain-of-custody timeline, and role-labeled photos — with no platform fees or DMV owner PII by construction.
DPPA-aware, audited DMV handling
Registered-owner lookups for mailing are gated and every read is written to an access audit. The recovery handoff stays defensible — and you control whether lookups run in-house or are deferred to a recovery partner.
Plate-correction audit with auto-void
A supervisor can fix an LPR misread or typo in place, with an immutable per-field audit trail. When a corrected plate turns out to match a paid permit, the charge auto-voids and the void cascades to collections and the mailing partner.
HMAC-signed webhooks & developer log
Every state change — issued, evaluated, paid, voided, disputed, corrected — fires an HMAC-signed webhook with retries, and a self-serve error log records failing field names only, never values.
Your tenant’s data, isolated by design.
A strict admin → operator → supervisor → agent hierarchy is enforced in three independent layers, with database row-level security as the source of truth — so every operator’s data is isolated and agents only ever see the zones they’re assigned.
Row-level security
RLS policies are the authoritative boundary, backed by proxy and per-page server guards.
Strict role hierarchy
Four roles, three enforcement layers that must all agree before a page renders.
Credentials in a vault
Provider secrets live in a managed vault and never round-trip to the browser.
Field-names-only logging
The API error log records which fields failed validation — never their values.
Compliance you configure — not legal advice.
nfors enforces the policies and gates, but you remain responsible for correct configuration, on-site signage, and truthful attestations. Our state policies are platform-researched and upgraded to counsel-validated jurisdiction by jurisdiction — they’re a strong default, not a substitute for your own legal counsel.
Enforce with confidence.
Start free and see how every charge carries its own grace record, evidence, and audit trail.