Back to ThatHand ThatHand Guide
Built into ThatHand · Stake.us & Shuffle.us

WagerGuard

Set your weekly target. Automate the upkeep.

Your seven-day playthrough keeps changing—even when you aren’t playing. Older wagers drop out, your total falls, and staying near your preferred level becomes another thing to manage.

WagerGuard handles that routine for you.

Built into ThatHand for Stake.us and Shuffle.us, WagerGuard tracks your estimated rolling seven-day playthrough and automatically runs maintenance sessions when your plan calls for them. Choose your target, set your preferences, and let ThatHand manage the ongoing upkeep while the app stays running.

Whether you’re working toward 50,000 SC, 100,000 SC, or a custom level, WagerGuard helps you plan around wagering requirements for bonus codes and rewards—with less guesswork about how much to play next.

Daily sessions can still leave gaps when start times vary.

Both strategies begin with the same 52,500 SC of playthrough. Every manual session still wagers 7,500 SC over eight hours, but its start time varies. WagerGuard stays available around the clock and starts replacement play when the rolling total reaches 50,500 SC.

Seven-day illustrative simulation with identical starting histories. Variable manual starts produce 18 hours below the 50,000 SC target and a low of 48,750 SC. WagerGuard has zero time below target and a low of 50,500 SC. Colored dots mark session starts; red shading shows only the manual shortfall below target.
Completing 7,500 SC every day can still leave gaps below a rolling seven-day target when session times vary. WagerGuard monitors expiring wagers around the clock and starts replacement play when needed. This simulation uses the same wagering speed for both strategies. The schedule is illustrative, not actual customer history.

Why starting a delayed session does not immediately restore the target

Thursday detail: expirations begin at 6 pm. The manual total reaches 50,000 SC at 8:40 pm and 48,750 SC at the delayed 10 pm start. Incoming and expiring wagers then cancel until 2 am. The total returns to 50,000 SC at 3:20 am, after 6 hours 40 minutes below target.
A four-hour delay uses up the 2,500 SC buffer after 2 hours 40 minutes. From 10 pm to 2 am, both wagering and expiration run at 937.5 SC/hour, so the total stays at 48,750 SC while the user plays. It rises only after the old session finishes expiring. WagerGuard starts earlier at its threshold; its line also stays level while incoming and expiring rates match.
Simulation assumptions and wagering totals
  • The comparison runs from Monday at 6 pm to the following Monday at 6 pm. Both strategies start with identical histories: seven preceding daily sessions of 7,500 SC, each from 6 pm to 2 am, for 52,500 SC total.
  • Manual starts: Monday 6 pm, Tuesday 9 pm, Wednesday 7 pm, Thursday 10 pm, Friday 6 pm, Saturday 8 pm, Sunday 9 pm. Each session lasts eight hours at 937.5 SC/hour. No sessions are skipped or reduced.
  • WagerGuard is available continuously, starts at 50,500 SC, and stops at 51,000 SC using the same wagering rate. The model assumes sufficient balance, no competing sessions, and immediate response at the threshold.
  • Wagers enter as they are placed and expire exactly 168 hours later. The model uses minute buckets to aggregate hands and accounts for incoming wagering and expiration together. After the shared history, each strategy expires its own wagers.
  • Time below target is measured across the entire seven days: manual play 18 hours, WagerGuard zero. Lowest rolling totals are 48,750 SC and 50,500 SC respectively. These are simulated results, not guaranteed coverage.
Seven-day wagering accounting; all amounts are SC. Starting history is excluded from new wagering.
StrategyStarting rolling totalNew wageringExpired wageringEnding rolling total
Manual play52,50052,50052,50052,500
WagerGuard52,50051,00052,50051,000

WagerGuard wagers 1,500 SC less during this window and also ends with 1,500 SC less playthrough in the rolling total. That difference is not a cash saving or a monthly projection. The main comparison is continuity of target coverage; wagering volume is not net loss.

  • Maintain your target automatically. Set when maintenance should begin and the level you want to restore. As older play leaves the window, WagerGuard evaluates the shortfall and starts a session when needed.
  • Control how each session plays. Choose your bet size, minimum and maximum batch amounts, and optional variation in session targets.
  • Choose your game. Use standard blackjack on Stake.us or Shuffle.us, or select BGaming Surrender Blackjack for Stake.us maintenance.
  • See what happened. Review maintenance runs with timestamps, starting and ending estimates, wagered amounts, and net gain or loss. Supported surrender runs also report surrender counts.
  • Keep the records automatically. Enable session creation to save completed and partial maintenance runs to your tracking dashboard.
  • Keep your plan across installations. Settings and maintenance history are stored against your linked casino account, so your setup stays with you.

You remain in control: automatic maintenance is opt-in, waits for existing betting sessions to finish, and provides a Stop Guard Mode control during each run.

Choose the level you want to maintain. Let WagerGuard handle the routine.

Requires ThatHand to remain open and connected on an awake computer with the intended account selected. Automatic maintenance requires sufficient current tracking history—normally an initial seven-day observation period. Eligible Shuffle accounts with no recent play can start from zero. Playthrough totals are estimates; each casino determines promotion and code eligibility.