Scan any UPI QR, pick a spending wallet, and see the warning if you're over budget - then pay in your own UPI app with your own PIN. No bank linking, no SMS reading, no analytics companies. A notebook for your spending, made in India.
No reviews yetBe the first to leave a review for Dhyan Pay
Maker
π
Namaste, Product Hunt.
I built Dhyan Pay because I kept opening GPay by reflex. UPI made paying so frictionless that my budget only existed at the end of the month, as a post-mortem. Every budgeting app wanted to fix this by reading my SMS or linking my bank more access, more automation, less thinking. I wanted the opposite: one deliberate second put back in front of the payment.
So it works like this: scan the shop's QR in Dhyan Pay, pick which wallet this comes from Food, Transport, whatever you've set up and see where the month stands before you pay. If you're over the limit you set yourself, it says so. Then it hands the payment to your own UPI app with the amount filled in; you pay with your own PIN like always, come back, and confirm. The app keeps score. That's all it does.
The part I care most about: it cannot see your money. Not "we promise not to look", but it has nothing to look at. No bank connection, no balance, no SMS permission, no PIN, ever. Payee UPI IDs are stored only as fingerprints, never readable. There's no analytics company in the app or on the site. The only data is what you chose to type; it exports to CSV any time, and "delete" means deleted instantly, nothing retained.
Honest limits, so nobody's surprised: it's not a payment app. Your UPI app moves the money; Dhyan Pay is the notebook in front of it. On Android the scan-to-handoff flow is smooth (GPay, Paytm, and CRED tested on real phones); on iOS you record payments more manually. It's a PWA - nothing to install from a store; add it to your home screen, and it behaves like an app.
It's free, there are no ads, and it's run by one person (me) in my own time. The help desk inside the app comes straight to my screen.
What I want from you: if you try it and stop using it, tell me what stopped you. That is worth more to me than an upvote. And if the pause actually changed what you spent, I'd love to hear that too.
Report
@hariprasad_k3 Does not linking the bank also protect people from the UPI scams that work by asking for exactly that access?
Report
Maker
@peterdigitalis I consider these points tangential. UPI scams typically involve phishing through custom links.
Apps such as Fold or other payment trackers monitor spends by retrieving transaction logs from your bank, with clear access permissions you can withdraw at any time.
Dhayn Pay aims to revive mindful spending habits by encouraging users to review their spend wallet (much like the older times) before each purchase.
If you save 100 bucks a day because you checked the Dhayn Pay wallet and chose not to spend, that is a success.
Report
@hariprasad_k3Β The fraud category RBI is most worried about is not link based. In authorised push payment fraud the victim initiates the transfer themselves, so no custom link ever has to exist.
RBI said in its 2025-26 annual report it would explore "certain frictions in digital payment processes", and its April discussion paper proposed a one hour delay on payments above βΉ10,000 before the money lands.
A central bank is proposing to slow payments down because speed is what the fraud runs on.
That is your mechanic. The pause before the spend is not tangential to fraud. It is the same instrument, built for a different reason.
Report
Maker
@peterdigitalisΒ I think you got it right. While the intent of the app wasn't to target reducing the fraudulent UPI transactions, the pause before pay definitely introduces a layer of check before the payment is made...
So a happy coincidence indeed!
Report
@hariprasad_k3Β Then it is worth keeping on purpose rather than by accident. The friction a central bank is proposing to legislate, you get for free, because the product already wants the user to stop and look before they spend. That is a good position to be launching from. Good luck with it.
Namaste, Product Hunt.
I built Dhyan Pay because I kept opening GPay by reflex. UPI made paying so frictionless that my budget only existed at the end of the month, as a post-mortem. Every budgeting app wanted to fix this by reading my SMS or linking my bank more access, more automation, less thinking. I wanted the opposite: one deliberate second put back in front of the payment.
So it works like this: scan the shop's QR in Dhyan Pay, pick which wallet this comes from Food, Transport, whatever you've set up and see where the month stands before you pay. If you're over the limit you set yourself, it says so. Then it hands the payment to your own UPI app with the amount filled in; you pay with your own PIN like always, come back, and confirm. The app keeps score. That's all it does.
The part I care most about: it cannot see your money. Not "we promise not to look", but it has nothing to look at. No bank connection, no balance, no SMS permission, no PIN, ever. Payee UPI IDs are stored only as fingerprints, never readable. There's no analytics company in the app or on the site. The only data is what you chose to type; it exports to CSV any time, and "delete" means deleted instantly, nothing retained.
Honest limits, so nobody's surprised: it's not a payment app. Your UPI app moves the money; Dhyan Pay is the notebook in front of it. On Android the scan-to-handoff flow is smooth (GPay, Paytm, and CRED tested on real phones); on iOS you record payments more manually. It's a PWA - nothing to install from a store; add it to your home screen, and it behaves like an app.
It's free, there are no ads, and it's run by one person (me) in my own time. The help desk inside the app comes straight to my screen.
What I want from you: if you try it and stop using it, tell me what stopped you. That is worth more to me than an upvote. And if the pause actually changed what you spent, I'd love to hear that too.
@hariprasad_k3 Does not linking the bank also protect people from the UPI scams that work by asking for exactly that access?
@hariprasad_k3Β The fraud category RBI is most worried about is not link based. In authorised push payment fraud the victim initiates the transfer themselves, so no custom link ever has to exist.
RBI said in its 2025-26 annual report it would explore "certain frictions in digital payment processes", and its April discussion paper proposed a one hour delay on payments above βΉ10,000 before the money lands.
A central bank is proposing to slow payments down because speed is what the fraud runs on.
That is your mechanic. The pause before the spend is not tangential to fraud. It is the same instrument, built for a different reason.
@peterdigitalisΒ I think you got it right. While the intent of the app wasn't to target reducing the fraudulent UPI transactions, the pause before pay definitely introduces a layer of check before the payment is made...
So a happy coincidence indeed!
@hariprasad_k3Β Then it is worth keeping on purpose rather than by accident. The friction a central bank is proposing to legislate, you get for free, because the product already wants the user to stop and look before they spend. That is a good position to be launching from. Good luck with it.