BigClash Withdrawal – Problems and solutions (Video)
I want to lead with the outcome that matters most: BigClash paid. I submitted a withdrawal of €65 and the funds arrived in my Mastercard account the same week. That result is the foundation of this article, and everything else I describe here should be read with that outcome already in mind.
Getting to that confirmed payout involved one significant detour, and understanding that detour is essential for any BigClash player who plans to cash out.
The Wagering Reguirements
BigClash requires a 1x wager on your deposit before the withdrawal option becomes active. Put in €100 and you need to wager €100 in real-money bets before you can cash out. I completed this across my gameplay sessions and my balance stood at €65.50 when the requirement was met.
The framing matters here. Without any bonus, casinos commonly require 2x or 3x wagering before permitting a withdrawal. Accept a bonus and the industry standard jumps to somewhere between 30x and 40x. A 1x condition with no bonus is as low as this requirement realistically gets, and it puts BigClash on the right side of the industry comparison. The one practical note is that BigClash should make this visible in the cashier during the deposit process. I found out about it only after completing my first gaming session, when the cashout option was not yet available. Showing it upfront would remove that confusion entirely.
Trying the PWA Cashier First
After clearing the wagering requirement, I opened the BigClash PWA mobile app and navigated to the cashier to submit the withdrawal. The cashier entered an infinite loading state. The screen loaded indefinitely without displaying anything usable. After several seconds, the interface also stopped responding to input. Tapping back, tapping navigation items, tapping anywhere on screen produced no reaction. The app was frozen on a permanently loading cashier with no way out except a full restart.
I restarted the PWA and tried again. The same thing happened. Restart after restart produced the same result: the cashier loads forever, the interface locks up, and the only option is another restart. Deposits and withdrawals are completely inaccessible within the PWA environment. This is not a case of the cashier being slow or occasionally buggy. It is broken in a consistent and reproducible way. The failure is documented in the cashier issue screen recording.
Players who intend to cash out at BigClash need to know this before they install the app, not after they have spent time trying to get a frozen screen to respond.
Switching to the Browser
The workaround is straightforward: use the mobile browser for all cashier operations. I opened Safari, navigated to bigclash1.com, logged in, and went to the withdrawal section. Everything worked correctly. The cashier loaded instantly, the interface was fully responsive, and the steps to submit a withdrawal were clear and quick to complete.
I selected Mastercard, the same card I used for the deposit, entered €65, and confirmed the request. The submission completed without any errors or unexpected prompts. No verification was requested during the process, no additional confirmation steps appeared, and the transaction went through cleanly. The successful withdrawal is shown in the website withdrawal screen recording, and the withdrawal confirmation email is in the withdrawal email screen recording.
After Submission
Following the submission, the withdrawal moved into a review or pending status. This is a standard part of the cashout process at virtually every online casino. BigClash does not display an estimated processing window at the point of submission, which means you submit the request and then wait without a clear sense of how long that wait will be. Adding a simple expected timeframe to the confirmation screen would make that waiting period significantly less ambiguous.
The funds did arrive
The correct amount landed in my account without any need to contact support or chase the payment. No further documentation was requested after the withdrawal was submitted. The process completed correctly once it was routed through the browser.
What BigClash Needs to Do
The PWA cashier issue is the most urgent thing on the list. Players are being directed toward a mobile app that cannot perform the most financially critical functions of a casino platform. There is no notice in the app warning users about this limitation, which means every player who installs BigClash and tries to deposit or withdraw through the PWA will hit the same infinite loading loop with no explanation.
Fixing the cashier, or at minimum adding a clear in-app notice directing users to the browser for financial operations, should be the immediate priority. The deposit fee inconsistency is a second important fix: showing a €4.50 charge on one attempt and nothing on the next, with no explanation for the difference, is the kind of thing that erodes confidence in a platform’s payment transparency.
The Verdict
BigClash paid out. The withdrawal completed, the amount was correct, and no obstacles appeared between the submission and receiving the funds. For players who go through this process knowing about the PWA cashier limitation and using the browser for financial transactions, the experience from deposit to payout is workable.
The platform has real strengths: clean website navigation, a fast deposit flow when it works correctly, genuinely favourable wagering conditions, no identity verification friction, and a cashout that delivers. The problems are real too and cannot be papered over. But the fundamentals, putting money in and getting money back out, work. That is the thing that ultimately matters most, and BigClash passed that test.
