Mobile / App
Opening a bk76 account asks for the email address you already use and a password you set yourself, and those same details then work on your phone, your tablet or a computer. Work through the fields on this page in the order they appear, and you can sign in and take a look around the lobby.
Setting up your account is a short sequence of screens, and it helps to know what each one asks before you start. First comes the email address you actually check, because that is where anything about your account will reach you. Next you choose a password and confirm it — pick something long enough to be awkward for anyone else and keep a copy of it where you can find it later. After that the form asks for the personal details it uses to match you to your account wallet, so type them the way they appear on your own documents. When you sign in later, the same email and password work on mobile and on a computer, which is why we keep the flow identical on both. If a screen asks for something you were not expecting, pause and read it before typing; the published support routes are listed further down this page. We do not promise a set completion time for any step, because checks can vary depending on what the account needs.
The form asks for what your account wallet needs: your name, an email address and a password. Type each field the way it appears on your own documents, because a mismatch there is the usual reason a later step stalls and sends you back to the same screen.
Anything about your account arrives at the address you register with, so use one you open often rather than an old inbox you have abandoned. If that address changes later, update it in your account settings on the same day.
Sign in on your phone during the day and the same account opens on a computer later — nothing is locked to one handset. Inside, the lobby carries Cricket GoalBet and Crash Rush, live tables from the studios we carry including PG Soft and Microgaming, and cricket markets around BPL and international fixtures.
The support route we publish sits in the footer of this site and on the sign-in screen, so you can reach it from the page where a problem shows up. We keep that path in the same place across the site instead of moving it around.
Payments here start with the account, not the other way round. Once your sign-in details are set, the deposit screen lists the local routes we support — bKash first, Upay as the alternative we keep alongside it, with Nagad and Rocket shown for wallets that already use them. What you pick is your call, and you can change it on a later transfer without touching your login. Each one works as a path rather than a logo: you choose the route, the screen tells you what to send, your wallet app confirms it, and the entry then appears with the rest of your account activity. We do not publish a fixed processing window, because how quickly a wallet posts depends on the wallet itself. If an amount or a step looks wrong before you confirm, close the screen and ask through the support route published on this site rather than sending twice. Check the fields shown in your own account before your first transfer, and keep the confirmation message your wallet sends you.
bKash sits first because it is the route we get asked about most. Open the deposit screen, pick bKash, then follow the wallet prompts on your phone and read the confirmation before you send anything. Your account wallet shows the entry once it lands.
Upay is the alternative we keep listed for you, and it follows the same shape: choose it from the deposit list, complete the payment inside the Upay app, then come back to your account to see the entry logged. Nothing else about your sign-in changes.
Nagad appears in the same deposit list for wallets set up with it. Select Nagad, send from your wallet as the screen instructs, and keep the confirmation message on your phone until the entry shows in your account wallet. The steps match what you see in the app.
Rocket is there if your wallet is already set up with it. Pick Rocket on the deposit screen, follow the prompts, and let the confirmation finish before you close the app. The record then sits with your other account activity for as long as you need it.
Before you fill in anything, spend a minute on the things that slow registration down. Confirm you are on the address you normally use for this site rather than an old bookmark, since a stale link is the usual reason a sign-in screen looks unfamiliar. Have your phone nearby and charged, because the email address you register with is the one you will need to reach from that device. Decide on a password now instead of inventing one mid-form, and keep a copy of it where you can find it later. Keep your personal details to hand as well, spelled the way they appear on your own documents, so the form does not stall halfway through. None of this takes long, and doing it first avoids the common situation where you lose your place, close the tab and start again. When everything is ready, work through the fields in the order the page shows them.
Open the site from the address you usually type or the shortcut saved on your home screen, and glance at the address bar before you enter anything. If it looks different from the last time you signed in, close the tab and start again rather than typing your email into it.
Keep the handset you use every day within reach, because the email address on your account is the one you will need to open from it. If that inbox is crowded, clear some room now so nothing about your access gets buried.
Choose something long enough that guessing it is not worth anyone's time, and write it down somewhere you keep safe rather than reusing a password from another site. If you change it later, update that copy on the same day.
Type your name and the other details exactly as they appear on your own documents, without shortcuts or nicknames. Getting that right at the first attempt saves you a second trip through the same screen when you come back to sign in.
Losing access is annoying, and the first thing to do is work from the sign-in screen rather than guessing at what went wrong. Open that screen and read the options it shows you — anything your account can use is listed there, and we do not ask you to follow a route that is not on the page. If you still cannot get in, the published support route is the next step, and whoever answers will tell you which detail they need from you. Do not send your password to anyone, including us; no genuine part of this site will ask for it in a message. Keep the email address on the account reachable, because that is where anything about your access will arrive. If you have signed in on more than one device, try the one you used most recently before you assume the account itself is the problem.
Start on the page you normally use to sign in and read every option listed under the form. Anything your account can use to get back in is shown there, and if a link is not on that screen it is not part of our flow.
A surprising share of failed sign-ins come down to a mistyped email or an old password saved in the browser. Retype the address by hand, and if your browser fills in a password automatically, clear that field before you try again.
If the screen's own options do not fit your situation, go to the support route linked on this site and describe what you see. Do not include your password in that message, and keep the reply thread so you can follow it up later.
Whichever device you try, use the address tied to your account. If you no longer read that inbox, sort it out through support before anything else, because a reply cannot reach an address you have left behind.
If something about sign-up or sign-in does not behave the way this page describes, the support route published on our site is where to take it. We keep that entry point in the same place, linked from the page footer and from the sign-in screen, so you do not have to hunt for it while you are stuck mid-form. When you write in, tell us which screen you were on, what you typed, and what the page said back — that detail is usually enough for a useful first reply. Never send your password. If your question is about a payment you have already sent, include the confirmation message your wallet gave you, since that is what the wallet provider will want to see. For everything else, our account pages are written to answer the common questions first, and the short list below covers what comes up most often.
The route linked in the page footer is the one we publish for account questions. Open it, describe the screen you are stuck on, and leave your password out of the message. That single page takes you from a problem to someone who can read your account.
When a sign-in attempt fails, read what the screen itself says before trying again. Most of those messages name the field that needs attention, and following the instruction there usually settles the problem without a message being sent at all.
Save the confirmation your wallet sends after a transfer. If you ask us about a deposit that has not appeared in your account, that message is the first thing we will ask you for, and it also helps your wallet provider trace the payment.
Your sign-in details are worth as much as the wallet behind them, so treat them the way you treat any banking password. We never ask for your password inside a message, and no page on this site will ask you to type it anywhere except the sign-in form itself. Check the address bar before you log in — if a link came from a message rather than your own bookmark, type the address by hand instead. Read our published terms and privacy pages when you want to know what we do with the details you give us, since those documents, not a rumour in a group chat, are the record that matters. Access to the lobby depends on your local law and eligible regions, so check that before you begin. Shut down a shared device when you have finished, and if someone else uses your phone, sign out rather than leaving the session open.
Glance at the address bar each time before you type your password, and keep a single bookmark for this site rather than clicking through from a message or an advert. A page you reached by accident should never see your login.
Our terms and privacy pages sit in the footer of every page, and they describe how your details are handled and what you agree to when you open an account. Read them once at the start rather than after something has gone wrong.
Whether you can use the lobby depends on your local law and eligible regions, so make sure you are in a place where the site is available to you before you deposit. If you are unsure, ask through the published support route first.
Sign out when you finish, especially on a shared phone or a computer you do not own. If you let a browser remember your password, allow that only on the device you keep with you, and clear it if the handset changes hands.
These are the things people ask us most often about creating an account and signing back in. Each answer points to the screen or published route where you can check the details yourself, so you are never relying on a second-hand explanation. If your question is not here, the support route linked in the footer takes it from there. We keep the same answers on the page rather than changing them from device to device, because the account flow is the same whether you are on a handset or a computer.
An email address you check often, a password you have not used anywhere else, and your phone within reach. Keep your personal details nearby as well, typed the way they appear on your own documents, so the form does not stall halfway through.
Yes, one account covers both. Sign in on your handset during the day and the same details open the lobby on a computer later. Nothing is tied to a single device, so you can pick up wherever you left off.
The deposit screen lists what we support: bKash first, Upay as the alternative, with Nagad and Rocket shown for wallets that use them. Pick the route you prefer each time, and changing it does not affect your login.
Do not open a second account. Go to the support route published on this site, describe what went into that field, and let the reply tell you what happens next. Keep the message in your inbox until the matter is closed.
That usually means an old bookmark or a link that came from a message. Close the tab, type the address you normally use by hand, and check the address bar before entering your password. If it still looks unfamiliar, ask through support.
No. Your password belongs in the sign-in form and nowhere else. If a message, a call or a page asks you to send it, that request is not from us — ignore it, and report it through the support route we publish.