Our FAQ keeps account, wallet, lobby, and support answers in one place, so you can check the step you need before opening an account.
The FAQ is written for practical account decisions: how you create a profile, where wallet history sits, what to do when a QRIS scan times out, and how support checks your request. If you contact us from Jakarta, we ask for your username, transaction time, and payment rail so the team can trace the issue without asking you to repeat the same
details. Access to any lobby area depends on local law, and we keep that wording clear.
Most questions come before the first session, during a wallet check, or after you switch games.
You can check how our FAQ names game categories before entering the lobby, including Speed Blackjack, Starlight Princess, MotoGP Betting, Aviator, Bingo, and Fish Hunter, with short notes on where each category appears.
The wallet FAQ explains what pending, received, and checked mean for DANA, OVO, GoPay, and QRIS activity, so you know whether to wait, refresh history, or send a support message.
When a question touches account access or eligibility, we use the wording depends on local law. That keeps answers plain while still telling you which account step comes next.
A useful FAQ should not trap you on the same page when your account needs a human check. Our answers tell you which channel fits the issue, what detail to prepare, and when the team is active. For wallet questions, include the rail name, amount, and time; for login questions, include your username and device browser.
Use live chat from 09:00 to 02:00 WIB when your FAQ answer says the issue needs a same-day check, such as a QRIS scan that shows paid but has not reached wallet history.
WhatsApp works for account checks where screenshots help, such as a DANA or OVO receipt. We ask you to hide private balance details and show only the transaction time and reference.
Email fits longer FAQ cases, including profile correction requests or repeated login errors. Send your username, device type, browser name, and the last successful account step for a clearer reply.
We write FAQ answers from the same account flow your screen uses. That means the wording follows the actual menu labels, wallet states, and support requests you see after login.
FAQ steps use the same labels as your account menu, such as Profile, Wallet, History, and Support. This reduces guessing when you move from an answer to the action screen.
Wallet answers name DANA, OVO, GoPay, and QRIS separately because each receipt looks different. We explain what support needs without asking for unrelated account details.
Mobile answers mention Chrome on Android and Safari on iOS when browser behaviour matters, such as pop-up blocking, cached pages, or returning from a QRIS scan screen.
Lobby answers use visible category names and examples such as Aviator, Bingo, Fish Hunter, and Speed Blackjack, so you can connect an FAQ answer to the tile you are looking at.
When the answer involves checking a transaction, we ask for WIB time and the rail used. That gives our team a tighter search window in wallet records.
Eligibility answers avoid vague promises and use where local law permits. We keep that wording consistent so you know the account path may depend on your location.
FAQ pages often fail when they answer a different question from the one you searched.
| Specific question | A useful FAQ asks exactly what you would type, such as why QRIS is pending or where wallet history is located, instead of using a broad heading that hides the action. |
|---|---|
| One next step | Each answer gives one clear move first, such as open Wallet, refresh History, or send the receipt to live chat, so you do not have to choose between several paths. |
| Named rails | We name DANA, OVO, GoPay, and QRIS where they matter because payment screenshots, return screens, and confirmation times can differ across those rails. |
| Private detail control | FAQ answers tell you what to share with support and what to hide. For example, a receipt time helps us, while your full wallet balance is not needed. |
| Real menu path | When an answer mentions a setting, it follows the account path you can check, such as Profile to Security or Wallet to History, rather than using vague account wording. |
| Game context | If your question is about the lobby, the answer names categories like live tables, slots, sportsbook, Bingo, and Fish Hunter so the reply matches what you see. |
| Law wording | Where access is discussed, the answer uses depends on local law. That keeps the FAQ direct without making claims that may not apply to every location. |
The FAQ also helps you recognise the working parts of our account area before you commit time to setup.
These are the questions we see most often from people checking the account flow before joining or during their first wallet and lobby steps. Read the answer that matches your issue, prepare the detail named there, and use the support path shown if your account needs a manual check.