Reference

The Questions You Send Us Most

Straight answers to what you message us about: a bKash payment that has not shown on the wallet yet, a Nagad transfer stuck at pending, a live table that behaved oddly on mobile data.

Wallet and cashier answersWithdrawal checks explainedLogin and device stepsLive table questions
bdtbaji The Questions You Send Us Most
bdtbaji Where These Answers Come From

Where These Answers Come From

Every answer on this page started as a message to our support inbox. Someone could not see a bKash confirmation, someone else had a Nagad transfer sitting at pending, another wanted to know why a live table stuttered on a phone with a weak signal. We grouped those messages by what you are trying to finish — opening an account, moving money

in, moving money out, or picking a table — and wrote one answer per problem instead of scattering fragments. The payment chips below are the rails those messages mention most. That is not decoration. When we explain a bKash deposit, we mean the same PIN confirmation you already tap in the bKash app. When we explain Rocket, we mean the number you

typed when the wallet link opened. Naming the rail keeps the answer honest. Who writes them: the account and cashier team, the same people who read the wallet logs when something goes wrong. If a screen moves or a wallet adds a step, we rewrite the answer rather than add a correction underneath. Found a gap? Send it through the support paths

below and it gets added here.

  • bKash
  • Nagad
  • Rocket
  • Upay
  • Bank Transfer
WHY ANSWERS HOLD UP

How bdtbaji Keeps Answers Honest

No payout minutes are printed here, because those depend on the wallet and the network, not on a promise we can post. What you get instead is the step order: what we check, what you send, what happens next. Where a provider exposes RTP on a game screen, we point you to that screen rather than quote a figure. Same rule for table limits — read them on the table itself, not in our copy.

Written by the account team

The people who answer your chat also write these entries. So the withdrawal answer matches the check the cashier actually runs, not a version drafted somewhere else and pasted in.

No made-up timings

You will not see a deposit or withdrawal clock printed here. Wallet clearing depends on bKash, Nagad or Rocket and your signal, so we describe the verification path instead of a number.

Updated when screens move

If a wallet adds a step, or a lobby button shifts menu, the related entry is rewritten in the same pass. Old wording is deleted rather than stacked underneath.

Built for a local phone

We write for a mid-range Android with the wallet app in the background and a connection that drops. Dhaka readers get the same wording as everyone else in the country.

GETTING A REPLY

How to Reach the Desk

Chat is the route to use when you are mid-payment, because we can pull the wallet reference into the same thread. Email suits anything with screenshots — a bKash confirmation SMS, a Nagad transfer receipt, a stalled loading screen. If your issue is a withdrawal check, message from inside the account rather than a fresh address, so the desk can match the request to your wallet without asking you to prove who you are twice.

In-account chat Open chat from the wallet screen and the thread carries your account reference, so you do not retype a bKash or Nagad transaction number back to us.
Support email Send screenshots here — a Rocket receipt, a failed confirmation page, a table that froze mid-hand. Attach the image and the cashier team can trace the entry against the wallet log.
Account desk For login trouble, device changes and withdrawal checks. Come from the registered number where you can, and the desk matches the request to your wallet file directly.
ANSWERS AT A GLANCE

What Each Answer Handles

Live + slots
the two lobby types that raise most of the questions below
3 wallets
bKash, Nagad and Rocket steps spelled out in the payment answers
Phone first
answers written for a mid-range Android on a patchy connection
SSL
login and wallet pages run over SSL in the same browser session

Quick Answers to Common Cases

These six cover the messages that come in again and again. Read the one that matches your situation before you open a chat, because most cases close right there. Where an answer depends on which wallet you used — bKash, Nagad or Rocket — we say so plainly instead of blending three rules into one that fits none. If you have already sent money and the balance has not moved, start with the first question.

Open the bKash app and copy the transaction ID from the confirmation SMS. Send that ID through in-account chat. We match it against the wallet log and the balance updates once the entry is confirmed.

No. Sending twice creates two entries and slows the match. Leave the first transfer alone, keep the reference number, and message us from inside the account so the desk can see where it is held.

The name on the wallet has to match the account holder, and the play-through on any related entry has to be finished. Both checks run on the same request, so nothing is asked of you twice.

Yes, one account covers both. Log in with the same number and the session runs over SSL on either device. If a new device triggers a verification prompt, confirm it from your registered number first.

Cricket sits at the front of our sportsbook: BPL matches, international fixtures and the IPL when it runs. You see match markets, innings and player angles. Odds live on the sportsbook screen, not in our copy.

Access depends on your local law and eligible regions, so check before you travel. Wallets such as bKash, Nagad and Rocket follow local rules. Message the desk with your location and we will say what applies.
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.