Our FAQ puts account setup, wallet checks with DANA, OVO, GoPay and QRIS, plus lobby questions in one clear place.
The FAQ is written for the moments when you need a clear answer before moving on. We explain how to create your account, where to find wallet status, why a QRIS scan may need a fresh code, and how to reach us through live chat or WhatsApp from 09:00 to 01:00 WIB. If you read it from Surabaya on mobile data, the
same Menu > Help > FAQ path stays visible in Chrome and Safari so you can check steps without leaving your account flow.
We sort the FAQ around the questions you ask before opening the lobby, adding funds or contacting support.
Some FAQ answers end with a support route because account checks need live handling. We show the channel, the detail to prepare and the reason we ask for it.
We keep FAQ answers tied to things you can confirm in your account: menu labels, wallet status, support hours and named game categories.
Each wallet FAQ names DANA, OVO, GoPay or QRIS instead of using vague payment wording. That helps you match the answer to the rail you selected in your account.
We write device steps as they appear on screen, such as Menu > Help > FAQ or Wallet > History. The same labels are used on mobile browsers so you can check without guessing.
The FAQ states when live handling is available, including 09:00 to 01:00 WIB for chat. If a question needs manual checking, we tell you which channel keeps the record clear.
Lobby answers name categories and examples such as Live Roulette, Aviator and Super Bingo only when the question needs them. We keep the answer about finding or understanding the FAQ entry.
FAQ answers on profile changes explain why we may compare your registered phone, email or wallet name. That step protects account access before any wallet or password update is completed.
When an FAQ touches eligibility, we use the same phrase every time: depends on local law. We do not add extra claims around access, regions or account approval.
A useful FAQ should answer the question you clicked, not send you through unrelated copy.
| Direct first line | Every FAQ answer opens with the main action, such as refresh Wallet > History or open Menu > Help > FAQ. We avoid long openings because you usually need the next step quickly. |
|---|---|
| Operational detail | After the action, we add the detail that explains it, such as QRIS code expiry, sender-name checks or why a Live Roulette table appears under a live casino category. |
| Channel match | The FAQ points you to live chat, WhatsApp or account message based on the issue. Receipt checks go to chat or WhatsApp; profile spelling questions can sit in account message. |
| Device clarity | We write mobile paths for Chrome and Safari first because most FAQ checks happen by phone. If a wider screen changes placement, the answer tells you what label remains the same. |
| Wallet wording | DANA, OVO, GoPay and QRIS each get named when the answer involves timing or proof. That prevents confusion between e-wallet transfers and QR code scans in your history. |
| Lobby references | When a question mentions games, we use exact names like Rocket Crash, Royal Fishing or Mahjong Ways. The FAQ stays focused on where to find them and what menu label to open. |
| Policy placement | Access wording sits inside the policy FAQ rather than scattered through the page. If location rules matter, the answer says depends on local law and then returns to your account step. |
The FAQ also helps you confirm that you are reading our own page and not a copied answer elsewhere.
These are the questions we see most often when you are deciding whether to open an account or when a wallet step needs checking. Each answer is short, practical and tied to an account path, a named payment rail or a support channel so you can act without reading unrelated sections.