Hello everyone,
I want to share a serious issue I experienced on Stake.com, which completely stems from a technical infrastructure error on their side. Since their support team has been absolutely unhelpful, I am posting this here to raise awareness and warn everyone.
Yesterday (June 30, 2026), during the live match between France and Sweden, I suffered an unfair financial loss due to a technical system glitch. Here are the details of the incident:
📊 Account & Bet Information
Username: newyear
Bet ID: sport:612731642
Disputed Amount: €652.17
Event: France vs. Sweden (Market: Ousmane Dembélé to score)
🚨 Incident Summary & Technical Issue
During the live match, I attempted to place a bet of €652.17. While the coupon was processing, the system generated a "Bet Rejected" error.
Because the bet was rejected, the €652.17 stake was immediately credited back to my active account balance.
Since the platform explicitly stated that the wager failed and returned my funds, I closed the website, confident that no active bet was running.
After the match concluded, I logged back into my account only to discover that Stake.com had retroactively and automatically approved the previously rejected coupon without my consent or knowledge. Since the bet lost, my balance was wiped out.
⚠️ Grounds for Complaint
Lack of User Consent: The system officially told me "This bet was not placed" and refunded my money. It was impossible for me to monitor, manage, or cash out a bet that I was told did not exist.
Unfair Practice: Despite contacting Stake support, they refuse to acknowledge this blatant system lag and technical glitch. Reviving a rejected coupon after the match progression is completely unacceptable.
I have already submitted an official complaint to the Curacao Gaming Authority (CGC) demanding an investigation into their system logs for this Bet ID.
Has anyone else experienced a similar glitch on this platform, or do you have any advice on how to proceed? Be very careful with live betting on Stake.
https://bitcointalk.org/index.php?topic=5587293.0
