This page keeps the first answers in one place: how to open the account, how to read the lobby, what to check when a wallet entry is pending…
The FAQ is written to save time when you open an account, check the lobby, or look at wallet activity. Short answers sit beside longer ones, so you can scan first and read more only when you need it. We mention UPI, Paytm, PhonePe, and Google Pay only as support chips here, because this page is about answers, not promotion. If a
topic depends on local law, we say so plainly and keep the wording tied to where local law permits.
We group the most asked topics into three cards so you can jump straight to the part that matches your question.
The trust value of an FAQ comes from whether the answers stay specific and do not drift.
We keep each answer short enough to scan, but specific enough to act on.
When a question touches eligibility, we say it depends on local law and is available where local law permits.
Deposit and withdrawal questions name the fields we check, such as the reference, the method used, and the account details.
Browser, app, and network questions point to the simple checks that solve most problems first.
We update the text when a flow changes, so the FAQ does not carry stale steps.
The FAQ uses the same labels you see in the lobby and wallet, which reduces confusion when you move from…
Not every question needs the same length of answer, so the page separates short checks from fuller ones.
| Login | If you cannot move past login, the answer starts with the quickest checks: password, device, and connection. It stays short because the next step is usually obvious once the basic error is cleared. |
|---|---|
| Wallet | When the question is about UPI, Paytm, or PhonePe, we point to the reference, timing, and account details first. That keeps the answer practical and avoids mixing wallet checks with unrelated topics. |
| Eligibility | For access questions, the answer makes the local-law position clear and stops there if your region is not covered. Where local law permits, the next step is spelled out without extra filler. |
| Game help | If you ask about Live Baccarat, Aviator, or Kabaddi Crash, the answer stays tied to that title. You get the rule, the round flow, and any timing detail that matters. |
| Support handoff | Some questions need a person, not a long page. In those cases, the FAQ tells you exactly when to move to chat or email, so you do not repeat the same context twice. |
| Mobile read | Short mobile paragraphs make the page easier to use on a smaller screen. The comparison helps you see which answer is one tap away and which one needs a slower read. |
| Search use | Each answer uses the same terms as the question, which helps you find the right item again later. That consistency is useful when you return to the page with a different device. |
A few things make this FAQ easy to recognise: direct headings, short answers, local payment chips, and the local-law line that appears where access is discussed.
These are the questions we expect you to open first when you land on the page. They cover account access, wallet checks, device issues, game-specific doubts, and the local-law line for eligibility. If your question is not here, use the support paths above and we will keep the same wording when we reply.