Citizen Observation 37 of 777 | NHAI Local Pass | The Pass Is Visible. Can the Journeys Be Visible Too?

 Published on 27^th August 2026

A Local Pass is meant for repeated journeys. Can the journeys also be visible in the MIS?

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

 

Dear NHAI Tech Team,

At the outset hearty congrats for sharing a wide range of MIS on the vehicle’s movement on our country’s highways @ https://ihmcl.co.in/etc-transaction-reports/

The Starting Point

A Local Pass is meant for people who regularly use a particular toll plaza.

It is a very practical idea:

Pay once. Travel repeatedly.

The National Highways ecosystem already makes a substantial amount of ETC information publicly available through MIS reports.

But while looking through the published reports, one small question came to mind:

We can see the toll transactions. Can we also see how many journeys are being made through Local Passes?

Not the identity of the vehicle.

Not individual journeys.

Just aggregate Local Pass trips.

That could add another useful layer to the public picture of highway usage.

 

The Prospective Audience

This could matter to:

A daily commuter in Alwar.

A student travelling regularly between Mysuru and home.

A small-business owner in Siliguri.

A highway user in Anand.

A researcher studying mobility patterns from Durgapur.

A journalist in Nanded.

A family making frequent journeys around Madurai.

Different roads.
Different reasons for travelling.

One common question:

How much of the traffic is actually travelling through Local Passes?

 

Act I — The Missing Slice

The MIS already tells us a lot.

Perhaps Local Pass Trips could become one more visible slice of that picture.

The pass is visible.
Could its usage be visible too? Nothing More – Nothing Less

Act II — A Pass Is Not a Trip

A Local Pass tells us that a vehicle has access to repeated travel through a particular toll plaza.

But the pass itself doesn't tell us how much it is being used.

Consider a simple public MIS:

Local Passes Issued
↓
Local Pass Trips
↓
Toll Plaza
↓
Month

The exact format, definitions and reporting methodology can remain with the relevant authorities.

The citizen observation is much simpler:

Could the number of Local Pass trips be published as an aggregate?

 

Act III — One More Layer of Visibility

The existing ETC reports already provide a useful picture of highway transactions.

Adding Local Pass trips could help distinguish between:

overall ETC activity

and

repeated local usage through the Local Pass facility.

That could make the public data more meaningful for:

Mobility → Planning → Research → Public understanding

No individual vehicle details.

No personal information.

No individual journey tracking.

Just the aggregate number of journeys.

A small addition to an existing MIS could create a new window into how highways are actually being used.

Act IV — Let the Journeys Count

A Local Pass is created for repeated use.

So perhaps the public MIS could show not only how many passes exist, but also how many trips they enable.

For example:

Local Pass
→ Passes issued
→ Trips made
→ Toll plaza
→ Month

The numbers could help reveal patterns of local mobility without revealing any individual vehicle or traveller.

The intention is not to prescribe a new reporting architecture.

It is simply to ask:

Could Local Pass Trips become another visible part of the existing ETC MIS?

---

The First Line on the Whiteboard

The Local Pass is visible. Let the journeys made through it be visible too.

---

A Citizen Observation

From Alwar to Anand.

From Siliguri to Nanded.

From Mysuru to Madurai.

Thousands of people may make the same short highway journey again and again.

The Local Pass recognises that pattern.

Could the public MIS recognise it too?

Not who travelled.

Not where an individual travelled.

Just:

How many Local Pass trips happened?

A small number.

A useful number.

A number that could help us understand the everyday movement taking place on India's highways.

 

Closing Thought

The toll transaction tells us that a payment happened.

The Local Pass tells us that repeated travel was expected.

The trip count could tell us how much that facility was actually used.

Pass → Trip → Pattern → Understanding

Perhaps better highway statistics do not need more personal data.

They may simply need one more useful number.

---

April 11 — Digital Transactions Day

A highway journey may be physical.

But the payment journey is digital.

Pass → Travel → Pay → Record → Learn

Perhaps the better digital journey is not merely one that completes the payment.

It is one where the right aggregate story can also be understood.

