Citizen Observation 76 of 777 | NCMC Transit Cards Across India | One Common Mobility Card. Interoperable TOM Counters?

 Published: 01 November 2026

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

DC777 | CO777 | DTD777

 

The Introduction

One country. Many cities. Countless journeys.
A common mobility card is bringing them closer.

But can the services behind the card travel across cities too?

One NCMC card. One service experience.

Act 1 — A Common Mobility Vision for a Diverse Country

Imagine boarding a metro in Bengaluru, taking a city bus in Chennai, and travelling on another public transport system somewhere else in India.

Different cities. Different operators. Different journeys.

Yet, increasingly, one common idea connects them: the National Common Mobility Card (NCMC).

The vision is simple and compelling. A passenger should be able to use a compatible mobility card across participating public transport systems, reducing the need to carry separate cards for every journey.

But a mobility card is more than a ticket to enter a station or board a bus.

It also has a balance to check, a recharge to complete, and sometimes an online recharge that still needs to be updated on the physical card.

That brings us to a simple question:

Can the service experience become as common as the mobility card itself?

A Brief Background — NCMC and MTS-PPIs

The National Common Mobility Card is part of India's broader effort to make public transport payments more interoperable.

The Reserve Bank of India's framework for Prepaid Payment Instruments (PPIs) includes a category called Prepaid Payment Instruments for Mass Transit Systems (MTS-PPIs).

These instruments are designed for automated fare collection and transit-related payments.

The regulatory framework provides for MTS-PPIs to be used across various modes of public transport, including metro, buses, rail and waterways, as well as tolls and parking, subject to applicable conditions.

This creates room for a wider mobility experience.

However, using a card for travel across participating transport systems and accessing every card-service function across those systems are not necessarily the same thing.

Travel acceptance, recharge, balance update, balance enquiry and card servicing may involve different systems, issuers and technical arrangements.

And it is this distinction that deserves our attention.

Act 2 — Three Passengers. Three Cities. One Common Question.

The Trigger — A Times of India Report

On 30 October 2026, The Times of India published an article titled:

“MTC asks conductors to help passengers check NCMC card balance.”

The report describes how Chennai's Metropolitan Transport Corporation (MTC) has instructed its branch managers to ensure that bus conductors assist passengers who approach them for NCMC-related services.

Using their Electronic Ticketing Machines (ETMs), conductors can help passengers with recharge, balance updates and checking the available card balance.

The report also notes that the instruction follows an earlier Times of India report highlighting the difficulties Chennai Metro commuters faced in checking their card balances.

It is a useful example of a transport organisation extending assistance through its existing infrastructure.

And it leads us to a larger question.

If the NCMC vision is national, can the supporting card-service experience become more interoperable too?

Meet Seeta, Salma and Suzy

Imagine three passengers.

Seeta — Bengaluru

Seeta is travelling on Namma Metro. She carries a Singara Chennai NCMC card.

The card is accepted for her metro journey. But she has recently recharged it online and needs to update the balance on the physical card.

Can she approach a participating Namma Metro TOM counter and complete that update, even though her card was issued for use in Chennai?

Salma — Chennai

Salma uses her NCMC card across Chennai's public transport network.

She wants to check the available balance before beginning her next journey.

Where can she conveniently do so?

Suzy — Another Indian City

Suzy is travelling in another city with an NCMC-enabled transport system.

She has a card issued elsewhere. She expects the convenience of a common mobility card, and naturally wonders whether the supporting services will be equally accessible.

Seeta, Salma and Suzy may never meet.

They may use different transport systems, travel in different cities and carry cards issued by different institutions.

But their expectations are similar.

They want to travel, recharge, update and check their balances with as little friction as possible.

Three passengers. Three cities. One common question.

Act 3 — From One Common Card to One Common Service Experience

The Citizen Observation — Interoperable TOM Counters

Could India explore a network of Interoperable Ticket Office Machine (TOM) Counters across participating NCMC-enabled transport systems?

A passenger carrying an eligible NCMC card issued in one city could approach a participating counter in another city and access supported card services.

The possibilities could include:

• Balance enquiry: Check the available balance on the physical card.
• Balance update: Complete the update of an online recharge, where supported.
• Recharge: Reload the card through compatible payment and settlement arrangements.
• Card-service assistance: Obtain basic help with card-related queries and transactions.

