Mobile / App
Your bbt99 login is the one step between the account page and everything behind it — enter the email or mobile number you registered, confirm the password you chose, and the lobby opens with your account wallet sitting where you left it. Signing in from a phone browser uses the same fields as desktop, with nothing hidden behind a download.
Creating the account is a short form and nothing else: an email address or a mobile number you can reach, a password you choose, and a confirmation step the screen shows you before you continue. Once that is done, this same form becomes your way back in. You type the same details in a phone browser or on a desktop, and the lobby loads with your account wallet already visible in the corner, so you know the session belongs to you. Expect the account area to ask for details in stages rather than all at once. If a field is rejected, the screen tells you which one, and you can correct it without starting over. We keep the flow the same every time you sign in, which is why the form looks familiar after your first session. Nothing here depends on downloading a file, and nothing asks you to share your password with anyone, including our support route. If something does not look right, stop and use the published support page before you enter anything further.
The same fields work in a phone browser and on desktop, so you are not learning a second layout. If you usually sign in on mobile, the email or mobile number box, the password box and the button sit in the same order you remember.
After you sign in, the lobby shows your account wallet where you left it, so you can see what is available before you open a game or a table. You do not need to leave the page to check it.
If the form refuses something, the message points to the box that needs attention: a mistyped address, a space in the password, the wrong number. Correct that field alone and send the form again rather than filling everything out again.
If you cannot tell why a sign-in is failing, use the support route published on the site rather than trying new passwords. Describing exactly what you see on the screen helps support point you to the right step and saves you repeating the same attempt.
Funding starts from inside the account rather than from a separate page. Once you are signed in, open the wallet area and pick the payment name you actually use — bKash, Nagad, Rocket or Upay — then follow the fields on that screen with the number and the amount that match what you intend to send. The account shows the record afterwards, so the deposit sits next to the rest of your transaction history. Treat the wallet screen as the source of truth. The amount you type there has to match what the request asks for, and any instruction about a reference or a confirmation step appears on that screen rather than in an email. We do not ask you to send money to a personal number, and nobody from support will ask for your wallet PIN. If a deposit does not appear in your record, keep the confirmation message from your wallet app and raise it through the support route.
Start in the wallet area of your account and choose bKash there. Enter the number you use, enter the amount you intend to move, and finish the request inside your bKash app before you close the screen. Your account record then shows what the wallet confirmed.
The Upay route works the same way: open the wallet area, select Upay, and key in the number and the amount exactly as the screen asks. Keep the confirmation your app shows, because that message is what you would share with support if the two records ever disagree.
Choose Nagad in the same wallet area when that is the wallet you keep your money in. The screen lists the fields the request needs, and you confirm it inside Nagad itself. Anything the request says about a reference appears on that page, so read it before you finish.
Rocket deposits follow the identical path from the wallet area of your account. Type the number and the amount, complete the request in Rocket, then come back to your account record and check that the entry appears there before you move on to a game.
If you would rather use a bank, the wallet area lists Bank Transfer alongside the mobile wallets, with the fields shown on the same screen. Follow those fields as they appear, and keep the receipt your bank gives you for your own record.
Before you open the form, settle four small things and the sign-in or sign-up will take far less time. Check that the browser address bar shows the domain you meant to use, so you are entering details on the site you actually opened. Make sure the handset or inbox tied to your number and email is with you, because a confirmation step usually lands there first. Have a password ready that you have not reused anywhere else, and know the personal details you plan to enter, exactly as they appear on your own records. None of this takes long. Most of the delay people run into comes from a code sent to a phone that is in another room, or a password they half-remember. Take a minute, and the form moves in one pass. If the screen asks for something you cannot supply, stop there and use the published support page instead of entering a guess.
Look at the browser bar before you type anything. The domain you started from is the one you should still be on. If a link sent you somewhere with a different spelling, close it and open the account page again from the address you saved.
Keep the handset that holds your mobile number within reach, and know which email address you used. A confirmation step usually goes to one of those two, so having both ready saves you from abandoning a half-filled form and starting over.
Arrive with a password you have not used on another site and have not shared with anyone. You will type it every time you sign in, so it should be something you can remember without writing it on the screen or sending it by message.
The form may ask for your name and other details. Enter them the way they are written on your own documents, keeping the spelling consistent, and follow whatever the screen asks for next rather than adding fields it never requested.
Coming back is the same door as going in. The account page keeps one form for both, so a returning session looks exactly like the one you used the first time: your email or mobile number, your password, and the button beneath them. If those details are not accepted, look at the wording next to the form rather than guessing. The account page carries its own link for a password you no longer remember, and the page behind it states what it needs. Follow those steps exactly as written; do not add one because another site used it. When the on-screen steps do not clear it — a confirmation that never arrives, a sign-in that keeps failing — use the support route published on the site. Say what you see and which step you reached; that is usually enough for support to point you to the right screen.
Open the account page and use the sign-in form you used before. Your email or mobile number and your password are the only things it needs, and nothing about the layout changes between your first visit and your tenth.
If the form refuses your details, read the wording next to it. The account page carries its own link for a password you no longer remember, and the page behind that link sets out exactly what it needs from you before you continue.
Work through the steps as that page presents them, in the order shown. Do not add a step because another site used it, and do not hand your password or a confirmation code to anyone who contacts you first.
When the on-screen steps do not clear the problem, use the support route published on the site. Say which step you reached and what the screen showed, and keep the confirmation you received from your wallet app if money is part of the issue.
Support starts inside the site, not outside it. Every page footer carries a link labelled for help, and that link leads to the contact options we publish — the same options on desktop and in a phone browser. Read that page first; it explains what to include when you write to us. Two things make a message easy to answer. The first is which screen you were on when the problem appeared, described in your own words. The second is the record you already hold: a wallet confirmation, a deposit entry, or the exact wording of the error the form showed you. With those, support can usually tell whether the problem sits in your account or in the wallet step. Please never send your password. We do not need it, and no genuine message from us will ask for it. If somebody does ask you to share it, treat that as a reason to stop and report the message through the published route instead of replying to it.
Every page on the site carries a help link in the footer, on desktop and in a phone browser alike. That link leads to the contact options we publish, along with what to include in a message so the first reply is actually useful.
When a form refuses something, the wording beside the field tells you what it wants. Copy that wording into your message. A short description of the screen you reached is often enough for support to identify the step you are stuck on.
Your wallet app keeps a confirmation for each request you send, and your account keeps its own entry. Holding both means support can compare them directly. Never send your password or your wallet PIN along with any message.
A minute of checking protects the account you are about to use. Before you type a password, look at the address bar and confirm you are on the domain you intended to open; bookmark that address so you are not hunting for it next time. The footer of every page links to the terms and the privacy page, and both are worth reading before you put money in. Practical habits matter more than anything we could promise. Sign out when you finish on a shared phone or a friend's laptop. Keep your password to yourself, and treat any message that asks for it as a message to ignore. Keep the record of what you deposit, because that record answers most questions about your own account without anyone needing access to it. Access is not the same everywhere. Whether you can hold an account depends on the law where you are and on eligible regions, so check that before you continue, and read the terms for the full picture.
Type or bookmark the domain yourself instead of following a link from a message. If a page asks for your password on an address that looks slightly different from the one you saved, close it and start again from your own bookmark.
Every page footer links to our terms and to the privacy page. They describe how an account is used and how your details are handled, and reading them before you fund the account is the simplest way to avoid a surprise later.
Your password stays with you. We do not ask for it in a support message, and nobody legitimate needs it to look at your account. Change it if you think somebody else has seen it, and sign out on shared devices.
Availability depends on local law and eligible regions. If you are unsure whether you can hold an account where you are, read the terms on the site before you go further rather than relying on a message from somebody else.
An email address or a mobile number you can reach, plus the password you chose when the account was created. Both boxes sit on the same form, and that form works in a phone browser and on a desktop without any change to the layout.
Yes. The account is tied to your details, not to a single device, so you sign in with the same fields wherever you open the site. Keep your password private rather than sharing it between people who use the same handset at home.
Read the message beside the box, correct that one field and send the form again — a mistyped address or a stray space is the usual cause. If it still refuses, use the support route published on the site instead of guessing at new passwords.
Return to the account page and use the sign-in form there. If your password does not work, read the wording next to the form; the page behind that link states exactly what it needs from you, and support can step in if those steps do not clear it.
No. Our support route never needs your password to look into a problem. If a message asks you to share it, ignore the message, sign in from your own saved address and raise the matter through the help link in the site footer.
Your account keeps a record of them. After a bKash, Upay, Nagad or Rocket request is completed in the wallet app, the entry appears in that record, and comparing the two is the quickest way to confirm everything lined up on both sides.