The Joy of Digital Transactions.

---

Disclaimer

This Citizen Observation is based on publicly available ETC/MIS information and is intended as a citizen observation.

It does not seek individual vehicle, traveller or transaction-level information.

The suggested Local Pass Trips MIS is illustrative.

Definitions, data treatment, methodology and publication format would naturally remain matters for the relevant institutions and domain experts.

 

The Joy of Digital Transactions

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru
Advocating Digital Transactions Day (April 11)

Author’s Blogs

https://prashantrandomthoughts.blogspot.com
https://prashantnepayments.blogspot.com
https://innovationinbanking.blogspot.com

 

Citizen Observation 36 of 777 | UPI Statistics | The Numbers Are Public. Can the Journey Inside the Numbers Be Visible?

 Published on 26^th August 2026

UPI numbers tell us how big the ecosystem has become. Can they also show us how those transactions are travelling?

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

 

The Starting Point

Dear NPCI Team,

Thank you for making UPI statistics publicly accessible.

The numbers tell a remarkable story of scale.

But while looking at the UPI Product Statistics, I wondered:

Can the numbers also tell us a little more about what is happening inside UPI?

Today, UPI is not just one payment journey.

There are newer journeys such as UPI Lite and UPI LiteX, alongside the wider UPI ecosystem.

Yet the headline UPI numbers primarily tell us the overall volume and value.

That made me pause:

How much of that journey is actually travelling through UPI Lite or UPI LiteX?

Not because the numbers are absent.

Perhaps one more layer of granularity could make the existing numbers more useful.

 

The Prospective Audience

This could matter to:

A researcher in Dharwad.

A journalist in Aizawl.

A student in Tinsukia.

A small merchant in Balasore.

A digital-finance learner in Kottayam.

A shopkeeper in Beed.

A public-policy student in Gangtok.

A family business in Kasaragod.

A citizen following India's digital-payment journey from Port Blair.

And, which part of India are you right now?

Different places.
Different users.
Different payment journeys.

One common interest:

What exactly is happening inside the UPI numbers?

The numbers are already public.

Perhaps the next question is:

Can the composition of those numbers become easier to see too?

 

Act I — Inside the Number

The UPI headline number tells us how much happened.

A little more granularity could help us understand how it happened.

That is the small observation behind CO36.

 

Act II — One Number. More Than One Story.

A headline UPI number can tell us:

How many transactions happened.
What their value was.

That is important.

But imagine seeing a little more:

Total UPI

↳ UPI Lite
↳ UPI LiteX
↳ Other UPI journeys

Not as separate reports.

Not as another dashboard.

Within the existing UPI statistics.

The numbers could then begin answering two different questions:

How big is UPI?

and

How are the different UPI journeys contributing to that number?

 

Act III — A Small Addition to a Big Picture

The request is not for a new measurement framework.

The existing UPI statistics already provide a valuable public window into India's digital-payment journey.

Perhaps one additional layer could make that window clearer:

Total → Journey → Volume → Value

For example, if UPI Lite and UPI LiteX were separately identifiable within the appropriate UPI statistics, a reader could begin to see their relative contribution to the larger UPI picture.

The methodology, definitions, treatment of transactions and reporting format would naturally remain for the relevant institutions to determine.

The observation is simply:

Could the existing UPI numbers show a little more of what is inside them?

That would turn a number of scale into a number that also tells a story.

Act IV — From Scale to Composition

UPI has given India something remarkable:

A public window into the scale of digital payments.

Perhaps the next step is not simply to publish more numbers.

Perhaps it is to make the existing numbers tell a little more of the story.

If the overall UPI statistics could also show the contribution of journeys such as UPI Lite and UPI LiteX, users of the data could begin to see:

How much → Through which journey → At what scale

Not as a judgement.

Not as a comparison.

Simply as greater visibility into an ecosystem that is already transforming how India pays.

---

The First Line on the Whiteboard

The UPI numbers are public. Let the UPI journeys inside those numbers be visible too.

---

A Citizen Observation

