We built this FAQ for Indonesia so you can check account steps, DANA, OVO, GoPay, QRIS, and support timing before you open an account.
This page collects the questions we hear before your first account step and after you log in. You can check how DANA, OVO, GoPay, and QRIS are handled, what to do when a name or phone number does not match, and how the same answer changes on mobile or desktop. We keep the language simple so you can move from the question
to the next step without guessing. If you need a faster route, the chips below point you to the rail you use most.
These three cards point you to the parts of the FAQ people open first: the lobby path, the wallet route, and the local law note.
When an answer on the page is not enough, we move you into a live path instead of making you repeat the same question. Chat suits quick checks, email suits written follow-up, and the account form suits name or phone mismatches. Our team works in WIB, so you can plan around Indonesian hours and send the right details the first time.
Open chat during our daily 08:00-24:00 WIB window when you want a quick answer about account steps, payment status, or login. We keep the reply tied to the same details you see on screen, so you can act without back-and-forth.
Send email when you want a written reply you can keep. Include your sign-in name, the payment rail name, and the time you tried the action, because those details help us trace the exact FAQ question.
Use the in-account form when your question involves a name, phone, or device mismatch. That route keeps the record in one place and avoids asking you to repeat the same details across different channels.
We write FAQ answers from the same details you see in the account flow, payment screen, and support queue.
When we mention DANA, OVO, GoPay, or QRIS, we use the same spelling you see in the wallet and on the payment screen. That reduces confusion when you compare the FAQ to your transaction record.
We describe what to do on Android, iPhone, and desktop in plain language, including cache refresh, browser switch, and page reload. You do not need a long setup note to follow the answer.
If a question needs human help, the page points you to our WIB schedule and the channel that fits best. That way you know when chat is active and when email is the better route.
For access and eligibility questions, we do not bury the rule in small text. The answer says it depends on local law and is available only where local law permits, so the meaning stays clear.
When the FAQ mentions Live Roulette, Aviator, or Mahjong Ways, we keep the exact title from the lobby. That helps you match the answer to the same room or screen you opened.
Each reply is written to end on the next step, not on extra wording. That makes the page easier to scan when you are checking a login, a payment status, or a device change.
Use this section to see how the answers stay consistent across common situations. A question about login, a question about DANA, and a question about Live Roulette all follow the same rule…
We start with the sign-in step, the phone number, and the name on the record. If those details match, the next action is usually simple and you can move straight to the next screen.
We name the rail first, then the reference code, then the status you can see in the wallet. That helps you check DANA, OVO, GoPay, or QRIS without mixing the steps.
If you change from mobile to desktop, the answer tells you whether to reload the page, switch browser, or clear cache. That keeps the same question from turning into a longer search.
Questions about Live Roulette, Aviator, or Mahjong Ways stay tied to the exact title, so you do not need to guess which room the answer refers to. The next step stays visible.
When a status shows pending, rejected, or complete, we explain what the screen means and what detail to verify next. That prevents you from repeating the same check twice.
We point quick issues to chat, written issues to email, and record checks to the account form. Each path keeps the FAQ answer aligned with the kind of question you asked.
If the question is about access or eligibility, the answer follows local law first. That keeps the rule clear and avoids mixing one region's situation with another's.
These are the visible parts of bumihoki that shape the FAQ experience: action-led titles, local rail chips, clear screen labels, and short answers that keep the next step…
These questions cover the moments people usually stop and ask for help: opening an account, checking a payment, moving between phone and desktop, and confirming where support can step in. Each answer stays short, tied to the exact screen or step, so you can act on it without guessing. If your question is about access, we state the local law rule first.