Our FAQ puts account opening, Dragon Tiger rooms, QRIS timing, and live help hours in one place so you can decide your next step before you join.
The FAQ is the first place we send you when you ask how to open an account, where to find Aviator, or why a QRIS payment has not appeared yet. We write each answer around a real action: tap Account, confirm your phone number, check Wallet, then send a chat message if the record is missing. DANA, OVO, GoPay, and QRIS appear
as quick chips so you can jump straight to the wallet answer you need.
Our FAQ is arranged around the questions you ask before and after account opening, not around vague site claims.
Our lobby FAQ explains where Dragon Tiger, Mines, UFC MMA, Aviator, Bingo, and Fish Hunter sit in the menu, so you can match a game name with its category before opening the room.
The wallet FAQ covers DANA, OVO, GoPay, and QRIS with the action path Account > Wallet > History, plus the transaction ID we ask for when a payment needs a manual check.
The policy FAQ uses plain account language for name matching, phone checks, and access wording. When eligibility comes up, we state that use depends on local law without adding unclear promises.
Some FAQ answers solve the issue on the page, while others tell you exactly what to send us. We keep the live chat path, email path, and account message path separate because each one needs different proof. If you ask about a QRIS record, login reset, or game session, the FAQ tells you which channel fits the case.
Use live chat from 10:00 to 02:00 WIB when the FAQ points you to fast account checks, QRIS tracing, or a live table session question that needs a same-day reply.
Use email when the FAQ asks for a clearer file, account-name check, or longer wallet explanation. We can keep the full thread in one place and answer with the next exact step.
Use the account message path when the FAQ says your question needs wallet history or session data. After login, tap Help, choose the subject, and attach the reference shown on screen.
We do not treat the FAQ as filler copy. Each answer is checked against the account screen, wallet screen, and help flow before it goes live.
Every account FAQ answer names the screen path we expect you to see, such as Menu > Account > Phone Check, so you can compare our wording with your device.
We name only the local rails we support in the FAQ: DANA, OVO, GoPay, and QRIS. If a rail is not listed there, do not send funds through it.
When a game question needs help, the FAQ asks for the title, time, and session ID. Dragon Tiger and Aviator cases are easier to trace when those details are included.
The withdrawal FAQ explains why your account name and wallet name must match. If the names differ, we ask for correction before moving the request through the wallet queue.
Policy answers avoid heavy legal phrasing. If access or eligibility appears in an answer, we use depends on local law so the condition is clear before you continue.
When support gives an answer based on the FAQ, we keep the reply time and channel in the case record. That helps us continue the same issue if you return later.
A useful FAQ should not answer the same issue in two different ways. We compare the wording across account, wallet, lobby, and help sections before publishing changes.
| Account opening wording | The account FAQ always starts with phone number, password, and name check in that order. We keep the same order across help answers so you do not miss a required field. |
|---|---|
| Phone and large screen paths | When a path differs by screen size, the FAQ says so directly. Phone answers use tap language, while larger browser answers use menu language without changing the account requirement. |
| Wallet history reference | Every wallet answer points back to Account > Wallet > History before asking you to contact us. That keeps DANA, OVO, GoPay, and QRIS checks tied to a visible record. |
| Live casino naming | Live table answers use the same names you see in the lobby, including Dragon Tiger. If a session question needs help, the FAQ asks for the title and session time. |
| Sports market phrasing | Sports answers keep UFC MMA in its own category so you do not confuse it with casino rooms. The FAQ explains where the market sits and what reference support may request. |
| Security step order | Security answers use one order: confirm phone, reset password, then contact live chat if the account remains locked. We repeat the same order wherever login issues appear. |
| Eligibility sentence | When eligibility is part of an FAQ answer, we use where local law permits and keep that sentence consistent. We do not add side wording that changes the meaning. |
The highlights in our FAQ are screen cues you can match while you move through your account.
These FAQ entries cover the questions we answer most often before you open an account or ask live chat for help. Each answer gives a direct action, then adds the operational detail behind it. If your case needs a private check, we tell you what reference to send so the support team can trace it without repeating the same questions.