Reference

FAQ answers for Indonesia accounts

Our FAQ page answers the questions you ask before opening an account: what the form needs, how DANA, OVO, GoPay, and QRIS are checked, and where to ask…

ACCOUNT STEPSDANA, OVO, GOPAYQRIS CHECKSLOCAL LAW

Explore lobby Read FAQ

How this FAQ page is set up

We keep this FAQ page tight so you can move from question to answer without extra clicks. Each section is built around one real thing you may ask us: account checks, login recovery, payment confirmation, device behaviour on mobile, and where to reach support when something needs a human reply. The answers reference the same wallet names you see in the wallet

row: DANA, OVO, GoPay, and QRIS. If access comes up, we only discuss it where local law permits, because eligibility can change by region and account status.

DANA
OVO
GoPay
QRIS

QUICK PATHS

Three things you can check fast

Start with the question category that matches your need, then move straight to the answer that fits your account step.

Updated today

FAQ ROOM

Find the answer fast

We group questions by account step, payment check, and device use, so you do not have to read the full page. That layout works well on mobile when you only need one reply.

WALLET CHECK

Local names stay visible

When you ask about payment confirmation, the answers mention DANA, OVO, GoPay, and QRIS by name. We keep the wording aligned with the labels you see in the account area.

LOCAL RULES

Access stays region-bound

Any access question is answered with the same rule: it depends on local law and is available only where local law permits. That keeps the FAQ factual when you read it from Indonesia or abroad.

PAGE SHAPE

The page shape at a glance

answer groups we keep in the FAQ

local wallet names written in full

main support channels linked from the page

08:00-22:00 WIB

daily reply window for chat checks

HELP ROUTES

Where your questions get handled

When a FAQ answer is not enough, we keep three contact paths ready: live chat, WhatsApp, and email.

ANSWER CARE

What keeps our answers steady

We keep the FAQ steady by matching each answer to what is visible in the account area, the wallet row, and the device path you are using.

Matched to live labels

We update FAQ wording when a lobby label, wallet name, or device step changes, so the answer you read matches what you see on screen.

Same-name checks

For any payment question, we ask you to keep the sender name and account name aligned when the FAQ says that match is required. It cuts down on manual back-and-forth.

Screenshot support

If a QRIS or wallet scan needs checking, the FAQ points you to send a screenshot through chat or WhatsApp. That gives support the exact reference without guessing.

Region wording

Whenever access is mentioned, we repeat the local-law line instead of making broad claims. That keeps the FAQ usable for Indonesia while staying careful about eligibility.

Mobile first

Our answers mention Android, iPhone, and desktop paths when the steps differ. You do not have to translate device instructions from one screen to another.

Human handoff

If the FAQ does not resolve your case, support can continue in chat or email without making you restate the whole question. That keeps the thread short and usable.

How the answers stay consistent

This FAQ page is arranged so you can compare one answer against another without losing the thread.

Short answer vs full answer	Short answers cover one step. Full answers add the wallet name, login path, or support channel when you need more context.
Mobile vs desktop	Mobile entries mention the smaller menu and chat button. Desktop entries point to the wider form and side rail so you do not hunt for the same control.
Payment check vs access check	Payment checks focus on DANA, OVO, GoPay, or QRIS. Access checks use the local-law line and do not mix that point with wallet handling.
Chat vs email	Chat is for quick fixes and screenshot checks. Email is for questions that need a written record or longer back-and-forth.
Account step vs recovery step	New account questions stay on the form fields. Recovery questions focus on login reset, code timing, and what to do when a field is missing.
Local law vs device path	We keep legality and device steps apart so the answer stays clear. One tells you whether access applies; the other tells you where to tap.
FAQ page vs support channel	The FAQ gives you the first answer. If your case needs a person, the same page points you to live chat, WhatsApp, or email.

What stands out on this page

The highlights here are the visible signals that make the page easy to use: short labels, clear wallet names, device paths, and the same local-law line…

Search-first layout

Questions are grouped by account, wallet, device, and access so you can scan the page fast on mobile or desktop.

Local wallet names

DANA, OVO, GoPay, and QRIS appear exactly as you see them in the account area, which keeps the answer easy to match with your screen.

Straight wording

We keep the answers short, plain, and tied to one task, so you do not need to interpret long paragraphs before taking the next step.

Device paths

When a step changes between Android, iPhone, and desktop, the answer says so directly instead of assuming one screen fits all.

Support handoff

Every place where the FAQ may stop points you to live chat, WhatsApp, or email, so the next move stays obvious.

Local-law line

If access is asked about, the answer repeats the local-law rule and avoids broad promises about availability.

Common FAQ questions you may ask

These questions are the ones people usually ask after landing on the page, so we keep the answers short, direct, and tied to the same account steps, wallet names, and support paths. If you need more than one reply, the page points you to chat, WhatsApp, or email, and the local-law line stays in place whenever access is part of the question.

It covers the questions we hear before and after account opening: form steps, wallet checks, login recovery, device paths, and where support takes over. If access is mentioned, we keep the local-law rule in place.

Those replies sit in the payment checks part of the page, where we use the same wallet names you see in the account area. That keeps the wording matched to your screen and easier to follow on mobile.

Yes. The page is written so you can read it on Android, iPhone, or desktop without losing the step order. When a control moves between screens, we say so directly in the answer.

Open live chat and mention the step that stopped you, such as a password reset, code delay, or a missing field. If you have a screenshot, send it with the message so support can answer the exact issue.

We answer access questions with the local-law line first, then we point you to the relevant step if your region and account status allow it. That keeps the reply clear without making a broad promise.

Chat and WhatsApp are handled during 08:00-22:00 WIB, so quick questions often move faster there. Email is slower, but it is useful when you need a written record or a longer case thread.

If the answer solves it, follow the step in your account and continue. If not, take the same question to chat or email so the next reply starts from the exact point you reached.