I deposited an amount of ₹700 into my Parimatch account (Player ID: 245263***) on 4 February 2026 via UPI. Without asking for my consent, Parimatch automatically converted this entire deposit into a bonus balance. Because of this, the money is locked in the bonus section, and I am neither able to withdraw it nor use it freely to place normal bets, especially on cricket matches as I intended. I tried to contact Parimatch support in every way I could find, but there is no clear or direct way to reach a real agent. Their customer support only shows preset answers to selected questions and there is no proper live chat where a person actually assists the customer, so my specific issue remains unresolved and I have not received any individual response or solution. I consider it unethical that my deposit was converted into a bonus without my explicit permission, and that I am now unable to use my own money as I wish. I request that my ₹700, which is currently locked as a bonus, be immediately converted back into my main Parimatch balance so I can use it for betting on cricket matches, or otherwise released in a way that allows me to use or withdraw it freely. I also ask Parimatch to review this practice so that deposits are not turned into bonuses without clear and informed customer consent in the future.
I am using Parimatch from India, and on February 3, 2026, my deposited balance was automatically converted into bonus balance without my consent. I deposited 1,000 INR via UPI as real money, but instead of remaining in my main balance, the entire amount was moved to the bonus section. This issue is ...
I am writing about a problem I experienced with the Parimatch deposit section. On 07/12/2025, I deposited ₹1700 via UPI. The amount was successfully d...
I am writing regarding an issue with my Parimatch account where my deposited amount has been blocked without any explanation. On 28/12/2025, I made a deposit of 1,500 via UPI from India into my Parimatch account, and shortly after, the amount suddenly became blocked and inaccessible. There was no pr...
Comments (6)