Will WAXP support ask for my private key?

No. WAXP support never needs a private key, seed phrase, recovery phrase, or wallet password.

What should I include with a failed swap report?

Include the token direction, amount, wallet account, approximate time, exact error message, and any WAXP support code shown.

WAXP help center

Clear answers.
Useful evidence.

Understand wallet prompts, resolve common swap issues, and send a report that reaches the WAXP operations queue.

Non-custodial supportWAXP support never needs your private key, seed phrase, or wallet password.

Start here

Fix the common blockers first.

↻

Quote changed

Refresh the quote and review the new route. WAXP will not silently sign a different transaction.

Open swap →

◫

Balance looks wrong

Refresh the portfolio, then compare the exact token contract and ticker—not the ticker alone.

Check portfolio →

⌁

No executable route

The listed market may have no usable liquidity or its token contract may reject venue transfers.

Inspect token →

◇

Wallet will not open

Reconnect the wallet, confirm you are on WAX mainnet, then retry from the reviewed transaction screen.

Review safety flow →

Support codes

Copy the code—not your secrets.

When WAXP rejects a route, the red message may include a support code. It identifies server-side evidence without exposing a private key or wallet credential.

1
Copy the complete support codeInclude the `swap_…` value and the exact token direction.
2
Record what you enteredAmount, pay token, receive token, wallet name, and approximate time are useful.
3
Never share a secretSeed phrases, private keys, wallet passwords, and unredacted recovery screens are never required.