Our FAQ gives you quick answers on account opening, wallet checks, lobby access, and support contact before you jump into the lobby where local law permits.
The FAQ is written for the questions you ask before placing a stake: how to open an account, where the OTP code appears, what the wallet status means, and how to reach us if a page does not load. We keep wallet examples concrete, so DANA, OVO, GoPay, and QRIS appear as chips rather than vague wording. We also explain the device
path, Menu > Help > FAQ, so you can move from a phone browser to a computer without searching twice.
Three FAQ areas come up most often before you open your account: what is inside the lobby, how wallet questions are handled, and which account rules affect access.
The lobby FAQ names game categories such as Dragon Tiger, Zeus vs Hades, Aviator, and Royal Fishing, then explains where each category appears after login. We use the same category labels you see in the lobby menu.
The wallet FAQ explains how a pending mark differs from a failed mark, and where you check reference numbers after using DANA, OVO, GoPay, or QRIS. We keep the language tied to real wallet screens.
The policy FAQ states when identity checks may be requested, why duplicate accounts can be blocked, and that access depends on local law. We write these answers plainly so you know what may happen before joining.
The FAQ should answer routine questions, but account issues sometimes need a direct check.
A useful FAQ has to match the account flow you actually see. We check wording against the live menu, wallet labels, and support responses before publishing changes.
FAQ paths are checked against the current mobile menu, including Menu > Help > FAQ and Wallet > History. If a label changes on the site, the related answer is edited to match.
We name DANA, OVO, GoPay, and QRIS only where they are actually part of the wallet flow. That keeps each FAQ answer clear for Indonesia accounts without relying on generic transfer language.
FAQ answers that mention contact timing use our stated help window, 09:00 to 01:00 WIB. If you write outside that window, the FAQ explains what details to include for the next reply.
Identity and account checks are described through visible steps, such as phone OTP and Profile > Verification. We avoid vague security wording and explain when a request may appear on your account.
When the FAQ mentions Dragon Tiger, Rocket Crash, Super Bingo, or Royal Fishing, we use the same labels shown in the lobby. That makes the answer easier to confirm after login.
FAQ edits are checked after wallet, login, or lobby updates. We aim for answers that reflect the current flow, so you are not following an old button name or missing menu step.
You should not get one answer on mobile and another on a computer. Our FAQ is written around the same account actions, then adjusted for the screen path…
| Mobile path | On mobile, the FAQ points you through Menu > Help > FAQ, then into account, wallet, lobby, or support sections. We use tap-based wording because that is how most Indonesia accounts reach help. |
|---|---|
| Computer path | On a computer, the FAQ keeps the same answer groups but may refer to the left menu or header link. The subject stays identical, so you are not learning two separate account flows. |
| Wallet wording | Wallet answers use the same terms across devices: pending, successful, failed, and history. If you used QRIS on mobile, the FAQ still tells you where to check the status on a computer. |
| Login checks | Login FAQ answers explain phone OTP, password reset, and locked account steps in the same order. That makes it easier to follow a fix whether you started on a phone or computer. |
| Lobby labels | Game FAQ answers keep category names consistent, including live tables, slots, fishing rooms, and sportsbook. Specific titles such as Dragon Tiger or Dota 2 are referenced only where they fit the answer. |
| Support routing | The FAQ tells you when to use live chat, WhatsApp, or email based on the issue, not the device. A wallet case still needs the same reference details whichever screen you used. |
| Local access | Where account access is discussed, the FAQ uses the same wording across pages: depends on local law. We keep that statement visible near rules that affect opening or using an account. |
The FAQ should feel like part of our own account flow, not a detached help page.
These are the FAQ questions we expect you to check before opening or using an account. Each answer is written around one action: finding a menu, reading a wallet status, confirming support hours, or understanding a rule. If your case needs a direct check, use the channel named in the related answer.