LAZ Parking: Payment &
Software Integration
Opportunity Map
This brief maps every major payment and software integration opportunity across a large-scale parking operation. For each capability it describes the business case, the technical requirements, the relevant API surface, and the competitive landscape. It is intended as a working reference for the development team evaluating a custom Jackrabbit Gateway integration for LAZ Parking.
Market Context| Metric | Figure | Note |
|---|---|---|
| Smart Parking Market (2023) | $8.5 Billion | Industry research composite |
| Smart Parking Market (2033 projected) | $48.3 Billion | ~19% CAGR |
| Revenue uplift — digital payments adoption | +15–20% | Operators reporting post-migration |
| Revenue uplift — dynamic pricing | +10–30% | AirGarage case studies, 300+ properties |
| LAZ Parking locations (approx.) | 6,000+ | Confirm exact figure with Sean |
| Potential annual payment volume (6,000 locations) | $20B+ | Internal estimate — see Section 10 |
Monthly parkers — commuters, building tenants, corporate employees — represent the highest-value, most predictable revenue segment in any parking operation. Most large operators currently manage this through a mix of manual ACH pulls, emailed invoices, and spreadsheet tracking. A purpose-built subscription billing engine replaces that entirely with automated recurring billing, access-control integration, and corporate account management.
Core Capabilities Required- Recurring card and ACH billing — automatic charge on defined billing cycle
- Failed payment retry logic with configurable retry schedule (Day 1 / Day 3 / Day 7)
- Proration engine for mid-month starts, cancellations, and rate changes
- Self-service portal — parkers manage payment method, view history, download receipts
- Corporate account billing — one invoice covers multiple employee permits
- Automated access suspension on payment failure — gate credential deactivated until resolved
- Waitlist management — automated notification and payment capture on availability
- Permit type management — monthly, weekly, overnight, flex-day, carpool, EV-reserved
| POST /permits | Create permit — associate parker, plate, space type, billing profile |
| POST /permits/{id}/payments | Capture recurring payment against permit |
| PUT /permits/{id}/access | Enable or suspend gate access credential (webhook trigger on payment failure) |
| GET /permits?account={corp_id} | Retrieve all permits under a corporate account |
| POST /permits/{id}/prorate | Calculate and apply prorated charge for mid-cycle change |
| POST /webhooks/payment.failed | Trigger access suspension and retry workflow |
| GET /invoices/{corp_id}/monthly | Generate consolidated corporate invoice with line-item detail |
Monthly parking subscription on ACH costs approximately $0.25–$0.50 flat per transaction. The same $150/month permit on a credit card costs $3.00–$4.50 in interchange (2–3%). At 6,000 locations with an average of 50 monthly parkers each (300,000 parkers total), ACH migration saves approximately $850K–$1.2M annually in processing costs on monthly permits alone. Build ACH as the default payment method with card as fallback.
Reservation-based parking commands a 15–30% price premium over walk-up transient and allows operators to yield-manage inventory the way hotels manage room inventory. A garage running 70% occupancy on walk-ups can reach 90%+ with a reservation layer. The payment integration complexity is significant — pre-authorization, variable capture, cancellation fees, and refund logic must all be handled programmatically.
Core Capabilities Required- Inventory management — available spaces by hour, zone, and type
- Pre-authorization on booking — hold card for full or partial amount, capture on arrival/exit
- Dynamic cancellation fee logic — configurable by hours-before-arrival (free >24hr, 50% 2–24hr, 100% <2hr)
- Waitlist with automated payment capture on availability opening
- Oversell logic with configurable buffer and automated refund on displacement
- QR code or license-plate confirmation at entry — no ticket required
- Extension payments — parker extends stay mid-session, additional charge captured automatically
- Corporate pre-purchase — companies buy block reservations billed monthly
| GET /inventory?location={id}&date={dt} | Real-time space availability by location, date, and zone |
| POST /reservations | Create reservation — capture card pre-auth, issue confirmation and QR |
| POST /reservations/{id}/extend | Extend reservation — calculate delta, capture additional payment |
| DELETE /reservations/{id} | Cancel — apply cancellation fee logic, process refund if applicable |
| POST /reservations/{id}/arrive | Confirm arrival — LPR or QR scan triggers, release pre-auth hold |
| POST /reservations/{id}/depart | Departure capture — final charge based on actual duration vs. reserved |
| GET /reservations/corporate/{corp_id} | Corporate reservation history for monthly invoice generation |
Dynamic pricing maintains optimal occupancy rates of 85–95% and case studies consistently show 10–30% revenue increases within months of implementation. The critical technical dependency is a payment gateway that can execute real-time rate changes via API without hardware reprogramming at the gate. Most operators currently cannot do this — rates are hard-coded into kiosk firmware.
Pricing Models to Support| Model | Description | Trigger |
|---|---|---|
| Time-of-Day | Peak/off-peak rate tiers by hour | Schedule-based |
| Occupancy-Based | Rate rises as garage fills (+$2 per 10% occupancy above 80%) | Real-time sensor feed |
| Event Surge | Elevated rate for defined radius/time window around events | Event calendar API |
| Demand Forecast | AI-predicted rate based on historical + contextual signals | ML model output |
| Competitive | Rate adjusts to stay within defined band of competitor pricing | Competitor price feed |
| Long-Stay Discount | Rate reduction for stays exceeding defined duration threshold | Session duration trigger |
| PUT /locations/{id}/rates | Push new rate schedule — takes effect immediately at gate |
| GET /locations/{id}/occupancy | Real-time occupancy percentage (requires sensor integration) |
| POST /pricing/rules | Create pricing rule — define trigger conditions and rate output |
| GET /pricing/events?location={id} | Retrieve upcoming events with pricing impact flag |
| POST /sessions/{id}/rate-change | Handle mid-session rate change — record entry rate, recalculate on exit |
| GET /pricing/audit?location={id}&date={dt} | Audit trail of all rate changes for reconciliation |
The payment gateway must accept rate updates via API and apply them to new sessions within seconds, without requiring a gate reboot or kiosk firmware update. This is the architectural gap in most current integrations. The Jackrabbit gateway must be designed API-first with a real-time rate injection endpoint from day one.
LPR is becoming the dominant access and billing mechanism in modern garages. A plate-linked payment profile that works across every LAZ location creates a frictionless experience that no competitor currently offers at this scale — and creates strong switching costs because the parker's payment method is embedded in their plate registration.
Core Capabilities Required- Plate registration — parker registers plate + card/ACH once; all future sessions billed automatically
- Cross-location plate recognition — registered plate works at any LAZ facility nationwide
- Touchless exit — LPR reads plate, calculates session, charges on file, raises gate. Zero hardware interaction
- Corporate fleet billing — company registers vehicle fleet; all parking auto-billed to corporate account
- Enforcement and citation — LPR-flagged unauthorized vehicles generate digital citation with online payment link
- Permit validation — LPR confirms monthly permit holders without any parker action required
- Audit trail — every LPR read logged with timestamp, location, session ID, and payment outcome
| POST /plates/register | Register plate — link to parker profile and payment method |
| POST /lpr/entry | Entry event — LPR camera posts plate read, system creates session, logs entry time |
| POST /lpr/exit | Exit event — LPR posts plate, system calculates duration, charges on-file card/ACH |
| GET /plates/{plate}/profile | Look up parker profile, payment method, permit status, and visit history |
| POST /lpr/citation | Issue digital citation — LPR flags unauthorized plate, system sends payment link via SMS |
| POST /corporate/fleet | Register corporate fleet — associate multiple plates to one billing account |
| GET /lpr/audit?location={id} | Full LPR read log for reconciliation and dispute resolution |
Validation is a significant and largely manual revenue stream for most operators. Merchants in adjacent buildings pay to subsidize or cover parker costs to drive foot traffic. Currently managed through paper stamps or QR codes requiring manual redemption. A digital validation platform automates the entire workflow and turns validation into a fee-generating B2B service for LAZ.
Core Capabilities Required- Merchant portal — business purchases validation credits via online portal, no phone call required
- Digital validation delivery — parker receives validation via SMS link or QR from merchant at POS
- Automatic redemption — validation applied at exit gate automatically against parking charge
- Partial validation support — merchant covers $X of a $Y session; parker pays remainder
- Real-time credit balance — merchant sees remaining validation credit balance in portal
- Monthly invoicing — merchant billed at month end with full itemized report
- Platform fee layer — LAZ charges a service margin on validation credits
- Multi-merchant stacking — multiple validations applicable to single session with defined priority rules
| POST /merchants/{id}/credits | Purchase validation credits — charge merchant payment method |
| POST /validations/issue | Issue validation to parker — generate QR or SMS link |
| POST /sessions/{id}/validate | Apply validation to session on exit — calculate net charge to parker |
| GET /merchants/{id}/usage | Validation usage report — by date, location, and individual session |
| GET /merchants/{id}/balance | Real-time remaining credit balance |
| POST /invoices/merchant/generate | Generate monthly merchant invoice with full line-item detail |
LAZ manages parking for major venues across the country — arenas, stadiums, theaters, convention centers. Event parking has uniquely complex payment requirements: pre-sale inventory, surge pricing, same-day reconciliation, and post-event refund management. The financial services complexity is where a custom integration creates the most differentiation versus a generic processor.
Core Capabilities Required- Pre-sale inventory — customers buy guaranteed space in advance; revenue captured regardless of weather or cancellation
- Tiered event pricing — premium spaces closest to venue at 2–3× standard rates
- Bundle ticketing — parking + event ticket in single checkout with payment split at transaction level
- Surge pricing windows — elevated rates for defined hours around event start and end
- No-show handling — pre-sold space released at T-minus threshold, re-sold at walk-up rate
- Post-event reconciliation — automated settlement reporting by event, venue, and space tier
- Refund automation — event cancellation triggers mass refund workflow with configurable retention fees
- Operator dashboard — real-time occupancy, revenue, and pre-sale fill rate by event and zone
| POST /events | Create event — define location, inventory blocks, pricing tiers, and surge windows |
| GET /events/{id}/inventory | Real-time available inventory by tier |
| POST /events/{id}/reservations | Pre-sell space — capture payment, issue confirmation |
| POST /events/{id}/cancel | Cancel event — trigger mass refund workflow, apply retention policy |
| GET /events/{id}/settlement | Post-event settlement report — revenue by tier, refunds, net |
| POST /events/{id}/release | Release unsold pre-inventory to walk-up at T-minus threshold |
| POST /bundles/checkout | Bundled ticket + parking purchase — split payment allocation to correct accounts |
In December 2025, LAZ made a strategic investment in Epic Charging to deploy 50,000 Level 2 EV charging stations across its real estate portfolio. This creates an immediate integration opportunity — a unified billing session that captures both parking and charging in a single payment, allocated correctly in back-end accounting. Currently these are almost always two separate transactions on two separate systems.
- Unified session billing — one payment captures parking fee + charging cost, allocated to separate revenue lines
- Charging subscription tiers — monthly unlimited charging bundled with monthly parking permit
- Energy cost pass-through — bill actual kWh cost to parker at per-kWh rate plus service margin
- Corporate charging accounts — employer reimburses employee charging; automated expense reporting
- Real-time charging status — parker sees charging progress and cost accumulation in LAZ app
- OCPP protocol integration — open standard for communicating with Epic charger hardware (OCPP 1.6 / 2.0)
- Idle fee billing — charge for occupying charging space without active charging after session complete
- Fleet charging — EV fleet vehicles auto-billed to fleet account based on plate recognition
| POST /sessions/unified/start | Start unified parking + charging session — one auth covers both |
| GET /chargers/{id}/status | Real-time charger status, energy delivery, and estimated completion |
| PUT /sessions/{id}/charging | Update session with charging data — kWh delivered, current rate |
| POST /sessions/{id}/close | Close session — calculate parking fee + charging fee, capture single payment |
| POST /charging/subscriptions | Create charging subscription — link to existing parking permit |
| GET /charging/corporate/{id}/report | Corporate charging usage report for expense reimbursement |
| POST /charging/idle-fee | Apply idle fee when vehicle occupies charger post-session |
Major employers in every city LAZ operates are paying for employee parking through expense reports, manual invoicing, or individual reimbursement. A corporate account product turns LAZ into a B2B payments provider for corporate mobility — a fundamentally higher-margin revenue stream than transient consumer parking. This is the segment where Fiserv has the most strategic interest given their existing B2B commercial payments infrastructure.
Core Capabilities Required- Corporate enrollment — company sets up account, defines approved employees/vehicles and spending rules
- Virtual parking cards — issue virtual credentials to approved employees linked to corporate billing account
- Plate-linked profiles — employee registers plate; all parking at any LAZ location auto-billed to employer
- Spending rules — per-employee daily limit, approved locations, permitted hours, vehicle type restrictions
- Consolidated monthly invoicing — one invoice covers all employees with itemized per-employee, per-day detail
- Expense system integration — API feed to Concur, SAP, or custom HR/expense platforms
- Real-time spend monitoring — corporate admin dashboard showing live spend vs. budget by employee and location
- Volume-based pricing — contracted rate for high-volume corporate accounts (500+ employees)
| POST /corporate/accounts | Create corporate account — define billing, admin users, and policy rules |
| POST /corporate/{id}/employees | Add employee — link to account, set spending rules and approved plates |
| GET /corporate/{id}/activity | Real-time transaction feed across all employees and locations |
| POST /corporate/{id}/invoice | Generate monthly invoice — consolidate all employee sessions |
| POST /corporate/{id}/export | Export to Concur/SAP format for expense integration |
| PUT /corporate/{id}/rules | Update spending policy — location restrictions, daily limits, hours |
| GET /corporate/rates/{id} | Retrieve contracted rate for corporate account at defined locations |
A loyalty and stored-value product that works across all LAZ locations is a direct switching-cost mechanism for consumer parkers. A parker who has loaded $200 onto a LAZ wallet or earned points toward free parking has a tangible financial reason not to use a competitor garage. At LAZ's scale, the network effect of a multi-location loyalty program is something no single-location or regional operator can replicate.
Core Capabilities Required- Stored value wallet — parker loads funds via ACH or card; wallet charged on exit across any LAZ location
- Auto-reload — configurable trigger (e.g., reload $100 when balance falls below $20)
- Points accrual — earn points per dollar spent with multipliers for monthly parkers, off-peak, EV
- Redemption — points redeemable for free parking, reserved space upgrades, or EV charging credit
- Loyalty tiers — Silver/Gold/Platinum with progressive benefits (guaranteed space, priority access, discounts)
- Corporate loyalty — employer earns volume-based rebate credits; employees earn personal points on corporate-paid parking
- Referral program — parkers earn points for referring new registered users; tracked via unique referral code
- Expiry management — configurable point expiry with advance notification to reduce liability
| POST /wallets | Create wallet — link to parker profile, set auto-reload rules |
| POST /wallets/{id}/load | Load funds — ACH or card, return new balance |
| POST /sessions/{id}/wallet-charge | Charge session to wallet — deduct balance, return updated total |
| POST /loyalty/earn | Award points — triggered on session close with multiplier logic |
| POST /loyalty/redeem | Redeem points — apply to session or purchase reward |
| GET /loyalty/{parker_id}/balance | Current points balance and tier status |
| GET /loyalty/corporate/{id}/rebate | Corporate rebate calculation for current billing period |
This is the least visible but most operationally impactful capability for an operator at LAZ's scale. A payment integration that produces location-level P&Ls, operator-level settlement, and corporate consolidation automatically eliminates what is currently a massive manual reconciliation burden across thousands of locations. For a PE-backed operator with covenant reporting and investor obligations, the accuracy and timeliness of financial data has direct economic value.
Core Capabilities Required- Location-level P&L — daily net revenue by location: transient, monthly, event, EV, validation as separate lines
- Real-time settlement — funds settled to location or operator accounts on configurable schedule (daily, T+1, T+2)
- Multi-party split settlement — revenue automatically split between LAZ and property owner for managed locations
- Automated bank reconciliation — transaction-level match between gateway records and bank statement
- Tax reporting — sales tax calculation and reporting by jurisdiction (varies by state/municipality for parking)
- Revenue leakage detection — exception reporting flags sessions where gate opened but no payment captured
- Operator dashboard — corporate-level view across all locations with drill-down to individual session
- Accounting system integration — API feed to QuickBooks, NetSuite, SAP for automated journal entry
- Audit trail — immutable log of every transaction, rate change, refund, and access event for SOC 2 compliance
| GET /reports/settlement?location={id}&date={dt} | Daily settlement report — all sessions, fees, refunds, net |
| GET /reports/pnl?location={id}&period={p} | P&L by location and revenue category for defined period |
| POST /settlement/split | Execute multi-party split — allocate revenue between LAZ and property owner |
| GET /reports/leakage?location={id} | Revenue leakage report — gate events with no corresponding payment |
| GET /reports/tax?jurisdiction={id}&period={p} | Tax liability report by jurisdiction and period |
| POST /accounting/export | Export to QuickBooks, NetSuite, or custom GL format |
| GET /audit/transactions?session={id} | Full audit trail for specific session — all events and payments |
| GET /reports/corporate/portfolio | Enterprise dashboard — all locations, all revenue streams, consolidated |
A garage doing 500 transactions/day at $18 average = $9,000/day. Across 6,000 locations = $54M/day in payment volume = ~$20B annually. Net payment economics at 50 bps = $100M+ annual revenue from the payment layer alone, independent of the residual income from merchant processing. This is the number Fiserv is underwriting when they evaluate a platform acquisition.
| Platform | Strength | Weakness | Relevant Sections |
|---|---|---|---|
| FlashParking | Hardware integration, access control, LPR | Limited third-party API integrations | 4, 3 |
| T2 Systems Flex | Permit management, enforcement | Primarily universities/municipalities, not commercial scale | 1, 4 |
| netPark | Integrated PARCS + payments, monthly billing | Limited corporate account features | 1, 2 |
| ParkMobile | Consumer mobile app, reservations | No operator-native payment layer | 2, 9 |
| SpotHero / ParkWhiz | Consumer reservation marketplace | No operator integration — competitive to LAZ | 2 |
| HONK | Mobile-first, strong analytics, dynamic pricing | Smaller operator focus | 3, 2 |
| AirGarage | Dynamic pricing, gateless, NOI focus | Newer entrant, limited enterprise scale | 3 |
| Parkify | AI-powered dynamic pricing | Pricing only — no full payment integration | 3 |
| Epic Charging (LAZ investment) | EV CPMS, payment automation | Charging only — no parking integration | 7 |
| Jackrabbit Gateway (proposed) | Unified all-capability payment layer, custom LAZ fit | Does not yet exist — this is what we build | All sections |
API-First, Hardware-Agnostic. The Jackrabbit Gateway for LAZ should sit between LAZ's existing PARCS hardware and the payment networks without requiring hardware replacement. It integrates with existing gates, kiosks, and LPR cameras via OSDP or proprietary SDK. All business logic lives in the platform layer — not in the hardware. This is the architecture that creates switching costs.
Key integration standards: OSDP v2 (access control hardware) | OCPP 1.6/2.0 (EV chargers) | ISO 8583 / EMV (payment networks) | REST/JSON APIs for all business logic | Webhooks for real-time event propagation to LAZ BI platform
| Priority | Capability | Rationale | Complexity |
|---|---|---|---|
| P0 — Immediate | Monthly permit billing + ACH | Highest ROI, replaces manual process, ACH economics | Medium |
| P0 — Immediate | LPR-linked payment profiles | Core switching cost mechanism, enables all other features | Medium-High |
| P1 — Phase 1 | Dynamic pricing engine | 10–30% revenue uplift, API-first design enables all rate logic | Medium |
| P1 — Phase 1 | Corporate account billing | B2B revenue stream, Fiserv strategic interest | Medium |
| P1 — Phase 1 | Reconciliation + reporting | Required for LAZ financial operations and investor reporting | Medium |
| P2 — Phase 2 | Advance reservation | Revenue uplift, requires inventory management layer | High |
| P2 — Phase 2 | EV unified billing | Leverages Epic Charging investment already made by LAZ | Medium-High |
| P2 — Phase 2 | Validation platform | B2B product, incremental revenue | Low-Medium |
| P3 — Phase 3 | Event parking pre-sale | Venue-specific, high complexity, high upside | High |
| P3 — Phase 3 | Loyalty + stored value | Consumer switching costs, long-term retention | High |