QR collection and daily reconciliation for city parking and market fees
TL;DR Tallyrun gives each municipal parking lot and market stall row its own UPI QR code that pays straight into the city's bank account, then matches every rupee against expected collections each night. Municipal bodies pay a per-site fee. The pitch is simple - find out what your contractors are really collecting.
Cities collect small fees on the street, and a lot of it goes missing somewhere between the motorist and the treasury. Delhi's municipal corporation launched a QR pilot at Ramlila Maidan in October 2025 because complaints of contractors overcharging kept coming in[2]. By June 2026 it was planning a single gateway with daily reconciliation audits and penalties for operators who don't comply, though it published no figure for the loss[1].
Most smaller cities have nothing like this. Contractors bid a lump sum, collect in cash or on their own QR, and the city never sees the real footfall.
What it does, in regulatory terms: collection tracking and reconciliation software. Money moves through the city's own bank merchant account. Tallyrun never holds funds, so it should not need a payment aggregator licence. Confirm that with payments counsel.
The seed pitched a new micropayment system for city fees, and I've reframed it. UPI already handles tiny payments well, so a new wallet adds nothing. The real gap is knowing what was collected.
Each lot, stall row or toilet block gets a printed QR tied to the city's account and a site code. Attendants log entries by vehicle number or stall on a phone app, and the payer sees the official rate on screen. Every night Tallyrun matches the bank's credit file against logged entries and flags the gaps - cash-heavy shifts, entries with no payment, sites whose takings dip on certain days. For contractor-run sites, the city sees real gross collections before the next auction.
Motorists and vendors pay the same fee as before. The city pays Tallyrun a per-site monthly fee or a small share of the uplift in recorded collections, bought through GeM or a tender[5]. Revenue and parking departments are the buyers. Smart-city companies with leftover project budgets are a second route.
Delhi's move toward daily reconciliation in 2026[1] gives other cities a model to copy. Indore pairs a GIS property survey with digital payments and collected over ₹1,000 crore in municipal taxes in 2024–25, up 27.5%[3]. Councils now see digital collection as a revenue tool, not just a convenience.
No public figure exists for leakage in municipal parking or market fees, or for spending on collection software. The firmest signal is buyer behaviour, because India's largest municipal body is buying a reconciled gateway[1]. On the adjacent side, Indore's 27.5% jump in tax collection shows what digital collection plus better records can do[3]. It is a different revenue line though.
One Indian parking-tech startup sells parking software to municipalities, universities and airports, with QR and app payment[4]. eGov Foundation offers a revenue-collection module called mCollect to cities on its platform[6]. Banks give cities merchant QR codes but no matching against site activity. The gap is a cheap, site-level reconciliation tool for cities of 2–20 lakh people that run parking and markets through contractors.
| Difficulty | Moderate (45/100) |
| Starting capital | ₹45–90 L |
| Time to launch | 6–9 months |
Building the app is easy. Getting a city's bank to share a daily credit file in a usable format is not. Contractors who do nicely out of today's system will push back, sometimes openly. Government sales cycles and late payments pile on more strain.
Tallyrun should not need a payments licence, as long as money never passes through it. Get that checked first.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't use an AI flag alone to accuse an attendant or penalise a contractor. Treat it as a reason to audit, and keep the decision with city officials who check the evidence.
Want to work out the AI layer for Tallyrun? Talk to Yash →
I'd back a founder who has worked inside municipal revenue or parking operations and can stand up to contractors. If you're a pure fintech team then this is the wrong fight. Prove first, at ten sites in one city, that recorded daily collections rise at least 20% within 60 days.
Plan for roughly ₹45–90 L, covering the app, bank integrations, QR rollout at sites and a security audit.
Not if money flows straight into the city's own bank account and you never hold it. If you pool or settle funds, RBI payment aggregator rules apply, so get counsel to check your flow.
Yes, cash leakage at parking lots and markets is common in many places. Check local payment regulation and public procurement rules before you pitch.
The free Tallyrun validation kit has the line-by-line capital breakdown, the effort scoring, the payments and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for municipal officers and contractors, and 5 assumptions to test. Download the kit →
Thinking about building Tallyrun or something close to it? The make-or-break bit is getting a city's bank file and keeping contractors on board during the pilot, and I can help you plan for both. If you need a hand, you know where to find me. Talk to Yash →
For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.