Reference

The FAQ Desk for Your Account

Every question we hear most often sits here in one place, grouped by what you're trying to do: open your account, move taka through bKash or Nagad, get into the lobby on your phone, or reach a person who can fix something.

Account and wallet answersbKash, Nagad, Rocket stepsMobile access fixesSupport channels
35bd2 The FAQ Desk for Your Account
DESK BY NUMBERS

Four Structural Facts You Can Check

3
Local wallets you can move taka with — bKash, Nagad, Rocket
2
Ways in: mobile browser and desktop lobby, with separate step paths
EN
Language of the interface, this page and written support replies
SSL
Encrypted connection on account, wallet and login screens
35bd2 What This FAQ Page Covers

What This FAQ Page Covers

This page exists because most messages to the 35bd2 support desk start with the same handful of questions. We wrote the answers down, in plain English, sorted by the task you came to do rather than by internal department names. Wallet entries sit together — bKash, Nagad and Rocket each have their own steps, and the wording matches what appears on screen

when you confirm a transfer with your PIN. Account entries cover the code we send at login, the details we check before a withdrawal leaves, and what to do when a session ends on its own. Mobile entries explain why the lobby loads differently on data than on Wi-Fi, and where the menu collapses on a smaller screen. Support entries tell you

which channel to pick, so you don't queue in the wrong one. We add to the page whenever the same question turns up twice in a week, and we'd rather cut an entry than leave a stale one standing. Nothing here replaces the terms — where those disagree, the terms decide. Questions about eligibility get a straight answer too: access depends on

local law and eligible regions.

  • bKash
  • Nagad
  • Rocket
  • Upay
  • Bank Transfer
REACHING A HUMAN

Where to Ask When the Answer Isn't Here

Written answers run out eventually. When they do, two channels reach the same team: chat inside your account and the email address on our contact page. Chat suits anything attached to a transaction, because the agent can pull up the wallet record while you're both looking at it. Email suits screenshots, longer explanations and anything about a session that closed. Either way, give us your account number once at the start — it saves the back-and-forth. The path is the same whether you're in Dhaka or Chattogram.

Team online

Chat inside your account

Open your account, tap the support icon in the header and type your question. Chat is the channel to use for wallet issues because the agent can see the transfer you're asking about.

Email the desk

Longer questions, screenshots, or anything about a session that closed on its own go to the email address on our contact page. Include your account number so we can match the record without asking twice.

Check the wallet first

Before you write, open bKash, Nagad or Rocket and check the transaction history. A failed transfer carries a reference number there, and that reference saves a round of questions on our side.

WHY OUR ANSWERS HOLD

How We Keep These Answers Accurate

No answer on this page was written once and left alone. The support team owns these entries, so a change in a wallet flow or a login step reaches the same people who hear about it first. We keep the wording plain on purpose: an entry that tells you exactly where the code arrives is worth more than three paragraphs of policy language. Where a short answer and the account terms pull apart, the terms win and we say so plainly.

Written by the support team

The people who answer your chats write these entries. When a wallet flow changes, the same team edits the answer, so the page and the desk don't drift apart.

Steps, not pointers

We describe the actual screen path — where the code arrives, where the wallet reference sits, where a withdrawal check happens — instead of pointing you to account settings and leaving you there.

Terms come first

Where an answer here and our account terms say different things, the terms decide. We'd rather tell you that plainly than let a short line promise something the rules don't allow.

Region-aware answers

Every entry assumes you're in an eligible region and following local law. If you log in from outside Bangladesh, check the access rules first — the answer may differ.

Questions You Send Us Most

Six questions come up more than any others. Read them before you write in — most wallet and login issues are already answered below, and the fix is often a step or two away. If yours isn't listed, the desk is one tap from your account.

Start with the wallet entries if your question is about money — bKash, Nagad and Rocket each have their own steps. Account and mobile entries come next, and anything else goes to the support desk.

Use the wallet entry for the app you sent from and keep the transaction ID handy. Send it through in-account chat so we can trace that same transfer on our side.

Yes. The lobby entries cover where cricket markets sit, including BPL and international fixtures, and how a placed bet shows in your account history. Odds and results stay in the sportsbook, not on this page.

Send the page name and the sentence itself through in-account chat. The support team writes these entries, so a correction lands with the people who can edit the line instead of bouncing between departments.

We add an entry when the same question arrives twice in a week. If yours is tied to your own account — a verification check, a closed session — it stays between you and the desk.

Yes. Chat opens inside your account, which is how we match your question to the right wallet or session record. Email works without logging in — include your account number so the thread doesn't stall.
Reference

FAQ

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.