Reference

FAQ that answers what you need

Our FAQ keeps the questions you ask most often in one place, from account setup to support hours and access checks, so you can read a direct answer…

Clear answersLocal railsFast searchMobile ready

Browse Lobby Read FAQ

What this FAQ page covers

We wrote this page to answer the questions you ask before, during, and after account setup: what the FAQ covers, where to reach support, which payment rails appear in answers, and how device access behaves when you switch between phone and desktop. When a topic touches funding, we keep the local names in view - DANA, OVO, GoPay, and QRIS - so

you do not have to guess which rail a question refers to. The page is also built for fast scanning, with short headings and direct language that make each answer easy to compare.

DANA
OVO
GoPay
QRIS

THREE PATHS

Three FAQ paths we show first

These three cards show the route we expect you to take first: the FAQ entry point, the rail context, and the policy line that matters when access is in question.

LOBBY PATH

Start from the first screen

Open the page, read the first block, and jump straight to the question that matches your…

RAIL CONTEXT

Local payment context

When a question involves funding, we name DANA, OVO, GoPay, and QRIS so the answer stays…

LAW CHECK

Eligibility wording

Any access or eligibility question ends with the same line: available only where local law permits.

STRUCTURE SNAPSHOT

FAQ page at a glance

FAQ questions

help routes

local rail chips

device paths

HELP ROUTES

Ways to reach us fast

When a FAQ answer is not enough, our support team takes over through live chat, WhatsApp, and email from 08:00-23:00 WIB every day. We keep the same tone as the page: short, direct, and tied to the exact account step you are asking about, so you can attach a screenshot or reference ID without repeating the whole story.

Team online

Live chat

Use live chat when you need the fastest reply on an account step, a missing screen, or a wording check. Send the exact question and one screenshot, and we can usually point you to the right FAQ entry without a long exchange.

WhatsApp is useful when you are away from the desktop and want the same answer in a chat thread you can keep. Include your device, the section name, and what you already tried so we can narrow it fast.

Email

Email works best for detailed cases that need a clearer trail. Send the issue, the time you saw it, and any file or screenshot, and we can answer with the same wording the FAQ uses.

EDITORIAL CHECKS

How we keep answers consistent

The FAQ is written by the same team that handles account issues, so the wording stays aligned with what support can actually do.

Current wording

We keep each answer tied to what support can do today, so you do not end up following outdated steps.

Local law line

Any access or eligibility question points back to local law, and we say that in plain English instead of hiding…

Named rails

When a question touches funding, we name DANA, OVO, GoPay, and QRIS directly on your screen, so you know which…

Device parity

The same FAQ answer should read the same on mobile and desktop, with the same steps and labels.

Support handoff

If a question needs more detail than the page can hold, our chat team can pick it up with the…

Searchable structure

Short headings, compact paragraphs, and clear question labels make the page easy to scan when you are checking one answer…

CONSISTENT ANSWERS

What changes and what stays

The answer style on this page is intentionally steady: each section uses the same direct language, the same local terms, and the same account steps whether you read it on a phone…

Mobile vs desktop

The wording stays the same, while the layout shifts to fit your screen. That means the answer you read on a small phone still matches the one you see on a wider browser.

Before login vs after login

Questions that do not need account data stay public; account-specific questions point you to chat after login so we can check the right details without guessing from your side.

Support vs page text

The FAQ gives the short answer first, then support can add the missing step if your case is unusual. Both use the same terms, so nothing gets lost in translation.

Local rails vs generic wording

When a funding question appears, we name DANA, OVO, GoPay, and QRIS directly. That keeps the answer specific and easier to compare with what you see in your wallet.

Access vs eligibility

Access tells you how the page works; eligibility tells you whether local law allows it in your area. We keep those apart so the answer does not overpromise.

Quick question vs detailed case

Simple questions get short replies, while detailed cases may ask for a screenshot or the exact step where you stopped. The core wording stays the same either way.

FAQ vs account form

The FAQ tells you where to go and what to expect; the account form collects your details. We separate those jobs so you do not repeat yourself before you need to.

PAGE MARKERS

What stands out on this page

The page feels different because it behaves like a fast answer hub: question labels are short, the first screen shows where to go next, and the local rails…

Short labels Each question uses plain wording, so you can spot the…

Rail chips DANA, OVO, GoPay, and QRIS appear as chips where payment…

Direct steps When an answer includes an account step, we name the…

Eligibility line Any access question ends with a local-law reminder, written in…

Support pointer The page shows where to ask next if the FAQ…

Mobile fit The same FAQ wording works on a narrow screen, so…

Questions people ask first

These are the questions we answer first because they come up before someone opens an account or sends a message. Each answer is short on purpose: it tells you what the FAQ covers, how to find the right topic, when to contact support, and where local-law wording appears. If your situation is unusual, the same page still points you to the next step.

This page gives you the shortest path to account, access, and support answers. We keep the wording direct so you can read one question, check one answer, and move on without extra back-and-forth.

Start with the question headings, then use the short section labels and chips to narrow the topic. If your issue is about funding, look for DANA, OVO, GoPay, or QRIS in the answer.

No, the wording stays the same on mobile and desktop. The layout adjusts so the page still reads cleanly on a small screen, which helps when you check a question on the move.

Open live chat or send us a message through the contact path shown here. Include the exact step, your device, and a screenshot if you have one, so we can answer the right issue first time.

Because access and eligibility depend on where you are and what local law allows. We keep that line visible in the answer so you know the limit before you try to continue.

When a FAQ answer touches funding, we use DANA, OVO, GoPay, and QRIS by name. That way you can match the wording on the page with the wallet or QR screen you already use.

We change it whenever support steps, access wording, or payment rail details need a refresh. The goal is simple: the answer you read here should match the answer our team sends in chat.