Permits, passes, payments and gates in the same console.
The back office of a parking program is usually four products and a spreadsheet. In Parkeze, a permit creates the right to park, a payment has one record from checkout to settlement, and a gate checks the same rights an officer does.
01
What the back office runs
Permits
A branded storefront, applications with a full-screen approval queue, renewals, grace periods, waitlists and address rules.
Guest passes and validations
Permit holders send guest passes. Businesses validate their customers inside the city's or campus's program.
Reservations
Book a space from the web, a kiosk or Microsoft Outlook, with the calendar and the lot always in agreement.
Payments
Every channel on one payment record: checkout, settlement, refunds and disputes. Guest checkout with no account.
Access and gates
Lanes, credentials and every passage from any gate vendor, with allow and deny lists and a manual open that is logged like any other.
Fleets and businesses
Fleets, rental companies and employers get their own accounts, their own people and one invoice.
02
One payment record, checkout to settlement
Parkeze connects to your processor rather than standing between you and it. The processor hosts the card form and settles to you. Each payment carries its refunds, disputes and the session, permit or citation it paid for.
| Channels | App, web, QR, text, phone |
| In person | Cashier stations |
| Wallets | Apple Pay, Google Pay |
| Processors | Stripe, Fiserv, + |
| Refunds | Full and partial |
| Disputes | Tracked to outcome |
| Permits | Apply, approve, renew |
| Gates | Any vendor |
03