Reference

Your FAQ answers in one place

Start here for login, account, wallet, and support answers. If you are in Yogyakarta, the same FAQ flow opens cleanly on mobile or desktop, and each answer stays…

Browse Lobby Read FAQ

What this FAQ page covers

This page is built for the questions that usually come up before you open an account: how to read the login step, where the wallet names appear, and when a support handoff is worth it. We keep the same wording across the page so you can compare an answer on phone, then continue on desktop without re-learning the path. The chips for

DANA, OVO, GoPay, and QRIS sit beside the answer blocks as a quick cue, not as filler, so you can match the right route before you send anything.

DANA
OVO
GoPay
QRIS

THREE CHECKPOINTS

Three points that matter first

The first thing we clarify is where the question belongs: login, account steps, wallet matching, or support follow-up.

Updated today

LOBBY

What the FAQ points to first

This FAQ points you to the login and account steps first, so you can open the right answer without scanning the whole page. It is written for quick use on phone or desktop.

WALLETS

How the wallet names are shown

We show DANA, OVO, GoPay, and QRIS beside the relevant answers, so the wallet name is visible before you send any request. That keeps the FAQ tied to the right rail.

POLICY

The line we keep exact

When access is mentioned, we use the exact line where local law permits and keep it in the same place each time. That makes the answer easy to compare across sections.

PAGE AT A GLANCE

A few quick FAQ facts

sections on this FAQ page

local wallet chips shown

support channels named here

account-name match before a request moves on

HELP ROUTES READY

How to reach us on FAQ issues

If an answer still feels unclear, live chat is the fastest route, and WhatsApp works well when you want to send a screenshot of the question.

Live Chat Use live chat when you want the fastest reply on login, wallet, or account questions. During 09.00-23.00 WIB, the same thread stays attached to your case, so you can return with a screenshot if needed.

WhatsApp WhatsApp works well when your FAQ question needs a photo or a pasted code from the screen. We answer in the same 09.00-23.00 WIB window and keep the wording short so you can follow the next step.

Email Email is useful for longer checks, especially when a wallet name or login step needs another look after chat. We keep the subject tied to your account so the reply does not get lost.

WHY ANSWERS HOLD

Trust signals inside the FAQ

We keep this FAQ practical: short answers, the same wording across devices, and clear handling when a question needs verification.

Exact wording

We repeat the same access line each time, so you know when where local law permits applies. The FAQ does not shift the wording from one section to another, which helps you compare answers quickly.

Name match

Before any withdrawal question moves forward, we check that the account name matches the wallet or bank record. That step is simple, but it prevents back-and-forth if the details do not line up.

Device log

If you contact us from phone or desktop, we can note the browser, device, and time of contact. That gives the support team a clear trail when a FAQ answer needs verification.

Short answers

The answers stay short on purpose, because long text hides the step you actually need. Each block gets straight to the point, then points you to the next action or support path.

Channel trace

Live chat and WhatsApp both keep a readable message history, so you can check what was said if you return later. That makes the FAQ easier to follow after a pause.

Local law line

When access comes up, we use the same legal phrasing and do not swap it for softer wording. That consistency helps you see exactly what applies before you move on.

CONSISTENT ACROSS SCREENS

How the FAQ stays the same

A question asked on phone should land on the same answer you see on desktop, even if the layout shifts.

Phone vs desktop

Phone and desktop show the same answer order, even though the screen size changes. You can start on mobile, then continue on a larger screen without losing your place.

Login vs account

The login step and the account step are separated, so you can tell whether the issue is access or profile setup. That saves time when you ask the next question.

DANA vs QRIS

DANA, OVO, GoPay, and QRIS appear as their own chips, not hidden in long text. You can compare the wallet name against the answer before you send anything.

Live chat vs WhatsApp

Live chat is faster for back-and-forth, while WhatsApp is easier when you need to send a screenshot. The FAQ points to both so you can choose the cleaner route.

Verification vs follow-up

Verification asks for matching details first; follow-up happens only if the answer needs another look from our side. The FAQ keeps those two stages separate so you know what comes next.

Access line vs local law

The access line always uses the same words, and the local-law phrasing stays untouched from section to section. That lets you compare eligibility language without guessing whether the meaning changed.

Mobile scan vs longer read

On mobile, the answer blocks stay compact. On desktop, the same text is easier to compare side by side when you want to read it more slowly or check another answer.

VISIBLE FAQ TOUCHES

What stands out on the page

The most visible parts are the short question blocks, the chip row with DANA, OVO, GoPay, and QRIS, and the support links that sit close to the answers.

Short blocks The short question blocks are the first thing you see…

Chip row The chip row keeps DANA, OVO, GoPay, and QRIS visible…

Account step The account step appears in plain words, not in a…

Support links Live chat, WhatsApp, and email sit near the questions that…

Local-law wording The same where local law permits line appears wherever access…

Desktop carryover Desktop carries the same order you saw on phone, so…

Questions before you open

These are the questions we hear before an account is opened, and each answer stays on one job: explain the FAQ path, show the wallet names, or point you to support. We keep the language short so you can move through it on mobile, then revisit the same answer on desktop if you want to check a step again. Where local law permits, the wording stays exact.

It covers the questions that usually come first: login, account steps, wallet names, and where to send a support request. The answers are short, so you can move through the page without losing the thread.

Yes, you can read it first. The page is written for pre-account checks, so you can see the login path, wallet chips, and support routes before you decide what to do next.

We show DANA, OVO, GoPay, and QRIS in the chip row. That keeps the wallet name visible beside the answer, so you can match the right route before you send a request.

Use live chat first if you want the fastest reply, or WhatsApp if you want to send a screenshot. Email is there for longer checks when a wallet name or login step needs another look.

The most common step is the name match check. We confirm that the account name matches the wallet or bank record before a request moves on, because that keeps the next step clear.

No, the wording stays the same. On mobile the blocks are compact, and on desktop the same answers appear in the same order, so you can compare them without relearning the page.