Reference

FAQ Help For Your Account

This FAQ puts login, access, and local-law answers in one place, and you can open it on phone or desktop in seconds.

Browse Lobby Read FAQ

How We Structure These Answers

This page exists for the questions you ask before you open an account and the ones that come up after login. We keep each answer short enough to scan, but each one still includes the step, channel, or condition you need to act on it. If your question is about DANA, OVO, GoPay, or QRIS, we name the rail exactly as it

appears in the account flow. When eligibility is part of the question, we say it depends on local law and is available only where local law permits.

DANA
OVO
GoPay
QRIS

THREE CHECKS

Three Things The FAQ Clarifies

We built the FAQ around three questions: where to start, what local wallet names appear in the flow, and what the policy line says when access is discussed.

LOBBY PATH

Questions Before You Open

If you want the shortest route into the FAQ, start with account access, login, and device…

LOCAL WALLET

Account Steps With DANA

When a question touches money rails, we name DANA, OVO, GoPay, and QRIS exactly as written…

POLICY LINE

Access and Local Law

Where access or eligibility comes up, we state the local-law line plainly.

PAGE SHAPE

FAQ Structure At A Glance

core FAQ pairs on this page

help paths in the support section

local rails named in the answers

device paths: phone and desktop

HELP ROUTES

Where To Ask Follow-Up Questions

If your question still needs a check, we keep the next step simple. Send the account ID, the screen you saw, and one screenshot through live chat or WhatsApp, then keep the same thread open until it is solved. We answer during 08:00-24:00 WIB, and email works well when you want a written trail for later.

Team online

Live chat

Use the live chat box when you need a quick check on login, access, or the wording inside the FAQ. We keep the same conversation open so you do not have to repeat your details every time.

WhatsApp works well when you want to send a screenshot from Android or iPhone. Keep your account ID in the first message and we can move straight to the point without asking you to resend the same screen.

Email

Email suits longer follow-up questions or cases that need a written trail. We read it during 08:00-24:00 WIB, and you can return to the FAQ while the reply is in progress.

PROOF POINTS

Signals We Keep Visible

A useful FAQ does more than answer a question once. It shows the same terms, the same channels, and the same access line every time you return.

Local-law wording

Whenever eligibility comes up, we say it depends on local law and is available only where local law permits. That line stays in the FAQ so you can read it before you send a message or open the account form.

Named rails

DANA, OVO, GoPay, and QRIS appear exactly as written when the question needs a rail. You can match the answer to the screen on your phone, instead of guessing which method we mean.

Device parity

The same answer reads cleanly on Android Chrome, iPhone Safari, and desktop browsers. We do not change the wording by device, so your next step stays the same wherever you opened the page.

Threaded support

Live chat and WhatsApp keep one thread per case, which makes it easier to return with a screenshot or a follow-up question. That is useful when the answer needs one more check.

Plain steps

We write the FAQ in steps you can follow without another page open. If a question needs verification, we say which detail to send and where the reply will land.

Saved wording

The copy stays stable after we publish it, so the answer you read today matches the answer you see tomorrow. That helps when you come back from mobile during a break and need the same line again.

Same Answer, Every Path

The FAQ should feel consistent whether you read it first, ask in chat, or return from a new device.

Page vs chat	The page gives you the full answer in writing; chat gives you a short follow-up when you need one more screen checked. The wording stays aligned either way.
Mobile vs desktop	On mobile, the FAQ stacks in one column and keeps the question labels close together. On desktop, the same copy opens wider so longer answers are easier to scan.
Login vs after login	Before login, the FAQ focuses on access and eligibility. After login, it shifts to the exact account step, support thread, or screen you need.
DANA vs QRIS	Both names appear where the answer needs a local rail, and we keep the spelling the same as the flow. You can match the label to your screen without guessing.
Fast read vs full check	Short labels help when you only need a quick line. The longer body stays underneath so you still have the detail when the case is less simple.
WhatsApp vs email	WhatsApp is better for screenshots and short back-and-forth. Email is better when you want a written trail and do not need the answer in one message.
Open account vs ask first	If you want to ask first, the FAQ gives you the conditions before you open the form. If you already have an account, the same page points you to the next step.

VISIBLE MARKERS

What Stands Out Here

These are the page details you will notice first: short question cards, a local-law line, named rails, and support routes that keep the same wording across phone and…

Short question cards Each card opens with the question you would actually ask…

Local-law line The access wording is written in plain language and stays…

Named rails DANA, OVO, GoPay, and QRIS appear only where the answer…

Device-friendly layout On Android Chrome, iPhone Safari, and desktop browsers, the same…

Support routes Live chat, WhatsApp, and email sit beside the page content…

Searchable wording We use plain terms like login, access, and verification, which…

FAQ Questions We Hear Often

These are the questions we expect first when you open the FAQ, and each answer stays short enough to scan on mobile. We keep the language direct so you can check access, support, and account steps without opening several tabs. If you need a deeper check, use the support paths listed above and keep the same thread open.

It covers the questions we hear before and after you open your account: access, login, support hours, device behaviour, and the exact local rail names that appear in the flow. If eligibility matters, we state the local-law line clearly.

Yes. The page stacks cleanly on Android Chrome and iPhone Safari, and the same answer stays visible on desktop. That helps when you want to check one screen during a break and finish the case later.

We name DANA, OVO, GoPay, and QRIS where the answer needs a rail label. That keeps the FAQ tied to the account step you see, instead of using a generic phrase that feels hard to match.

Send your account ID, one screenshot, and the exact question through live chat or WhatsApp. We keep the thread open so you can return with the next detail without starting from zero.

We say that access depends on local law and is available only where local law permits. If that is the only part you need, you can check it right in the FAQ before opening a message.

We answer during 08:00-24:00 WIB. If the first reply needs a check, we keep the same thread open and use email when you want a written trail for later.