Reference

Open FAQ answers for Indonesia

We keep our main FAQ in one place so you can check account steps, login help, and the local payment rails before you open the lobby.

Account stepsLocal paymentsSupport hoursDevice checks

Browse lobby Read FAQ

Browse the questions we answer first

This page is the place we send you when you need a straight answer, not a long pitch. We group the questions that come up most often: how to open an account, how login works on Android or desktop, what to do when a payment name does not match the wallet, and where to ask about support hours. The answers stay short

on purpose, but each one points to a real step you can check inside your account. For local rails, we name DANA, OVO, GoPay, and QRIS so you know which route the FAQ is talking about.

DANA
OVO
GoPay
QRIS

THREE PATHS

Open FAQ cards by topic

Each card sends you to one question set: account access, local payment checks, or local-law eligibility.

ACCOUNT CARD

Login and sign-in

Use this card when you cannot get into the account area.

WALLET CARD

DANA, OVO, GoPay, QRIS

Use this one for payment questions inside the FAQ.

POLICY CARD

Local eligibility

This card explains when access is available and when it is not.

PAGE SHAPE

Explore the FAQ structure at a glance

core question groups

support channels named

local payment rails listed

account path to follow

HELP ROUTES

Switch to support when an answer is not enough

When the FAQ does not settle it, we point you to our live chat, WhatsApp, or email so you can send the exact question and the screen you are seeing. Our team is set for 09:00-23:00 WIB, and the fastest replies usually come when you include your phone number, the wallet name, and the time you tried the step. That lets us answer the same account step without making you repeat the whole story.

Team online

Live chat

Use chat for login, account, and wallet questions when you are already inside the site. We can ask for the page you see, the time of the error, and the phone number tied to your account.

Send a clear screenshot and the exact question if the FAQ does not match your case. We use it for quick follow-up during 09:00-23:00 WIB, especially when you need to show the screen.

Email

Use email when your question needs a longer reply, such as an account step or a payment name mismatch. Keep the subject short and include the wallet name you used.

ANSWER QUALITY

Open the checks behind each answer

We write the FAQ from real account steps, not from broad promises. Each answer names the screen you should open, the payment rail you should check, or the support channel you should…

Plain step order

We state the first click, the second check, and the final screen so you can follow the answer on Android, iPhone, or desktop without guessing.

Named rails

When a question touches money, we name DANA, OVO, GoPay, or QRIS instead of using vague labels, so you know which wallet or scan flow the answer covers.

Support window

We show the support hours and channel in the same answer when timing matters, which helps you decide whether to use chat, WhatsApp, or email.

Device path

We note whether the step is easier in Chrome mobile, the desktop browser, or the app shell, so your FAQ answer matches the device in your hand.

Eligibility line

Whenever access depends on local law, we say so plainly and keep it limited to places where local law permits. That keeps the answer factual and easy to verify.

Account detail

We ask for only the details needed to identify your issue, such as your username, wallet name, or the time of the error, so the next reply stays focused.

Browse how answers stay the same

The FAQ stays consistent across the page, even when the topic changes. A login question, a payment question, and a device question all follow the same pattern: what…

Login vs account	Login answers cover password reset, phone number checks, and the correct sign-in screen. Account answers add profile details and verification timing, so you know whether the fix belongs in the browser or in support.
Payment vs wallet	Payment answers name the exact rail, like DANA or QRIS, and tell you what to match on your side. Wallet answers also point out whether the issue comes from the sender, the receiver, or the scan step.
Phone vs desktop	Phone answers focus on mobile browser behaviour, while desktop answers mention wider screens, pop-ups, and browser tabs. You can see the same logic in both, but the buttons may sit in different places.
Quick question vs detailed case	Short questions get a short route, and longer cases get the supporting step and contact path. That keeps the FAQ readable when you only need one line, and still useful when the issue is specific.
Chat vs WhatsApp	Chat is better when you are already inside the site; WhatsApp is better when you need to send a screenshot from your gallery. Both routes point back to the same answer set.
Local law vs access	If your question touches eligibility, we answer it with the local-law line first. That way you can see whether access is allowed before you spend time on account steps.
Game question vs account question	Game questions name the room or title you are asking about, while account questions stay on login, profile, or contact details. The wording changes, but the action path stays clear.

Open the elements you will notice

These are the visible parts that make the FAQ easy to use on first pass: a search field, category chips, short answer cards, and a support…

Search field

You can type login, wallet, device, or support terms and jump straight to the matching answer. We keep the search text simple so it works the same on phone and desktop.

Category chips

The chips split the page into account, payment, device, and support questions. That lets you move faster when you already know the topic and do not want to scan the full page.

Answer cards

Each card pairs the question with a short answer and one next step, which makes it easier to skim before you open the full section.

Support box

The support box shows the channel, the hours, and the kind of question that belongs there. You do not have to guess whether chat or email is the faster route.

Device hint

We point out when a step is easier on mobile browser, desktop browser, or the app shell, so the same FAQ can help you on any screen.

Local-law line

When access comes up, the line stays visible and plain: it depends on local law and is available only where local law permits. That keeps the page clear from the start.

Switch to the questions people ask

These are the questions we see most when someone checks the FAQ before opening an account. Each answer stays short enough to skim, but still names the step, channel, or device path you need. If your case is tied to a wallet, a login screen, or local eligibility, you can use the answer here as the first check and then move straight to chat if it still does not fit.

Open the login section in the FAQ, then check the reset step, the phone number on file, and the browser you are using. If the screen still rejects you, send us the time and error text.

Look at the rail named in the answer first, then compare the sender name, account name, and phone number. For DANA, OVO, GoPay, or QRIS cases, the FAQ tells you which detail should match before the next step.

Yes. The same answers open on Android, iPhone, and desktop, but the button path may sit in a different place. We point that out so you can follow the same question without guessing the layout.

Check the support section of the FAQ for live chat, WhatsApp, and email. We list the active window as 09:00-23:00 WIB, so you know when a fast reply is most likely.

It does. We keep the verification step next to the account question so you can see what detail we need, such as a phone number or an ownership check, before you send a message.

The FAQ says access depends on local law and is available only where local law permits. If your location is outside that range, the answer will tell you to stop at the eligibility check.

Yes, if you are checking a title like Aviator, Andar Bahar, Crazy Time, Bingo, or Fish Hunter, the FAQ points you to the right category and the account step that follows.