Stake
United States flagUnited States

Stake US Support

Resolve account, reward, purchase and redemption questions with the right request details.

Choose the issue category

Separate a login failure from a missing reward or an unsettled redemption. For access, record the exact error and recovery step already attempted. For a daily reward, note the last successful claim. For a payment, retain the wallet reference and method. A precise category avoids sending the same general message to multiple channels.

What to include in a request

Describe the expected action, what happened instead and the time shown in the account. Include a request reference or transaction hash where relevant. Screenshots should omit passwords, security codes and unrelated personal data. Keep the case in one thread so earlier checks remain visible.

Account recovery

Use the recognised recovery form for the US profile. A request to reveal an authenticator code or to transfer coins to unlock a password is not a normal password-reset step. If email access has changed, tell support which part of recovery is unavailable instead of creating another profile.

Follow-up and resolution

Ask which stage is pending: account review, platform processing or external settlement. A payment cannot be traced in a bank or explorer until the corresponding transfer exists. Once resolved, save the reference with your transaction history and review security settings if the case involved unexpected account activity.

Stake Crash English game interface

Account, games and payments

Questions about Stake.us

What helps support trace a redemption?

Provide its request reference, amount, method and last visible status. For a broadcast crypto transfer, add its hash and network.

Should a support message include my authenticator code?

No. A case description does not require your password, recovery phrase or one-time authentication code.