Our FAQ puts account opening, lobby access, DANA, OVO, GoPay and QRIS questions in one place, so you can decide your next step without searching through chat first.
The FAQ is the first place we send you when the question is practical: how to open your account, why phone verification appears, where the wallet status sits, and how to read lobby labels before you join a room. On mobile, open Menu > Help > FAQ; on a wider screen, use the Help link near your account panel. We keep DANA,
OVO, GoPay and QRIS chips beside wallet answers only as quick context, not as a sales pitch.
Most questions we receive fall into three groups, so the FAQ is arranged around those same habits. We separate lobby, wallet and account-rule answers to reduce back-and-forth before you open a ticket.
The FAQ should solve common questions, but we also show where to go when your account screen looks different.
An FAQ is only useful when the wording matches what you see in your account. Our team checks screen paths, wallet labels and support handoff text before publishing edits.
Before we publish an FAQ edit, we confirm the mobile path and wider-screen path still match live account menus. That keeps Menu > Help > FAQ wording aligned with your session.
DANA, OVO, GoPay and QRIS answers are checked against the wallet status labels you see after submitting a transaction. We explain pending, completed and returned states plainly.
Each answer that may need human help includes the channel we expect you to use. Live chat covers quick checks, while email is better for longer account history questions.
We write account answers in the order our team checks them: username, phone number, password reset request, device history and wallet record. That reduces repeated questions.
When our FAQ names Lightning Roulette, Wild Bandito or MotoGP Betting, we confirm the lobby label and category before keeping the answer live. Titles change only after a check.
Any FAQ answer about access includes our plain reminder that eligibility depends on local law and is available only where local law permits. We keep that wording consistent.
You should not have to guess whether an answer is old. We compare FAQ text against account screens, wallet behaviour and support questions before changing it.
If an FAQ answer points to a menu that moved, we replace the path and mention the new account panel location. We do not leave two different paths active.
When wallet status wording changes for DANA, OVO, GoPay or QRIS, we align the FAQ with the label you see after submitting the request.
Password reset answers are compared against the current phone verification step. If the code screen changes, we edit the FAQ before support scripts are adjusted.
We keep game category answers tied to visible lobby labels, such as live tables, slots, Crash Games and MotoGP Betting. That helps you search by the same names.
If our support window changes, the FAQ is edited in every answer that mentions 09:00-02:00 WIB. We keep channel timing in one checklist.
Device and profile answers are compared with the checks our team can actually perform. We avoid asking you for details that do not help account handling.
Access-related answers carry the same local-law line, so you see one clear rule across account, lobby and help topics instead of mixed wording.
The FAQ also explains how to recognise our own pages and avoid confusion when you move between account, lobby and help screens.
These are the FAQ questions we expect you to search before opening an account or asking support for help. Each answer stays practical and points to the account step, wallet rail, lobby label or channel that solves the issue. If your screen does not match the answer, contact us during 09:00-02:00 WIB with the exact path you followed.