An existing example is the RBL Bank Namma Metro NCMC card service, which describes balance enquiry at a Metro Station Customer Service Desk using a card reader, alongside other digital and physical card-service channels.

Could such existing service facilities become a starting point for exploring wider interoperability?

The idea is to make essential card services more accessible, even when the passenger is outside the city where the card was issued.

What Could One Common Service Experience Look Like?

A passenger may enter a metro station in one city and board a bus in another using an NCMC card.

The next step in the journey could be to make essential card services more accessible beyond the city or system that issued the card.

Could existing TOM counters, ticket vending machines and compatible card readers become part of a wider interoperable service network?

Could a passenger walk up to a participating counter, tap a card issued elsewhere and check its balance or complete an eligible balance update?

The card may be common. Can the service experience be common too?

What Could Bring the Stakeholders Together?

An idea of this scale would naturally require participation from multiple stakeholders.

Transport operators, banks, card issuers, technology partners and relevant authorities may all have a role to play.

But what could bring them together around this common objective?

Could a sustained citizen conversation help?

Could more discussions on professional platforms, social media, public transport forums and industry events bring visibility to the passenger's experience?

Could a shared recognition emerge that the convenience of an interoperable mobility card should ideally extend to the essential services associated with it?

Perhaps the first step is simply to place the idea on the table.

Can we start a conversation around Interoperable TOM Counters?

Nothing More. Nothing Less.

This observation does not prescribe a particular technology, operating model or implementation mechanism.

It does not suggest that every transport counter must immediately support every service across every NCMC card.

It simply proposes exploring the possibility of interoperable TOM counters so that passengers can access essential card services across participating transport systems.

The actual implementation approach, technical architecture, operational arrangements and rollout priorities are best left to the concerned stakeholders — transport operators, banks, card issuers, technology partners and relevant authorities.

The suggestion is for a common service experience. The solution belongs to the stakeholders.

Nothing more. Nothing less.

Closing Thought

Seeta in Bengaluru.
Salma in Chennai.
Suzy somewhere else in India.

Three passengers. Three journeys. One common mobility aspiration.

The success of a common mobility card is not measured only by how many gates it can open or how many buses accept it.

It is also reflected in how easily a passenger can manage the card.

One NCMC card. Many cities. One service experience.

Could interoperable TOM counters help take India's common mobility journey one step further?

One observation at a time.

April 11 - Digital Transactions Day (Proposed)

A Small Step Towards April 11

April 11 is proposed as Digital Transaction Day — an opportunity to recognise the role of thoughtful digital systems in making everyday experiences simpler, safer and more inclusive.

Mobility is one such everyday experience.

A common card can make travel easier. Interoperable services can make the journey around that card easier too.

Progress is meaningful when convenience travels with the citizen.

Disclaimer

This is an independent citizen observation prompted by The Times of India's report on Chennai MTC's NCMC passenger-assistance initiative, published on 30 October 2026. Seeta, Salma and Suzy are illustrative characters.

Interoperable TOM counters are a citizen suggestion for consideration, not a statement of existing capability or regulatory mandate.

Actual implementation is subject to the assessment and decisions of the concerned stakeholders, applicable regulations and technical feasibility.

---

The Joy of Digital Transactions

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

LinkedIn Profile

Author's Blogs

Prashant Random Thoughts

Prashant NePayments

Innovation in Banking

 

 

Citizen Observation 75 of 777 | Microsoft Voluntary Separation | When Employment Ends, Should Insurance History Reset?

 Published 31st October 2026

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

DC777  CO777 DTD777

 

The introduction

One employment chapter closes.
The health-insurance journey should not start from zero.
Should an already-insured employee be treated as a new entrant?

The Trigger

Imagine three colleagues: Amar, Akbar and Anthony.

Amar accepts a voluntary separation offer. Akbar decides to resign. Anthony, too, finds himself at the end of an employment chapter.

Different circumstances. One shared question.

All three have enjoyed health-insurance coverage under their employer's group policy. When they leave, that cover may cease. Their next step could be an individual health-insurance policy.

But what happens to the insurance history they have already built?