Could the existing UPI Product Statistics, within the appropriate methodology, include a UPI Lite and UPI LiteX breakup within the main UPI statistics view?

The intention is not to prescribe the format.

It is simply to ask whether greater granularity could make already-public statistics even more useful.

For a citizen in Chikkamagaluru.

For a researcher in Sivaganga.

For a journalist in Dimapur.

For a student in Alappuzha.

For a merchant in Bundi.

For a policymaker studying digital payments from Leh.

For the wider digital-payment ecosystem.

The numbers tell us how big UPI has become.

Perhaps the composition can also help us understand how UPI is evolving.

---

Closing Thought

From Dharwad to Aizawl.

From Tinsukia to Kasaragod.

From Beed to Port Blair.

Different places.

Different users.

Different journeys.

One public set of numbers.

Perhaps the more we can see inside those numbers, the better we can understand the digital-payment journey that they represent.

More visibility.
More context.
Better understanding.

---

 

April 11 — Digital Transactions Day

A digital ecosystem may begin with a number on a dashboard.

But behind every number are millions of individual journeys.

Count → Break Down → Understand → Learn

Perhaps better digital statistics do not merely tell us how much happened.

They help us understand what is happening inside the number.

The Joy of Digital Transactions.

---

Disclaimer

This Citizen Observation is based on publicly available UPI statistics and information.

It is a citizen observation and does not constitute a request for, or recommendation on, any specific reporting architecture, methodology or regulatory framework.

The suggested UPI Lite and UPI LiteX visibility is illustrative. Definitions, data treatment, methodology and publication format would naturally remain matters for the relevant institutions and domain experts.

 

The Joy of Digital Transactions

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru
Advocating Digital Transactions Day (April 11)

Author’s Blogs

https://prashantrandomthoughts.blogspot.com
https://prashantnepayments.blogspot.com
https://innovationinbanking.blogspot.com

Citizen Observation 35 of 777 | UPI @ 10 | One Decade. One Digital Journey. What Should the Next Decade Look Like?

 Published on 25^th August 2026

UPI has completed ten years. Can we make the next ten years easier to see, one transaction journey at a time?

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

 

The Starting Point

UPI has completed ten years.

The numbers are extraordinary.

But today, I noticed something much smaller.

I made UPI transactions through two different routes.

One through UPI Lite.

Another directly through my main bank account.

Both were successful.

Both were UPI transactions.

But when I later tried to follow their journeys, I noticed something:

The place where I look changes what I can see.

For the UPI Lite transaction, the detailed transaction journey is available within the respective UPI application.

For the regular UPI transaction, the bank account clearly shows the debit — but the UPI-app journey is not immediately obvious from the bank statement alone.

Nothing has gone wrong.

The money has moved.

The transaction has completed.

Yet the citizen's view of the journey can be distributed across different places.

And that made me wonder:

If UPI is becoming a family of digital transaction journeys, should the citizen's view of those journeys become easier to follow?

The Prospective Audience

This isn't only about someone who regularly studies bank statements.

Think of:

A student in Kohima.

A shopkeeper in Sangli.

A parent in Dibrugarh.

A small merchant in Chitradurga.

A senior citizen in Karaikal.

An Indian traveller in Muscat.

A son in Toronto, helping his parents understand a payment made back home.

Different people.

Different UPI journeys.

One simple expectation:

If I made the payment, I should be able to understand what happened to it.

 

Act I — One Transaction. Multiple Possible Journeys.

UPI has grown beyond one simple way of making a payment.

A citizen may now encounter journeys involving:

Main UPI → UPI Lite → UPI Circle → Credit Line → International → …

The question is not whether these features are useful.

It is:

Can the citizen later understand which journey actually happened?

That question becomes increasingly relevant as the UPI ecosystem grows.

The payment may be seamless.

The citizen's view of the journey should be equally easy to follow.

That is where my small observation begins.

Act II — What Happened Between “Pay” and “Done”?

We often see the beginning.

Scan → Enter Amount → Pay

And we see the end:

Successful.

But between those two points, a digital transaction has travelled through a system.

