Our FAQ puts account opening, wallet checks with DANA, OVO, GoPay and QRIS, plus lobby answers for Sic Bo, Dragon Hatch and Basketball Betting in one place so…
Your first FAQ visit should answer what happens before you open an account, not leave you comparing scattered details. We explain the account step from mobile header to Menu > Wallet > QRIS, how a phone number is matched to your profile, and when a wallet check moves to support. The same FAQ points you to live chat or WhatsApp during 09:00-23:00
WIB, so you know which channel fits your question before you start.
The FAQ is split around questions you normally ask before joining: what is in the lobby, how wallet timing is checked, and which account rules affect access.
Game FAQ entries name rooms such as Sic Bo, Fish Hunter, Rocket Crash and Super Bingo, then explain where each sits in the menu. We avoid vague labels so you can match the answer to the lobby screen.
Wallet FAQ answers separate DANA, OVO, GoPay and QRIS checks because each rail may show a different reference code. We tell you which receipt detail support needs if a balance has not updated.
Policy FAQ answers state when local law affects access, why one phone number should stay on one account, and how we verify a withdrawal request before releasing it to the wallet name on file.
Some FAQ answers can be solved on the page; others need a person to check your account. We mark the difference clearly, then send you to the channel that can act on it. Live chat is faster for account access, WhatsApp is better when you need to share a QRIS receipt, and email fits longer wallet traces.
Use live chat between 09:00 and 23:00 WIB when the FAQ says an account check is needed. Our team asks for your username and last action, then checks access or wallet status inside the console.
WhatsApp fits FAQ cases where you need to share a DANA, OVO, GoPay or QRIS receipt image. Keep the reference code visible so our support team can match the wallet request without extra messages.
Email is useful when your FAQ question covers several account events, such as a changed phone number and a pending withdrawal. Send the username, time, payment rail, and device type in one message.
A useful FAQ has to match the product you see after login. We check wording against the account screen, wallet panel and support scripts so the answer does not drift away from…
FAQ steps are written against the same mobile menu labels you use after login, such as Account, Wallet and History. That makes each answer easier to follow when you move from reading to action.
Wallet answers explain what we check before a balance update or withdrawal release: rail name, reference code, account name and time stamp. Those fields help us confirm the request without exposing private details.
Our chat team uses the same wording as the FAQ for common cases, so you do not receive a different answer after contacting us. If a case needs review, the agent says what detail is missing.
When the FAQ mentions Sic Bo, Dragon Hatch, Fish Hunter or Basketball Betting, we check the category placement against the lobby. If a room moves, the answer is adjusted to keep the path clear.
Access answers include local-law wording because availability can vary by location. We keep that language plain, so you understand why an eligibility answer may differ from a wallet or game answer.
When we edit an FAQ answer, we check linked support replies and wallet labels at the same time. That reduces mismatched wording between the public page and the account area you use after login.
You should not need to learn a new term each time you move between FAQ answers.
| Account vs Wallet | Account FAQ answers cover login, phone number and profile checks. Wallet FAQ answers cover DANA, OVO, GoPay and QRIS references, so you know whether the next step is identity access or payment tracing. |
|---|---|
| Game vs Category | A game FAQ answer names titles like Rocket Crash or Super Bingo. A category answer explains where slots, live tables or sports markets appear, which helps when you know the room but not the menu path. |
| Chat vs WhatsApp | Chat is used for quick account status checks during support hours. WhatsApp is better when the FAQ asks for an image, such as a QRIS receipt or wallet transfer record. |
| Mobile vs Computer Browser | Mobile FAQ steps point to the header menu and wallet button. Computer browser steps use the left navigation and account panel, so you can follow the answer on the device you actually opened. |
| Pending vs Completed | Pending FAQ answers explain what still needs checking, such as a rail reference or account name. Completed answers tell you where to see the final status inside History or the wallet panel. |
| Self-Serve vs Agent | Self-serve FAQ answers stay on the page and show a direct path. Agent-needed answers name the contact channel and list the details our team needs before they can act. |
| Access vs Eligibility | Access FAQ answers cover password, device and session checks. Eligibility answers explain that availability depends on local law and is available only where local law permits. |
The FAQ also shows how our brand appears in practical places, not just in a logo.
These are the FAQ questions we expect you to search before opening an account or contacting support. Each answer is short, practical and tied to a visible step, such as a wallet rail, game category, support channel or account screen. If an answer needs private checking, we say which channel to use and what to prepare.