Do they enter the next policy as complete newcomers, or should their years of previous group coverage count?

Microsoft's worldwide voluntary separation announcement gives us a timely reason to examine this question. But it reaches far beyond one company.

When employment ends, should an employee's health-insurance history begin again at zero?

 

The Act 1 — Three Colleagues. Three Different Exits.

Amar, Akbar and Anthony have worked in the same organisation.

They may have different roles, different lengths of service and different personal circumstances.

Amar chooses a voluntary separation scheme. The offer gives him an opportunity to move on.

Akbar decides that it is time to resign and explore a different professional path.

Anthony's employment journey also comes to an end, through a different set of circumstances.

Their exits are not the same. But during their employment, all three were covered under the organisation's group health-insurance policy.

For years, that coverage formed part of their employment benefits. It offered a layer of financial protection for themselves and, depending on the policy, their eligible family members.

Now the employment relationship has ended.

The office access card is returned. The email account is closed. The salary stops.

And the group health-insurance cover?

That, too, may come to an end under the terms of the employer's policy.

The three colleagues now face a question that may not have received the same attention as their separation payments.

What happens to the health-insurance history they leave behind?

The Act 2 — New Entrant or Existing Insured?

Imagine Amar approaches an insurer for an individual health-insurance policy after leaving his employer.

He has been covered under a group health-insurance policy for several years.

Should the insurer look at him as someone entering health insurance for the first time?

Or should the years of previous coverage be recognised as part of his insurance history?

The distinction matters.

A person who has never held health insurance and a person who has been covered continuously under an employer's group policy may arrive at the insurer's door with very different coverage histories.

Yet, when seeking a new individual policy, the employee may have to understand fresh terms, waiting periods, underwriting requirements and other conditions.

This is where the policy question deserves attention.

The proposal here is not to transfer the employer's group policy, nor to demand automatic acceptance of a new policy on identical terms.

It is to ask whether prior group health-insurance coverage should be recognised when determining the employee's status and continuity of insurance history.

A change in employment should not, by itself, erase the fact that the person was already insured.

And this should not depend on how the employment ended.

Whether Amar accepted a voluntary separation offer, Akbar resigned, or Anthony left through another form of separation, the underlying question remains the same.

Should the insurance history belong to the individual, even when the policy was provided through the employer?

The Act 3 — A Question for the Insurance Ecosystem

This is not a question for employers alone.

Insurers, regulators and employee-benefit administrators all have a role in making the transition clearer.

Could the insurance ecosystem consider a more consistent approach to recognising prior group-policy coverage when an employee seeks an individual health-insurance policy after separation?

A few questions deserve examination:

• Recognition of previous coverage: Can the employee's verified group-policy history be considered when assessing the new proposal?
• Waiting periods: Can the coverage already completed under the group policy be given appropriate credit, rather than making the employee start afresh in every respect?
• Pre-existing conditions: How should conditions already covered or disclosed during the group-policy period be considered under the new policy's terms?
• Underwriting clarity: Can insurers explain in advance what continuity recognition is available, what remains subject to underwriting and what exclusions or conditions may apply?
• Family coverage: Should the insurance history of eligible family members covered under the group policy also receive appropriate consideration?

This is not a demand for identical premiums, guaranteed acceptance or an automatic waiver of every condition.

A new policy may still require underwriting. The insurer may need to assess the proposed sum insured, product eligibility and other applicable risk factors.

But the employee's previous coverage is a real part of their insurance journey.

Could that history be recognised more consistently and transparently?

In this ever changing employment conditions, health insurance is an important part, which is always overlooked.  

The Citizen Observation

Microsoft's voluntary separation announcement has brought the subject into focus. But the question belongs to every employee who leaves an organisation, whether through a voluntary separation scheme, resignation or another form of separation.

Amar, Akbar and Anthony may have chosen different exits.

Their health-insurance histories, however, should not become invisible merely because their employment has ended.

The policy question is simple:

Can an employee who was already insured under a group health policy be recognised as an existing insured individual when seeking future health insurance, rather than being treated as a first-time entrant?

The answer deserves thoughtful consideration by the insurance ecosystem.

Nothing More. Nothing Less.

This observation does not seek automatic portability of an employer's group policy.

