Reference

capcusjp FAQ for Indonesia Accounts

Open your account in seconds and we will show the full FAQ set, from sign-in checks to wallet status for DANA, OVO, GoPay, and QRIS.

Account checksDANA, OVO, GoPay, QRISAndroid, iPhone, desktopLocal law applies

Explore the lobby Read FAQ

What This FAQ Page Covers

This static page groups the questions you ask most about sign-in, wallet status, device access, and support timing. We keep the answers short, so you can move from a DANA or QRIS check to the next step without scanning long paragraphs. If a question touches eligibility, we say it depends on local law and is available only where local law permits. The

same page reads the same on Android Chrome, iPhone Safari, and desktop Chrome, which makes it easy to return later.

DANA
OVO
GoPay
QRIS

FAST ANSWERS

Three FAQ Paths We Answer

Most questions land in three places: account checks, wallet timing, and policy wording.

Updated today

LOBBY PATH

Find the right thread

Use the FAQ entry icons to jump to sign-in, wallet, or device questions. The layout keeps the common account step one tap away, which matters when you are reading on a small screen.

LOCAL RAILS

Wallet questions

We name DANA, OVO, GoPay, and QRIS where they matter, so you can match the FAQ answer to the exact transaction type before you resend a proof or open chat.

POLICY LINE

Access wording

If a question touches eligibility, we state that it depends on local law and is available only where local law permits. That keeps the answer clear without overpromising.

QUESTION FLOW

How the FAQ Is Structured

local payment rails named in the answers

support paths listed beside the FAQ

device paths we test for reading

static page for quick account checks

HELP LINES

Where to Ask a Follow-Up

If an answer does not settle the issue, we keep the follow-up simple. Open live chat, send email, or use the contact form, then mention the exact FAQ topic, your device, and the time you tried it. Our desk answers every day from 09:00 to 23:00 WIB, and that window covers most sign-in and wallet questions before you return to the page.

Team online

Live Chat

Use the chat bubble for the quickest FAQ reply. Tell us whether the issue is sign-in, DANA, OVO, GoPay, or QRIS, plus the browser you used, and we can narrow the answer quickly.

Email

Email works well when you want to attach a screenshot or transaction code. Add your username, device name, and the FAQ topic in the subject line so we can route it to the right desk.

Contact Form

The form keeps a single thread for account checks, policy wording, or a wallet status follow-up. We store the time stamp and reply in one place, which makes it easier to revisit later.

EDITORIAL CHECKS

Signals Behind Each Answer

Every answer on this page is written to be checked against a real account step, a named payment rail, or a device path you can repeat yourself.

Named rails

Where a question touches wallet flow, we name DANA, OVO, GoPay, and QRIS directly so you can match the answer to the exact rail you used.

Device checks

We test the FAQ reading flow on Chrome for Android, Safari for iPhone, and desktop Chrome, because those are the paths most people use when they ask us for help.

Account step

When a thread needs verification, we ask for the username, the registered phone number, or a fresh screenshot, depending on the topic and how the account was opened.

Time stamps

Support replies stay tied to the time you sent the question, which helps when you are comparing one wallet attempt with another and need the exact sequence.

Plain wording

We keep the answer short enough to scan on mobile, but still specific enough to tell you which button, tab, or status message to look for.

Local law note

If a question touches access or eligibility, we say that it depends on local law and is available only where local law permits.

ACROSS DEVICES

How Answers Stay Consistent

The same FAQ answer should read the same way whether you check it before sign-in, after sign-in, or on a different device.

Before sign-in

You can read account, wallet, and eligibility answers before opening a session, which helps you decide whether to continue or ask support first.

After sign-in

The same topics appear with your current status in mind, so you can compare a wallet delay or a profile issue against what the account page shows.

Android Chrome

On Android, the FAQ cards stack vertically and the text stays short enough to scan while you move between chat, wallet, and lobby tabs.

iPhone Safari

On iPhone, the same answer order remains visible, so you do not lose the thread when you switch from a message to a transaction screen.

Desktop Chrome

Desktop gives you more room for the support paths and the local payment chips, which makes it easier to compare several questions at once.

Wallet checks

If the question is about DANA, OVO, GoPay, or QRIS, we keep the answer near the transaction step instead of sending you through unrelated pages.

Policy wording

If the question touches access or eligibility, the same local law note appears wherever you open the page, so the phrasing stays consistent.

WHAT SHOWS FIRST

What You See First

The visible pieces on this page are the question chips, the support paths, the device labels, and the local payment names that reappear where they matter.

FAQ Chips The chips point you to account, wallet, and device questions…

Local Names We repeat DANA, OVO, GoPay, and QRIS only where they…

Game Tags When a question refers to slots, live tables, or crash…

Support Hours The service window appears near the contact paths, making it…

Device Paths Android Chrome, iPhone Safari, and desktop Chrome are shown as…

Local Law Line If access comes up, the wording states that it depends…

FAQ Questions We Hear Most

These are the questions people ask when they want a fast answer before they open the lobby or send a chat. We keep each reply short, tied to one step, and easy to check against your screen. If you need a live reply, use the support paths above; if you only need clarity, these answers cover the usual account and wallet cases.

Open the FAQ chip near the header or footer, then choose the topic that matches your question. On mobile, the cards stack cleanly, so you can reach account or wallet answers in one tap.

We name DANA, OVO, GoPay, and QRIS wherever the topic is about a local transaction. That lets you match the answer to the exact rail you used before you contact chat.

Send the time, the payment name, and a clear screenshot of the status line. Add your username if the question is tied to the account, because that helps us compare the event with your thread.

Yes. The same page opens in Chrome on Android, Safari on iPhone, and desktop browsers, and the answer order stays the same so you do not lose your place when you switch screens.

For account-linked questions, we may ask for the registered phone number, the username, or the last visible status on screen. That keeps the reply tied to the correct account step.

We mention slots, live tables, and crash rooms when the question touches category-specific access or screen behavior. That way the answer points you to the right section instead of sending you across the lobby.

Our desk is active every day from 09:00 to 23:00 WIB, and live chat is usually the quickest path. If you send email or the form, the answer comes in the same thread.