Promotion-wallet reconciliation
Keep RoboCat Casino, Sport and Crypto Promotions Separate
Offers shown under different promotion tracks may use different qualifying deposits, wagering products and settlement rules. Treat each wallet as a separate contract.
Open RoboCat and compare current promotion tracksChoose one promotion track
Open the Casino, Sport, Crypto or Specials category attached to the account and save the exact offer terms. Confirm currency, qualifying method, minimum action and activation order.
Do not combine headline values from multiple tabs. A deposit that qualifies for one track may not trigger another.
- Track
- Qualifying action
- Restricted balance
- Expiry
Map wagering to the right product
Casino wagering may depend on game contribution and stake caps, while sports wagering can depend on settled bets, minimum odds or excluded markets. Crypto describes a funding route, not automatically a separate withdrawal entitlement.
Record which ledger receives the reward and which products reduce its requirement. Keep void or refunded activity separate from settled qualifying activity.
Avoid conflicting opt-ins
Check whether activating a new offer cancels or suspends an existing one. Save the active-promotion screen and balance split before pressing an opt-in or cancel control.
If more than one offer appears active, ask which takes priority for the next qualifying action. Do not rely on the order in which banners are displayed.
Reconcile before cashout
Confirm that all required bets or rounds have settled and that restricted value has converted to cash. Review maximum conversion, withdrawal caps and any route-specific return rule.
When cancelling, verify exactly which cash and reward balances change. Keep the confirmation message with the withdrawal record.
RoboCat questions
Can one RoboCat deposit qualify for casino and sport offers?
Only the current offer terms can confirm compatibility; treat each track separately.
Does a crypto promotion guarantee crypto withdrawal?
No. Check the current withdrawal route and return-to-source rules separately.
Useful current references
Last reviewed: 11 August 2026, 12:15 UTC