It does not seek guaranteed issuance of an individual policy, identical pricing or exemption from all underwriting requirements.

It asks for something more fundamental: recognition of an employee's previous health-insurance coverage when the employee moves from employer-sponsored group insurance to an individual policy.

Employment may end. The employer's group cover may end.

But should the insurance history of the individual disappear with it?

Closing

Amar chose voluntary separation.
Akbar chose resignation.
Anthony's employment journey took a different turn.

Three exits. One shared concern.

An employee may leave an organisation, but the years spent under its group health-insurance cover remain part of that person's history.

Can we make that history count?

Because the end of employment should not automatically mean the beginning of an insurance journey from zero.

One observation at a time.

 

April 11 – Digital Transactions Day (Proposed)

A Small Step Towards April 11

April 11 is proposed as Digital Transaction Day — an opportunity to recognise how thoughtful digital systems can make everyday experiences simpler, safer and more inclusive.

The same spirit of citizen-centric thinking applies beyond payments.

Whether it is a digital transaction or a health-insurance transition, the experience should recognise the person behind the process.

Digital progress is meaningful when it makes life's transitions easier.

 

Disclaimer

This is an independent citizen observation prompted by Microsoft's October 2026 voluntary separation announcement and media reporting on the associated employee benefits. Amar, Akbar and Anthony are illustrative characters and do not represent actual Microsoft employees.

This observation is not legal, insurance or financial advice. It does not interpret any individual separation agreement or employer group-policy contract.

The proposed recognition of prior group health-insurance coverage as an established insurance history is a policy suggestion, not a claim that every insurer is currently required to classify a former group member as an existing entrant or issue a new policy on identical terms.

Any new policy remains subject to applicable regulations, product terms, eligibility and underwriting.

However, it is high time for HR Leaders and IRDAI to ponder  into this aspect.

The Joy of Digital Transactions

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

https://in.linkedin.com/in/prashantnayakanti

 

Author’s Blogs

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

 

 

Citizen Observation 74 of 777 | Mr. Anand Mahindra & Mr. Dilip Asbe | The Conversation That Could Change NPCI BHIM Adoption

 Published 30th October 2026

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

DC777  CO777 DTD777

 

The Introduction

One conversation. A new perspective.

One UPI app discovered. A choice reconsidered.

Could this spark a wider journey towards NPCI BHIM adoption?

The Trigger — When a Conversation Changes the Picture

Sometimes, a change in digital behaviour begins not with a new technology, but with a conversation.

On 26 October 2026, Business Today reported that Mr. Anand Mahindra had switched to BHIM after a conversation with Mr. Dilip Asbe, Managing Director and CEO of NPCI. 

The exchange brought BHIM into sharper focus for Mahindra and prompted him to reconsider his choice of UPI app.

What makes this moment noteworthy is not simply that a prominent business leader switched apps. 

It is that a conversation appears to have opened a new window into an app and the wider UPI ecosystem behind it.

Could greater awareness of NPCI BHIM inspire more people to explore it?

And what turns that first moment of discovery into sustained adoption?

The Act I — The Conversation

Sometimes, a new choice begins with an unexpected conversation.

Mr. Anand Mahindra, a familiar name in Indian industry, had not been using NPCI BHIM as his preferred UPI app. Then came a conversation with Mr. Dilip Asbe, Managing Director and CEO of NPCI.

What followed was more than an exchange between two individuals. It brought BHIM into focus for someone who was already familiar with digital payments.

Mr. Anand Mahindra subsequently shared that he had switched to BHIM.

The moment invites a simple reflection.

A product may be available. Its benefits may exist. Yet a potential user may not fully appreciate either until someone takes the time to explain them.

Sometimes, adoption begins when awareness meets an open mind.

The Act II — Beyond the App on the Screen

When we make a UPI payment, we usually focus on the app we open, the QR code we scan and the confirmation that appears.

But the wider UPI ecosystem involves infrastructure and coordination beyond the screen in our hands.

The conversation between Mr. Mahindra and Mr. Asbe also brings attention to the institution behind BHIM and the wider UPI ecosystem: the National Payments Corporation of India (NPCI).

For a user, however, awareness is only the beginning.

