Validations
Validations your tenants run themselves —
and abusers can't game.
and abusers can't game.
Give every tenant a branded self-service portal. Set time limits and usage caps per tenant. And because Mitte sits on the payment layer, you can do what no other validation tool can: backdate to arrival, extend a stay, or refund and validate — across every payment app you use.
app.joinmitte.com/tenant-management/tenants
01 — Problem → Shift
Every leak a stamp leaves — closed.
Validation tools bolt a code beside your payment systems. Mitte puts validation on the payment itself. Leak by leak, here's the difference:
The leak
The copied validation QR
One tenant's code hits a WhatsApp group and half the neighborhood parks free. Your tool finds out at month-end — if at all.
Mitte's answer →
QR codes you can kill
Every validation is tracked per tenant, per use. Leaked code? Regenerate it in one click — the copy dies instantly.
The leak
The citation gap
Parks at 2:00, validated at 3:15. Tools that can't see the LPR arrival start it at 3:15 — the gap becomes a wrongful citation.
Mitte's answer →
Backdated to arrival
Mitte reads the LPR arrival and applies the validation from the moment the car parked. The gap — and its disputes — disappears.
The leak
The double-payment dead end
The customer already paid on their app. The tenant validates. Eat the charge? Refund by hand? Tools outside the payment have no answer.
Mitte's answer →
Extend or refund
Extend the stay on top of what they paid, or refund it and apply the validation. Clean for the customer, clean for your books.
The leak
The blind ledger
Who validated how much, for whom, this month? Scattered across stamps, plate lists and five vendor portals — you can't bill what you can't see.
Mitte's answer →
One system, one ledger
Every validation across every payment vendor lands on a single ledger — bill each tenant for exactly what they used.
02 — See it live
We didn't build a better stamp. We built validation into the payment.
Because Mitte sits on your payment apps and LPR, one validation system spans every vendor — and a leaked code dies the instant you regenerate it.
One validation system across every payment app you use
SpotHero
ParkWhiz
Honk
GoPass
FlyPass
T2
Blinkay
Ballparc
Innova
+ more
03 — The loop
Two sides of one system.
You configure the program once. The driver uses it in seconds. The rest of this page walks both sides — here's the whole loop in three moves.
You configure it
Add each tenant and set the rules once: validation types, time limits, monthly caps, branded portal.
The driver validates
On their phone via QR, or the tenant's tablet: plate, pick a validation, done. Ten seconds, no training.
Mitte applies it everywhere
The validation lands on the real session — whichever payment app or gate — on one ledger you can bill from.
04 — For the operator
Configure the whole program from one screen.
This is move one. Set what a validation can include, watch every one on a single ledger, brand each tenant's portal, and let known plates through automatically — all from the same place.
05 — For the visitor
For the driver, it's ten seconds.
Move two. They scan the QR on their phone — or use the tenant's tablet — enter a plate, pick a validation, and they're covered. Then a link lets them track time and extend.
Live demo
The visitor validates themselves — scan, plate, done
After validating — they track time and extend from a link
06 — Every case
Give time, or give money back.
A validation is either free parking (time) or money back (a refund on what they already paid). Mitte reads the session and applies it the right way — every case.
Free parking — give time
Money back — refund
Case 1 - Paid within the period
Money back
Arrived at 12:00, paid for 2 hours. Validates at 1:00 with a 2-hour validation — the paid period is covered.
$4.00 refunded by SpotHero
Case 2 - No paid parking
Free parking
Arrived at 12:00 with nothing purchased. A 2-hour validation covers the whole stay at no cost.
2 free hours - covered 12:00 to 2:00 PM
Case 3 - Plate not found
Free parking
The plate isn't in the system yet. The visitor confirms it's correct and the validation applies from that moment.
Applied from now - covered from validation time
Case 4 - Partly uncovered
Partial
A 30-minute validation on a longer stay. The rest stays uncovered — the visitor is told clearly.
Covered to 12:30 PM - enforcement may apply after
07 — One real day
A Saturday at Riverside Commons.
A mixed-use property with 40+ tenants and three payment apps. Here's one validated stay, end to end.
2:04 PM
Customer parks
The LPR camera reads plate GTR 4088 at the gate.
3:15 PM
Café validates
Copper Kettle staff scan the ticket in their portal — 10 seconds, no phone call.
INSTANTLY
Backdated to arrival
Mitte applies it from 2:04 PM — the 71-minute gap never becomes a citation.
SAME SECOND
Lands everywhere
The validation hits the live session — whichever of the three payment apps the driver used.
MONTH-END
Billed exactly
Every validation is on one ledger — the property bills Copper Kettle for exactly what they used.
Proof
Running today, at scale.
300+
tenants validate through Mitte
50+
locations
500k+
parking transactions / month, in 5 countries
The comparison
Everything a validation tool does — plus the payment layer it can't reach.
Other tools register plates. Mitte builds validation into the payment itself. Where it counts:
Guest validations & virtual permits
Validation-only tool
Mitte
Real-time plate push to LPR enforcement
Validation-only tool
Mitte
Backdate to camera-verified arrival
Closes the citation gap
Validation-only tool
—
Mitte
Validate a session the driver already paid
Stacks on the paid amount — no second transaction
Validation-only tool
—
Mitte
Refund the paid amount and apply the validation
Validation-only tool
Roadmap
Mitte
Reminders that touch the payment
Driver pays or extends from the phone
Validation-only tool
Reminders only
Mitte
"The current workaround is clunky, especially in multi-vendor environments… actively being explored."
— A validation-only tool's own product roadmap, on validating already-paid sessions.
Their roadmap is our shipped product.
Objections
The questions operators actually ask.
"We already use a validation tool."
Ask it three questions: Does it know when the car actually arrived? Can it touch what the customer already paid — extend or refund? Can it kill a leaked code instantly? If not, you have a digital stamp. Mitte is built on the payment and LPR layer — a difference in kind, not degree.
"We already validate through our payment app."
That works for one app. The moment you accept two or more vendors — or customers pre-pay on any of them — per-vendor validation breaks: codes don't cross apps, and paid sessions can't be validated without the clunky refund dance. Mitte validates above the vendors.
"Our tenants won't learn a new system."
There's nothing to learn. Each tenant gets a branded portal; staff scan and go. If they can use a phone camera, they're trained.
"What does it cost?"
Validations start at $99 per location/month; Advanced Tenant Management (validations + permits) is $199. No per-validation transaction fees — a busy tenant month costs the same as a quiet one.
"What if it doesn't work for our property?"
That's what the pilot is for: 60 days, all features, no cost. You keep the data; we take the risk.
Every stamped ticket is a small leak. Add them up.
Run validations the controlled way for 60 days — free, on your existing vendors and hardware, live in days.
No setup fees · Works with your current payment apps · You keep the data