Clicking the claim button on the Ruby Fortune welcome offer is the easy part; what happens next depends on a wagering rule that many players skim past. That rule does not change what you win, but it decides whether the bonus money and its winnings can leave the account at all. Read it as a condition on your own cash: until the playthrough is finished, the bonus balance stays locked to the site.
Getting the Welcome Offer
The welcome offer is claimed once per player, and the steps below are the order that keeps the claim valid.
- Open the site in a normal phone browser first. This lets you see the current offer wording before you enter anything.
- Register a new account with details that match the person who will withdraw later. Mismatched names cause problems long after the claim.
- Confirm the email address the site sends to you. An unconfirmed account cannot hold a bonus balance.
- Make the first deposit from an account in your own name. A deposit from someone else’s account breaks the offer conditions.
- Enter the bonus code shown with the offer when you deposit. A code entered after the deposit is generally not applied.
- Wait for the bonus balance to appear before you start playing. Playing on the deposit alone can use up money the offer needs.
- Note the date the offer expires, and plan your play so the wagering finishes inside that window. Unfinished playthroughs lose the bonus.
The steps look simple, but each one carries a condition that the site applies at withdrawal rather than at sign-up. A new account must belong to one person only, and duplicate accounts are closed before any payout. The first deposit counts only when it is made with your own money from a method registered to you. Bonus codes are tied to the moment of deposit, so a code saved in a note later is worth nothing. The bonus balance sits apart from your cash balance, and the site uses one before the other in a set order. Games you play before the bonus lands count toward nothing. An expired offer cannot be reopened by asking support. Players who finish the playthrough inside the window keep the winnings; players who ignore the date keep the cash they deposited and lose the rest. The Ruby Fortune bonus itself is a single welcome package, not a monthly reward you can claim again with a second account.
Key Terms in Plain Words
The table sets out the terms that decide whether bonus money turns into withdrawn money.
| Term | What it means | What to check |
|---|---|---|
| Wagering requirement | How many times the bonus must be played before withdrawal | Which figure the multiple applies to: bonus alone or bonus plus deposit |
| Expiry window | The period in which the playthrough has to finish | Whether the clock starts at the deposit or at the claim |
| Game contribution | The share of each stake that counts toward the requirement | Which game groups count in full and which count partly or not at all |
| Maximum stake per spin | The largest bet allowed while a bonus is active | Whether the cap covers the total bet or each line |
| Maximum withdrawal | The most that can leave the account from bonus winnings | Whether the cap applies to the whole win or to the converted bonus |
Of these, the maximum stake per spin is the term players misread most often. Many assume a big single bet simply counts faster toward the requirement, when in fact it can void the bonus and its winnings entirely. The cap applies while the bonus is active, not only while you are playing with bonus money.
Contribution follows the same logic in a gentler form: a game that counts a small share still uses your balance at full speed but moves the requirement slowly. The expiry window punishes slow progress twice, because time spent on low-contribution games counts against the clock. The base of the multiple matters most: on a bonus-only figure the requirement is smaller than on a combined deposit and bonus figure. The maximum withdrawal caps the upside even when the playthrough is complete, so a large win from bonus play can shrink at cashout. Reading the cap before you play tells you what a good outcome looks like.
A Worked Example
The numbers below are an illustration, not the Ruby Fortune terms; they show how the formula behaves.
Example only: a player deposits 50 with a bonus of the same size, and the requirement is 35 times the bonus.
The requirement total is the bonus multiplied by the multiple: 50 times 35 equals 1750. That figure is the amount of stake that has to count toward the requirement, not the amount you must win. Players often confuse the two and expect a win of that size to clear the bonus.
Each bet adds to the running total only by the contribution share of the game played. A game that counts in full moves the total by the full stake; a game that counts a small share moves it by that fraction. This is why the same spending produces very different progress on different games.
Suppose the player spends on games that count in full. After 1750 in total stakes, the requirement is met and the bonus is released into withdrawable money. The player has not lost 1750; that is turnover, and part of it may have come back as winnings along the way.
Now suppose the player mixes games that count a small share. The running total rises slowly, and more stakes are needed for the same release. The expiry window can close before the total is reached, and the bonus goes with it.
If a single bet goes above the cap, the example breaks: the bonus and its winnings can be removed regardless of how much progress was made. The size of the win is irrelevant in that case, because the breach is about the stake, not the result. The formula itself is fixed and predictable, so the whole outcome rests on the player’s choices.
Withdrawing After a Bonus
A withdrawal request made before the playthrough is finished is normally refused or rolled back. Money from the bonus stays inside the account until the requirement is met, whatever the cash balance shows. Trying to withdraw early is the fastest way to discover the condition you skipped.
When the playthrough is done, the bonus converts according to the site’s rules and the cap on bonus winnings applies. The amount above the cap is removed rather than paid, so a strong run can still end at the ceiling. The ceiling belongs to the bonus, not to the cash you deposited yourself.
Identity checks run before any payout leaves the account. The name, address and payment details must match the registered player exactly. A mismatch at this stage freezes the request until it is corrected, and the correction may not always be possible.
Your own deposited cash is not locked in the same way, but the site may treat the mixed balance as one pool until the bonus is settled. That means a request can be treated as a bonus withdrawal even when you meant to take only your deposit back. Knowing the order in which the balances are released avoids the surprise.
Withdrawing everything at once is cleaner than making several small requests. Multiple open requests on one account can slow the checks and invite questions about where the money came from. One settled request leaves a clear record.
If a request is refused, the reason is usually one of three: unfinished wagering, an expired offer or a breach of the stake cap. Each reason has its own fix, and none of them is solved by opening a second account. A refused request does not remove the cash you deposited before the bonus.
Game Contribution
Contribution is the share of each stake the site counts toward the wagering requirement, and it varies by game. On Ruby Fortune Canada, slots usually count in full while table games and live dealer titles count partly or not at all. https://rubyfortunesca.com/ sets these shares in the bonus rules, and the differences are large enough to shape a whole plan.
Progress is measured in counted stake, not in time spent at the screen. A long session on a game with a low share can leave the running total almost where it started. Choosing a game by its contribution first is the single decision that changes the outcome most.
Some titles are excluded from bonus play altogether. Playing an excluded game while a bonus is active can void the bonus even if nothing was won. The exclusion list is separate from the contribution list, so a game can be allowed but count for little.
Live dealer tables sit at the low end of contribution because their house edge is small. A player who prefers them will need far more turnover to finish the same requirement. That is a reason to check the shares before claiming, not after.
Games played before the bonus is credited count toward nothing at all. The running total starts when the bonus balance appears, not when the deposit clears. Playing early is the same as playing for free as far as the requirement is concerned.
Mixing game types splits your progress across different shares, which makes the running total hard to track. Picking one high-share game and staying with it keeps the total clear and the expiry date reachable. Mobile play through the phone browser works the same way, so the shares do not change with the device.
Common Mistakes
Most lost bonuses come from a short list of avoidable errors, and each one has a simple defence.
- Betting above the stake cap to finish faster. Keep every bet below the cap for the whole bonus period, and treat the cap as a hard ceiling.
- Playing a game with a low contribution share without checking. Choose games whose share is high before the first spin, not after the first loss.
- Leaving the playthrough until the end of the expiry window. Start the qualifying play soon after the bonus lands so the clock is never the problem.
- Claiming with details that differ from the withdrawal account. Register once with exact details and use the same name for every deposit and payout.
- Opening a second account after a refusal. Keep one account and resolve the refusal on it, because duplicates close both accounts.
- Assuming the bonus is cash the moment it appears. Treat the bonus and its winnings as locked until the requirement is met.
- Entering the code after the deposit has been processed. Enter the code during the deposit so the offer attaches to that payment.
Each mistake is cheap to avoid and expensive to repair, because the site applies these conditions in the same way at every withdrawal. The stake cap is the cruelest of them: a single large bet can erase a long, careful playthrough. Low-contribution games do the same damage slowly, which makes them harder to notice before the expiry date passes. A late start turns a comfortable requirement into a rushed one, and rushed players make the other mistakes on the list. Mismatched details surface at the worst possible moment and can stall a payout that was otherwise earned. Duplicate accounts break the one-player rule that every offer depends on, and the closure takes the cash with it. Treating the bonus as cash leads to a withdrawal request that fails and a support conversation that changes nothing. A code entered late is a small error with a total loss attached. The Ruby Fortune login gives you one account per person, and the offer is built around that single identity. Players who plan the game choice, the stakes and the timing keep what they win.