Reference

FAQ for your account and wallet

We keep this FAQ tied to the steps you actually need: how to open your account, how DANA, OVO, GoPay, and QRIS are used, and where to reach…

Account stepsDANA, OVO, GoPay, QRIS08:00-24:00 WIBMobile and desktop

Explore lobby Read FAQ

How this FAQ stays practical

This page is built to answer the small things you check before you move forward: which account details we ask for, which wallet rail fits your balance, and what to do when a login or verification step slows down. We keep the answers short on purpose, then add the action you can take next so you do not have to guess. If

you are on a phone, the same FAQ works in Chrome, Safari, and desktop browsers, with the menu and wallet row placed where you can reach them quickly. When access or eligibility comes up, we state the local-law rule first, then the step that follows.

DANA
OVO
GoPay
QRIS

THREE QUICK CHECKS

The three FAQ areas people open first

When you open the FAQ, you are usually checking one of three things: how fast your account step clears, which wallet to use, and what support path works…

Updated today

ACCOUNT

Login and verification

We explain password reset, one-time code checks, and the extra document request only when a profile needs it. That keeps the FAQ useful before you try the next step.

WALLET

DANA, OVO, GoPay, QRIS

Our payment answers tell you which wallet label to use, how the reference appears, and what to do if a transfer is pending. The same steps apply on phone and desktop.

POLICY

Access by local law

We state the local-law rule first, then the next action. If access is allowed where you are, you can continue; if not, the FAQ tells you to stop there.

PAGE SHAPE

What the FAQ groups together

wallet rails we name in answers

support channels you can use fast

device paths we spell out

local-law rule before access

HELP ROUTES

How to reach us from FAQ

If an answer does not solve your case, we point you to live chat and WhatsApp first, then to email if you need a written trail.

EDITORIAL SIGNALS

Why the FAQ feels grounded

The page is written from the same support flow we use with you, so the wording stays close to real account steps rather than abstract filler.

Support script match

Our FAQ uses the same wording our chat team uses, so the answer you read is the answer you can act on. That keeps login, wallet, and access steps aligned when you need to move quickly.

Named wallet rails

We list DANA, OVO, GoPay, and QRIS by name, then say how each step appears in the wallet row. You can match the label before you confirm anything.

Device checks

We spell out Android Chrome, iPhone Safari, and desktop paths where the screen changes. That matters when a code field, browser cache, or saved password affects the next step.

Verification order

We explain username first, then one-time code, then any document request only when a profile needs it. The sequence keeps the FAQ easy to follow and reduces guesswork.

Local-law wording

When access or eligibility comes up, we state the local-law rule before anything else. If your area is not covered, the answer stops there and does not send you into a dead end.

Plain action words

Each answer ends with a simple next move such as check, retry, or contact us. That keeps the page useful when you are reading from a phone and do not want extra text.

How answers stay consistent

The same question should not give you a different path on a different device, so we keep the FAQ wording stable across the main access points.

Login from home

The same account step appears from the home page or the FAQ, so you do not need to search for a separate help path before you sign in.

Wallet row

DANA, OVO, GoPay, and QRIS stay in the same order, so you can match the label before you submit a wallet step.

Android Chrome

On Android Chrome, the FAQ keeps short paragraphs and clear actions so you can read without zooming or losing the code field on screen.

iPhone Safari

On iPhone Safari, the same answer fits the smaller screen and keeps the wallet names visible above the next action.

Desktop browser

On desktop, the FAQ stays open beside the lobby, which helps when you are checking one step and completing another in the same session.

Live chat

We name live chat and WhatsApp together, then email, so you can pick the channel that matches the urgency of your FAQ question.

Eligibility check

When access is tied to local law, the answer states that rule first and stops there if your area is not covered.

What stands out in the FAQ

The page is built around visible cues you can scan fast: short cards, named wallet rails, clear support hours, and direct account steps.

Short card layout

Each answer is split into a short card so you can move from one question to the next without losing the thread. That is useful when you are on a phone and want a quick scan.

Wallet labels

DANA, OVO, GoPay, and QRIS appear where they matter most, which helps you match the right label before you submit a wallet step. The names stay unchanged across the page.

Support hours

08:00-24:00 WIB is shown in the help path, so you know when a live reply is most likely. That keeps the FAQ tied to a real support window instead of a vague promise.

Device split

Mobile and desktop wording stays aligned, but the FAQ still points out where the screen looks different. That helps you keep track of login fields, wallet rows, and code prompts.

Account steps

The FAQ names the steps in order: sign in, confirm the code, and complete any profile check only when needed. You can follow that sequence without digging through extra pages.

Local-law line

When eligibility matters, the answer says it depends on local law and is available only where local law permits. That is the line we use before any other detail.

Questions people ask before opening

This final block answers the questions we hear most: login, wallet labels, support hours, device checks, and what changes when local law affects access. Each answer stays short so you can scan it on phone, then move to the next step without losing your place.

Start with the question that matches your step, then follow the short action at the end. If you are checking from Android Chrome, iPhone Safari, or desktop, the wording stays the same.

Check the wallet label first, then confirm the reference or status shown in your app. If the step still waits after that, use live chat or WhatsApp with the screenshot and time.

We cover mobile Chrome, iPhone Safari, and desktop browsers because those are the places where screen layout changes most often. The FAQ shows where to find the code field and the next action.

Most of the time, no. If your profile needs a one-time code or a document check, the FAQ says that in the answer before you move on, so you know what to prepare.

Contact us when the same step fails more than once, when a code does not arrive, or when the wallet status does not change. Use the channel that fits your pace, then send the exact step.

You can read the page, but access to the account steps depends on local law and is available only where local law permits. The answer will stop there if your area is not covered.

Yes. We use those categories only where they help explain the next account action, such as login, wallet selection, or device checks, so the FAQ stays focused on what you need.