Skip to main content

1. Scope

This page explains the stable player-facing expectations around wallet and withdrawal behavior. It is intentionally written to separate durable guarantees from operational controls that may change over time.

2. Wallet scope

The player-facing wallet surfaces may show:
  • Wallet address information
  • Deposit history
  • Withdrawal history
  • Withdrawal detail states
  • Related player-facing balance context
Players should use the wallet and activity surfaces together when reviewing account movement history.

3. Withdrawal lifecycle framing

The stable player-facing expectation is that a withdrawal request can move through a review and status lifecycle before it is final. The docs should be read as describing a lifecycle, not as guaranteeing immediate processing. Operational steps may include:
  • Request submission
  • Review or validation
  • Status updates
  • Final completion or rejection

4. Stable guarantees vs variable limits

Players should distinguish between:
  • Stable guarantees such as the existence of wallet history, request flows, and status review
  • Variable controls such as cooldowns, risk checks, rolling limits, fee-aware amounts, and anti-abuse restrictions
Unless a specific value is clearly published as a public commitment, players should treat those controls as policy-managed and subject to change.

5. Fee-aware and available amounts

This policy does not promise that the amount a player enters is always the final amount received or released. Depending on the active withdrawal flow, final player-visible amounts may be affected by:
  • Fees
  • Validation rules
  • Status-based constraints
  • Review outcomes
The current product surface shown at the time of request is the authoritative player-facing context for that withdrawal.

6. Support and disputes

If a player believes a wallet or withdrawal state is incorrect, the correct player flow is:
  1. Review the visible wallet and activity history
  2. Refresh the relevant player-facing page
  3. Contact support with the relevant details if the issue remains unresolved
When contacting support, include the identifying information and screenshots requested in Contact / Report / Appeal.