Live / App
Your nagay88 login is one door with two keys — the phone number or email you registered and the password you chose — and behind it sit the game lobby, your wallet balance and the bKash or Nagad funding route you set up. Access depends on your local law and the regions we are able to serve, so read the terms published on this site before you start.
Signing in takes two fields — the phone number or email you registered with, and the password you chose at that moment. Nothing else is needed before the lobby opens. If you joined with a mobile number, keep that number active on the phone you are holding, because the field reads it exactly as you typed it the first time. New and returning accounts use the same form, so the screen you meet minutes after registering is the screen you meet every week afterwards, and you always know which two boxes to fill. What sits behind the form matters as much. Your wallet balance, the game category you were last browsing and your saved payment preference stay attached to the account rather than the device, so moving from a phone to a laptop resets nothing. Sign out properly when you finish on a shared handset, and keep your password somewhere only you can reach. If a field refuses your entry, read the label again before retrying; a stray space or an old number is usually the reason.
The sign-in form behaves the same on a phone, a tablet and a laptop, so what you learned on the first visit still applies later. Your wallet balance and game history follow the account rather than the handset, which means switching screens mid-week changes nothing about what you see.
Both fields read exactly what you entered when you registered. An old number or a swapped email is the usual reason a correct password still fails, so compare what you are typing against the details you set up, and follow any verification instruction your account displays.
Choose a password you can recall without writing it on the phone, and change it if anyone else has handled the device. On a shared handset, sign out instead of leaving the session open. This one habit keeps the account yours.
If a field will not accept your entry, the support route printed on this site takes the question from there. Describe the message you saw and the device you used, and the reply comes back through the same channel, so keep it in your mailbox.
The wallet is where your sign-in pays off, so the funding route lives inside the same account you log into. bKash is the path most of our players reach for first: sign in, open the deposit area, choose bKash, enter the amount you want to move, then approve the request from your bKash app or menu exactly as the prompts describe. Nagad sits beside it as the ready alternative — the same flow through a different wallet. Rocket covers players who keep a Rocket balance instead, and bank transfer stays listed for anyone moving money that way. Whichever you choose, the transaction appears in your account history, so you can compare what you sent against what the wallet confirms. One habit helps before you approve anything: check the wallet number shown on the deposit screen against the number saved in your phone. Follow the fields and verification steps exactly as your account displays them.
bKash is the route most of our players pick first. After you sign in, open the deposit area, choose bKash, type the amount, then approve the request through your bKash app or menu as the prompts show. The wallet number on that screen is the only one we ask you to send to.
Nagad works as the ready alternative when your balance sits there instead. The steps mirror bKash: sign in, pick Nagad in the deposit area, enter the amount, and confirm from your Nagad app. Keep the confirmation message; it is the simplest way to match a wallet record against your account history later.
Rocket suits players who already move money through it. Select Rocket on the deposit screen, follow the fields shown there, then approve from your Rocket wallet. Because the request starts inside your signed-in account, the transaction lands in your history without you noting it separately.
Bank transfer stays listed for anyone who prefers a bank route over a mobile wallet. The deposit screen shows the details to use and the reference to attach, and the amount appears against your account once the transfer is recorded. Compare your bank receipt with the account history if anything looks different.
Four things decide whether your sign-in goes smoothly, and all four sit on your side of the screen. Start with the web address: type it in yourself or open a bookmark you saved, and treat a link you did not ask for with suspicion. The address bar is the one place worth a second look before a password goes in. Next, the contact you registered with. If it was a mobile number, that phone has to be with you and able to receive messages; if it was email, you need to open that inbox. Have your password ready rather than guessing at it, and if it lives in a phone's password manager, unlock that first. Lastly, identity details. When your account asks you to confirm a name or date of birth, the answer has to match the record you set up, because mismatched details are what most often stall a sign-in or a wallet step.
Type the domain yourself or open a bookmark you saved earlier. Links arriving from messages you did not request are worth ignoring, because the address bar is the one place you can confirm before entering a password. Check it once, then carry on.
Whichever contact you registered with has to be available when you sign in. If it was a mobile number, keep that phone to hand; if it was email, be able to open the inbox. Getting back in is harder once the registered contact has changed.
Know the password before you start typing. If you store it in a password manager, unlock that first. Random attempts rarely help and slow you down, so one careful entry from a saved copy beats five hurried guesses.
When your account asks you to confirm a name or date of birth, the answer must match what you set up. Mismatched details are the usual reason a wallet step or a sign-in stalls, so keep the record you registered with close at hand.
If a sign-in does not go through, work forward from what the account screen tells you instead of guessing at fixes. The sign-in form usually carries its own route for the case where the password has slipped your mind, and following it shows the fields the account wants, in the order it wants them. We do not publish a shortcut around that screen, and nobody from nagay88 will ask for your password over a message. When you have signed in before on the same device, the browser may be offering an old entry; clearing it and typing again settles more cases than anything else. If the account still refuses you, use the support route shown on this site and describe what you see — the field name, the message, the device you are on. Our team reads those details and replies through the published channel. Being locked out is not the end of the account either, because the profile keeps everything attached to it.
Open the sign-in screen and read the options printed under the fields. Where a password has slipped your mind, the form itself carries the route the account expects you to follow, so use that rather than a workaround you found elsewhere.
A browser that stored an older password will keep offering it. Delete the saved entry for this site, type the password again, and try once more. This single step settles more failed sign-ins than any other.
If the screen still refuses you, write through the contact route on this site. Include the phone number or email on the account, the exact message you saw, the browser you used and roughly when it happened. A clear first message shortens the exchange.
Nothing is lost while you are locked out. The wallet balance, deposit history and saved game preferences stay on the profile, so once you are back inside they sit exactly where you left them, including any unfinished table.
Account questions reach us through the routes published on this site, and each one exists for a different kind of problem. The contact page carries the message form we read for sign-in trouble, wallet questions and anything that needs a written record. If you would rather use a channel you already keep open, the support address published there works the same way — send the detail and hold on to the reply. Before writing, gather the facts that make an answer possible: the phone number or email on the account, the exact wording of any message you saw, the device and browser you used, and when it started. We ask for those because a sign-in problem on a phone behaves differently from the same problem on a desktop, and the answer follows the difference. Support is not a queue you have to shout into. Describe the issue once, clearly, through one published route.
The contact form on this site is the route we read for sign-in problems, wallet questions and anything needing a written trail. Send the account contact, the message you saw and your device, and the reply returns to the same place.
If email suits you better, the support address published on the contact page reaches the same team. Keep the thread in your inbox; quoting it later saves you from repeating the details of an earlier sign-in problem.
Some answers are already written down. The terms and privacy pages cover how the account works and when access is available in your region, so check those before writing in about eligibility or account rules.
Everything we ask you to rely on here is something you can confirm without our help. The web address in your browser is the first check: it should be the domain this site publishes, and a page asking for your password under any other address deserves a second look before you type. Bookmark the real one and use the bookmark. Your rights are written down rather than implied, too. The terms and privacy pages linked from this site set out how the account works, what we collect and how eligibility is decided, and both can be read before you register. Access depends on your local law and the regions we are able to serve, so those pages are the place to settle whether the account is open to you. Signed-out behaviour is treated the same way. On a shared phone, sign out when you finish and never leave the password field filled on a device other people use. When a question remains, the support route on this site answers it.
The domain printed across this site is the one to use. If a page asking for your password sits under a different address, close it. Saving the real address as a bookmark removes the guesswork on your next visit.
Account rules, eligibility and how data is handled are set out on the terms and privacy pages linked here. Reading them before you register tells you plainly whether the account is open to you under your local law and region.
On a phone or laptop other people use, sign out when you finish and let the browser forget the password. It takes a moment and keeps your wallet balance and game history out of someone else's hands.
When something looks wrong, the published support routes are the ones that carry your question to us. Keep the reply in the same inbox or thread so the record of the issue stays with you.
The questions below are the ones we are asked most about getting into an account, and each answer points to the screen or route where you resolve it. Read them before you write to support, because most sign-in trouble ends with a checked field rather than a message to us. Where an answer tells you to follow the instructions on your account screen, do that first — those prompts reflect your own profile, and the support team will point you back to the same place.
Open the sign-in page, enter the phone number or email you registered with, then your password. Both fields read exactly what you set up, so check the spelling and any stray spaces. The lobby opens once they match, and your wallet balance is waiting inside.
Read the options printed under the sign-in fields, because the form itself points to the route your account expects for a forgotten password. Follow those on-screen instructions in order. If the screen still will not let you through, write to the support route published on this site.
Yes. The form is the same in a mobile browser and on a desktop, and your account carries the wallet, game history and saved preferences with it. Nothing resets when you move between devices, so you can start on a laptop and finish on the phone.
The usual cause is a mismatch rather than a wrong password: an old mobile number in the contact field, a letter typed in the wrong case, or a browser filling in a password you changed earlier. Clear the saved entry, retype both fields, and try once more.
Treat a shared handset carefully. Sign in, do what you came for, then sign out and let the browser forget the password. Your balance and account details stay tied to the profile, so signing out costs you nothing and keeps the next person out.
Use the contact route published on this site. Tell us the browser and device you used, the exact message on screen, and roughly when it started. That detail lets the question be settled in one reply instead of several back-and-forth messages.