How Google Pay Is Using UPI Circle To Reach Young Bank Customers In India
If you are a retail banking leader in India, your future customer may already be learning how digital money works — and it may not be through your bank. This is not a future scenario; it is happening now. While bank digital teams debate how much control is “too much,” customers have been clear about what they want: clear limits, visible controls, and the ability to stop things instantly. Google Pay appears to have understood that instinct faster than most banks have.
Its new Pocket Money feature is not just another UPI update. It is how many children in India will first learn how digital money works. And that matters more than it sounds.
Pocket Money turns UPI Circle into something families can understand and trust
Pocket Money lets parents give children controlled access to digital payments without opening a bank account in the child’s name. Parents can set monthly limits, see transactions in real time, receive alerts, and pause access instantly. The money comes directly from the parent’s bank account. For the child, this creates a first sense of independence while parent retain clear control and Google Pay gains early relationship with a future customer.
The feature runs on UPI Circle, NPCI’s delegated payments framework. Banks have had access to these rails from day one. What Google Pay added was not new infrastructure, but a simple, well‑named product that fits naturally into how families already manage money.
Banks have known about the youth banking opportunity for years
This development should not come as a surprise. In earlier research on youth banking in India, I looked at how banks consistently treated under‑18s as a low priority, despite clear signs of demand for supervised digital money experiences. Every year, millions of under‑18s get their first smartphone. Increasingly, their first lessons about money happen through apps — but not bank apps. The opportunity was visible. What was missing was a product designed around family behaviour rather than internal constraints.
Pocket Money is a shared finance experience, not just a youth feature
Pocket Money is being described as a “kids” product, but the framing misses the point. At its core, it is really about shared finance – how families manage money together across different levels of access and responsibility. This shared setup builds trust and sets expectations about how money should work inside a household. Once families get comfortable managing money together inside one interface, that interface starts to feel like the natural home for financial decisions.
Google Pay reduced adoption friction by designing for parents, not platforms
Four design choices explain why this works so well.
- They used language parents already understand. “Pocket money” is familiar and easy to explain. Parents rarely adopt features; they adopt ideas they can describe to their child easily.
- They designed for the decision‑makers. Children use the feature, but parents decide whether it exists. Limits, alerts, and pause controls are always visible. This removes the fear of losing control.
- They put it where parents already act. Pocket Money sits alongside contacts parents already pay. It feels like a natural extension of existing behaviour, not a separate setup task.
- They made safeguards obvious. Identity checks are part of onboarding. Instead of feeling like friction, they signal safety. Trust is felt early, not buried in terms and conditions.
None of this is technically complex. It is behavior‑led design.
When Google Pay becomes the default, habits and future value start to shift
Every Pocket Money transaction is funded by a parent’s bank account. Banks process the payment, hold the balance, and earn the transaction economics. What banks do not control is where habits form. Over time, Pocket Money makes Google Pay the default app for everyday payments in the household. Defaults matter because people rarely change them. Once families get used to paying this way, they stop reconsidering alternatives. As Google Pay adds more products, users are far more likely to try what is already in front of them than move elsewhere.
This matters because these children will not always be spending pocket money. Over time, they will manage allowances, then income, then savings. If their relationship with money already sits outside the bank’s own app, banks risk becoming background utilities — present, but not central. This pattern is familiar from UPI’s broader growth: shared infrastructure enabled scale, but customer habit formed around a small number of dominant interfaces.
Banks can still act by designing for identity, not just access
Google Pay does not have a banking licence, nor can it offer deposits, long‑term savings, or credit on its own. Banks can. But reclaiming relevance with young customers requires more than enabling payments. Our research shows demand for shared finance experiences continues to grow, even as many traditional providers underinvest in them. It also explains why digital teams at financial providers should invest in shared finance in the first place.
Here’s what banks should do next:
- Define a clear youth proposition built on UPI Circle, with language families trust.
- Lead with parental controls, treating reassurance as the main driver of adoption.
- Link spending to saving early, so children learn both under the bank’s brand.
- Surface it prominently, where parents already move money.
- Measure success by identity creation, not feature activation.
In banking, the first place people learn how money works often shapes where they stay later and that is the risk banks now face.
What To Read Next
Forrester clients can explore related research:
How Parents Help Children Open A Bank Account: A Shared Finance Journey Overview
Shared Finance Keeps Growing While Traditional Providers Ignore Rising Demand
And if you’d like to discuss this topic, set up an inquiry or guidance session.