Reference

FAQ Answers for Indonesia Accounts

We built this FAQ to answer the questions you usually want solved before you open an account: how to reach the page, which wallet names appear, and what…

Account stepsLocal walletsDevice checksSupport paths

Browse Lobby Read FAQ

What this FAQ page covers

This static page keeps the answers close to the questions that matter most, so you do not need to hunt through the lobby before you understand the account flow. We group access, wallet, device, and support questions together, then keep the language plain enough to compare with what you see on screen. If you need to check local payment names, you will

see DANA, OVO, GoPay and QRIS in the same place each time. For anything that touches access or eligibility, the answer depends on local law and is available only where local law permits.

DANA
OVO
GoPay
QRIS

LOBBY QUESTIONS FIRST

Three checks inside the FAQ

Each card below points to a real question people ask before opening the FAQ or reading through it again later.

Updated today

LOBBY

Account paths first

We place the account and room terms near the top so you can check how to reach the FAQ, where to open Help, and which labels match Dragon Tiger or Aviator without scrolling through unrelated text.

WALLET

Local rail names

The wallet card keeps DANA, OVO, GoPay and QRIS in view, because many FAQ questions start there. You can check the same names against your own screen before you ask us to look at a pending step.

POLICY

Access wording

When a question touches access, we keep the answer tied to local law and say plainly that availability depends on where the law permits it. That keeps the FAQ readable without turning it into legal noise.

PAGE SHAPE CHECK

Page structure at a glance

7 blocks

in the FAQ page

4 local rails

named in the answers

3 help routes

chat, WhatsApp, form

2 device paths

mobile and desktop

HELP CHANNELS

Where to reach us fast

When a FAQ answer still leaves a gap, we give you three ways to ask again: live chat, WhatsApp, and a contact form. The help desk uses the same wording as the page, so you can send a screenshot of what you see on Android, iPhone, or desktop and get a reply that matches the screen.

Team online

Live chat desk

Open live chat from the FAQ footer when an answer needs a manual check. Our team uses the same short wording you read here, and it is available in English during 08:00-23:00 WIB.

WhatsApp line

Send the question by WhatsApp if you want a screen capture reviewed alongside your text. That works well when the browser on Android or iPhone shows a different label from the one you expected.

Contact form

Use the form when you want one message that includes your account step, device type, and the question itself. It helps us reply with the exact FAQ block you should open next.

WHY WORDING HELPS

Why the answers stay clear

We keep the FAQ useful by writing each answer with one task in mind, then naming the exact path, rail, or screen that matters.

One answer, one task

Each block answers one question, not three at once, so you can scan the page quickly and avoid mixing wallet checks with access questions. That keeps the wording easy to compare later.

Named rails only

When the topic is about funds, we use DANA, OVO, GoPay and QRIS by name. That lets you match the FAQ text to the same rail label you see on your screen.

Same steps on both screens

We write the steps once for phone and desktop, then keep the order the same on both. If you open the FAQ again later, the layout should feel familiar without forcing you to relearn it.

Local law wording

If a question touches access or eligibility, we say it depends on local law and is available only where local law permits. That is clearer than guessing from vague site language.

Support handoff

When the page cannot answer a detail, we point you to chat or WhatsApp instead of leaving you stuck. The handoff is simple: send the screen, state the question, and wait for the matching block.

Plain editing

We trim extra words so the FAQ reads like something a real operator wrote, not a long article. Shorter lines make it easier to spot the exact instruction you need on mobile.

How the answer blocks stay aligned

The compare block helps you see how the FAQ stays consistent from one question to the next.

Open vs logged in	Before you open an account, the FAQ explains where the page sits and which labels to tap. After login, the same block shifts to account steps, wallet checks, and what to do if the answer changes.
Phone vs desktop	On phone, the answers stay stacked and thumb-friendly. On desktop, the same text spreads across a wider view, but the wording does not change, so you can compare both screens without confusion.
Wallet vs bank	A wallet question names DANA, OVO, GoPay or QRIS. A bank transfer question keeps the wording separate, so you can tell whether the FAQ is talking about a local rail or a manual transfer path.
Quick check vs full check	Some answers tell you where to tap next, while others ask you to verify a screenshot or account label first. That difference helps the FAQ stay short when the next step is obvious and longer when it is not.
Access vs support	Access wording points to local law. Support wording points to chat, WhatsApp, or the contact form. Keeping those two tracks separate helps you know whether to read, ask, or stop at the correct place.
Game label vs FAQ label	A game name like Dragon Tiger belongs in a room question, while a label like Help belongs in a page question. The compare block makes that split easy to see before you move on.
Fresh visit vs return	On your first visit, you may need the full path. On a return visit, the FAQ should feel like a quick lookup, with the same order and the same short labels waiting in the same place.

VISIBLE PAGE MARKS

What stands out on the page

These are the page elements that make the FAQ easy to read: short accordion blocks, visible wallet chips, direct support links, and clear account steps.

Accordion blocks The answers open one at a time, so you can…

Wallet chips DANA, OVO, GoPay and QRIS appear as short chips, which…

Direct help links Chat and WhatsApp links sit close to the questions, so…

Device path hints We mention the same taps for Android, iPhone, and desktop…

Clear account steps The page shows the next step in plain language, such…

Local law line When access comes up, the wording stays tied to local…

Questions we hear most often

The questions below cover the ones we hear most when someone opens the FAQ for the first time or returns after a wallet check. We keep the answers short, specific, and tied to the same labels you see on the page, so you can compare the wording with your screen instead of guessing what to do next.

Open the home page, tap Help in the footer, then choose FAQ. On Android and iPhone, the same accordion layout appears in your browser, so you can read the answer without changing apps.

It covers account access, wallet labels, device steps, support routes, and the wording we use when local law affects access. That keeps the page focused on the questions you are likely to ask first.

Yes. When a question involves a local rail, we name DANA, OVO, GoPay and QRIS directly so you can compare the answer with the same label on your screen.

Refresh the page once, check whether you opened the mobile or desktop view, and send a screenshot through chat if the label still looks different. We can point you to the matching block.

Yes. The order stays the same on both, with the same question groups and the same wording. You may only see more space around the text on desktop, not a different answer.

When access comes up, we say it depends on local law and is available only where local law permits. That keeps the answer clear without making claims we cannot support.

Use live chat, WhatsApp, or the contact form from the FAQ page. Send the question, your device type, and a screenshot if needed, so we can reply with the exact step you need.