What makes someone explore a different UPI app? What gives them the confidence to try it?

And what makes them continue using it after the first few transactions?

The answers may include familiarity, ease of use, useful features, trust and the everyday experience of completing a payment. Different users may value different things.

BHIM's opportunity is not merely to be noticed. It is to give people a reason to explore it, experience it and decide whether it suits their needs.

Awareness may open the door. The user's experience determines whether they return.

The Act III — From One Conversation to Wider Adoption

One prominent user's decision can bring an app into the public conversation. But a single announcement cannot establish how many other users will follow, or whether their use will continue over time.

That is where the wider citizen question begins.

Could conversations such as this encourage more people to discover NPCI BHIM?

Could clearer communication about the app's features and purpose help users make informed choices among the UPI apps available to them?

And how might adoption be understood—not merely through downloads or initial trials, but through continued use and the value people find in the experience?

These are questions worth examining.

The objective need not be to persuade every UPI user to switch apps. Users should remain free to choose the app that best meets their needs.

Rather, the opportunity is to ensure that people know their options and can make those choices with greater awareness.

Mr. Mahindra's announcement offers a timely moment to ask whether a conversation can do what a product announcement alone may not: make someone curious enough to take a closer look.

The Citizen Observation

India's UPI ecosystem has made digital payments part of everyday life. Within that ecosystem, multiple apps give users different ways to access UPI.

The story of Mr. Anand Mahindra and Mr. Dilip Asbe brings an important dimension of adoption into view: awareness.

A user may already be comfortable making digital payments and still remain unfamiliar with a particular app.

A conversation can introduce a new perspective, but the decision to adopt ultimately belongs to the user.

For NPCI BHIM, the opportunity is to build on that moment of attention through clear communication, a useful user experience and sustained confidence.

The wider lesson extends beyond one app.

Digital payment adoption is not only about making technology available. It is also about helping people discover their choices and experience their value.

Nothing More. Nothing Less.

This observation is not a claim that BHIM is superior to every other UPI app, nor that users should abandon the apps they already prefer.

It is not a prediction that one prominent user's switch will automatically lead to widespread adoption.

It is an invitation to consider the role of awareness in digital behaviour—and how a conversation can encourage someone to explore a choice they had not previously considered.

One conversation has brought BHIM into focus. What the wider ecosystem does with that moment is the next question.

Nothing More. Nothing Less.

The Closing Thought

A conversation can introduce a possibility.

An experience can earn confidence.

And a choice, freely made, can become a habit.

Could one conversation inspire a million new discoveries?

The million represents an aspiration to encourage discovery—not a prediction of downloads, switches or active users.

The opportunity is to make more people aware of their choices and let their experience shape what follows.

The One observation at a time.

April 11 — Digital Transactions Day (Proposed)

Digital progress is not measured only by the systems we build. It is also shaped by how well people understand, trust and use them.

The conversation around NPCI BHIM is one reminder that awareness can be part of the journey from availability to adoption.

April 11 is proposed as Digital Transactions Day—a day to recognise the role of digital transactions in everyday life and encourage informed, confident participation in the digital economy.

Explore the proposal: https://movethebarrier.blogspot.com/

Disclaimer

This is an independent citizen observation prompted by Business Today's report on Mr. Anand Mahindra's decision to switch to BHIM following a conversation with Mr. Dilip Asbe.

The observation does not independently verify the conversation or assess BHIM against other UPI apps.

Any wider adoption impact remains uncertain. No app is endorsed as universally preferable; the purpose is to reflect on awareness, user choice and digital payment adoption.

As it is UPI is wonderful, the actual debit happens in the linked bank account or other instrument, via any UPI App.

This is the core differentiator of the UPI design.

The Joy of Digital Transactions

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

https://in.linkedin.com/in/prashantnayakanti

 

Author’s Blogs

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

Citizen Observation 73 of 777 | Namma Metro Cards & Bengaluru | When the Journey Ends, What Happens to the Balance?

 Published 28^th October 2026

Nayakanti Prashant
3rd Gen Banker & Citizen Lobbyist – Bengaluru

DC777  CO777 DTD777

 

The Introduction

One card. Many journeys.

Sometimes, a small balance remains.

