Reference

FAQ for your account in Indonesia

We keep this FAQ focused on the questions you need before you open an account: which wallet names we accept, how long a DANA or QRIS action usually…

DANAOVOGoPayQRISAndroid

Browse Lobby Read FAQ

What this FAQ page answers

This page groups the account questions we hear most, so you do not have to search through the lobby for each step. We explain what name must match on DANA, OVO, GoPay, and QRIS, what happens after you send an OTP, and how to check the same page on Android, iPhone, or desktop. The answers also tell you when live chat is

open and which requests need a manual check. If access or eligibility comes up, we state that it depends on local law and is available only where local law permits.

DANA
OVO
GoPay
QRIS

CLEAR ANSWERS

Three answer paths you need

Each card points to a different part of the FAQ, so you can move straight to the answer that fits your question.

LOBBY

Questions Before You Open

We place the first answers around account creation, login, and what you will see after the…

WALLET

Wallet Names We Accept

The FAQ names DANA, OVO, GoPay, and QRIS directly, so you can match the wallet on…

RULES

Access Depends On Local Law

When the question is about who can proceed, we answer it plainly: access depends on local…

PAGE SHAPE

How this page is shaped

wallet rails named across the FAQ

device paths we explain clearly

main help channels listed here

first account check we ask for

HELP CHANNELS

Where to ask us next

If one answer still leaves a gap, we give you a direct path to ask again instead of making you search elsewhere. Live chat handles the quick questions, email handles the cases that need a written thread, and the form keeps device or account changes in one place. You can use the same channels on mobile or desktop without changing the wording of your question.

Team online

Live chat

Our chat team answers FAQ questions every day from 08:00 to 24:00 WIB, including wallet timing, OTP delays, and account-name checks. If you are reading from Semarang, the same hours apply.

Email

Send the exact question, your registered phone number, and the wallet name you used. We use email for cases that need a manual answer, such as mismatched account details or a login code that did not arrive.

Help form

Use the form when you want one written thread for a password reset, device change, or FAQ question about access. We keep the reply in the same ticket so you can check it again later.

CHECKABLE SIGNALS

Why these answers stay clear

We write the FAQ the same way we handle account questions behind the scenes: direct wording, named rails, named devices, and a clear next step.

Named wallet rails

We state DANA, OVO, GoPay, and QRIS by name, so you can compare the FAQ against the wallet on your…

Clear timing language

Where timing matters, we use plain words like under a minute or same-day checks, then explain what part waits for…

Device-specific steps

The same answer tells you how it behaves on Android, iPhone, and desktop, because the path is not identical on…

Named account step

We spell out the step before any first withdrawal request, including name matching and OTP confirmation, so you know which…

Local-law boundary

If access comes up, we do not blur the rule.

Single-page memory

The FAQ keeps related answers close together, so when you read one wallet, device, or support question, the next one…

How each answer stays consistent

The comparison below shows what changes from one FAQ topic to another and what stays the same.

Before you open

Before you open your account, the FAQ tells you which wallet names and device paths we accept. After you open it, the same page points you to OTP checks and support hours.

DANA route

When you compare wallet questions, the DANA answer is written the same way as OVO, GoPay, and QRIS, so you can scan for your own wallet instead of reading separate wording.

Mobile path

On Android and iPhone, the FAQ uses the same order: login, check the screen, follow the prompt, then read the next step. On desktop, we keep the same sequence but name the buttons differently.

Fast answer

Short questions get short replies, while anything about identity or access gets a fuller answer. That keeps the page easy to scan when you only need one detail before moving on.

First check

The first account check is not treated like a hidden rule. We compare the request against your registered name and the wallet name, then explain what happens if the details do not match.

Chat versus email

Chat suits quick timing questions, while email suits cases that need a written trail. The FAQ separates them so you can choose the channel that fits your question.

Allowed versus blocked

If the answer depends on local law, we say so directly rather than wrapping it in vague wording. That contrast makes the page usable even when the result is not the one you hoped for.

PAGE MARKERS

Visible details in our FAQ

This page is built for quick scanning: each answer stays short, each card names a real step, and the support block shows where to ask next.

Short answer blocks Each block starts with the direct point, then adds the…

Wallet names in text DANA, OVO, GoPay, and QRIS appear in the copy where…

Device mention We name Android, iPhone, and desktop when the path changes…

Support window The FAQ shows the hour range in WIB and the…

Eligibility line When access is part of the question, the answer points…

Game names Where a question refers to the lobby, we use names…

Common questions you may ask

These are the questions people usually look for first when they want a fast answer about account access, wallet timing, device behaviour, or support hours. We keep each reply short enough to scan and specific enough to use, so you do not have to guess which step comes next. If a question depends on local law, we say that clearly inside the answer.

Start with the section that matches your question, then follow the next step only if it applies to your setup. We keep the answers short, so you can move from OTP, wallet names, or device access without re-reading the whole page.

We name DANA, OVO, GoPay, and QRIS directly in the answers. That lets you check whether your own wallet matches the wording before you send a request or ask us to look at a timing question.

Have your registered phone number, the exact account name, and the same wallet name ready. If anything does not match, the FAQ explains what we can verify first and what needs a fresh submission from you.

Yes. The same page reads well on Android, iPhone, and desktop, and we mention where the buttons or prompts move on each screen. That matters when you are checking login, OTP, or the first account step.

Simple wallet questions are usually answered quickly, and DANA, OVO, GoPay, and QRIS entries are written with clear timing words so you know what to expect. If a manual check is needed, we say so in the answer.

Our live chat runs every day from 08:00 to 24:00 WIB, and email stays open for written cases that need extra detail. We also keep the form available for account questions that need one thread.

No. When a question involves access, we say it depends on local law and is available only where local law permits. That is the exact answer we use whenever eligibility matters.