Validator™ | A Record Of Why The Benefit Was Granted

Feature

A record of why the benefit was granted

See which rule applied and what qualified the visit, so exceptions are not a mystery at the end of the month.

The operational problem

Operators and property teams often lack a consistent record of why a benefit was granted. Disputes become he-said stories, and lease rules are hard to stand behind.

What Validator does

Each validation and its basis is recorded: the session or transaction, the rule that ran, the benefit applied. That is operational visibility—not a promise of a named analytics or audit-trail product.

Why it matters

When someone asks why a car parked free, the answer should be in the record, not in someone’s memory of a busy Saturday.

How it fits the platform

Recording the outcome is the last step of the same loop: session or transaction, qualification rule, earned benefit, recorded result.

Verification, not the honor system

Confirm the visit that earns the benefit before parking is discounted—not a code scan, a desk stamp, or a claim at the gate.

Rules that can actually be enforced

Write the policy your property needs. Validator applies it the same way every time—layered criteria, exceptions, and stacking included.

Validation that matches the visit

A coffee stop and a dinner reservation are not the same visit. Give each business a benefit that reflects the time it actually takes.

Modernize without replacing everything

Add a verification layer to the parking and payment stack you already run. No forced rip-and-replace.

One platform for many rulebooks

Support distinct policies across tenants on a shared lot—without forcing every business into one template.

Less guesswork for staff

Frontline teams stop interpreting layered rules and arguing eligibility. The policy runs; they help customers.

Protect the parking. Reward the customer.

Give back only the parking benefit each visit earns, so customer spaces stay available and revenue does not leak one exception at a time.