Sending Idle EV Wallet Money to Family, Without the Hassle

Sending Idle EV Wallet Money to Family, Without the Hassle

10 min read · Sep 29, 2026

10 min read · Sep 29, 2026

A UX case study on ChargeZone: designing a flow to share dormant wallet balance with the people who actually drive the car

A UX case study on ChargeZone: designing a flow to share dormant wallet balance with the people who actually drive the car

The backstory

My family recently bought an EV. It lives in Jamnagar with them, while I live in a different city. When it needs charging, we use ChargeZone, and the account and wallet are on my phone.

That created a small but recurring problem: money sat in my wallet doing nothing, while the people plugging in the car couldn’t easily use it. Every charge became a phone call, a UPI transfer, or a “can you pay from your side?”

This case study is about fixing that one moment.

My family recently bought an EV. It lives in Jamnagar with them, while I live in a different city. When it needs charging, we use ChargeZone, and the account and wallet are on my phone.

That created a small but recurring problem: money sat in my wallet doing nothing, while the people plugging in the car couldn’t easily use it. Every charge became a phone call, a UPI transfer, or a “can you pay from your side?”

This case study is about fixing that one moment.

The problem

EV wallets assume one person owns the car, the phone, and the money. In many Indian families, that isn’t true. The person who pays isn’t always the person who drives.

Leftover wallet balance ends up dormant. It can’t easily move to someone else who needs it, so money gets stuck while another family member tops up separately

“The money is there. It’s just on the wrong phone.”

EV wallets assume one person owns the car, the phone, and the money. In many Indian families, that isn’t true. The person who pays isn’t always the person who drives.

Leftover wallet balance ends up dormant. It can’t easily move to someone else who needs it, so money gets stuck while another family member tops up separately

“The money is there. It’s just on the wrong phone.”

Who this is for

The payer: often lives away from the car, tops up the wallet, wants control and visibility.

The driver: a parent or sibling at home who just wants to charge and go, with minimal app steps.

The payer: often lives away from the car, tops up the wallet, wants control and visibility.

The driver: a parent or sibling at home who just wants to charge and go, with minimal app steps.

Understanding the current flow

The wallet in ChargeZone is simple. At the top, you see your total balance and a single action: Add money. Below that is a transaction history you can filter by Top-ups, Sessions, and Cashback, or by date.

The wallet in ChargeZone is simple. At the top, you see your total balance and a single action: Add money. Below that is a transaction history you can filter by Top-ups, Sessions, and Cashback, or by date.

The money in this wallet moves in only two ways:

In: when you add money, or when a refund comes back

In: when you add money, or when a refund comes back

Out: when a charging session is paid for

Out: when a charging session is paid for

Looking at my own history made the problem clear. On one day, I added ₹1,000 twice to start a session. That session was auto-cancelled, and the full ₹713.90 was refunded to the wallet. Another session used fewer units than expected, and ₹55.93 came back as a refund.

None of this money returns to my bank. It all stays in the wallet. By the end, I had ₹2,055.93 sitting in an account I wasn’t the one using, while the car was in another city.

Looking at my own history made the problem clear. On one day, I added ₹1,000 twice to start a session. That session was auto-cancelled, and the full ₹713.90 was refunded to the wallet. Another session used fewer units than expected, and ₹55.93 came back as a refund.

None of this money returns to my bank. It all stays in the wallet. By the end, I had ₹2,055.93 sitting in an account I wasn’t the one using, while the car was in another city.

Key insights

1. The wallet only goes one way

“Add money” is the only action on the screen. You can’t transfer, withdraw, or share. Once money is in, it can only be spent from that account.

“Add money” is the only action on the screen. You can’t transfer, withdraw, or share. Once money is in, it can only be spent from that account.

2. Dormant balance builds up without you noticing

Refunds from cancelled sessions and unused units quietly add to the balance. Users don’t choose to keep this much money in the wallet; the system just fills it up.

Refunds from cancelled sessions and unused units quietly add to the balance. Users don’t choose to keep this much money in the wallet; the system just fills it up.

