Reference

FAQ for Account Answers

We keep the FAQ focused on account access, wallet status, and support timing, so you can find the right answer without digging through the lobby or scrolling past…

Account accessWallet checksSupport timingMobile and desktop

Browse The Lobby Read FAQ

How this FAQ page works

This static page is built as a quick answer map for the questions we hear most: login trouble, wallet status, device changes, and where to ask for help when something needs a second look. Each section stays short on purpose, because the useful part is the exact step or the exact channel, not a long explanation. If a question touches access or

eligibility, we keep it tied to local law and only where local law permits. When the answer points to a wallet check, the chips below point you to DANA, OVO, GoPay, and QRIS.

DANA
OVO
GoPay
QRIS

THREE PATHS

The three FAQ paths

Most questions on this page fall into three groups: where to open the right account step, how to read a wallet status, and when local-law wording matters.

Updated today

ACCOUNT

Find the right step

Account access, wallet status, and support questions sit in one FAQ trail, so you do not need to search page by page. Open the item that fits and follow the same steps our support team uses.

WALLET

Read the status line

When you ask about DANA, OVO, GoPay, or QRIS, we point you to the exact steps the FAQ uses for status checks, name matching, and what to send if a request is still pending.

POLICY

Keep access local

If a question touches access or region eligibility, the answer stays tied to local law and only where local law permits. That keeps the FAQ factual, brief, and useful for Indonesia readers.

PAGE SHAPE

What the FAQ page covers

question families we separate

device paths we name

24/7

chat access we mention

wallet names shown

HELP ROUTES

Where to ask next

If the FAQ answer is not enough, we point you to the shortest help path instead of asking you to repeat yourself. Live chat is the fastest option when you need a quick account check, while email works better when you want a written record or have screenshots to send. We also keep the question text simple so you can copy it into a message without changing the meaning.

Team online

Live Chat

Use it when the FAQ tells you to confirm login, wallet status, or a page error. Our chat is open 24/7, and the same plain-English steps apply on phone or desktop.

Email

Choose it when your question needs screenshots, a longer account note, or a reply you can keep in your inbox. The FAQ points to email only when a slower written trail makes more sense.

Help Form

If you want a structured handoff, the form matches the FAQ questions to the right team. Add your username, phone number, and the exact screen you saw so we can check it faster.

TRUST SIGNALS

Why these answers hold up

We write the FAQ from the account flow first, not from a generic script. That means the answer names the screen, the step, or the channel you actually need, and it keeps…

Exact steps

We spell out the tap or click order for the question, so you can repeat it without guessing what comes next on phone or desktop every time cleanly.

Named wallets

DANA, OVO, GoPay, and QRIS appear by name where they matter, which keeps the answer aligned with the screen you see when you check status or send a message.

Clock times

When a reply window matters, we use clear times instead of vague language, so you know whether to wait or send a follow-up from the same channel again.

Minimum data

If a lookup needs your username, phone number, or a screenshot, we ask only for that and nothing extra, so you can send the right detail in one message.

Local-law line

Any access or eligibility question stays tied to local law and is available only where local law permits.

One topic each

Each answer sticks to one task, which keeps the page easy to scan when you are reading on a small screen and helps you move from one question to the next without losing context.

SIDE BY SIDE

How the answers stay consistent

The FAQ keeps the same logic across every question, so the wording does not change when you switch from account help to wallet help or from phone to desktop.

Account access

Use this path when login fails, a password needs a reset, or the phone number on file needs checking.

Wallet status

Use this path when DANA, OVO, GoPay, or QRIS shows pending or does not match the expected status.

Support hours

Use this path when you need to know whether chat is open or email is the better record.

Android Chrome

On Android Chrome, the steps stay in the same order, so you can follow them with one hand.

iPhone Safari

On iPhone Safari, the same short wording helps you move between tabs without losing the place.

Desktop

On desktop, the answer reads the same, but the larger screen makes screenshots easier to compare.

Local law

If local law applies, the answer says access depends on it and is available only where local law permits.

VISIBLE DETAILS

Visible details in the FAQ

A useful FAQ page should be easy to spot at a glance. We keep the question text short, call out the exact wallet names, and separate device steps…

Short questions Each question is written in plain English, so you can…

Named wallet chips DANA, OVO, GoPay, and QRIS appear where they matter, which…

Separate device steps Android Chrome, iPhone Safari, and desktop get their own wording…

Clear support timing When chat or email timing matters, we write the hours…

Local-law wording Any access-related answer says when local law applies, so you…

Account detail prompts We only ask for the account detail needed for the…

FAQ questions we hear most

These answers are written for the questions people actually ask first: where to start, what to send, how long to wait, and which device path fits your screen. We keep each answer short enough to skim, but specific enough that you can use it right away. If a question touches access or eligibility, the answer will say it depends on local law and is available only where local law permits.

Open the question that matches your issue, read the first step, and only move to support if the answer still leaves a gap. That keeps the process short and avoids sending the wrong details.

Check the phone number on file, confirm the password, and try the same step once on Android Chrome or iPhone Safari. If it still fails, send the exact error text to chat.

We name DANA, OVO, GoPay, and QRIS where the answer depends on the wallet screen. That way you can match the wording to the option you actually used.

Live chat is the fastest route and is open 24/7. If your question needs screenshots or a written trail, use email and include the page or message you saw.

Yes. The steps are written so they still read cleanly on Android Chrome, iPhone Safari, and desktop, with the same order of actions in each case throughout the answer.

Then the answer says so directly. We only cover access where local law permits, and we avoid giving you a step that does not fit your region there.

Have your username, phone number, and a screenshot or exact time ready. That gives us enough detail to trace the question without making you repeat the whole story.