Mobile / App
Signing in to bkl33 takes one field and one confirmation, and it ends on the same home screen you left — whether you started on a phone this morning or a desktop tonight. If a screen looks different from what we describe here, the contact link in the footer reaches a person, and the terms you agreed to sit beside it.
Signing in starts on the brand home page, not on a separate portal: the sign-in link in the header opens the form, you type the email address attached to your account, and one confirmation step follows before the home screen loads. That order does not change with the device. Start on a phone during a commute, finish on a desktop at night, and the account you open is the same one — same wallet, same saved games, same history. New accounts follow the same form. You choose an email you can open, set a password, and fill the personal details the page marks as required; from then on that email is how we know you. Nothing about the account is tied to one handset, which is why we ask you to keep the password somewhere you can find it rather than relying on a saved browser session. Once you are inside, your balance, the rails you have used and your shortcuts are on the home screen already. If a step does not behave the way this page describes, close the tab and write to us through the footer link.
Your email address is the name we know you by, and the password you set on the account page is the only key we ask for. Type both, complete the step the form shows, and you land on your own home screen with your balance and shortcuts already in place.
Open the account on a phone in the morning and a desktop at night and it is identical: same wallet, same saved games, same history. Nothing needs setting up twice, and no session belongs to one device. That continuity is the reason the sign-in form stays short.
Every field on the account page is one you complete yourself — email, password and the personal details the form requests. We keep that list to what an account actually needs, and anything you later change is changed from inside the signed-in area rather than before signing in.
The contact link is published in the site footer on every screen, signed in or not, so you never need to reach the lobby to ask a question about access. Quote the email you sign in with and the screen you were on, and your message arrives with context.
Your wallet only exists after you sign in, and that is where every local rail lives. Nagad and Rocket are the two we run for funding and withdrawals; the wallet tab shows the rail, the amount field and a record of what you have moved, in that order, on any screen size. We do not put a payment request on the sign-in form — before the account is open there is nothing to fund. If a rail is not listed for you, the reason is regional rather than technical: what we can offer follows local law and eligible regions, and the wallet screen reflects that instead of the marketing page. Where a rail is available, the flow is the same — choose it inside the wallet, follow the fields the screen lists, and keep the reference the page gives you. Check the record in the wallet before repeating a transfer, because two identical requests are harder to untangle than one.
Nagad is one of the two rails we run for wallet funding, and it appears in the wallet tab once your account is open. The screen shows the rail, the amount field and your own record of what has moved, so a transfer is never a guess. Availability follows local rules and eligible regions.
Rocket sits beside Nagad in the same wallet row. Pick it, read the fields the screen asks for, and the movement is logged against your account so you can see it later in the same place. We publish no processing time here; what the screen shows when you submit is what applies.
bKash is the wallet many visitors already keep on their phone, and it is listed in the wallet area wherever that rail is available for your region. The flow matches the others — choose it inside the wallet, follow the fields, then check the record instead of sending a second request.
Four things make a first sign-in uneventful, and none of them take long to prepare. The first is the address itself: type the domain rather than following a link from a message, and check the bar before you fill anything in. The second is an inbox you can open while you are on the form — your email is the name on the account, and the account page may ask you to confirm something through it. The third is a password you have not used elsewhere. Set it on the account page and put it somewhere you will still reach next month, because a saved browser session on one phone is not the same as knowing your password. The fourth is your own details, typed consistently: support can only look up what you actually entered. Work through those in order and the form becomes a short task rather than a detour.
Type the domain yourself rather than following a message link. The address this page belongs to is the one we publish, and the sign-in form should sit under it with the field order you see here. If the bar shows something else, close the tab.
Your sign-in name is an email address, so it needs to be one you can reach while you are on the form — not an old inbox from a phone you have replaced. Have it open in another tab in case the account page sends a step to confirm.
Set a password on the account page rather than accepting one from a message. It should be something you have not used on another site, because a shared password turns one leak elsewhere into a problem here. Store it where you can actually find it.
The form asks for personal details so a later support conversation can find your account quickly. Type them the same way each time; a name spelled two different ways across one account makes matching harder when you ask us to look something up.
If the sign-in form rejects what you type, work from the screen rather than from memory. Start again at the sign-in link on the brand home page, read the error under the field, and try once more with the password exactly as you set it — capital letters and punctuation included. Where the account interface publishes a route for regaining access, it sits under the password field; follow what that route asks for and nothing beyond it. Where no such route appears, do not improvise with a link someone sends you. Use the contact link in the site footer, write from the email on the account if you can still open it, and put the name on the account in your first line. If you cannot reach that inbox at all, say that straight away — it changes how we look for you. Returning after months away follows the same path: sign in as before, or write to us.
Begin where you began the first time: the sign-in link on the brand home page. The form is the same one you used before, so a mistyped password shows as a plain error under the field rather than a dead end. Read the message before trying again.
If the account interface offers a way to regain access, it is published under the password field. Follow exactly what that route asks for and nothing more. Where no such route is shown, do not improvise — the support link is the next step, and a person reads it.
When you contact us about access, send the message from the address on the account if you can still open it. If you cannot, say so in the first line and include the name on the account, so the conversation opens with something we can check.
The address you used at the start is the thread that ties your account, wallet record and messages together. If you change providers, update the address from inside the signed-in area before the old one closes, so your access never depends on an inbox you no longer hold.
One published route, used well, answers almost every account question. Start with the questions on this page — the sign-in form, device switching, and what to do when a screen will not move are all covered there in a few lines, which is usually quicker than waiting on a reply. When your question is about your own account rather than the process, use the contact link in the site footer; it appears on every screen, signed in or not. Write with the email you sign in from, the screen you were on and what it said. A screenshot helps if there was an error. If your details no longer match what the form asks for — a name spelled differently, an address you have replaced — say so in the first line so the reply is about the right problem. Please never send your password, and keep to one message per issue, because a single thread with context beats three that start from nothing.
Every screen on this site carries a contact link in the footer, including this one, and it works whether or not you are signed in. Use it for questions about your own account: the email you sign in with, what you were trying to do, and what the screen said.
Before you write, the questions below cover the sign-in form, switching between phone and desktop, and what to do when a page will not move. Many messages we receive are settled there in a few lines, which is quicker than waiting for a reply to arrive.
Two published pages answer most of what people ask before they write: the terms of use and the privacy commitments, both linked in the footer. Read them when your question is about what we expect from each other rather than a specific screen you are stuck on.
Two habits keep an account in the right hands. The first is typing the address yourself instead of following a link from a message you did not expect — the domain this page belongs to is the one we publish, and a sign-in screen that arrives by SMS or through a group chat is not ours. The second is reading what you accept before the form submits. The terms of use and the privacy commitments sit in the footer of every screen, including this one, and they set out what applies to your account and what we expect from each other. Neither is long, and both are written for people rather than lawyers. If anything on the sign-in screen does not match what we describe here — a different field order, a payment request before you are inside the account, a domain that ends somewhere else — close the tab and reach us through the support route published on this site.
Look at the address bar before you type a password. Our sign-in form sits under the domain we publish, opens with an email field, and asks nothing about money at that stage. Anything that looks close but not identical is somewhere else, and closing the tab costs you nothing.
The terms of use and the privacy commitments are linked in the footer, on this screen and every other. They describe what you agree to when you open an account and what we commit to in return. Two short reads now save a longer exchange later.
An account is only as reachable as the email attached to it. Update your address from inside the signed-in area when it changes, and keep the name on the account spelled the way you would write it on a form, so support can match records without asking twice.
An account is easy to leave alone for an evening, a week or a season, and signing back in later is no harder than the first time. If you notice you are opening the lobby out of habit rather than because you want to, take the break and come back when the reason is there.
What people ask us about signing in is fairly consistent, so we have answered the six that come up most: the form itself, one account across devices, a forgotten address, a wallet that seems missing on a new phone, the confirmation step, and a page that will not load. Each answer describes what the account interface actually shows rather than a workaround. Two habits prevent most of these problems. Type the domain yourself instead of following a message link, and keep the email on the account one you can still open. Everything else — the password, the wallet rail, the record of what you have moved — hangs off those. If your question is about your own account rather than the process, the footer contact link is the right route, and the terms and privacy pages beside it answer the rest.
Tap the sign-in link on the brand home page and type the email address on your account with the password you chose. Complete the confirmation step the form shows and you arrive on your own home screen. The form is the same whether you opened it on a phone or a desktop.
Yes — one account covers every device. Sign in on a phone, close the tab, then sign in again on a desktop later and you will find the same wallet, saved games and history. Nothing needs to be installed to keep the two in step, and nothing is tied to a single handset.
Try the addresses you actually read — the one on your phone is the likely one. If none of them opens the account, write to us through the footer link and describe the name and details you entered, so we can look for the account instead of you guessing at inboxes.
Your wallet belongs to the account, not the handset. Sign in on a new phone or a borrowed desktop and the balance, the rails you have used and your record of transfers are exactly where you left them. Nothing has to be re-linked to see them, and the sign-in form stays the same short one.
The form pauses once so you can see which account you are opening before the home screen loads — useful if you hold more than one address. Read what it says and complete what it asks. If it will not move, the contact link in the footer is the fallback.
Check the address bar first, since a page that will not load is often a mistyped domain. Then try another browser or a mobile connection. Still nothing? Use the contact link in the footer, which is published on every screen of this site.