Sports / Mobile
299bf keeps account access on the screen you already use: open the login page, enter the same email address or phone number you registered with, and your lobby, wallet and game history load behind it. Access depends on your local law and eligible regions, so we show every step inside the account before you commit to it.
No two sign-ins look exactly alike, but the account side of 299bf keeps the same order every time. You start on the sign-in screen, where you choose the email address or phone number you registered with and type the password you set yourself. If you have not created an account yet, the sign-up form asks for the same basics: your name as it appears on your documents, a reachable phone number, and an email address you can open from the phone in your hand. From there the screen moves you through whatever your account still needs; anything unfinished appears as a prompt rather than a hidden error, so you always know what is left. Once you are through, the lobby opens on the game tiles you last touched, and your wallet sits in the same menu whether you signed in from a browser or from a shortcut saved on your home screen. Nothing moves between devices: the balance, the payment record and the games you have open all belong to one account. If a field does not look right, use the support route published on this site before you continue. We would rather you take the extra minute than sign in to the wrong page.
Everything you do sits under a single account, so the games you opened, the wallet balance and the payment record follow you from phone to computer. Sign in on either one and the lobby reloads in the state you left, instead of opening a separate profile each time.
The form shows what is still missing rather than failing with no explanation. If one field needs attention, you can leave it, come back to the same account page and pick up from there, without rebuilding the whole sign-up from the start.
You set the password when the account is created and nobody else sees it. Store it somewhere your phone can reach, because the login screen asks for it again whenever a session ends and you want the lobby back in front of you.
When a step is unclear, the site lists the support route we answer on, so you are not guessing which form to fill. Describe what your screen shows and the reply applies to your account, not to a general case.
Your wallet sits inside the account, so every payment starts with the same sign-in you already know. We take bKash and Nagad deposits: open the deposit screen, pick the rail, follow the fields shown and the entry appears in your transaction list once the account records it. Match the number you send from with the number registered on your account: that mismatch is the usual reason a deposit needs a second look. Hold on to the confirmation message from your wallet until the same entry shows in your own record. Withdrawals travel back along the rail you used, and the amount, status and reference sit in the history you can open after any sign-in. We do not publish fixed processing windows, and we never ask you to send money outside the payment screens in your account. If a rail looks unavailable when you open it, treat that as availability in your region rather than a fault on your side, and read the terms page published here.
Deposits through bKash start on the deposit screen inside your signed-in account, where the fields for the number and the amount sit together. Send from the number registered to your account and keep the confirmation you receive, because it is the simplest way to trace a payment that has not yet appeared in the record.
Nagad works the same way: sign in, open the deposit screen, choose the rail and complete the fields shown there. Nothing moves until the account confirms it, and the amount then shows in your transaction list beside the reference, ready for you to check at the next sign-in.
Every bKash and Nagad payment leaves a line in your account wallet with the amount, the rail and the time it was recorded. Open that list after signing in to compare what you sent with what arrived, and use the support route published on this site if the two do not line up.
Two minutes of checking before you sign in is worth more than a rushed attempt. Start with the address: the login page you use should sit on the 299bf domain you already know from previous visits, and a link that arrives from somewhere unexpected deserves a second look before you enter anything. Next, make sure you can reach the email address or phone number tied to the account, because that is what the sign-in screen asks for first. Have your password ready rather than guessing at it; retyping a form is easier to avoid than to repair. If you are creating the account rather than returning to one, keep your identity details nearby as well, since the name you enter should match the documents you hold and a mismatch there is the step most often left unfinished. Finally, check your connection and your browser. A slow signal looks a lot like a broken page, and reloading once on a stable connection clears most of what looks wrong.
The sign-in page should sit on the same 299bf address you have used before. Type the address yourself or open it from a saved bookmark instead of following a message link, and take a moment when a page asks for your password somewhere you have not seen it before.
The form asks for the email address or phone number registered to your account, so make sure that inbox or SIM is available to you right now. If the number has changed since you joined, sort that out through the support route before you try to sign in again.
Retyping a sign-in form mid-way is avoidable. Type your password from wherever you keep it rather than from memory, check that caps lock is not on, and use the same keyboard layout you used when the account was created, since a layout switch is a common reason a correct password is refused.
Creating the account asks for the name you use on your documents, so keep those details to hand while you fill in the form. Enter them exactly as they appear, and finish the remaining prompts in the same sitting so nothing is left half-filled when you first sign in.
Sessions end, phones get replaced, and details slip out of reach; it happens to returning users more often than to new ones. What we can say plainly is where to look. Anything the account itself can settle shows up on the sign-in screen or inside the account menu once you are through, and those prompts are the ones to follow first, because they reflect the state of your own record. When a step asks for something you no longer have, do not keep retrying the same field. Pause, write down the exact wording on screen, and use the support route published on this site to describe it. That route is the one place where account-specific questions get an account-specific answer. If you keep a browser shortcut to the lobby, refresh it before deciding the link is broken; stored pages age, and a page loaded from an old copy can miss the prompt you need. Keep the email address or phone number on the account current, too. An out-of-date contact is the quietest way to lose access.
Open the login page and read what it shows before you do anything else. If the account needs a step finished, the screen usually says so, and that message is more dependable than trying the same password over again from memory.
Old browser tabs and home-screen shortcuts can load a stale copy of a page. Pull the address to refresh, or retype it, and see whether the prompt changes before you assume something is wrong with the account itself.
When the screen asks for something you cannot supply, write down the exact words shown and take them to the support route listed on this site. That route handles account-specific questions, and the wording you bring with you tells us where to look.
If the phone number or email on the account has changed since you joined, that is worth correcting straight away. An old contact detail is the most common reason a returning user cannot finish a step the account is asking for.
Help that works starts with the right doorway. This site publishes its support route, and that route is where account questions belong: sign-in trouble, a deposit that is not showing in your wallet record, or a form field that will not accept what you typed. You will not find a private number or a shortcut handle here, because we do not run channels we cannot keep consistent. What you can do is make the first message count. Tell us the email address or phone number on the account, the rail you used if the question is about a payment, and the exact wording the screen gave you. A screenshot of the page helps, and it is safer than a description typed in a hurry. If you are writing about a deposit, keep the confirmation message your wallet sent you, since the reference inside it is the simplest way to trace the entry. And if the problem is that you cannot get past the login screen at all, say so on the first line. It changes which checks we start with.
Write to the support route published on this site and start with the contact you use on the account. Add the exact wording the login screen showed you, plus what you already tried. That combination lets the reply match your own account instead of describing a general case.
If a bKash or Nagad payment has not appeared in your wallet record yet, keep the confirmation message your wallet sent and quote the reference it contains. Send that reference with the amount and the number you paid from, and the check can start from your account's own transaction list.
Joining for the first time? Send the question before you sign in rather than after, especially if the sign-up form is asking for a document name that does not look right. Mention which field is causing the hesitation and you will get an answer aimed at that step.
The checks that protect an account are mostly ones you can perform yourself, and we would rather you ran them than took our word for anything. First, the address bar. Bookmark the 299bf page you use and come back through it, so a lookalike link has less chance of catching you before a sign-in. Second, the pages we publish about how data is handled and what the terms are; both are linked from this site, and both are worth reading once, before your first deposit rather than after it. Third, your own pace. Access should fit what suits you and what your local law allows, and if a session no longer feels right, taking a break is a decision nobody has to justify to us. Fourth, the support route published here, which is where a question about your account actually gets answered. Notice what we are not claiming: nothing on this page asks you to take a hidden process on faith.
Keep the 299bf page you use in your bookmarks and open the login screen from there. Typing the address yourself is just as good. Both habits do more for your account than any warning we could print, because they keep you away from links that arrive uninvited.
Terms and privacy pages are published on this site, and they are short enough to read once before you deposit. They explain how the account is run and how your data is handled, so a question about either one has a written answer you can go back to.
Fill in your password and any account detail on the sign-in and account pages themselves. If a message, a call or a page you did not open asks for those details, close it and come back to this site directly instead.
Availability depends on your local law and eligible regions, and how often you sign in is your call. If you want to step away from the lobby, step away; the account keeps your record and the games wait where they are.
Most sign-in questions come down to four things: the address you landed on, the details you typed, the device you typed them on, and what the screen told you back. The answers below take those in turn. If yours is not here, the support route published on this site is the place to take it. When you write, bring the wording the screen showed you, because that single line usually decides the answer. We keep these replies short on purpose. They describe what the account pages themselves show, not a set of steps that only applies to some accounts, and nothing here replaces the prompts in front of you. It is also worth saying that the page you sign in on matters as much as the details you type into it, which is why several answers start there.
Open the login page in your phone browser, or from the shortcut you saved, and enter the email address or phone number you registered with, followed by your password. The lobby then loads with your wallet and the games you last opened already in place.
Either one works if it is the contact you attached to the account when you joined. Use whichever you can reach right now, since the account may ask you to confirm something through it. If both have changed since you joined, correct them through the support route before your next sign-in.
Whether a session is held depends on the browser you use and the option you pick on the sign-in screen. On a device only you unlock, staying signed in saves you retyping details. On a shared phone, close the session instead, and treat any borrowed device as a public one.
Refresh once on a stable connection first, and check that the address still sits on the 299bf domain. A stale saved page can show fields that no longer match the live form. If the page still behaves oddly, take a screenshot and send it through the support route published on this site.
Yes. Your wallet and its transaction list sit behind the account, so the deposit screen and the record of what you sent are only visible after you sign in. That is deliberate: the entry for a bKash or Nagad payment belongs to your account, not to a public page.
The screen will keep asking for the correct one, so slow down rather than rushing another attempt. Check the keyboard layout, caps lock and any saved entry your phone is filling in for you. If your stored password no longer works, take the wording on screen to the support route published here.