Account and security
Support routes include verification, login, 2FA, sessions, frozen accounts, and recovery.
Support is not the hero of the site, but investors will judge it. Flux support content covers account access, wallet movement, gameplay issues, verification questions, and escalation paths for a real-money crypto product.
Support docs list a 100-chip minimum deposit where one chip equals one cent.
Support docs list a 500-chip minimum withdrawal.
Support docs describe Solana confirmations as usually under thirty seconds.
Support docs describe most withdrawals as completing in fifteen to thirty minutes, with exceptions possible.
Support, payments, fairness, and responsible play all affect whether Flux can operate a serious real-money product.
Support is an operating signal. A poker room can have beautiful tables and still lose trust if money movement, account recovery, and verification questions feel unsupported.
Flux's support story tells investors that the team understands the full product surface, not only the table.
The deeper operations packet can then show policies, staffing assumptions, tooling, and escalation procedures.
Support routes include verification, login, 2FA, sessions, frozen accounts, and recovery.
USDC movement, chip accounting, failed deposits, withdrawals, and on-ramp boundaries need clear ownership.
Hand records, table behavior, rake display, verifier routes, and fairness questions are supportable surfaces.
A real-money product needs clear escalation, incident ownership, and response expectations.
Money-product support has to route issues quickly and create evidence for operational review.
Login, invite, session, and 2FA questions.
Deposit, withdrawal, chip accounting, and reconciliation routing.
Hand packet review, transcript questions, and redaction education.
Limits, eligibility, self-exclusion, and escalation resources.
Operational support reinforces whether Flux can run a serious money product.