When it cannot be refunded or transferred, who ultimately benefits?

 

The Small Trigger _ A Bengaluru Commuter's Dilemma

Prashant is a regular Bengaluru Metro traveller. For years, his Namma Metro smart card has been his familiar companion on daily journeys.

He knows the routine: recharge the card, tap at the gate, board the train and get on with the day.

Now, he hears about the National Common Mobility Card (NCMC), designed to make travel across participating transport systems more convenient. With NCMC adoption growing in Bengaluru, he begins to consider switching.

The question appears straightforward.

Should he continue using his existing Bengaluru Metro card, or move to NCMC?

The new option sounds promising. One card could make more of his everyday journeys convenient.

Then Prashant remembers something.

There is still money left on his old Metro card.

It may not be a large amount. But it is money he has already paid, and he wants to understand what happens to it before making the switch.

Can he transfer the balance to his new card? Can he obtain a refund? Must he continue using the old card until the balance is exhausted?

A seemingly simple choice now comes with an unanswered question.

The decision is no longer just about choosing a card. It is about what happens to the value left behind.

The Big Trigger — A Report from Bengaluru

This is not merely a hypothetical concern.

A report published by The Hindu on 19 October 2026 described Bengaluru Metro commuters who said they could neither transfer the remaining balance on their traditional Namma Metro smart cards to NCMC nor obtain a refund while their old cards remained usable. BMRCL officials reportedly said they would look into the issue.

The report also highlighted a practical difficulty faced by commuters trying to use up their remaining balance.

Consider the reported example: a journey costing around ₹67, a minimum balance requirement of ₹90 for certain journeys, and a minimum recharge amount of ₹50.

The precise circumstances matter, but the underlying dilemma is easy to understand. A passenger may have a balance that is inconvenient to use for the next intended journey. Using it up may require another recharge, leaving a residual amount on the old card even after the passenger has decided to move to a different mobility option.

The issue is not necessarily that the passenger cannot use the card at all. It is that moving on from the card may be less straightforward than expected.

For Prashant, the question remains: should choosing a new card mean having to leave some value behind?

The Act I — A New Card. An Old Balance.

Let us stay with Prashant for a moment.

He is not trying to find fault with the Metro system. He is simply weighing the convenience of a new mobility option against the practicalities of leaving his old card behind.

He may decide to continue using the existing card until the remaining balance is as low as possible. He may choose to use NCMC for journeys where it offers additional convenience while retaining the old card for Metro travel. Or he may look for an authorised way to transfer or recover the remaining value.

Each option has a practical implication.

Keeping both cards means managing two instruments. Continuing with the old card may not suit his preferred travel pattern. Moving entirely to NCMC leaves him wondering about the value on the earlier card.

The emotional question is modest, but real.

“Why should I have to think so hard about a small amount that I have already paid?”

For one passenger, it may be a few rupees. For another, the amount may be different. The point is not to exaggerate the financial impact. It is to recognise that convenience includes knowing what happens to the money already loaded onto an instrument.

A new payment option may make future journeys easier. What happens to the previous balance is part of that transition too.

The Act II — Two Cards. Different Frameworks.

Prashant's question leads him to a more fundamental distinction.

His existing Namma Metro smart card is a closed-loop instrument, designed for use within its specific transit ecosystem. NCMC, by contrast, is intended to support interoperable payments across participating transport systems.

The transition is therefore not simply a matter of moving money from one card to another. The instruments may operate under different arrangements, with differences in technology, issuance and customer identification requiring consideration.

These differences may complicate migration, but their precise role in BMRCL's current position needs confirmation from the relevant authority.

There is also a wider regulatory context worth examining.

The Reserve Bank of India's Master Directions on Prepaid Payment Instruments (PPIs) contain a distinct category for Mass Transit System Prepaid Payment Instruments (MTS PPIs). Under paragraph 10.2, instruments within this category can have an outstanding balance of up to ₹3,000 and can have perpetual validity. Cash withdrawal, refunds and funds transfers are not permitted under this category.

These provisions describe the MTS PPI framework. They should not automatically be applied to the legacy Namma Metro closed-loop card without establishing its precise regulatory treatment.

That distinction matters. We should not assume that the rules governing one category directly explain the restrictions encountered with another.

