Reference

99nobu FAQ for DANA, OVO, GoPay, and QRIS account questions

Open your account and this page gives the answers people ask most about login, lobby access, wallet checks, withdrawals, and device behavior.

Account stepsDANA / OVO / GoPay / QRISLive chatMobile and computer

Browse lobby Read FAQ

What this FAQ page covers

This page is built for quick checks, not long reading. We group the questions you are most likely to ask about account access, how DANA, OVO, GoPay, and QRIS are handled, what happens after a withdrawal request, and which device paths work best on Android, iPhone, and computer. If you are in Makassar, you can open the same FAQ on mobile data

and reach the lobby in seconds, then come back to any answer without losing your place. When access or eligibility is mentioned, it depends on local law and is available only where local law permits.

DANA
OVO
GoPay
QRIS

LOBBY PATHS

Three places your questions start

Most questions begin in one of three places: the lobby, the wallet, or the access line at the end of the page.

Updated today

LOBBY

Account and lobby questions

We answer the first questions you ask after login: where the lobby opens, how to switch from slots to live tables, and what to check if a page loads slowly on mobile data or Wi-Fi.

WALLET

DANA, OVO, GoPay, QRIS checks

The payment answers explain which local rail you used, where to confirm the reference code, and why a request can stay pending until the wallet confirms it. That keeps your next step clear.

RULES

Access and eligibility

When a question touches access, account status, or region use, we keep the answer tied to local law. If something is not available where you are, the page says so plainly instead of guessing.

PAGE FACTS

Page facts you can check

question groups on the page

local rails named here

contact paths we show

09:00-23:00 WIB

daily reply window

HELP ROUTES

Where to send a question

If the answer on the page still leaves one detail open, we give you three ways to reach us: live chat, WhatsApp, or the form.

EDITORIAL CHECKS

How we keep answers steady

We keep the page practical by writing answers from the same account flow we use for login, wallet, and device checks.

Same-step testing

We write answers after running the same steps on Android, iPhone, Chrome, and Safari, so the wording matches what you see when you tap through the page and ask a follow-up.

Wallet references

DANA, OVO, GoPay, and QRIS appear in the same order we use in the lobby chips, so you can match the question to the rail you chose without translating the label first.

Clear handoff

If a withdrawal or login question needs a human check, we say which detail to send first, such as username, time, or reference code, instead of asking you to repeat everything.

Local law line

Any access or eligibility answer stays tied to local law and is available only where local law permits, so there is no confusion about region use when you come back later.

Single source

We keep the FAQ, lobby labels, and support replies aligned, so you do not get different wording from one place to another when the same question appears in two screens.

Short paths

Each answer points to one next step only, which makes it easier to finish login checks, wallet checks, or device checks without extra back-and-forth or a long thread.

How each answer stays aligned

The comparison section shows how we answer the same question in different situations.

Login question

If your question is about access, we ask you to check username format, password entry, and browser cache first. That keeps the answer short and helps us separate a typing issue from an account issue.

Wallet question

For DANA, OVO, GoPay, or QRIS questions, we compare the time you sent the request with the reference code and status shown in your wallet. That is usually enough to explain the next step.

Mobile question

On Android or iPhone, we expect the same FAQ page, but the button order can feel different. We mention both paths so you know where the same answer sits on a smaller screen.

Computer question

On a computer, the FAQ and lobby tabs stay open together, which helps when you are checking a code from one tab and reading an answer in another. The page text stays the same.

Live table question

If the question is about Baccarat or Aviator, we point you to the room name first, then the account step second. That order keeps the answer tied to the place you were actually checking.

Support question

When you need a human reply, we compare chat and WhatsApp by speed, file sharing, and how easy it is to send a screenshot. The FAQ tells you which channel fits the case.

Local law question

For access and eligibility, the answer never changes: it depends on local law and is available only where local law permits. That keeps the page consistent whenever you revisit it.

Page details you will notice

These page details matter because they help you find the right answer faster.

FAQ search bar

The search bar sits at the top so you can type a wallet code, a game name, or a device question and jump straight to the matching answer.

Topic chips

We keep short chips for login, lobby, wallet, and device questions, which makes the page easy to scan when you only have a minute on mobile.

Reply hours label

The contact window is shown beside the help paths, so you know when live chat is active before you send the first message.

Mobile and computer path

Each answer mentions both phone and computer where needed, because the same FAQ can feel different on Android, iPhone, and a full browser.

Game names in questions

We name Baccarat, Aviator, Fortune Mouse, and Fish Hunter inside the questions so you can match the wording to the room you were checking.

Local rails in plain view

DANA, OVO, GoPay, and QRIS appear as plain labels, not buried text, so you can spot the payment path before you open a message.

Common FAQ questions here

These are the questions we hear most about account access, wallet checks, device behavior, and how the answer changes when local law sets a limit. Each reply points you to one clear next step, so you can read, act, and come back only if something still needs a human check. That keeps the page quick to use on mobile data or computer browser.

Start with the question that matches your issue, then open the answer beneath it. We keep the steps short, so you can check login, wallet, device, or account details without scrolling through unrelated text.

We cover DANA, OVO, GoPay, and QRIS because those are the rails most often tied to account and wallet questions. If your reference code does not match, send the time and amount to chat.

First check that the wallet app shows the request as sent, not just saved. If the code matches and the status still waits, send the screenshot through live chat or WhatsApp during 09:00-23:00 WIB.

Yes. The page is written for mobile first, so the same answer works on Android, iPhone, and computer. If you are in Makassar, you can open it on mobile data and move between questions fast.

We compare the time, username, and reference code before we reply, then we point you to the next step only. That keeps the check focused and avoids asking you to repeat the whole story.

Baccarat, Aviator, Fortune Mouse, and Fish Hunter are named where they help you match the question to the room. If your question is about another title, send the exact name and we will answer that path.

Access depends on local law and is available only where local law permits. If a question is about region use, account status, or device access, we say that first so you know the limit before you continue.