We keep the FAQ short so you can find account steps, DANA, OVO, GoPay, and QRIS answers without digging through the lobby.
This page exists for one job: give you the answer fast, then point you to the next step. We group the FAQ by account setup, payment status, device behaviour, and support hours so you do not have to scan long paragraphs. When a question mentions DANA, OVO, GoPay, or QRIS, we keep the wording tied to the exact step you need. If
eligibility or access is discussed, it depends on local law and is available only where local law permits.
The FAQ is built like a fast path, not a long article. You can jump from account questions to payment status, then to support or access wording, without losing the thread.
When a question needs a human reply, we keep the route visible inside the FAQ. Live chat is the fastest path for account or status checks, WhatsApp is useful when you want to keep the thread on your phone, and email helps when you need to paste a longer reference. We state the hours next to the channel names, so you do not have to guess when someone is on duty. That saves time when your account step stalls or a payment answer is not clear.
Use this first for fast account, access, or status questions. We keep it open from 08:00 to 22:00 WIB, and it is the quickest way to match the FAQ wording with what you see on screen.
This is the easiest route when you want to keep your question on your phone. Send the detail, paste the screenshot if needed, and read the FAQ answer beside it before you send anything else.
Use email when your question needs a longer reference or a clear trail. We keep it for account steps that need more context, and we answer in the same language used across this FAQ.
Trust here comes from plain wording, not from extra claims. We keep the answer order consistent, name the local rails where they matter, and state the account step before the next action.
We place the step in the same order you will see it on screen, so you know whether to fill the form, confirm a code, or wait for a status update before moving on.
DANA, OVO, GoPay, and QRIS appear by name wherever they matter. That lets you match the FAQ to your wallet or transfer screen without guessing which method the answer is about.
When access depends on region, we say so directly and keep the phrase close to the answer. It helps you see whether the question applies where you are before you take the next step.
We show where the same answer works on mobile, tablet, and desktop, because your screen size can change the steps you need. That keeps the FAQ practical instead of abstract.
Each answer is trimmed to the point, then expanded only when the extra detail changes the step. You get enough context to act, but not so much text that the page becomes hard to scan.
We keep the support hours visible next to the channel name, so you know whether to message now or wait. That small detail helps when you are checking status after business hours.
The FAQ works because the same question gets the same shape every time. We keep the wording short, the account step in order, and the support route attached…
| Account step | We show the step before the explanation, so you can tell whether the answer is about starting, confirming, or checking a status. |
|---|---|
| Payment name | When the answer is about DANA, OVO, GoPay, or QRIS, we write the name first and keep it unchanged. That makes the FAQ easier to match with your own transaction screen. |
| Support time | The hour window appears with the channel, not far away in another section. You can see at a glance whether the help path is open when you need it. |
| Device path | Mobile, tablet, and desktop are all treated as real paths, not side remarks. We tell you which screen the answer fits, which saves time when your layout changes. |
| Eligibility line | If a question depends on local law, the wording stays direct and short. You do not have to guess whether the answer applies in your location. |
| Answer length | Each answer is kept tight enough to scan, but long enough to include the step you need. That balance matters when you are checking the page on the move. |
| Next action | Every answer ends with a clear next move, such as checking the field, waiting for a status, or contacting support. That keeps the FAQ practical from start to finish. |
These are the visible pieces you can expect every time you open the FAQ. We use short question labels, named local rails, clear device paths, and simple support…
This last block keeps the questions in the same language you would use when you message us. We cover how to find the right answer, which local rails are named, how support hours work, what device paths matter, and where local law changes the response. Each answer stays short enough for mobile, but still gives you the exact step or channel to use next.