3. The balance is shown, but not made useful

₹2,055.93 is displayed front and center, but the screen gives it no purpose. There’s no nudge like “Use this” or “Send this,” and no way to act on it.

₹2,055.93 is displayed front and center, but the screen gives it no purpose. There’s no nudge like “Use this” or “Send this,” and no way to act on it.

4. One account assumes one user

The transaction history shows what was charged, but not who charged it. The design assumes the person holding the phone is the person driving the car. For families like mine, where one person pays and another drives, that isn’t true.

The transaction history shows what was charged, but not who charged it. The design assumes the person holding the phone is the person driving the car. For families like mine, where one person pays and another drives, that isn’t true.

5. The fix belongs where the balance lives

Since users already look at this balance and tap “Add money” here, this is the right spot to add a second action, sending balance to family, without redesigning the entire wallet.

Since users already look at this balance and tap “Add money” here, this is the right spot to add a second action, sending balance to family, without redesigning the entire wallet.

Design goals

Make dormant balance visible and actionable

Make dormant balance visible and actionable

Let users send it to a family member in a few taps

Let users send it to a family member in a few taps

Build trust with clear confirmation on both sides

Build trust with clear confirmation on both sides

Keep it simple for less tech-comfortable family members

Keep it simple for less tech-comfortable family members

Why not just share the login?

The obvious workarounds already exist: share your account, or pay remotely whenever someone needs to charge. I considered both, and both break in real life.

The obvious workarounds already exist: share your account, or pay remotely whenever someone needs to charge. I considered both, and both break in real life.

Sharing one login

Login usually runs through OTP on the owner’s phone, so the family still has to call you to get in

Login usually runs through OTP on the owner’s phone, so the family still has to call you to get in

Saved payment methods and personal details become accessible to everyone

Saved payment methods and personal details become accessible to everyone

Charging history and receipts get mixed up across people

Charging history and receipts get mixed up across people

Paying on their behalf

Every charge depends on you being free and reachable

Every charge depends on you being free and reachable

If you’re in a meeting, travelling, or asleep, the car doesn’t get charged

If you’re in a meeting, travelling, or asleep, the car doesn’t get charged

For something urgent, waiting on someone else isn’t acceptable

For something urgent, waiting on someone else isn’t acceptable

The real need

Family members want independence. Their own account, their own control, charging whenever and wherever they need, without asking anyone. The sender just needs a way to fund that.

That’s why I chose transferring balance: it keeps money flowing between accounts while keeping each person independent.

Family members want independence. Their own account, their own control, charging whenever and wherever they need, without asking anyone. The sender just needs a way to fund that.

That’s why I chose transferring balance: it keeps money flowing between accounts while keeping each person independent.

Exploring ideas

Once the problem was clear, the question became: how can the person driving the car use money that’s sitting in someone else’s wallet?

Once the problem was clear, the question became: how can the person driving the car use money that’s sitting in someone else’s wallet?

I explored five directions and evaluated each against four things:

Independence: can the family charge without depending on me?

Independence: can the family charge without depending on me?

Effort for users: how many steps, how much setup?

Effort for users: how many steps, how much setup?

Trust and security: does anyone have to share personal access?

Trust and security: does anyone have to share personal access?

Fit with the current app: can it work within the existing wallet, or does it need a redesign?

Fit with the current app: can it work within the existing wallet, or does it need a redesign?

1. Share the login or pay on their behalf

The workaround families already use. It needs no new feature, but it keeps the family dependent on one person and exposes personal account access. (More on this in Why not just share the login?)

The workaround families already use. It needs no new feature, but it keeps the family dependent on one person and exposes personal account access. (More on this in Why not just share the login?)

Verdict: ❌ Solves nothing, just shifts the burden.

Verdict: ❌ Solves nothing, just shifts the burden.

2. Withdraw balance back to bank

Let users take their unused balance out, then send it to family through UPI. This fixes idle money, but the family still has to add it to their own wallet. That’s two extra steps, two apps, and a detour for money that was meant for charging anyway.

