A failed deposit is rarely a banking problem. On mobile, the payment request travels through the Casushi app or browser, the handset’s operating system, the card network and the processor before it reaches the cashier, and any link in that chain can stall it. The frustrating part is that most failures return a generic error, so the screen tells you nothing about which link broke. Working through a fixed checklist beats guessing, because it moves from the cheapest checks to the most disruptive ones and stops you reinstalling an app that was never the issue.
The first suspect on an iPhone is often not the Casushi app at all. Low Power Mode throttles background activity, and receipt validation for in-app purchases runs in the background, so a deposit can time out while the phone is trying to save battery. Turn that setting off, retry once, and note the result before changing anything else. On Android, where Casushi does not publish a standalone APK file, the equivalent culprits are browser state, Play Protect interference and stale app permissions. Apple users who download the Casushi app from the App Store and Android users who access the Casushi site through a mobile browser are dealing with different failure points, which is why the fixes further down are split by platform.
The checklist below runs in order: quick pre-checks, then the Low Power Mode fix for Casushi iPhone users, then cache, permissions and browser fallbacks, and finally the details Casushi support needs if nothing works. Keep a note of the exact time, amount and payment method for each attempt. That record turns a vague complaint into a traceable ticket, and it also stops you repeating a deposit that may already be pending at the processor. This website operates as an information page only and does not process payments or hold accounts, so anything account-specific has to go through Casushi’s own support channels.
Quick pre-checks before you retry a Casushi deposit
A failed deposit on Casushi is rarely a single dramatic fault. In most cases the transaction is stopped by one of five mundane conditions: a payment method limit, a balance shortfall, a mistyped card or wallet detail, a dropped connection, or an out-of-date app. Working through them in order takes about four minutes and resolves the majority of errors before you ever need to open a support ticket. Treat the list below as a sequence, not a menu. Change one variable at a time and retry after each step, otherwise you will not know which fix actually worked.
1. Check the payment method limit first. Every card issuer and e-wallet applies its own ceiling to gambling merchants, and that ceiling is often lower than the limit on ordinary retail spending. A GBP 20 deposit may clear while a GBP 200 deposit on the same card is declined without explanation. Log into your banking app or wallet and look for transaction limits, gambling blocks, or “card controls” toggles. Some issuers decline the first attempt and approve the second as part of fraud screening, so a single retry after a decline is reasonable. A second consecutive failure points to a genuine block rather than a glitch.
2. Confirm sufficient funds, including any hold. Pending authorisations from earlier attempts can sit on your available balance for up to five working days. If you tried a GBP 50 deposit three times, your issuer may be holding GBP 150 even though nothing reached Casushi. Check the available balance, not the ledger balance, and wait for holds to clear before retrying. This is also the point to confirm the deposit amount sits inside the minimum and maximum range shown in the cashier.
3. Re-enter the card or wallet details by hand. Autofill is a common culprit. An expired expiry date, a postcode that no longer matches the billing address, or a saved wallet handle tied to an old phone number will all produce a generic decline. Type the sixteen digits, the expiry, and the CVV manually. For e-wallets, confirm the wallet account is verified and funded rather than linked to a bank account that is itself awaiting verification.
4. Test the connection properly. A page that loads is not the same as a connection that can hold a payment session open. Switch from Wi-Fi to mobile data, or the reverse, and retry. Disable any VPN, since geo-checks on the cashier can fail silently behind one. If you are on a public network or a hotel captive portal, move to a private connection before trying again.
5. Confirm you are on the current version. Apple users should download the Casushi app from the App Store and let it update; Android users typically access the Casushi site through a mobile browser, so clear the browser cache instead. Note that Casushi does not publish a standalone Android APK file, so any APK you find elsewhere is not an official build and should not be installed. On either platform, pull up the mobile lobby and check that the welcome offer and cashier panels render correctly. If the lobby itself looks stale or partially loaded, the version or cache is the likely problem, not your payment method.
If all five checks pass and the deposit still fails, the cause sits deeper in the device or the account. That is where platform-specific fixes come in, starting with the setting most iPhone owners never think to look at.
Why Low Power Mode on your Casushi iPhone blocks deposits
Low Power Mode is the single most overlooked cause of a failed deposit on the Casushi iPhone app, and it almost never appears in generic troubleshooting lists. Apple’s battery saver throttles background activity across the system, including the StoreKit receipt validation calls that the Casushi app fires when you confirm a payment. If that validation does not return a signed receipt promptly, the cashier treats the transaction as unconfirmed and the deposit is declined or left pending. The money usually stays with your payment provider and is released back, but the deposit never lands in your balance.
The mechanism matters because it explains the symptom pattern. Deposits made with the phone plugged in and charged often succeed; the same deposit fails on battery at 18%. Casushi supports Face ID logins and a one-tap cashier flow, so the receipt check runs in the background while the interface moves on. Under Low Power Mode, background networking is batched and delayed, and the app’s request can time out before the receipt arrives. Third-party wallet redirects, which leave the app and return through a browser handoff, are hit hardest because the return trip competes with throttled background refresh.
| Fix | What it changes | Time cost | Trade-off |
|---|---|---|---|
| Turn off Low Power Mode in Settings > Battery | Restores normal background receipt validation for the Casushi app | Under 30 seconds | Battery drains faster; plan to charge soon after |
| Plug the iPhone into a charger before depositing | iOS exits Low Power Mode automatically once charging starts | Seconds, plus time to find a cable | Not practical away from a power source |
| Raise charge above 20% and retry | Low Power Mode can be re-enabled manually, but a healthy charge reduces the temptation to leave it on | Several minutes | No effect if you switched the mode on deliberately at 80% |
| Use the Casushi mobile site in Safari instead | Bypasses StoreKit validation entirely; the responsive site detects screen dimensions and serves the mobile lobby | 1 to 2 minutes, including login | Loses Face ID convenience and push notifications |
| Retry the deposit after a full app restart | Clears a stuck validation request left over from the throttled attempt | About 1 minute | Does nothing if Low Power Mode is still active |
To switch it off, open Settings, tap Battery, and toggle Low Power Mode to off. The yellow battery icon in the status bar should disappear. If the toggle is greyed out, the phone is charging and the mode is already inactive, so the failed deposit has another cause and you should move to the next checklist item. On iOS 15 and later you can also ask Siri to turn Low Power Mode off, which is quicker if the app is already open on the cashier screen.
One detail trips people up: Low Power Mode can switch itself back on at 20% battery even after you disable it, and some users enable it permanently through a Shortcuts automation. Check Settings > Battery again if a deposit fails a second time on the same day. Also confirm the Casushi app is current in the App Store listing, since older builds validate receipts less gracefully when a request is delayed. Once the mode is off and the app is up to date, retry the deposit through the Casushi app cashier and keep the app in the foreground until the confirmation screen appears. The welcome bonus and any deposit-linked offers in the mobile lobby credit only after that confirmation, so do not close the app early.
Casushi app versus Casushi mobile site: platform-specific deposit fixes
Once the basics are out of the way, the fixes split cleanly by platform. Work down the list in order and retest with a small deposit after each step, so you know which change actually cleared the error.
Casushi iPhone: clear the app’s local data, then reinstall. Apple users who download the Casushi app from the App Store sometimes end up with stale session data after an iOS update or a failed cashier deposit. Force-quit the app, reopen it, and sign in again. If the cashier still stalls, delete the app and reinstall it from your App Store listing, then log in and retry. This refreshes the stored receipt validation state the app uses to confirm deposit limits. https://casushi-online.uk/app/ offers additional context worth reviewing. Reinstalling does not touch your account balance or bonus status, and you can re-enable Face ID logins from the app settings afterwards. Before reinstalling, check that iOS is on the latest point release and that the app shows an update in the App Store; an out-of-date build can fail silently at the cashier step. Also confirm push notifications are enabled, since deposit confirmations arrive that way and a blocked notification can make a successful deposit look like a failure.
Casushi Android: check Play Protect and app permissions. Android users access the Casushi site through a mobile browser or via the installed app, and the browser route is usually the more reliable one on older handsets. If you use an installed build, open Settings, find the app, and confirm storage and notification permissions are granted. A denied storage permission stops the app caching payment tokens correctly. Next, open Google Play, tap your profile, go to Play Protect, and run a scan; Play Protect occasionally flags casino apps it does not recognise, which blocks background payment calls without an obvious error. Clear the app cache from Settings, then retry. Note that Casushi does not publish a standalone Android APK file, so any APK you find on a third-party site is not an official build. Stick to the Play Store listing or the browser, and avoid sideloaded packages entirely.
Fall back to the Casushi mobile site. The responsive site detects your screen dimensions automatically and runs the full mobile lobby, including the welcome offer and the cashier, in Safari, Chrome, or Samsung Internet. It is the fastest way to tell whether the fault sits with the app or with your account. Open a private or incognito tab, sign in, and try the deposit again. If it goes through in the browser but not in the app, the problem is local to the app and a reinstall usually fixes it. If it fails in both, the issue is more likely account-side or payment-method-side, which points to support.
Add a home screen shortcut. For a near-app experience without the install, use your browser’s “Add to Home Screen” option. The shortcut opens the mobile lobby full-screen, keeps you signed in, and sidesteps the app store review cycle entirely when a new build is pending. It is a practical fallback for anyone whose Casushi Android device is on an older OS version that the app no longer supports.
| Platform | First fix | Second fix | Fallback |
|---|---|---|---|
| iPhone (App Store) | Force-quit and sign in again | Delete and reinstall the app | Casushi mobile site in Safari |
| Android (Play Store) | Grant storage and notification permissions | Run a Play Protect scan, clear cache | Casushi mobile site in Chrome |
| Any device | Private browser tab test | Home screen shortcut | Contact support with details |
One caveat on the browser route: the Casushi mobile site offers responsible play tools such as deposit limits and session reminders, and these apply across app and browser alike. If a limit you set earlier is lower than the amount you are trying to deposit, the cashier will reject it without a clear message. Check your limits before you assume the app is broken.
This website operates as an information page only and does not process deposits or hold accounts. If every item above fails, move to the final step and contact Casushi support with your details ready.
When to contact Casushi support and what to include
What to collect before you open a support ticket
If the deposit still fails after you have switched off Low Power Mode, cleared the app cache, checked Play Protect, and tried the Casushi mobile site in a browser, the problem is no longer on your side of the screen. That is the point to stop retrying and hand the case to support. Retrying a failed deposit five or six times muddies the audit trail and can trigger a temporary block on the payment method, so one clean retry after each fix is enough.
Support can only act on facts, and a vague “my deposit did not work” ticket usually gets a vague reply asking for the same details you could have sent first time. Assemble the following before you write:
- Timestamp. The exact time of the failed attempt, including the time zone shown on your device. Payment processors log in UTC, so a local time with an offset saves a round trip.
- Amount and currency. The figure you entered, not the figure you intended to enter.
- Payment method. Card type and last four digits, or the wallet name. Do not send the full card number or CVV, and no support agent will ask for them.
- Device and OS version. For example, iPhone 14 on iOS 17.4, or a Samsung Galaxy A54 on Android 14. Mention whether you used the Casushi app or the Casushi mobile site.
- App version. Found at the bottom of the app menu or in the App Store listing under version history.
- Error message. Quote it word for word. “Transaction declined” and “payment provider unavailable” point to completely different departments.
- Screenshots. One of the error screen, one of the pending transaction in your banking app if the funds left your account.
If money has left your bank but not appeared in your balance, say so in the first line of the message. Pending deposits are usually reconciled automatically within a few hours, but flagged cases get priority when the agent knows funds are in limbo.
How to write the ticket so it gets resolved in one reply
List the checks you have already completed. State plainly that Low Power Mode is off, that you reinstalled the Casushi casino app or cleared its cache, that you tried the Casushi mobile site in a browser, and whether the same card works elsewhere. This stops the first response being a script that asks you to do exactly what you have done. Agents work through checklists too, and a ticket that pre-empts the checklist moves straight to the escalation queue.
Send the ticket from the email address registered to your account. Requests from a different address usually stall while ownership is verified. If you contact support through live chat, paste the same details in one message rather than splitting them across several, and ask for the ticket reference number before the chat closes.
One expectation to set: support cannot see your device settings, your bank’s fraud rules, or your network. They can see the transaction log on the Casushi side, the status returned by the payment provider, and whether your account has any deposit restrictions attached. Frame your question around those three things and you will get a useful answer rather than a generic one.
Keep the ticket open until you receive either a transaction ID for the successful deposit or a clear written reason for the decline. If the reply does not address the timestamp and amount you supplied, reply once with those details repeated and ask for escalation. A single, well-documented ticket beats a dozen fresh ones, and it gives you a written record if you later need to raise the matter with your card issuer.
If every check above has been completed and the deposit still will not clear, the fastest route to a resolution is the Casushi support channel, and the quality of your first message decides how quickly it moves. Send the time of the failed attempt, the amount, the payment method, the device model, the operating system version and the Casushi app version, along with a screenshot of the error screen and one of the transaction in your payment provider’s history. State plainly which fixes you have already tried: Low Power Mode switched off, app reinstalled, cache cleared, browser fallback tested. That saves a full round of back-and-forth questions and lets support check the cashier logs against a specific timestamp rather than a vague description.
One practical habit worth keeping: after any failed deposit, wait for the pending status to settle before trying again. Duplicate attempts are the usual source of double holds on a card, and a hold can take several working days to release even when the deposit itself never completed. Check the cashier history first, confirm nothing is marked as pending, then retry once with Low Power Mode off and a stable connection. If that single retry fails the same way, stop and contact support with the details above rather than repeating the attempt. Note that this website operates as an information page only and does not process deposits, so any account-level issue has to go through Casushi directly. For anything involving a payment dispute, keep the reference number from your first support ticket and quote it in every follow-up until the matter is closed.