How to track UPI spending across GPay, PhonePe and Paytm

Take a salaried person earning ₹40,000 a month who makes 90 UPI debits averaging ₹180. That is ₹16,200, or 40.5 percent of salary, through a channel that produces no receipt anyone keeps. The household is illustrative; the arithmetic is the point, and you can redo it on one month of your own statement.

Split the 90 payments by size. The ten largest average ₹650 and add up to ₹6,500. The remaining 80 average ₹121 and add up to ₹9,700. So the payments that feel like spending are 40 percent of UPI spend and the ones that feel like nothing are 60 percent. Ask this person what they spend on UPI and they will say something near ₹6,500: not a guess, a faithful report of the part they can see.

Method one is the spending chart inside your payment app. It is accurate for what it sees, and it sees only that app; most people run two or three. Give the household a 55/35/10 split across three apps: the main app's chart reports ₹8,910 of a real ₹16,200, with a confident category breakdown, and nothing on the screen suggests ₹7,290 is missing. A chart of the wrong total is worse than no chart, because it answers the question and closes it.

Method two is the bank statement. It is the only complete record, because every UPI debit from every app settles through the same account. Its weakness is naming. A UPI row carries the counterparty's virtual payment address, often a mobile number with a handle, or a registered entity name that looks nothing like the shop sign. Read 90 rows and perhaps 36 are recognisable on sight. The other 54 are amounts with no merchant attached: you can total them, you cannot act on them.

Method three is logging each payment yourself at the moment you pay. It names everything and sees every app, and works for exactly as long as you keep doing it. Ninety entries at twenty seconds is 30 minutes a month, 360 minutes a year, affordable until it is spread across 90 separate interruptions. It stops in the first busy week, and the month it stops is the month with the most to see.

The fourth method starts from a fact the other three ignore: your bank already tells you about every UPI debit, as it happens, in a message carrying the amount, the date and the counterparty's address. It does this whichever app you paid from, because the app only initiates the payment; the bank executes it and sends the alert. Collect the alerts and you have the statement's coverage with no export and no typing.

Three things make this tracking rather than a second inbox. It has to read both channels the bank uses, SMS and email, and know that an SMS and an email about the same ₹121 are one payment. It has to need nothing from the account: no bank password, no UPI PIN, no linked login, because reading a notification requires none of those. And it has to solve the naming problem by matching each address against a database of who that address is.

Unyfy reads your bank and card transaction emails and, on Android, your bank's transactional SMS alerts to log every UPI debit across every payment app with no manual entry and no bank password or UPI PIN, then matches each address against a merchant database of about 10,000 entries and drops any debit it has already seen through the other channel. That is the whole mechanism. SMS reading is on Android. On iPhone, use the web app at app.unyfy.co.in, which reads your bank's email alerts and statements.

The method sees all 90 payments, and the database turns each address it knows into a merchant name.

A list of 90 rows is a starting point. The month-end review takes fifteen minutes and produces three lists.

The first is the ten largest payments, named. This is the ₹6,500 you half-knew. Its value is calibration: if the ten largest are ₹6,500 and the total is ₹16,200, your instinct undercounts by ₹9,700, a number worth writing on the wall.

The second is every UPI AutoPay mandate, the payments that never asked. Four small ones at ₹149, ₹199, ₹299 and ₹99 come to ₹746 a month, 4.6 percent of UPI spend, which feels like nothing. Over a year it is ₹8,952. Each was a decision once, on one day, and has run on that day's reasoning since. The question is not whether it is expensive but whether the reasoning still holds.

The third is the repeated small payment. The illustrative version is ₹60 twice a working day, a tea and a snack or a short ride each way. Over 22 working days that is ₹2,640 a month and ₹31,680 a year, on nobody's mental list because no single instance is an expense. This is the payment the page is about: the one memory cannot hold and logging cannot sustain, visible only because something counted it 44 times.

Tracking fixes not knowing. It does not fix knowing and being unable to act.

If you already know your UPI spend within a few hundred rupees, better tracking tells you what you know with more decimals. The real issue may be that ₹16,200 of essential small spending on ₹40,000 leaves ₹23,800 for rent, EMIs and everything else. That is an income problem or a fixed-cost problem, and a tracker will not turn it into a spending problem.

If one month is dominated by a single large UPI transfer, a deposit or a hospital bill paid in one go, the total says nothing about your habits. A ₹25,000 transfer on top of the usual ₹16,200 makes the month look like a crisis, and reading it as one means cutting the ₹60 tea in response to a hospital bill. Take it out and review the rest.

And if the tracking has become the activity, a careful spreadsheet whose totals never change a decision, the 30 minutes a month is a cost with no return. If no number it produced has changed something you did in three months, stop or switch.

Five questions decide whether any tracker, or your own statement method, is worth the effort.

Does it need your UPI PIN or bank login? It should not. The PIN authorises payments; tracking reads them afterwards. A tool that needs the PIN to draw a chart has confused two jobs.

Does it see every app? Ask where the data comes from. 'This app's transactions' means that app's share. 'The bank's alerts or statement' means complete by construction.

Does it name merchants, and how? Ask what it does with an address it does not recognise: showing the address is honest, guessing a category is not.

On Android, what does the SMS permission cover? Reading transactional SMS is how a tracker sees the bank's alerts, and the permission that allows it is broad. Read what the tool says it reads, what it does with messages not from a bank, and whether messages leave the phone. A vague answer is the answer.

Can you export? Your 90 rows a month are yours. A tracker that cannot hand them back as a file has made itself a dependency, and the day it shuts down the history goes with it.

The month-end review on this page needs three lists, and two of them, the mandates and the small repeat, are exactly what memory and a single payment app miss. Because the app reads the bank's own alerts rather than any payment app's history, every UPI debit lands in one list whichever app started it, with an SMS and an email about the same payment counted once.

For the second list, the Fixed Expenses screen on Pro predicts what next month is already committed to and keeps a Subscriptions list: each recurring subscription with its amount and whether it is due or paid this month. For the third, handles are matched against a merchant database of about 10,000 entries, so repeated small payments to one address collect under one merchant name and the daily tea or ride shows up as a pattern instead of scattered rows.

It never asks for your bank password or UPI PIN, and every payment is one you authorise. You cancel a mandate in the UPI app that set it up.

Install Unyfy on Android, or on an iPhone use the web app at app.unyfy.co.in, which reads your bank's email alerts and statements.