Let users take their unused balance out, then send it to family through UPI. This fixes idle money, but the family still has to add it to their own wallet. That’s two extra steps, two apps, and a detour for money that was meant for charging anyway.

Verdict: ❌ Fixes dormancy, not the family problem.

Verdict: ❌ Fixes dormancy, not the family problem.

3. Shared family wallet

One wallet that several family members can charge from, each with their own login. It’s powerful, but it changes how the wallet works: who owns it, who adds money, who sees what, and how limits are set. It’s a much bigger product decision than the problem needs right now.

One wallet that several family members can charge from, each with their own login. It’s powerful, but it changes how the wallet works: who owns it, who adds money, who sees what, and how limits are set. It’s a much bigger product decision than the problem needs right now.

Verdict: ⚠️ Promising for the future, too heavy for now.

Verdict: ⚠️ Promising for the future, too heavy for now.

4. Add family as linked users

The account owner adds family members who can start sessions using the owner’s balance. This works like a lighter version of a shared wallet, but it still involves permissions, spending limits, and managing roles, and the family’s usage is tied to one account.

The account owner adds family members who can start sessions using the owner’s balance. This works like a lighter version of a shared wallet, but it still involves permissions, spending limits, and managing roles, and the family’s usage is tied to one account.

Verdict: ⚠️ Good control, but complex to set up and manage.

Verdict: ⚠️ Good control, but complex to set up and manage.

5. Send balance to family ✅

Let users send part or all of their wallet balance to another ChargeZone user. Each person keeps their own account and full independence. The sender decides how much to share and when. It fits right next to the existing “Add money” button, so no redesign is needed.

Let users send part or all of their wallet balance to another ChargeZone user. Each person keeps their own account and full independence. The sender decides how much to share and when. It fits right next to the existing “Add money” button, so no redesign is needed.

Verdict: ✅ Solves the core problem with the least friction.

Verdict: ✅ Solves the core problem with the least friction.

Sending balance wasn’t the most ambitious idea, but it was the most direct. It turns idle money into something useful, gives family members their own control, and works within the current wallet. The shared wallet idea isn’t gone; it’s in What’s next.

Sending balance wasn’t the most ambitious idea, but it was the most direct. It turns idle money into something useful, gives family members their own control, and works within the current wallet. The shared wallet idea isn’t gone; it’s in What’s next.

The solution - Send balance to family

The goal was simple: money sitting idle in one wallet should reach the person actually charging the car, in under a minute, without a phone call.

The flow has six steps, from spotting idle balance to seeing the transfer in your history.

The goal was simple: money sitting idle in one wallet should reach the person actually charging the car, in under a minute, without a phone call.

The flow has six steps, from spotting idle balance to seeing the transfer in your history.

1. A wallet that does more than “Add money”

The original wallet had one action. The redesigned wallet has four: Add money, Send, Request, and Family. They sit as equal quick actions just below the balance, so moving money becomes as visible as adding it.

Recent activity now shows where each session happened and who sent money, not just “Debit - Session.”

Design decision: Quick actions instead of a single big button. Adding money is still the first option, but it’s no longer the only one.

The original wallet had one action. The redesigned wallet has four: Add money, Send, Request, and Family. They sit as equal quick actions just below the balance, so moving money becomes as visible as adding it.

Recent activity now shows where each session happened and who sent money, not just “Debit - Session.”

Design decision: Quick actions instead of a single big button. Adding money is still the first option, but it’s no longer the only one.

2. Choosing who gets the money

The recipient screen is ordered by how likely someone is to be picked:

The recipient screen is ordered by how likely someone is to be picked:

Family at the top, as avatars (Mom, Papa, Riya)

Family at the top, as avatars (Mom, Papa, Riya)

Recent contacts, with context like “Sent ₹500 on 2 Sep”

Recent contacts, with context like “Sent ₹500 on 2 Sep”

Contacts on ChargeZone, marked with a badge

Contacts on ChargeZone, marked with a badge

Contacts not on the app yet get an Invite option

