A mistyped password on your last Ruby Fortune login attempt can trigger a security lock, and the site then refuses the correct password with the same error message. The common cause is a run of failed attempts that the account treats as suspicious activity.
Withdrawal still pending after the request
The cashier shows the withdrawal as pending while the balance has already been reduced, and the money has not reached the player's account.
- Identity or address checks on the account are unfinished.
- The bonus attached to the money was not fully played through.
- A payment method was used that the account does not hold in the player's own name.
- A previous withdrawal request is still open and blocks the new one.
- The account details differ from the documents supplied at registration.
- Open the cashier and note the exact status shown against the request before changing anything.
- Confirm that the identity checks on the account are complete, because a pending check holds every payout.
- Check the bonus balance: money won with a bonus usually has to be played through before it can leave.
- Make sure the payout method matches one the player used before and holds personally.
- Cancel any duplicate request, since two open requests on one account cannot both go through.
- Compare the name and address on the account with the documents already sent.
- Look at the message centre in the account for a request for extra documents.
- Upload any missing document once, in a clear and full image, rather than sending it repeatedly.
- Leave the request alone for a while after the checks clear, because re-submitting restarts the queue.
- Keep the confirmation shown after the request was made, since support will ask for it.
Contact support once every check on the account is complete and the withdrawal has still not moved.
Welcome bonus or free spins missing
The account shows a deposit or a fresh registration, but the welcome offer and its free spins are absent from the bonus section.
- The bonus code was not entered at the moment of the deposit.
- The offer was already claimed on an earlier account or deposit.
- The deposit was made after the offer had been closed to new claims.
- A payment method excluded from the offer was used.
- The bonus was credited and then removed because a game was played that does not count.
- Open the bonus section of the account and look for a claim button next to the welcome offer.
- Check the deposit history to confirm the payment was recorded on the account and not left pending.
- Enter the code again only if the offer still shows as available; a second entry on a used offer does nothing.
- Review which games count towards the offer, since some titles move the balance far more slowly.
- Confirm the deposit method is one the offer allows.
- Log out and back in, as a credited bonus sometimes appears only after a fresh session.
- Note the offer name and the date of the deposit in case support needs them.
- Do not make a second deposit expecting the same offer to appear twice.
- Keep the bonus confirmation screen or message if one was shown.
- Write down what was on screen at the time of the deposit, including any code.
Contact support when the offer still shows as available, the deposit is recorded and nothing has been credited.
Phone browser will not load the site or the games
On a phone the page loads partially, spins forever, or a game opens to a blank frame while the rest of the site works.
- The mobile network has a weak or unstable connection.
- A browser cache or an old page copy is being served.
- The browser blocks scripts or cookies that the games need.
- A VPN or a content blocker is interfering with the connection.
- An outdated browser version cannot run the game client.
- Switch from mobile data to Wi-Fi, or the other way round, and reload the page once.
- Clear the browser cache and cookies, then open the site again from a fresh tab.
- Try a different browser on the same phone to see whether the problem follows the browser.
- Turn off any VPN or content blocker for the session and reload.
- Update the browser to its current version from the phone's store.
- Close other tabs and background apps that may be holding memory.
- Allow cookies and scripts for the site in the browser settings.
- Open the Ruby Fortune casino login page directly rather than through a saved bookmark that may be stale.
- If a single game fails while others open, note its name for support. Players who keep returning to the phone should treat ca-rubyfortune.com as their starting point, since a fresh page load clears most stuck sessions.
- Restart the phone if every site, not just this one, behaves the same way.
Contact support when other websites load normally and only this site or its games keep failing.
Deposit taken by the bank but absent from the balance
The bank statement shows the payment has left the account, yet the casino balance has not moved and the cashier shows no matching deposit.
- The payment is still travelling between the bank and the casino.
- The cashier page was closed before the confirmation appeared.
- A bonus code was added to a deposit that failed the first time and was retried.
- The bank flagged the payment for a manual check.
- Two deposits were sent close together and only one was recorded.
- Take a screenshot or note of the bank entry with its reference before doing anything else.
- Refresh the cashier and the balance a few times over the next hour.
- Look in the transaction history on the account for an entry marked pending.
- Check the bank app to see whether the payment is completed or only reserved.
- Do not send the deposit a second time while the first is unresolved.
- Confirm the account was logged in when the payment was sent, as a session timeout can interrupt the return.
- Keep the reference number from the bank, because support needs it to trace the payment.
- Note the amount and the time shown on the bank statement.
- Compare the bank entry with the transaction history on the account.
- Stay logged in until a confirmation message appears for any retried payment.
Contact support with the bank reference as soon as the payment shows as completed at the bank and the balance is still unchanged.
Quick Reference
The table below lines up each problem with the cause seen most often and the first thing to check.
| Problem | Usual cause | First check |
|---|---|---|
| Withdrawal pending | Identity checks unfinished | Account verification status |
| Bonus not credited | Code missing at deposit | Bonus section for a claim button |
| Games stuck on phone | Cache or blocker interference | Reload after clearing the cache |
| Deposit missing | Payment still in transit | Transaction history and bank entry |
| Login refused | Repeated failed attempts | Password reset on the login page |
A pending withdrawal almost always waits on an unfinished check, so completing verification early removes the delay. A missing bonus usually comes down to a code not entered at the deposit, which the bonus section shows plainly. Phone loading faults are cleared most often by a fresh page load without a blocker in the way. A deposit that has left the bank but not arrived needs the bank reference kept safe before any retry. Players in Ontario meet the same four problems and the same checks apply. Working through one check at a time keeps the account in a state support can trace.
Log out fully at the end of every session and write down the bonus code before depositing, which prevents most of these problems from starting.