@shraddha First time saw behind the scenes.
6 Likes
Millions of trades, thousand lines of codes & hundreds of passionate dedicated team.
Engineered for Traders, Designed for Performance and Proudly Built in India 
4 Likes
And a muted team silent on the feedbacks, follow-ups.
Hi @sri1647 Well we have mentioned this earlier as well - we do collect all feedbacks and suggestions from our users. They are discussed, lined up for development post consideration and on release cycles. Many release that Dhan does require participation in mock trading, exchange audits, and more processes.
To expect every suggestion to get implemented and immediately, is something that can’t happen. As we build and scale, we ensure we continue to listen to our users and deliver experiences from time to time. We have been doing that for nearly last 4 years and will continue to do.
Hi Sir, two points for your consideration -
- Your team works only on selective feedback, well known based on my 2 years experience with dhan. Your team focuses only on complex functionalities, leaving aside all the basic features.
- Your team don’t know the difference b/w issues and feedbacks. They won’t act even after committed deadlines. The margin summary, positions data issue on the home screen are the prime examples for this.
Moreover, no sensible person expects the immediate implementation of the feedbacks but there are many such feedbacks, in my case especially, which didn’t shape since the past 1 or 2 years.
All the things like listening to users etc., are just cover ups but every trading app does only what is in its and its team mind.
1 Like
@sri1647 I believe, you wrote earlier that you shifted out of Dhan. Can you please explain what are the issues that are bothering you so much?
Not true. Check out my profile and feeds from last year, whatever I wished was delivered and bugs were fixed. Not saying that it is flawless now, but it is much better than what I started with.
Same here. I have my own thread running on this forum where i share minor bugs and sometimes issues too. Those have mostly been fixed or partially fixed. Several times I also get a call from dhan team to get more details. I believe most of Dhan team knows my name now 
Ya even i agree on this. Few times even i have told them “ki ye issue nahi hai feature request hai”
The way you ask this na sometimes make me feel you also work with Dhan that’s why i tagged you on that post that day 
1 Like
Hi @sri1647
We’ve had multiple discussions around your suggestions and feedback, including inputs from several stakeholders. As mentioned earlier, while we value your input, it is not possible to implement every suggestion.
We’ve always acknowledged your contributions respectfully. However, I must point out that repeated posts criticizing unimplemented feedback—despite receiving responses—can be demoralizing for other community members, the team, and does not help us move forward productively.
As I mentioned on our call, if any of your suggestions are taken up, I will personally reach out to you and update you on the progress.
Like many of our community members, you are an important and integral part of our journey. But for us to continue building positively together, feedback must be shared constructively without repeatedly revisiting the same points.
1 Like
That’s what I am saying they are selective.
Hi Rahul, you had stopped responding to me after our initial 1-2 conversations. Moreover the things I pointed out are issues, not feedbacks FYI. Moreover, not even a single issue is rectified till now. So don’t tell me a generic sentence that every feedback can’t be implemented.
The main issue with dhan team is you people take feedbacks very well and throw them in the dustbin later. Your team won’t share a single update even if the feedback is dropped.
The margin summary issue highlighted four months ago is not rectified till now whereas the commitment from your team is 2 weeks.
Dhan team takes selective feedback and work for only select set of users.
Hmm, let’s all relax here. I understand you are very frustrated @sri1647 and one piece of advice that I can give you is, try the top 20 brokerages each for several weeks, and a few months later you are likely to end up back at Dhan again, or maybe Groww. My personal experience.
The positive side of your issue is, you get faster order fills at Dhan so your trade costs are better than anywhere else.
1 Like
Haha, no bro. I’m a non-paid actor here. 
1 Like
Hi @sri1647 We have all your 3 feedbacks with us, the first one is extremely difficult as exchanges treat F&O as a single segment, and margin differentiation is way to difficult to achieve within that segment, hence this is parked.
On P&L for open positions - you can already see it on individual positions, but to show that separately isn’t something we are picking up anytime soon. We have nearly ~10 Lac users who are accustomed to a certain way of seeing P&L, making a mandatory change to this is a experience risk for us.
Third, your feedback on TradingView charts has been already shared with the TV team and our team has followed it up. Until the same is updated by the TV team, we will have to wait until then.
Hope this helps you. Once again, we have everyones feedback and also our own ways and reasons to pick it up or park it. Asking the same multiple times, would definitely lead for you get to get frustrated - which neither you or we want. As a platform we have to ship things keep in mind many many things.
Hi Sir,
Based on your reply I can clearly see that your team didn’t understand the requirements at all and there is a huge communication gap.
-
F&o pnl in margin summary - my requirement is simple to display the f&o pnl in margin summary. Almost all brokers display it for better visibility of available funds for trading. I haven’t asked any differentiation between futures and options. It’s been 4 months since I spoke with your team and I have been informed the entire margin section is going for a revamp and it is in development and now you are saying it is parked.
Let’s say that it is parked, wasn’t it responsibility of your team to inform the same to me after these many follow ups? -
Your understanding is completely wrong. My query is wrt the display in the home screen. The wordings say open positions but the result you display is of total pnl.Moreover, many brokers show the realised and unrealised pnl separately on the mobile app as well.
Other feedbacks like search icon in order window, sensex contracts search etc., are ignored completely.
In nutshell, it clearly shows your team is not concentrating on the feedbacks and they are just listening for namesake.
Based on this video and past few videos and change in name.
I have a strong feeling that Dhan (Raise) is planning on IPO soon!
In that case i need community quota or existing user quota in the IPO.
1 Like
I don’t think Dhan is going public before it has multiple revenue streams.
Just in case you did not know, Dhan (aka Raise Securities) is part of Raise Fintech Ventures Private Limited. Which has other finance related tie ups and affiliate companies too.
See:
And also see:
https://blog.raiseholding.co
I was talking about Raise Fintech eyeing an IPO not Raise Securities.
Just a speculation.
1 Like
Yes @amish I know. Even before Dhan launched, Raise had a website, with insurance, credit, etc.
Btw, I’d be happy if Raise launched LAS and LAMF.
Having used Dhan for a few weeks, one thing I’ve noticed is a critical lack of clarity in the responses to most API-related issues; for instance, there is significant confusion around the latest stable version of the dhanhq package, where community forums cite 2.0.2, your customer service recommends 2.1.0 (which users report has been yanked without a clear response), and the documentation sometimes references an unavailable 2.2. It would be greatly beneficial to have an official, definitive source for version information and changelogs. Furthermore, clarity is needed on whether packages like Tradehull are official and supported by your team or are community-maintained, as this directly impacts where developers can seek help. My two cents are not to say you aren’t helping, but that the support often lacks the specific, consistent context required for developers to work effectively.
1 Like