Contacts not on the app yet get an Invite option

A short note at the bottom reassures users: the app only checks which contacts use ChargeZone, and numbers are never shared.

Design decision: Family first, because in this use case, most transfers will go to the same one or two people.

A short note at the bottom reassures users: the app only checks which contacts use ChargeZone, and numbers are never shared.

Design decision: Family first, because in this use case, most transfers will go to the same one or two people.

3. Amount, with guardrails

The recipient card stays at the top with a Verified tag and masked number, so users always know who they’re sending to. The transferable balance is shown under the amount, and quick chips (₹200, ₹500, ₹1,000, Max) cover most cases in one tap.

An optional note, like “For the Nexon this month,” helps the receiver understand what the money is for.

Design decision: Max directly solves the dormant balance problem: clear the entire idle amount in a single tap.

The recipient card stays at the top with a Verified tag and masked number, so users always know who they’re sending to. The transferable balance is shown under the amount, and quick chips (₹200, ₹500, ₹1,000, Max) cover most cases in one tap.

An optional note, like “For the Nexon this month,” helps the receiver understand what the money is for.

Design decision: Max directly solves the dormant balance problem: clear the entire idle amount in a single tap.

4. Review before sending

A bottom sheet summarizes everything: amount, recipient, source, note, fee (₹0 · Free), and balance after the transfer.

Design decision: Showing “Balance after” and “Free” upfront answers the two questions people have before sending money: how much will I have left? and is there a catch?

A bottom sheet summarizes everything: amount, recipient, source, note, fee (₹0 · Free), and balance after the transfer.

Design decision: Showing “Balance after” and “Free” upfront answers the two questions people have before sending money: how much will I have left? and is there a catch?

5. Success, with a safety net

The success screen confirms ₹500.00 sent to Neha Pandya · Mom with a receipt: transaction ID, date, source, and new balance.

Below it is a countdown: Sent by mistake? Undo in 09:42. Users can also share the receipt, which is handy when family asks, “Did you send it?”

Design decision: The 10-minute undo window. Money transfers feel risky, and a short, visible undo period makes users more confident without making transfers feel temporary.

The success screen confirms ₹500.00 sent to Neha Pandya · Mom with a receipt: transaction ID, date, source, and new balance.

Below it is a countdown: Sent by mistake? Undo in 09:42. Users can also share the receipt, which is handy when family asks, “Did you send it?”

Design decision: The 10-minute undo window. Money transfers feel risky, and a short, visible undo period makes users more confident without making transfers feel temporary.

6. A history that tells the family story

A new Transfers filter brings together all family money movements, each with its own state:

A new Transfers filter brings together all family money movements, each with its own state:

Sent, with Undo available while the window is open

Sent, with Undo available while the window is open

Received, along with the sender’s note (“Thanks bhai!”)

Received, along with the sender’s note (“Thanks bhai!”)

Requested, for example Papa requested ₹1,000, with expiry and a Pay button

Requested, for example Papa requested ₹1,000, with expiry and a Pay button

Returned, when an invite link goes unclaimed and the money comes back automatically

Returned, when an invite link goes unclaimed and the money comes back automatically

Design decision: Every transfer state is visible, so nobody has to wonder where money went.

One person can fund, another can charge, and both know exactly what happened. That’s the whole idea.

Design decision: Every transfer state is visible, so nobody has to wonder where money went.

One person can fund, another can charge, and both know exactly what happened. That’s the whole idea.

What I learned

Small personal problems make strong design problems

This started with a simple annoyance: money in my wallet, a car in another city. Designing from lived experience helped me see details a brief would have missed, like how refunds quietly pile up and how often “Can you pay?” turns into a phone call.

This started with a simple annoyance: money in my wallet, a car in another city. Designing from lived experience helped me see details a brief would have missed, like how refunds quietly pile up and how often “Can you pay?” turns into a phone call.

The balance was never the problem. The lack of purpose was.

