Live / Mobile
Our login screen has one job: getting you from the phone in your hand back into your basa55 account wallet and the lobby rail you already know. Enter the email tied to your account, confirm the details on the next screen, and the signed-in home opens with your balance and recent activity in view.
Creating the account is the longer visit; signing back in is the short one. On the create screen we ask for an email address or mobile number you can open straight away, a password you will recall without hunting around, and the basic details tied to your own name. Read each field before you send it, because the login screen later matches exactly what you saved there. After that first visit, access is two fields, identifier and password, and the signed-in home opens on your account wallet, your recent session history and the lobby rail. Where a step needs something extra from you, it appears as an instruction inside your account area, and you follow the wording on that screen rather than guessing. Sensible housekeeping on our side of the page: the flow is the same in a phone browser and in a laptop browser, so nothing jumps position when you switch. Keep the device you use most as your default and the return trip stays familiar.
Your email or mobile number is the handle the login screen will expect every time, so pick one you can open without switching SIMs or hunting for a charger. You can check what you saved from inside the account area, and change it there when your number changes.
Choose something you will still remember next month rather than a throwaway string. The password field accepts what you set, and the same password carries you into the account wallet, the lobby rail and the area where your session history sits. Refresh it from the account area, never from a link you cannot place.
The signed-in home opens on your account wallet and the record of your recent visits, so you can see where the last session ended. That view is the quickest way to tell whether anything looks unfamiliar before you move into the lobby. Your balance is shown on that same screen.
If a step confuses you halfway through the form, the support routes printed on this site are the ones to use, and they are listed again further down this page. We would rather you ask than guess at a field and lose the visit.
Payments sit behind the login for a reason: your wallet is the part of the account only you should see. Once you are signed in, the cashier area lists the rails we have configured for Bangladesh, and the two we have set up first are Rocket and Bank Transfer. A Rocket payment runs from the wallet app on your phone, so the amount you send matches what you enter in the cashier. Bank Transfer suits larger transfers and moves through your own bank account, which means you keep the record from both ends. Enter the amount, confirm on the screen shown, and the transaction appears in your account wallet history so you can check it later. Only use the numbers and accounts printed inside your signed-in account area. Availability of any rail depends on your local law and eligible regions, so confirm what applies to you before you send.
Rocket is the rail most members reach for on a phone, because the wallet app already sits on the device you sign in from. Open the cashier while signed in, enter the amount, send it from your Rocket wallet, then check the record in your account wallet history.
Bank Transfer works through your own bank account and suits larger movements of money. Copy the account details printed inside your signed-in cashier area, make the transfer from your bank app or, and keep your own receipt so both ends of the record match.
Every top-up and every return shows in the account wallet history, listed with the rail you used. That list is the page to open when a figure looks different from what you expected, and the reference it carries is what we ask for if you write to support.
Two minutes of checking saves an evening of locked doors. Start with the address bar: you should be on the domain this page belongs to, spelled the way we publish it, with nothing tacked on the front. Next, make sure the inbox or messages app on the phone in your hand can actually open the email address or number tied to your account, because that is the handle the sign-in screen reads. Then confirm your password. If you are not sure of it, settle that before you begin typing, not halfway through. Finally, have the details you registered with in front of you, for the same reason a counter clerk asks for them, which is that they have to match what we hold. Get those four in order and the login itself takes seconds. If any one of them is off, use a published support route instead of trying the form again and again.
Look at the address bar before you type anything. The sign-in form belongs on the domain this page loads from, with nothing pushed in front of it and no extra characters after it. Save that address as a bookmark on your phone so the habit carries over next time.
The inbox or messages app on your phone has to open the email address or mobile number you registered with, because that is the handle the sign-in screen reads back. If you have changed SIM since opening the account, settle that inside the account area first.
Know your password before you start typing. If you are unsure of it, deal with that on the sign-in screen or through the published support route rather than filling the field again and again. Repeated guesses waste more time than one careful check before you begin.
Keep the details you gave when you opened the account within reach, for the same reason a counter clerk asks for them, which is that they have to match what we hold. If something has changed since then, correct it in the account area.
Most access problems on a phone are ordinary: a stale session, a browser that cleared itself, or a password typed with the keyboard still on the wrong layout. Start where the account interface starts. Open the sign-in screen and read the options printed under the fields. Whatever recovery wording your account shows is the wording that applies to you, and a remembered sequence from a different site is worth ignoring. If the screen offers a route you have not used before, follow the instructions exactly as written, including the details they ask for. Where nothing on the screen helps, the support routes published on this site are the way in; describe what you see, not what you expected to see. Keep the address bar in view the whole time. And if you are on a borrowed phone, close the browser rather than leaving a signed-in tab behind for the next person.
Open the sign-in page and read the options printed under the two fields. Whatever recovery wording your own account displays there is the wording that applies to you. A remembered sequence from another site is worth ignoring when the fields differ.
Where the screen offers a route you have not used before, work through it exactly as written, including every detail it asks for. Half-finished steps leave the session in an unclear state, which then looks like a second problem when you come back.
If nothing on the screen resolves it, use a support route published on this site and describe the page in front of you rather than the one you expected. Screens are easier to match when the wording is exact, including the message printed under the field.
On a borrowed phone or a shared laptop, close the browser when you finish instead of leaving a signed-in tab behind. Clearing that tab costs you one extra sign-in later and saves you a conversation you would rather not have.
Help here runs through routes you can see, not a number passed around in a chat group. The support page on this site is the first place to look, and it carries the contact paths we publish for account questions: a field that would not accept your password, a session that ended oddly, a wallet entry you want explained. The published terms and privacy pages are the next place to look, because most questions about what we hold and what you agreed to are answered there in full and in plain wording. Inside the account area, notices appear where they belong, beside the feature they concern, so read them while you are signed in rather than chasing screenshots from elsewhere. When you write to us, include the identifier on your account and the screen where the problem happened. That single habit is what turns a slow exchange into a straight answer.
Our support page is the first place to look, and it carries the contact paths we publish for account questions, from a field that would not accept your password to a wallet entry you want explained. Start there rather than in a group chat.
Questions about what an account involves, what we hold and what you agreed to are answered on the published terms and privacy pages. Read them signed in or signed out; the wording does not change. If a clause is unclear, ask through support and quote the page name.
Inside the account area, notices sit beside the feature they concern, so read them while you are signed in. That is where a change to a field, a rail or a screen is explained, and where you can look over your own session history without leaving the page.
What we can evidence, we say plainly; what we cannot, we leave out. The domain is the one this page sits on, and that is the only address you should be typing a password into, so bookmark it on your phone and the habit carries over. Our terms and privacy pages are published for you to read before you open anything, and they set out what an account involves under the law that applies where you are. Access itself depends on your local law and eligible regions, so settle that question before you commit, and treat any message promising you a way in from somewhere else with suspicion. Your password belongs to you alone; nobody from our side will ask you to read it out in a message. If something looks off, a page that will not load or a screen asking for more than the usual two fields, leave it and come back through the bookmark.
Everything starts with the address. The sign-in form lives on this domain and nowhere else we control, so bookmark it once and reach your account through that bookmark rather than through a link forwarded to you. What cannot be verified is not worth a password.
Our terms and privacy pages are open for you to read before you open anything, and they set out what an account involves under the law that applies where you are. Nothing on this page stands in for them, so treat them as your reference point.
Whether you can hold an account depends on your local law and eligible regions, and that is a check only you can complete. If a message promises you access from somewhere else, or asks you to send money outside the routes printed in your account, treat it as suspect.
Your password is yours alone, and nobody from our side will ask you to read it out in a message, send a picture of it, or confirm it on a call. The only screen that should ever receive it is the sign-in form on the domain you bookmarked.
The same handful of questions reaches our support page most weeks, so we have answered them here in the order they usually arrive. Read the first three if you are signing in for the first time on a new phone, and the last three if a session has gone wrong somewhere. Every answer points at a screen you can open yourself: the sign-in form, the account area, or a page published on this site. Where an answer depends on the device in your hand, we say so rather than offering a single rule that fits every browser. Nothing here replaces the terms and privacy pages, which stay the reference for what an account involves where you are.
Open the browser on the device you normally use, load this site, and tap the sign-in entry on the page. Enter the email address or mobile number tied to your account, then your password. The signed-in home opens on your account wallet and your recent session history.
The email address or mobile number you registered with, and the password you set at that point. Nothing else is required to reach the signed-in home. If your account screen shows an extra step, follow the wording printed there before you continue.
Do not keep refilling the same field after a rejection. Read the options printed under the sign-in fields and follow the recovery wording your own account shows. If nothing there applies, use a published support route on this site and describe the screen in front of you.
That depends on the browser and the settings on your device, which is why the sign-in screen behaves differently on a shared phone than on one you alone use. On your own device, letting the browser hold the session is convenient; on anything borrowed, sign out and close the tab.
No. The fields are the same and the signed-in home opens on the same wallet view, whether you use a phone browser or a laptop one. The lobby rail rearranges itself to fit the wider screen, and your account area keeps the same layout you already know.
Work through the recovery section on this page first: the sign-in screen options, the address bar check, then the support routes published here. Use the contact path listed on our support page and include the identifier on your account and the screen where it went wrong.