But the broader question remains relevant:

When a passenger moves on from a prepaid instrument, what happens to the value left behind—and what should the passenger be told about it?

The Act III — Where Does the Value Go?

Prashant's experience opens the door to a wider question.

Across a large number of prepaid transit instruments, what happens to balances that remain unused? How are they accounted for? What rules govern their treatment over time? Who, if anyone, ultimately benefits from that value?

These questions should not be answered by assumption.

An unused balance does not, by itself, prove that the issuer has recognised it as income or that the passenger has permanently lost the value. The accounting treatment, applicable contractual terms and regulatory requirements need to be established.

But when a passenger cannot readily transfer or recover a residual balance, transparency becomes especially important.

Passengers should be able to understand the conditions of the instrument before loading money onto it. They should also be able to understand their options when their travel habits change, a new mobility instrument becomes attractive, or a residual balance becomes difficult to use.

Could the relevant authorities and transit operators examine whether the treatment of residual balances can be made clearer to passengers?

Could a fair, transparent and operationally feasible mechanism be explored, where permitted by the applicable regulatory framework?

These are questions for examination, not assumptions about what the rules should permit.

The objective is not to prescribe an answer in advance. It is to make the issue visible and invite a reasoned assessment of the options.

The Citizen Observation

A digital payment instrument should be convenient to use. But the passenger's experience does not end with the last successful tap. It also includes what happens to any value left behind.

The transition from a traditional Metro smart card to a more interoperable mobility card is an opportunity to consider the complete passenger experience—not only the convenience of the new instrument, but also the treatment of the old one.

The legacy Namma Metro card and MTS PPIs must be distinguished correctly. Their respective regulatory and operating arrangements need to be understood before drawing conclusions about refunds, transfers or the destination of unused value.

At the same time, the reported commuter experience raises questions worth examining:

• Are the limitations affecting residual balances clearly communicated to passengers?
• What options are available to a passenger who no longer wishes to use the old card?
• How are unused balances accounted for and ultimately treated under the applicable rules?
• Could a compliant mechanism address balances that passengers cannot practically use?

This observation does not presume that all commuters are affected, that every residual balance is irrecoverable, or that an issuer automatically benefits from unused value.

It asks for clarity, transparency and a passenger-centred examination of an issue that may otherwise remain invisible because the amount on any one card is small.

Drops only make an ocean.

The Nothing More. Nothing Less.

Prashant's dilemma is illustrative, but the question is worth examining.

A new mobility card can offer new possibilities. The transition should also account for the value that may remain on the old one.

The answer may lie in clearer communication, better transition arrangements, regulatory clarification or another approach permitted by the applicable framework. The appropriate solution requires evidence and examination.

The starting point is simple: understand the passenger's experience, establish the rules that apply, and make the treatment of unused value transparent.

The Closing Thought

The balance on one card may be small.

The question it raises is not.

When the journey ends, what happens to the balance?

One observation at a time. Nothing More. Nothing Less.

 

April 11 — Digital Transactions Day (Proposed)

Digital transactions are increasingly woven into everyday journeys—from paying for a ride to moving between transport systems.

Trust in that ecosystem depends not only on how easily people can pay, but also on how clearly they understand the rules governing their money.

April 11 is UPI Beta launch Day.

Digital Payments are a sub-set of Digital Transactions.

April 11 is proposed as Digital Transactions Day: an invitation to keep the citizen's experience at the centre of digital progress.

Explore the proposal: https://movethebarrier.blogspot.com/

Disclaimer

This is an independent citizen observation prompted by media reports about unused balances on Namma Metro smart cards during the transition towards NCMC. Prashant's story is illustrative.

The reported issues, the precise regulatory treatment of legacy cards, and the accounting treatment of residual balances have not been independently established here.

RBI's MTS PPI provisions are discussed as wider regulatory context, not as rules presumed to apply directly to the legacy closed-loop card. No fault or improper financial benefit is attributed to BMRCL, any issuer or other stakeholder.

The policy questions are exploratory and do not presume that refunds, transfers or donations are permitted under the applicable framework.

The Joy of Digital Transactions

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

https://in.linkedin.com/in/prashantnayakanti

 

Author’s Blogs

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