Mobile / Live
Built for Bangladesh accounts, the ef88c login screen asks for an email or mobile number and a password, then drops you into the lobby with your wallet balance already in view. Confirm the address bar reads ef88c before you type, and remember that access depends on your local law and eligible regions.
Opening an account takes one short form. We ask for the mobile number you actually carry, an email you can open, your name as it appears on your ID, and a password you do not reuse on other sites. Signing in later is the same pair of fields. None of it needs an app download; the page runs in your phone browser and on a computer the same way. After you are in, the lobby loads first, then your wallet, then the rails of live tables and self-paced games. If a field rejects what you typed, the message under it names the part to change — usually a mistyped digit in the number or a password typed with the wrong letter case. Keep those details to yourself. Our team will not ask for your password inside a chat message. When a step repeats for you, take it to the support route published on this site rather than guessing at the form.
Four lines and you are moving: full name as printed on your ID, a mobile number you can answer, an email you can open, and a password. We keep it on one screen so you are not scrolling between steps on a phone.
Coming back needs the email or mobile number you registered plus that password. No second app, no separate code to carry around. Sign in on a new handset and the account page still shows the same wallet and the same lobby you left behind.
Your session stays inside the browser you signed in with. Close the tab and it ends on most phones; leave it open and you return without retyping. Sign out from the account menu before you pass the phone to anyone else.
The first screen after sign-in is the lobby, not a menu. Live tables fill one rail, self-paced slots another, and the crash titles we carry, Crash Zone and Barisal Crash Arena among them, sit one swipe away. Wallet balance stays in view above the rails.
Money moves after sign-in, from the wallet tab, not from the login screen. Two rails sit inside your account: bKash for mobile transfers and Bank Transfer for a bank account you hold. Open the wallet, pick the rail, and the page prints the details to send to plus a reference field you fill in yourself. The amounts, the minimums and any verification request are shown on that same page, so read them there instead of relying on what you heard elsewhere. When a transfer does not show up in your balance, open the transaction record, copy the reference and the amount, and take both to support. Keep the confirmation your wallet or bank gives you until the record lines up. Nothing about a transfer lives on the login form, so sign in first and decide afterwards. Whether a rail is open to you depends on your local law and the region you registered in, and the wallet tab is where we state it.
bKash is the wallet rail most of our Bangladesh accounts use. After sign-in, open the wallet, choose bKash, and the page shows the number to send to along with the reference field. Match the amount exactly, keep the message short, then check the transaction record in your account.
Bank Transfer suits you if you would rather move money from a bank account than a mobile wallet. The wallet page prints the account details and the reference to quote. Save the confirmation your bank gives you until the same record appears on your side.
Four checks take a moment and save a wasted attempt. Start with the address bar: the page should read ef88c, and a link that arrived by message and points anywhere else should be closed rather than filled in. Next, confirm the phone or email you are about to type is the one attached to the account — a number you swapped out last month will not open anything. Then make sure you know the password instead of guessing at it; a careful single attempt beats three hurried ones. Finally, have your ID details within reach in case the account page asks you to confirm a name or a date of birth. Not one of these steps involves money, because all four belong to access, not to the wallet. Run them once and the form behaves the way it should. If one of them fails, pause there and use the account recovery route instead of retyping the same field.
Type ef88c yourself or open a bookmark you saved. A link that arrives in a message can point anywhere, and the login form is the last place to test that. The address bar, not the page design, tells you where you actually are.
The contact on the account has to be one you can still reach. If you changed numbers and never updated it, the form will reject you no matter how right the password is. Sort that through support before you try again.
Know the password rather than working through guesses. Letter case matters, and a phone keyboard in the wrong language can quietly change what you type. If you are unsure, type it once, slowly, and read it back before you submit the form.
The account page sometimes asks you to confirm a name or a date of birth. Have the same details you registered with in front of you, spelled the same way. It is an access check, not a payment step, so no wallet or bank information is involved.
Locked out is a normal thing, not a crisis. Open the account page and read what it offers before you try anything creative with the form. Where the interface shows a way to reset or retrieve access, follow the fields exactly as printed and use the same phone number or email the account was built on; a new address will not carry the request through. If the page offers no self-service route, the published support channel is your next place to go, and a short message works better than a long one: tell us the email or mobile number on the account, what the login screen says when you try, and when you last got in. Do not send your password in that message, and do not send a photo of your ID unless the account page asks for it. Nothing about this should be improvised — the routes exist so you use them in order.
The account page states what it can do before you act. Read the fields and the message under them, because a rejected attempt often explains itself right there. If you changed your phone number or email since registering, the old one will not carry the request through.
Type the email or mobile number the account was opened with. A different address cannot show the account is yours, so the request stalls at the first field. If you have lost that number as well, say so in the first line of your message.
No one on our side needs your password, and a message that asks for it is not from us. Send the login screen's wording, the contact on the account and the last time you signed in successfully. That is enough for support to start looking with you.
Support for login sits behind the contact route published on this site, and that route is the only one we point you to. Use it for a password you cannot remember, a phone number you no longer hold, a name typed wrong at registration, or a session that will not open on your handset. Keep the message to three facts: the contact attached to the account, what the login screen says back to you, and what you already tried. A screenshot of the error helps; a screenshot of your password does not. If your question is about a wallet entry or a transaction record, copy the reference into the same message so the person reading can look at both halves at once. Nothing is gained by opening a second thread on another channel, because the published route is the one that reaches us. Reread the page before you send: its wording is current, and anything quoted elsewhere may not be.
The contact route published on this site is where login problems go. It reaches the desk that handles accounts, so put the contact on your account and the exact wording of the error in the first message rather than spreading the same question across several.
Where the login screen answers you, read that answer as the first clue. A rejected field usually names itself under the box. Copy that line into your message so the person helping you starts from the same sentence you are staring at.
If the question is about a wallet entry rather than the sign-in itself, sign in first and copy the reference from the transaction record. One message carrying the reference and the amount saves a round of questions and keeps the thread on one screen.
Credibility on a login page comes from small verifiable things, not from a badge. The address in your bar should read ef88c every time; the padlock tells you the page is served over a secure connection and says nothing about who runs it, so match the domain as well. Our terms and privacy pages are linked in the footer of every screen, this one included, and they are the written version of what we do with the details you hand over. Read them once. They explain what the account keeps and what you can ask us to change. Access itself depends on your local law and eligible regions, and we would rather you check that than find out later. Keep your password off shared family phones, and treat any message offering to fix your account for a fee as someone else's problem, not ours. If a page ever looks different from what you remember, close it and type the address yourself instead of clicking through.
Every screen we run sits on ef88c. Before you type a password, read the address bar and compare it. A bookmark you saved yourself is safer than a link forwarded through a group chat, and closing a doubtful tab costs you nothing at all.
Both are linked in the footer, here and on every other screen. They spell out what the account holds and how to ask us to correct it. Skim them once with your own details in mind rather than saving them for the day something goes wrong.
Whether you can hold an account depends on your local law and eligible regions, not on what a forwarded link promises. Check that before you register, and if the answer is unclear where you live, ask through the published contact route before sending anything.
Sign in from a phone or browser you control. Shared family handsets keep sessions alive after you walk away, and a machine you do not own can store what you typed. Sign out from the account menu when you finish, each time you finish.
These are the questions that reach us most often about getting in, so we answer them in one place. Nothing here replaces what the account page and the published support route tell you, and where the two differ, trust the page you are looking at while signed out. Keep your password to yourself and check the domain before you type it.
The email or mobile number you registered with and the password you set at that time. Nothing else is needed on the login screen. If you opened the account with a number you have since replaced, use the support route rather than opening a second account.
Check the letter case and the keyboard language first; both are common causes on a phone. Then type it fresh rather than pasting, because a copied password can carry an invisible space with it. If it still fails, pause and use the route the account page publishes.
Your session lives in the browser you used. Leave the tab open and you can return to the lobby without typing the details again; close it or sign out from the account menu and the next visit starts fresh. Sign out before handing the phone to someone else.
No, and it should never ask. Signing in only shows the account is yours. bKash and Bank Transfer both sit inside the wallet after you are through, where the amount, the reference and any verification step are printed on the page you are using.
Open the support route published on the site and say so in the first line. Include the name on the account and any detail you can confirm, such as the last time you signed in. Do not open a second account to work around it.
Nothing here needs one. The account page runs in your phone browser, so save ef88c and sign in from there. A browser also lets you clear the session by clearing site data, which is a useful lever when a shared handset is involved.