The original wallet showed ₹2,055.93 clearly. What it didn’t do was give that number anything to do. The biggest improvement in this project wasn’t a new screen; it was the nudge that asks, “Who’s driving it now?” Sometimes the most useful design move is asking the right question at the right moment.

The original wallet showed ₹2,055.93 clearly. What it didn’t do was give that number anything to do. The biggest improvement in this project wasn’t a new screen; it was the nudge that asks, “Who’s driving it now?” Sometimes the most useful design move is asking the right question at the right moment.

Trust is designed in small pieces

Moving money makes people cautious. No single feature fixes that. Instead, trust comes from many small details: a verified tag on the recipient, “Balance after” before confirming, “₹0 · Free” stated clearly, a 10-minute undo, and a receipt to share. Each one answers a doubt before the user has to ask it.

Moving money makes people cautious. No single feature fixes that. Instead, trust comes from many small details: a verified tag on the recipient, “Balance after” before confirming, “₹0 · Free” stated clearly, a 10-minute undo, and a receipt to share. Each one answers a doubt before the user has to ask it.

Designing for two users at once

Every screen had two people behind it: the one sending and the one receiving. Features like notes, requests, and a shared history exist because the receiver’s experience matters as much as the sender’s, especially when the receiver is a parent who just wants to charge and go.

Every screen had two people behind it: the one sending and the one receiving. Features like notes, requests, and a shared history exist because the receiver’s experience matters as much as the sender’s, especially when the receiver is a parent who just wants to charge and go.

Say no to the big idea, at least at first

A full shared family wallet was tempting. But transfers solved the core problem with far less complexity. Starting small kept the flow focused, and the bigger idea became a supporting feature rather than the main one.

A full shared family wallet was tempting. But transfers solved the core problem with far less complexity. Starting small kept the flow focused, and the bigger idea became a supporting feature rather than the main one.

What’s next

Test with real families

This design is based on my own experience. The next step is usability testing with families where one person pays and another drives, especially older parents, to see if the nudge feels helpful or intrusive and if the flow is clear for less tech-savvy users.

This design is based on my own experience. The next step is usability testing with families where one person pays and another drives, especially older parents, to see if the nudge feels helpful or intrusive and if the flow is clear for less tech-savvy users.

Measure what matters

If this shipped, I’d track:

If this shipped, I’d track:

How much dormant balance gets transferred after the nudge

How much dormant balance gets transferred after the nudge

How often users choose “Remind me in 30 days” versus sending

How often users choose “Remind me in 30 days” versus sending

How often undo is used (a high rate could signal confusion)

How often undo is used (a high rate could signal confusion)

Whether receivers top up less often on their own

Whether receivers top up less often on their own

Fully design Family Circle

Family Circle appears in the activity log, but it deserves its own flow: adding members, setting spending limits, deciding who can see what, and what happens when someone leaves the circle.

Family Circle appears in the activity log, but it deserves its own flow: adding members, setting spending limits, deciding who can see what, and what happens when someone leaves the circle.

Smarter nudges

Right now, the nudge is triggered by idle balance. It could get smarter: alert the receiver when their balance is low, suggest a recurring monthly transfer, or remind the sender when a family member charges often.

Right now, the nudge is triggered by idle balance. It could get smarter: alert the receiver when their balance is low, suggest a recurring monthly transfer, or remind the sender when a family member charges often.

Edge cases and compliance

Wallet-to-wallet transfers come with real-world constraints, like transfer limits, KYC requirements, and fraud prevention. These would need to be validated with ChargeZone’s product and compliance teams before this becomes more than a concept.

Wallet-to-wallet transfers come with real-world constraints, like transfer limits, KYC requirements, and fraud prevention. These would need to be validated with ChargeZone’s product and compliance teams before this becomes more than a concept.

More case studies.

Turning Spira’s onboarding data into product value

How one onboarding answer could help Spira understand its users, while giving every user a more relevant path to their first post.

Oct 22, 2026

Simplifying a New Financial Payment Model

Simplifying an unfamiliar checkout model where users lock a refundable deposit instead of paying upfront, making it easy to understand and trust.

Oct 22, 2026

back