This FAQ gives you the short path to account setup, wallet checks, Live Dealer Lobby access, Zeus vs Hades, Aviator, and account support before you open an account.
The FAQ is written for the questions you ask before sharing a phone number, choosing a wallet rail, or entering the lobby. We explain how account creation starts, where OTP checks appear, why your wallet name must match your account, and when support may ask for a screenshot. You also get the device path we use most often: Menu > Wallet >
Transaction Records. Read it first, then open your account with fewer surprises.
Our FAQ is arranged around the moments where questions usually slow you down: account entry, wallet movement, and the rules that affect access.
The lobby FAQ names the game areas you will see first, including Live Dealer Lobby, slots, sportsbook, Bingo, Fishing God, and Aviator. We also explain why some rooms may appear only after account verification.
The wallet FAQ explains where each rail appears, how QRIS codes refresh, and why DANA, OVO, or GoPay details should match your account name. Most wallet questions start from Menu > Wallet.
The policy FAQ keeps the plain parts visible: one account per person, accurate contact details, and access only where local law permits. We use those answers when support checks account change requests.
The FAQ should solve the common questions, but some account checks need a live person. We keep the help paths close to the answers so you do not have to search around when a QRIS code expires, an OTP is late, or a withdrawal check needs a clearer screenshot.
Use live chat from 10:00 to 02:00 WIB when the FAQ answer points to an account check. Share your registered phone number and the screen name you are stuck on, not your password.
WhatsApp is useful when the FAQ asks for proof of a wallet issue. Send one clear screenshot from Menu > Wallet > Transaction Records, then wait for the support reply in the same thread.
Email helps when your FAQ question involves contact changes or repeated OTP failures. We may ask you to confirm the original phone number, registered email, and the wallet rail you last used.
We write FAQ answers from the same account flow our support team sees each day. When a wallet label changes, a browser menu moves, or a verification request needs clearer wording, we…
FAQ steps are tested against the account screen we operate, including phone entry, OTP prompt, password reset, and wallet name checks. If a field changes, the related answer is adjusted.
DANA, OVO, GoPay, and QRIS terms are kept in the FAQ exactly as they appear in the wallet area. That reduces confusion when you move between the answer and the payment screen.
We state the 10:00 to 02:00 WIB support window inside relevant FAQ answers. If you contact us outside that window, you can still leave the issue for the next available reply.
When the FAQ mentions Live Dealer Lobby, Zeus vs Hades, Mobile Legends, Aviator, Bingo, or Fishing God, we use the same names shown in the lobby so you can find them faster.
FAQ security answers say what we may ask for and what we never need. We may request account identifiers or screenshots, but we will not ask for your password through chat.
When an FAQ answer discusses account access or eligibility, we state that it depends on local law and is available only where local law permits. That wording stays consistent across related answers.
A useful FAQ should not change its wording from one section to another. We keep the same terms for wallet rails, support channels, account checks, and lobby areas…
| Before account opening | The FAQ tells you what to prepare first: a reachable phone number, an active email, and wallet details under your own name. Those same details are used later if support checks your account. |
|---|---|
| During OTP entry | OTP questions explain when to wait, when to request a fresh code, and when to contact support. We keep the wording direct because mistyped phone numbers cause many access delays. |
| Inside the lobby | Lobby FAQ answers use the same category names you see after login: Live Dealer Lobby, slots, sportsbook, Bingo, and Fishing God. That helps you find a room without guessing the label. |
| Wallet movement | Wallet FAQ answers point to Menu > Wallet > Transaction Records for status checks. We use that path for DANA, OVO, GoPay, and QRIS questions so the answer stays easy to follow. |
| Withdrawal review | Withdrawal questions explain the account-name check, transaction record check, and screenshot request that may happen before release. We avoid vague wording so you know why a verification step exists. |
| Mobile browser use | Mobile FAQ answers mention Android Chrome and iOS Safari because those are common access paths in Indonesia. If a button sits lower on one browser, the answer says where to look. |
| Support handoff | When an FAQ answer cannot solve the issue alone, it tells you which channel fits: live chat for urgent account checks, WhatsApp for screenshots, and email for contact-detail changes. |
This section keeps the FAQ tied to visible parts of our site rather than broad promises.
The FAQ mirrors the registration form wording for phone number, email, password, and OTP. That makes the answer useful while you are filling the form instead of after you have made a mistake.
We use exact lobby names in FAQ answers, including Live Dealer Lobby, slots, sportsbook, Mobile Legends, Aviator, and Bingo. You can scan the lobby and match the answer to the room.
The FAQ repeats one wallet path for status checks: Menu > Wallet > Transaction Records. Keeping that path stable helps you send the right screenshot when support asks for account evidence.
FAQ answers mention Android Chrome and iOS Safari when menu placement matters. If a wallet button sits below the fold on mobile, the answer tells you to scroll before contacting support.
The FAQ names live chat, WhatsApp, and email exactly as they appear on the contact panel. We also include the 10:00 to 02:00 WIB window beside account-related help answers.
Where the FAQ discusses eligibility, we keep the same sentence: access depends on local law and is available only where local law permits. You will see that wording across access-related answers.
These FAQ entries answer the questions that usually come before you open an account or return to a pending wallet request. Each answer is short enough to act on, but specific enough to point you to the right screen, channel, or account detail.