Reference

Open the FAQ for clear account answers

This FAQ keeps your account questions in one place, from DANA, OVO, GoPay and QRIS checks to access rules that depend on local law and are available only…

Open accountWallet checksDevice pathLocal law

Browse lobby Read FAQ

Explore the answers that matter

This static page is where we keep the questions that appear most often before an account is opened. You can check how the first form works, which wallet name should match your profile, where DANA, OVO, GoPay and QRIS sit in the flow, and when an access answer depends on local law. We also point you to the device path, so you

know whether to finish on Android, iPhone, or desktop. If you need one answer before you move on to Live Dealer Lobby, Aviator or Sweet Bonanza, this page is built for that.

DANA
OVO
GoPay
QRIS

FAST ANSWERS

Switch between lobby, wallet and policy

These three cards pull the FAQ into the parts you usually need first: lobby access, wallet checks, and the local-law sentence that decides whether a question can be…

Updated today

LOBBY

Account questions first

Before you open anything, we point you to the answer that matches your step: form, login, wallet status, device path, or support channel. That keeps the FAQ moving without extra clicks.

WALLET

DANA, OVO, GoPay, QRIS

When a wallet question appears, the answer names the rail and the status you should watch next. That way you know whether to wait, retry, or send the reference to chat.

POLICY

Local-law access line

If the question is about access, we answer with the local-law line first and keep it visible. That gives you a direct rule for Indonesia instead of a vague reply.

PAGE COUNTS

Browse the account facts

named wallet rails

device paths we mention

main help channels

local-law access line

HELP CHANNELS

Open support paths that answer fast

When a FAQ answer needs a person, we give you the contact path without making you search the site again. Live chat, WhatsApp and email all use the same plain language, and we list the reply window in the page so you know when to expect a response. If you are handling a wallet question after work, that saves a second trip through the page.

Team online

Live chat

Open live chat when you need a quick answer about the FAQ, then keep the same thread while we check your account step, wallet status or device path. We answer daily from 09:00-23:00 WIB.

Use WhatsApp if you want to send a screenshot before you continue. We keep replies short, name the exact step, and point you back to the same FAQ entry without making you restate the question.

Email

Email fits longer questions, especially when you want the access wording or wallet check in writing. We keep the tone plain and answer in the same language you read on this page.

CLEAR SIGNALS

Explore how we keep answers clear

The trust signals here are practical, not decorative. We name the step, the channel and the condition that applies, then we keep the wording the same when the rule repeats.

Plain wording

We keep answers short enough to scan, but each one still says what to do next, which channel to use, and whether any access rule changes by region. That way you can read once and move on.

Named rails

When a question involves DANA, OVO, GoPay or QRIS, we name the rail directly and explain the next status you should expect before you send anything else.

Local-law line

If access depends on local law, we say so in the first line and keep it there. You do not have to guess whether the page is talking about your region.

Phone and desktop

The same FAQ text works on Android, iPhone and desktop, so you can start on mobile, then return later on a bigger screen without losing the thread.

Account match step

We mention when your wallet name, login name, or ID check needs to line up before anything else moves forward. That keeps account answers practical instead of vague.

Clear reply window

Our channel hours are named in the page, so you know when chat, WhatsApp, or email is active. That saves time when you want one clean answer before you continue.

Switch between similar FAQ cases

This section compares the questions that sound similar but need different answers.

Open account vs read first

Opening your account starts with the form step; reading first means you are checking the rule, the channel, or the wallet name before you act. We keep both answers separate so nothing feels mixed.

Wallet status vs wallet name

A pending status asks you to wait for the result, while a name mismatch asks you to check the profile detail first. We say which one applies, so you do not chase the wrong fix.

Android vs desktop

On Android you can scan the answer and switch apps quickly; on desktop you may want the longer support path. We mention both so the same FAQ works on either screen.

Chat vs email

Chat fits quick checks, while email fits questions that need the wording in writing. We point you to the right channel instead of making you guess which one will answer faster.

Lobby question vs access question

A lobby question asks where a room or title sits; an access question asks whether local law allows it. We separate those meanings so the answer stays accurate.

Aviator vs Sweet Bonanza

If you ask about a game title, we answer with the room or device step; if you ask about the FAQ rule, we stay on the rule. That keeps the response tied to your exact search.

Jakarta vs general Indonesia

When we use Jakarta in body copy, it is only to ground the page locally. The answer itself still applies to Indonesia-wide questions where local law allows access.

VISIBLE MARKS

Browse the visible brand markers

These are the visible markers that make the FAQ easy to scan: named wallet rails, named devices, plain reply hours and the same local-law line whenever eligibility comes…

Indonesia phrasing We keep the copy in clear English for Indonesian readers…

Named rails DANA, OVO, GoPay and QRIS appear when a wallet step…

Device paths Android, iPhone and desktop are named directly, which helps when…

Game titles Live Dealer Lobby, Rocket Crash, Aviator and Sweet Bonanza appear…

Reply hours Chat, WhatsApp and email hours are written plainly, so you…

Access wording Whenever eligibility comes up, we repeat the same sentence: available…

Open the questions we hear most

This is the part you use when you want a direct answer before opening the account form or switching devices. We group the questions by wallet rail, access rule, support channel and device path, then answer them in the same order each time. That makes the page easy to scan on mobile, and still clear when you come back on desktop.

It covers the account questions you ask before you move on: how to open your account, which rail fits the wallet step, where support is active, and when access depends on local law.

We name DANA, OVO, GoPay and QRIS whenever the answer involves a wallet check. That makes it easier to match the question to the right step before you send anything else.

Yes. The FAQ works the same on Android, iPhone and desktop, so you can start on mobile, then return later without losing the thread or repeating the question again.

Wait for the status to change, then check the name match and the last message from support. If it still sits in the same state, open chat or WhatsApp and send the reference.

Use the account form, finish the login step, and keep your wallet name aligned with your profile name. After that, we point you to the next FAQ entry that fits your question.

Yes. When eligibility comes up, we say it depends on local law and is available only where local law permits for your region. That line appears whenever the question touches access.