Stake Casino – generel debat (side 10)

Hello, feel free to describe your situation and I will try to advise you on whether you should file a complaint. 

If you have any problems, feel free to use a translator for your reply.

Let me know what happened.

The promo code post also said the bonus is available from Bronze and that you can activate it as many times as you want. Activate it here stake.com mirror: stake1170.com

Have you already used it yourself? Any nice winnings?

Hello, I am a Platinum 2 member on Stake (Username: amitnain1199). I am facing a serious issue with a missing withdrawal of ₹47,499.05 from January 30, 2026.

Stake support provided UTR: 603033357401, but my bank (IndusInd Bank) has officially investigated and confirmed that no such funds have reached their gateway (Bank Ref: 82338683).

Despite being a high-level VIP player, live support (JelenaVE) keeps telling me to 'patiently wait' due to an 'overloaded workflow' without giving any technical trace from their payment processor, Silkpay. I have already submitted my bank statement as proof. I am posting here to get a faster resolution as the bank confirms the transaction never arrived.

It's good that you provided the bank statement because when they have this, they can't argue, right?

Unfortunately, we are unable to investigate before the 14-day time frame passes, so I really hope it will be resolved before that.

Please keep us informed about how it goes. Could you?

Thanks Romi for the support. Stake Finance (JelenaL) has already escalated my case after I provided the unlocked PDF Bank statement. I will keep you posted once I get their final reply

I hope that everything will be resolved soon, then.

We'll wait for your updates here.

Jeg vil gerne indgive en klage til Casino Stake Argentina. De har blokeret min konto for indbetalinger i kryptovaluta. Årsagen er, at jeg har givet 98% af oplysningerne, inklusive billeder og mine personlige data, til verifikation. Jeg har mistet adgangen til kryptokontoen af ​​en eller anden grund, og de beder om de sidste tre indbetalinger fra den konto, som jeg ikke længere har. Det er alt sammen meget kompliceret. Jeg har investeret penge på den Stake-konto, penge jeg gerne vil hæve nu, men jeg kan ikke. Jeg har tilbudt at give billeder, videoer og meget personlige oplysninger for at løse dette, men de vil ikke lade mig det. Jeg er nødt til at hæve pengene.

Jeg vil have den løsning for de penge, jeg har indsat og på den konto, og så kan de gøre, hvad de vil med kontoen.

Mit brugernavn på Satake Argentina:

Hello, I see you made the official complaint request, so from now on our colleagues will take care of you.

I understand the situation is complex; therefore, I will avoid speculation or guesses. Just in case you would appreciate a little talking, go ahead. We'll try to respond, if possible.

I hope your complaint goes well.

is stake give refunds for bug issues that caused a loss

The best option would probably be to contact the casino directly and describe the bug in detail, including what exactly happened and which game you were playing.

Could you briefly explain what kind of bug you encountered? Have you already reported it to the casino and asked what options you have or whether anything can be done about it?

The Issue: A client-side frontend input-mask race condition and event-listener glitch occurring specifically on Linux using the Wayland compositor and Mozilla Firefox.

What Happened: When attempting to clear an existing value and rapidly type a decimal amount (such as entering $0.23) on Stake's bet input element, the input mask swallows the initial decimal point (.) keystroke. Instead of formatting as 0.23, it strips the dot and multiplies/concatenates the input into an unintended $23.00 wager before the user has a chance to correct it.

Evidence: Two distinct video recordings were captured—one isolating the bug occurring exclusively on Stake's wager input field, and a control video proving that Firefox and the Linux/Wayland system environment handle decimal delimiters normally across other websites and standard web forms, confirming the bug is strictly tied to Stake's frontend code.

Previous Reports & Casino Response

Live Support Interaction: The issue was initially reported to Stake's live support along with the video evidence. However, support agents dismissed the proofs with generic boilerplate responses, blamed browser quirks, and refused to investigate or escalate the matter.

This is much more useful than a general description because you’ve documented a reproducible sequence and also recorded comparison videos.

I’d just be a little careful with presenting the exact technical cause, such as a race condition or event-listener bug as confirmed unless Stake’s developers have actually verified that. But if entering 0.23 can repeatedly turn into 23.00 specifically on Stake while the same input works normally elsewhere, then the behavior itself is definitely worth investigating.

Since live support apparently didn’t escalate it, I’d try to get the videos and exact reproduction steps in front of Stake’s technical team rather than continue debating it with frontline chat.

If this bug actually caused a real wager to be placed for a much larger amount than you intended, mention that clearly as well, because then it becomes more than just a UI bug report and there may be a concrete disputed loss to review.