Exige | Zelda Validation

Feature

Zelda validation

Guests submit proof. Zelda checks it against the offering before the parking benefit is applied.

The operational problem

A stamp, a code, or a cashier's word discounts parking without confirming the visit that was supposed to earn it.

What Zenith does

Operators configure validation offerings, including when an evidence image is required. Zelda uses the example image on the offering to judge what guests submit. In the guest flow, Zelda walks the person through redeeming the validation. Written rules across many businesses are the standalone Validator product at validator.exige.io.

Why it matters

The benefit should follow the proof, and the proof should be the one the operator configured.

How it fits the platform

Validations are a Zenith module. The results show up in validation analytics next to revenue.

Scan to Pay and Text to Pay

Guests pay from a phone browser. Scan a sign or text the lot — no app install.

Sessions, permits, and subscribers

Transient parking, recurring permits, and the people who hold them — one parking record.

Vision

License-plate visits from the lot, scored and matched to a session when one exists.

Enforcement

Citations, penalties, and partners — plus a field app for officers on the lot.

Premium Spaces

Sell an upgrade into a higher-value stall from the same guest checkout.

Valet

Open and close valet tickets from the lot, and run the lane from the Valet app.

Analytics

Charts, revenue, and validation results across locations — in the Zenith dashboard.

Accounting

SaaS fees, beneficiaries, transfers, destinations, and deposits for the money the platform moves.

Handheld terminal and integrations

Take payment on a terminal, register devices, and connect the systems you already run.

Team, brands, and audit

Members, location brands, and an audit log — scoped to the organization.