Perhaps the citizen should be able to understand that journey without becoming a payment-system expert.

Initiated → Processing → Successful → Received → Settled

And when something goes wrong:

Initiated → Interrupted → Reason Visible → Recovery → Resolution

The second journey may matter just as much as the first.

Because when everything works, we rarely ask questions.

It is when something doesn't work that the journey becomes important.

 

Act III — One Transaction. One Visible Trail.

Imagine making a payment today.

Tomorrow, you want to find it.

Perhaps the ideal citizen view could answer, in one place:

What was paid?
When was it paid?
From where?
Through which UPI journey?
To whom?
What was its status?
What happened next?

Not necessarily a new app.

Not necessarily a new statement.

Not necessarily another layer of technology.

Just a clearer transaction trail.

Because the citizen should not have to reconstruct the journey from:

Bank statement + UPI app + notification + merchant confirmation + memory.

 

Act IV — One Citizen Illustration

Perhaps the future transaction view could be as simple as:

Transaction Journey	Citizen View
Amount	₹XXX
Initiated	Date / Time
Journey	UPI / UPI Lite / Other applicable route
From	Account / applicable funding source
To	Person / Merchant
Status	Successful / Pending / Failed
Reference	Transaction reference
Next Step	Completed / Processing / Action required

 

 

 

Illustrative example only.

The fields, architecture, data-sharing arrangements, privacy safeguards and technical standards would naturally remain matters for the relevant institutions and domain experts.

The observation is much smaller:

Can the citizen see the transaction journey without having to assemble it themselves?

Because the next decade of digital payments may not only be about more transactions.

Perhaps it can also be about better visibility of every transaction journey.

One Citizen Thought

Ten years ago, the challenge was to make digital payments possible at scale.

The next decade may present a different opportunity:

Make the UPI transaction journey easier for the user to understand.

Not only when it succeeds.

Especially when it is:

Pending.
Failed.
Reversed.
Refunded.
Disputed.

A user should not need to become a payment-system expert to answer:

“What happened to my money?”

---

The First Line on the Whiteboard

The UPI transaction is digital. Let its journey be visible for the users.

---

A Citizen Observation

Could transaction visibility become one of the considerations for the next decade of digital payments?

Not necessarily through another application.

Not necessarily through a new dashboard.

But through greater consistency in how a user can understand:

What happened → Where it happened → Through which journey → What its current status is → What happens next.

As UPI journeys become more diverse, perhaps the user experience should become simpler, not more fragmented.

The actual architecture, interoperability, privacy safeguards, data availability and standards would naturally remain matters for the relevant institutions and domain experts.

The citizen observation is simply:

If a UPI transaction can travel through multiple journeys, can its story remain easy for the user to follow?

---

 

Closing Thought

A student in Kohima.

A shopkeeper in Sangli.

A parent in Dibrugarh.

An Indian travelling through Muscat.

A family member in Toronto, helping someone back home understand a payment.

Different people.

Different journeys.

One expectation.

When the payment is complete, the journey should not disappear.

And when something goes wrong, the user should not have to become an investigator.

Ten years built the rail.

Perhaps the next ten can make the journey visible.

---

April 11 — Digital Transactions Day

A digital transaction may begin with a simple tap, scan or click.

But the journey behind that transaction can be much longer.

Initiate → Process → Complete → Record → Understand

Perhaps better digital journeys do not merely complete the transaction.

They make the journey easier for the user to understand.

The Joy of Digital Transactions

---

Disclaimer

This Citizen Observation is based on publicly available information concerning the ten-year journey of UPI.

It is a citizen observation and does not constitute a recommendation on payment-system architecture, regulation, technology, interoperability or data-sharing policy.

The transaction-visibility examples and illustrations are conceptual. Actual data availability, system design, privacy safeguards and implementation would remain matters for the relevant institutions and domain experts.

 

The Joy of Digital Transactions

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru
Advocating Digital Transactions Day (April 11)

Author’s Blogs

https://prashantrandomthoughts.blogspot.com
https://prashantnepayments.blogspot.com
https://innovationinbanking.blogspot.com