This guide answers one specific question: why might a withdrawal requested at Ruby Fortune still show as pending, and what evidence can help identify the cause? It covers the checks a Canadian player can make before contacting support. It cannot confirm the status of an individual account or promise a processing time; account terms, payment-provider handling and verification requirements can differ.
The useful boundary is the point between a submitted request and money arriving through the selected payment method. A pending label alone does not prove that something is wrong: the request may be awaiting an account review, a casino-side step or processing by a bank or payment service. For the official account and current terms, begin at https://rubyfortuneca.com, then compare the information there with the details of your own transaction.
Evaluation goal: locate the stage holding the withdrawal
Build a short timeline before changing anything. Record when the request was submitted, its displayed status, the amount and payment method, and any messages or verification requests. Then identify the latest stage that can be confirmed. A casino status such as “processing” and a bank statement showing a completed transfer are different kinds of evidence; neither should be treated as proof of the other.
This approach helps separate four plausible bottlenecks: incomplete identity or payment verification, a withdrawal condition that has not been met, a request still in the operator’s review queue, or a delay after the payment has been sent. These are possibilities to investigate, not claims about what has happened in a particular Ruby Fortune account.
Compact evidence checklist
- Request record: save the date and time, amount, method, transaction reference and exact status shown in the account.
- Account messages: check the registered email, account notifications and support history for a document request, rejection notice or instruction.
- Verification: confirm whether requested identity, address or payment-ownership documents were submitted successfully and whether their status is marked as accepted.
- Terms and balance: review the applicable withdrawal rules, any bonus conditions you accepted and whether a required playthrough or other condition remains outstanding.
- Payment details: verify the method and destination selected, and check with the bank or provider for a received, declined or pending transaction.
- Timeline: compare elapsed time with the current published guidance for that specific method. Do not assume that a general estimate applies to every payment.
Interpret strong and weak signals
| Evidence | What it may indicate | Next check |
|---|---|---|
| A clear request for documents | Verification may be the current hold point. | Ask whether each file arrived and whether anything remains outstanding. |
| A bonus condition shown as incomplete | The balance may not yet qualify for withdrawal under the accepted terms. | Check the relevant bonus rules and account activity before submitting another request. |
| Status unchanged, with no message | The request may still be under review, but the label alone is weak evidence of the cause. | Ask support to identify the stage and any action required from you. |
| Casino confirms payment was sent | The remaining delay may be with the payment provider or receiving bank. | Request the payment date and reference, then ask the provider to trace it. |
| Bank reports no traceable payment | Dispatch may not be confirmed, or the reference may not be sufficient. | Return to support for a written status and usable transaction details. |
Strong signals are specific and independently checkable: a named document is missing, a condition is visibly incomplete, or a provider can locate a transaction using its reference. Weak signals include rumours, generic estimates from another site, a brief status label, or an assumption that a withdrawal must be delayed because of the payment method. Keep conclusions proportional to the evidence.
Proceed-or-pause criteria
Proceed with one targeted follow-up
Contact Ruby Fortune support when the published method-specific period has passed, the status has not changed, or the account does not explain what is needed. Include the request date, amount, method, reference and a screenshot with sensitive details obscured. Ask three direct questions: Is the request still under review or has it been sent? Is any verification or withdrawal condition outstanding? If sent, what date and reference should the payment provider use to trace it? Save the reply and its date.
Pause before taking another action
Do not submit repeated withdrawal requests, switch methods or cancel a request simply to test what happens. Each change can make the timeline harder to follow and may have consequences under the account terms. Pause if identity checks are unresolved, the destination details appear incorrect, a bonus condition is unclear, or support has not confirmed whether the original request remains active. Never send passwords, one-time codes or full card details in a message.
If the evidence points to the receiving bank or payment provider, give that provider the confirmed transaction details and ask it to trace the transfer. If the operator cannot explain the status, provide a written response, or resolve the issue through its stated process, keep a dated record and consult the relevant provincial or territorial consumer-protection or gaming regulator for guidance. The practical decision is simple: proceed when the next step is supported by a specific finding; pause when the cause is still only a guess.