A withdrawal that sits at pending while the balance still shows as available is the first sign most players miss, and it usually comes from an identity or payment detail that was never finished. The most common cause is a mismatch between the name or payment route on the account and the one used for the request.
A pending withdrawal that takes longer than expected
The player sees the balance reduced but the payment stuck at pending, with no clear reason shown on screen.
- A verification step still open because the uploaded document is unclear or expired.
- The payment route used for the request belongs to someone other than the account holder.
- The withdrawal was requested while a bonus condition was still attached to the funds.
- Several withdrawal requests were sent in quick succession, so each one waits behind the others.
- The account details changed shortly before the request, which triggers an extra review.
- Open the account area and look for any outstanding request for documents before doing anything else.
- Upload a fresh copy of the required identity document with all four corners visible and no glare.
- Confirm the name on the payment route matches the name on the account exactly, including middle names.
- Cancel duplicate withdrawal requests and keep only one active.
- Leave the account otherwise idle so the review is not reset by new activity.
- Note the reference number the screen shows for the request, so support can find it fast.
- Return to the withdrawal list and check whether the status has moved from pending to processing.
Contact support once the request has stayed pending through a full review cycle and no document request is showing.
A locked account or a login that fails
The player types the right details but the screen returns an error, or a message says the account is locked.
- Failed attempts have stacked up and triggered a temporary lock.
- The password was changed on another device and the old one is still being typed.
- A browser autofill is inserting an older saved password.
- The account is already open in another tab or on another phone, which blocks the new session.
- Two-factor codes are being read from an older authenticator entry.
- Slow down and type the username by hand instead of letting the browser fill it.
- Clear the autofill entry for the site and enter the password manually.
- Close every other tab and any other device signed into the same account.
- Use the password reset on the login screen if the current one is not accepted.
- Set a new password that you have not used elsewhere and save it in a safe place.
- Open the authenticator and remove old entries so only the current code remains.
- Try once, wait, then try again rather than repeating attempts in a row.
- Switch to a different browser on the same phone if the error keeps returning.
Contact support when the reset emails never arrive or the lock message does not clear after a wait.
A deposit or withdrawal declined by limits
The player submits a payment and gets a refusal that mentions a limit on the account or on the route.
- The requested amount sits above the ceiling allowed for one transaction.
- The account has reached its daily or monthly movement total.
- The chosen payment route has a lower ceiling than the one the player assumed.
- A newly created account is still under a first-period restriction.
- Recent deposit and withdrawal activity looks unusual and has paused the route.
- Split the request into a smaller amount that fits inside the single-transaction ceiling.
- Choose a different payment route if the current one has a lower cap.
- Wait for the next daily cycle if the day total has been used.
- Space deposits and withdrawals out instead of sending several in one session.
- Finish any open verification so the account is not held under first-period rules.
- Keep using the same payment route for deposits and withdrawals to avoid extra checks.
- Write down what the refusal message said, since the wording points to the exact limit.
- Retry the request after the reset period with the smaller amount.
Contact support when the amount fits inside every limit you can see and the refusal still repeats.
Games or the site failing to load on a phone
The page half-loads, spins, or a game opens to a blank screen in the phone browser.
- A weak mobile connection drops the game files partway through loading.
- The browser cache holds an old version of the page.
- An ad blocker or privacy extension cuts a script the game needs.
- Too many tabs are open and the phone is short of memory.
- A game built for desktop is being opened on a small screen.
- Switch from mobile data to Wi-Fi, or the reverse, and reload the page.
- Casino de Montréal login should be opened in the phone browser rather than an in-app viewer, since the in-app view often blocks game scripts.
- Clear the browser cache and cookies, then sign in again.
- Turn off ad blockers for the site and reload.
- Close background tabs and other apps to free memory.
- Try a different browser on the same phone before blaming the connection.
- Pick a game tagged for mobile play instead of a desktop-only title.
Contact support when every game fails in every browser on the phone while other sites load fine.
Quick Reference
This table pairs each problem with its usual cause and the first thing worth checking.
| Problem | Usual cause | First check |
|---|---|---|
| Pending withdrawal | Open verification or name mismatch | Document request in the account |
| Locked login | Repeated failed attempts | Autofill inserting an old password |
| Declined payment | Amount above a route or account limit | Single-transaction ceiling for the route |
| Phone page not loading | Cache or blocked script | Cache cleared and blockers off |
| Two-factor rejection | Old authenticator entry | Only the current code in the authenticator |
A pending withdrawal is rarely a lost payment; it is nearly always an unfinished check. The login lock usually clears once autofill stops injecting an old password. Limit refusals respond well to a smaller amount or a different route. Mobile loading problems sit with the browser far more often than with the account. Two-factor trouble comes from stale entries in the authenticator. Most of these clear once the account details and the payment name match exactly.
Keep the name on the account, the documents and the payment route identical and current, and most of these problems never start.