Reference

Your Questions, Answered Without the Queue

Every answer on this page started life as a message in our support inbox, from a bKash confirmation that lagged to a login that kept timing out on a shared phone.

bKash, Nagad, Rocket answersMobile login stepsWallet checks explainedWhere to ask next
hbajee21 Your Questions, Answered Without the Queue
PAGE AT A GLANCE

FAQ Facts You Can Check Yourself

Mobile first
Login by mobile number and a one-time code, with no separate username to remember
3 wallets
bKash, Nagad and Rocket as the default local rails
Cricket
Cricket markets sit at the front of the sportsbook, with BPL and international series listed
SSL
Session traffic encrypted between your phone and our servers
HOW WE KEEP IT HONEST

Why You Can Act on These Answers

We'd rather you check than believe. Our answers name the exact screen you'll see — the PIN prompt in bKash, the reference line in Nagad, the confirmation SMS after a Rocket send — so you can match them against what's on your own phone. Nothing here promises a payout amount or a timeframe we don't control. Where a game's return figure matters, we point to the provider's screen and leave it there. And when an answer goes stale, we replace it openly.

Tested on a real handset Before a question goes live, someone runs the step on a phone with a working wallet and confirms the wording matches what you actually see on screen.
No figures we can't show We stay away from payout speeds, percentage claims and account totals. If a number appears here, it's a count you can see for yourself, like the three wallets.
Rewritten the same week A changed confirmation message or a moved login step gets rewritten here once the support desk sees it, so the answer you read isn't the one from last season.
One voice from support The people writing these replies also answer the chat queue. Same wording, same steps, no script that contradicts what a human tells you later.
hbajee21 Why We Wrote These Answers Down

Why We Wrote These Answers Down

We built this page after watching the same handful of questions land in support week after week. Nearly all of them are about money on the move: a bKash payment your phone shows as sent that hasn't reached your account wallet, a Nagad reference number typed with one wrong digit, a Rocket transfer sent during a busy evening in Dhaka when the

queue is long. The rest are about access — a one-time code that arrives late, a password reset going to a SIM you no longer use, a browser session that expires on a shared handset. Instead of making you wait for replies we already know by heart, we wrote them out here in the same words our support desk uses. Nothing here

stays fixed forever. When a wallet changes its confirmation wording or a login step moves, we rewrite the answer and put the new version live. If your case isn't covered, the support block below lists the real channels so you reach a person and not a form. One straight point before you send anything: whether a payment rail is open to you

depends on your local law and eligible regions, so confirm that first.

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

Where to Take a Question Further

Written answers cover most cases, but not every one. When your situation doesn't fit what's on this page, take it to the hbajee21 team through in-app chat, which keeps the thread tied to your account so you never retype your wallet number. Email suits screenshots better — a wallet confirmation screen, a failed code, a reference line. Either way, keep your wallet number and the time of the payment handy; that pair is what gets checked first.

In-app chat Opened from your account menu and tied to your wallet number, so the thread carries your payment references without any retyping on your side.
Email with screenshots Send a photo of the bKash, Nagad or Rocket confirmation screen plus the time you sent it. That single image settles most payment questions faster than a paragraph.
Wallet verification desk For a cash-out held over a name or number mismatch, this is the queue that looks at your documents. Bring the ID that matches your wallet registration.

The Six You Ask Us Most

These six come up again and again in the chat queue, so we've answered them plainly. Rail availability shifts with your own wallet and with local rules, so treat each answer as the process rather than a promise. If yours isn't among them, chat is one tap from your account menu.

Open bKash, send the amount to the number your account shows, confirm with your PIN, then paste the transaction ID into the payment screen. Your wallet updates once that reference matches.

That gap is usually a reference number that didn't match. Send the Nagad screenshot and the transfer time through chat; the team traces the entry against your wallet number.

Codes go to the number you registered, so an old SIM or a full inbox blocks them. Restart the phone, clear the inbox, request again. Still nothing? Email support to check the number on file.

Yes, but as a fresh login. Sign in with the same mobile number in the browser, take the code on your phone, and your wallet history follows you. Nothing stays saved on a shared handset.

A wallet number in your own name and an ID that matches it. If the name differs by even a letter, ask the wallet verification desk first; a mismatch is the usual reason a cash-out sits.

Crash ShockWave and Blackjack Blast carry the studio's own rule screen. Where a provider publishes a return percentage it shows there, and we don't restate it as a site figure.
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.