Reference

FAQ: Your Questions, Answered Plainly

Every question we hear most often about account access, wallet cash-in and switching between phone and browser is written out on this page, in the same words we would use on a support chat.

Account accessbKash, Nagad, RocketOTP problemsDevice switchingCash-out checks
nogd77 FAQ: Your Questions, Answered Plainly
ANSWERS THAT HOLD

How We Keep Answers Accurate

FAQ pages rot. A wallet app moves a menu, an OTP screen changes shape, and suddenly the steps you are reading are wrong. So we rewrite an entry whenever the flow behind it changes, and the support desk flags answers that keep generating follow-up messages, because that is the signal an answer is still unclear. We also keep the language plain: taka amounts stated as they are, no timing promises we cannot hold, and no licence or claims dressed up as fact. When something depends on your local law or eligible regions, the answer says that

Written by the support desk

The people who answer your chats write these entries. So an answer matches what you will actually be told, including the details we ask for before checking a wallet transaction.

Rewritten when flows move

When bKash, Nagad or Rocket change their app screens, the steps here get rewritten. We would rather publish a shorter answer that still works than leave a long one that fails on your phone.

Plain taka, plain steps

Amounts and steps are stated as they are. Where we cannot confirm a timing or a limit, the answer describes the verification path instead of inventing a number to sound quicker than we are.

Your messages shape the list

Every entry started as a real message to support. When one question keeps arriving, it earns a place on this page, which is why the list stays short and leans on wallets, access and cash-out checks.

QUICK ANSWER FACTS

What This FAQ Page Saves You

3
Local wallets at cash-in: bKash, Nagad, Rocket
1
Account that works on phone browser and computer
SSL
Encrypted sign-in and wallet pages
6
Answers on this page, each written by support
nogd77 Reading the Answers Before You Sign In

Reading the Answers Before You Sign In

This FAQ exists because most messages we get each day are the same six or seven questions, and you should not have to sit in a chat queue to read an answer we already know. So we wrote them down. How to get back into your account when the OTP does not land on your phone. What to do when a bKash

cash-in shows as sent on your side but has not reached your wallet. Whether your session follows you from the phone to the browser, and what changes when you switch devices halfway through. Where to write when a cash-out looks stuck, and what we will ask you for before we check it. Each answer comes from the support desk that handles your

messages, so the wording matches what you will actually hear. Payment answers lean on the rails most of you use, bKash, Nagad and Rocket, with Upay and bank transfer named where they apply. Where an answer depends on your local law or eligible regions, we say so instead of pretending otherwise.

  • bKash
  • Nagad
  • Rocket
  • Upay
HUMAN FOLLOW-UP

Where to Ask Beyond the FAQ

If your question is not on this page, message us rather than guessing. The support desk sits inside the same account area where you cash in, so we can look at the bKash, Nagad or Rocket reference you are asking about instead of requesting a screenshot of it. Chat is the quicker route for anything live, like a session that dropped or a code that expired. Email suits wallet verification and documents, because you will want a written trail. Either way, name the wallet and the amount you sent.

Live chat Open the chat panel inside your account and describe what happened. Chat suits dropped sessions, expired OTP codes, and anything you want sorted while you are still in the lobby on your phone.
Email support Write to the support address listed inside your account with the wallet name and the reference from bKash, Nagad or Rocket. Email keeps a written trail, which helps for wallet verification before a cash-out.
Wallet help desk For a cash-in that never landed or a cash-out sitting on verification, this is the queue to use. Have the wallet number, the amount and the transaction ID ready so the first reply can help.

Questions You Send Us Most

These six fill our inbox, so we put them in the order they usually arrive. Read the one you need and skip the rest. If your case is a variation we have not covered, message support with the wallet name and the transaction ID, and availability of any wallet method still depends on your local law and eligible regions.

Most delays sit between your bKash confirmation and our wallet screen. Send support the bKash transaction ID and the amount. We check it against the incoming record and credit your account once it matches.

Both work with one account. Sign in on your phone browser and the session picks up where the app left off; open a computer later and your wallet balance and open bets are already there.

Let the code window expire before asking for a new one, because a second request can cancel the first. Check your message inbox for a blocked sender, then use the resend link once.

Usually yes, once your wallet name is verified under your own details. We check that the receiving number matches the account holder before releasing a cash-out, so keep both wallets in the same name.

Cricket leads our sportsbook, with BPL fixtures and international matches listed as markets rather than results. Open a market to see what is on offer at that moment; nothing on this page quotes odds.

A verified wallet number in your own name, plus the details you used at sign-in. If anything does not line up, support asks for one document rather than turning the request down outright.
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.