DANA, OVO, GoPay, and QRIS are the wallet names we answer here, and this FAQ also covers login, device access, and support timing.
This static page groups the questions we hear most into one place, so you do not need to jump between the lobby, chat, and your wallet app. We keep the replies short on purpose: first the account step, then the device path, then the support route if you still need us. The chips below name the local rails we actually mention in
these answers, and the same wording appears in live chat so you can match it quickly on mobile or desktop.
The page is built around the questions you ask most often, not around broad platform language.
The FAQ opens with login, device, and name-check questions, so you do not have to search the lobby first. That keeps the shortest route ready when you only need one step.
We name the local rails inside the answers because that is what Indonesian accounts ask about most. Each reply shows the exact handoff step, where status appears, and what to do if the name does not match.
When a question touches access or eligibility, the answer stays tied to local law and the region where the feature is allowed. That keeps the FAQ factual and avoids loose promises.
When an answer needs a human check, you can reach us through live chat, WhatsApp, or email without leaving the page. The desk stays open 24/7, and we keep the same account steps whether you send a screenshot from Android, iPhone, or desktop. That matters when a wallet name, device session, or login code needs another look.
Use live chat when you want a fast account check. We keep it open 24/7, and the same desk can look at login, wallet status, or a missing code while you stay on the page.
WhatsApp works well on mobile when you want to send a screenshot of DANA, OVO, GoPay, or QRIS status. We answer in the same language and keep the next step short.
Email fits longer cases such as a name mismatch or a device session that needs another look. We reply with the exact step that matters, so you can continue without guessing.
We write these answers from the account steps we actually use: name match, device check, wallet status, and support timestamp.
Before a wallet handoff is confirmed, we check that the account name matches the payout name. That simple step reduces back-and-forth and gives you a clear reason if anything needs another look.
We keep a support timestamp for each chat so you can refer to the same case if you return later. It also helps us trace which login or device step was already checked.
If you open from Android, iPhone, or desktop, we compare the browser path, not just the device type. That makes the FAQ useful when a session behaves differently on one screen.
Whenever access or eligibility comes up, we keep the answer tied to local law and to the region where the feature is allowed. We do not stretch that into a promise that does not fit your area.
Each support reply says whether your request is pending, needs a small fix, or is ready for the next step. That keeps the FAQ consistent with what you see in chat and WhatsApp.
We keep one account path across the page: check the question, confirm the detail, then contact us if the answer still does not fit. That structure is easy to revisit on mobile data.
The same answer should read the same on Android, iPhone, and desktop, so we check each one before publishing.
| Android Chrome | The FAQ accordion opens cleanly on Android Chrome, so you can read one answer at a time without the page jumping. That matters when you are checking a wallet step on mobile data. |
|---|---|
| iPhone Safari | On iPhone Safari, the same answers keep the text width narrow and the buttons easy to tap. We test that path so your chat follow-up starts from the right question. |
| Desktop screen | On desktop, the FAQ leaves more room for longer support replies, which helps when a code, name, or device detail needs to be checked line by line. |
| DANA | DANA questions usually focus on whether the account name and wallet name match before you send another request. We answer that step separately so you can see the exact check. |
| OVO | OVO answers stay close to the same rule, but the wording points you back to the chat case if the session was already opened. That keeps the next action obvious. |
| GoPay and QRIS | GoPay and QRIS are grouped when the route is the same and split when the app handoff differs. We keep that distinction in the FAQ because it saves time on mobile. |
| Quick reply or full check | Short account questions get a short reply; name mismatches, device changes, or pending status checks take a fuller answer. The comparison stays useful because it tells you what happens next. |
These are the room names people ask about first, and we keep them visible because they tend to trigger the same account questions.
If a question is short, the answer here stays short too. We keep every reply tied to one account step, one wallet name, or one support route, so you can move from the page to chat without rereading a long block. Use the questions below when you want the cleanest path for DANA, OVO, GoPay, QRIS, device checks, or local-law access.