Casino / Mobile
The 1h88 register form asks for your email or phone number and a password you choose yourself, nothing more before the lobby opens. Fill that one screen and the same details sign you back in from any phone or desktop browser, wherever access is allowed in your region.
Opening an account on 1h88 is a single screen, and the fields are the ones you already expect: an email address or a mobile number, a password, and that same password again to confirm it. Type carefully. The contact you enter becomes your sign-in name, so a mistyped digit is the usual reason a first attempt bounces back. After you submit, the account page shows the next action for your case, and you follow the instruction printed there rather than a step you remember from an older visit. Signing in later uses the same two fields, and the lobby opens to the wallet strip and the game tabs you left. Cricket Boundary Blast, Baccarat Acehigh and Dealer 24x7 Live sit in that lobby once you are through. None of this needs a desktop: the form renders on a phone browser, and the buttons stay within thumb reach. Keep your login to yourself, because our support desk never asks you to type a password into a chat.
The email or phone number you enter becomes your sign-in name, so there is no separate username to memorise. Confirm the password beneath it and that same pair opens your account on a phone, a tablet or a desktop browser. Nothing else is needed before the lobby appears.
Each box on the form states what it accepts, and the submit button stays inactive until the required fields are filled. Read the line under the password box before typing, since it sets out the characters we take. If a field refuses your entry, the message sits directly beneath it.
Once you are through, the account area lists the routes open to you and the terms that go with them. Anything about your own sign-in record, your email or your phone number sits on that page rather than buried in a help file. Start there whenever a visit looks different from the last one.
The form is a single column on a phone and it does not push the submit button below a long scroll. Rotate to landscape or move to a laptop and the layout widens without reordering the fields, so the page you practised on is the page you get when you come back.
Your account wallet decides how you fund a session, and it lists the routes configured for you rather than a wall of logos. Nagad sits first for most of you: pick it from the wallet, read the number on screen, then confirm the transfer inside your own Nagad app. Rocket works the same way when you prefer it, while bKash and Upay appear alongside for anyone who already uses those wallets, and bank transfer covers those funding straight from a bank account. Whichever you pick, the wallet shows the destination before you send anything, so you are never guessing where a payment should land. Read the line under the route you select for the minimum and any charge that applies. If a route is missing entirely, it is not configured on your account yet, and the support page is where you ask about it.
Pick bKash in the wallet and the screen shows the number to send to before you open your bKash app. Complete the transfer yourself, then come back to the wallet, where the entry appears with the status our system records. Keep the bKash message until the line reads the way you expect.
Nagad is the route most of you reach for first, and it runs in three beats: choose Nagad, read the destination on screen, confirm the transfer in your own app. The wallet keeps the record, so matching it against your Nagad history later is a straight comparison. Nothing leaves our side without you approving it.
Rocket is the backup when your Nagad app is not to hand. Choose Rocket in the wallet, copy the destination exactly as it appears, and finish the payment inside your own Rocket app. The wallet then carries the entry beside your earlier transfers, which makes lining the two records up straightforward.
Upay sits in the same wallet list if you keep that wallet active. The steps do not change: select Upay, read what the screen gives you, then confirm from your phone. Because every route lands in the one wallet record, a Upay transfer can be compared with a Nagad one without leaving the page.
Bank transfer suits you if you fund from a bank account rather than a mobile wallet. The wallet shows the account details to use and the reference to quote, so your payment is matched to your account. Read the line beneath the field for the minimum that applies before you send anything.
Before you touch the register form, four small things are worth sorting out. First, make sure you are on the 1h88 address you normally use — check the domain in the browser bar rather than following an old link out of a chat group. Second, have the email inbox or the phone you plan to use open in front of you, because that is the contact the account gets tied to. Third, settle on a password now instead of halfway through the form, and store it somewhere you will find again. Fourth, keep the details yours: the name and contact you enter should belong to you, not a friend. Sort those four and the form is one pass, with no going back to fix a typo. Skipping the domain check is how people end up filling a lookalike page, so start there.
Open the register page from the domain you already use and read the address bar before typing a single character. A link forwarded through a group chat can point somewhere else entirely. If the domain looks unfamiliar, close the tab and type the address yourself.
Whatever you enter in the contact field becomes the way you sign in later, so have that inbox or that handset within reach while the form is open. Check the spelling or the digits before submitting; a mistyped contact means correcting things from the account pages afterwards instead.
Settle the password before the form asks for it, and pick something you do not use on another site. Both password boxes have to match exactly, and the line under the field states what we accept. Store it where you keep your other logins, since the sign-in screen will ask again.
The name and contact on the account should be yours. Using someone else's number or email ties their phone to your login and creates a tangle the account pages cannot unpick for you. Fill each field as it applies to you and leave nothing you are unsure about blank.
If you have not signed in for a while, start where you always did: the sign-in screen, with the same email or phone number and password. The account area carries whatever your case needs — open it and read the line printed there rather than guessing at a sequence. Some of you will find the saved password still works; others will need to follow the route the sign-in page points to. Either way, do not create a second account to get around a login you cannot recall, because two accounts tied to one wallet are harder to sort than one slow sign-in. If the account pages leave you stuck, the support page is the published route to us. A short message quoting the exact line on screen helps more than a long account of what you think went wrong, and sending it with the original wording attached gets us to the point quicker.
Use the same email or phone number you registered with, plus the password that goes with it. Check for a stray space at the end of the field, which is the most common reason a correct password is refused. Let the page take you through to the account area.
Whether you get through or the screen stops you, the account area states the next step for your situation. Follow the wording on screen rather than a sequence you remember from an older visit, because the routes shown there are the ones that apply to your account today.
Opening a fresh account to get around a login you cannot recall splits your wallet and your history across two records. Stay with the one you have and use the published support route if a step will not complete. That keeps your transfers and your sign-in in one place.
When you write to support, give us the email or phone on the account and quote the exact line the page shows. A screenshot helps more than a description of it. We reply from the published support route, and we never ask for your password in a message.
Account questions reach us through the routes published on this site, and those are the only ones we staff. When a form will not submit, a sign-in keeps returning you to the same screen, or a wallet entry looks wrong, send the detail: the email or phone on the account, the page you were on, and the exact words on screen. That is usually enough for us to point you to the right step. We do not ask for your password, and we do not take card or wallet numbers over a message — anything that does is not us. Keep your own record of what you sent and when, because a follow-up with the original message attached goes further than a fresh enquiry. If your question concerns a transfer, have the wallet record open before you write so you can quote the row you are asking about.
The support page linked from this site is the front door for account questions. It sets out how to reach us and what to put in a first message. Start there rather than in a social channel, where nobody speaking for 1h88 will answer you.
Most login questions are answered by the account area itself, since it shows the state of your sign-in and the routes currently open to you. Open it before writing to us and quote the line you see. That one detail saves a round of messages both ways.
For anything about a transfer, the wallet record comes first, because it lists each entry with the status our system holds. Screenshot the row in question and compare it with the message from bKash, Nagad or Rocket before you send your query through the support page.
Three habits handle most of what can go wrong with an account. Check the domain before a password goes anywhere — the address bar, not a link. Keep your login private, because nobody from our side will ask for it in a message or a call. And read the published terms and privacy pages once, so you know what we hold and how the service works. Everything else follows from those. Your account area shows your own record and the routes open to you, and the support page is where you raise anything that looks wrong there. We do not claim security standards or identity processes beyond what the site actually publishes, and we would rather you asked than assumed. Access to an account and to any wallet route depends on local law and eligible regions, so confirm that your own situation qualifies before you register.
Before any password goes into a field, check the address bar against the domain you normally use. Copies of a login page can circulate through chat groups and look close enough at a glance. If the address is unfamiliar, close the tab and type it out yourself.
Your password belongs to you and nobody else, including anyone who says they are helping with your account. No message from our side will ask you to type it, and no call will request it either. Treat a request like that as a signal to stop and check the support page.
Both the terms and the privacy page are published on this site and worth one read at the start. They set out what we hold about your account and how the service works. If something in either reads unclearly, the support page is where you raise it with us.
An account is yours to open or leave alone. If a session stops being enjoyable, step away and come back when you want to. Your sign-in details stay with you, and the account area is where you see your own record. Whether a route is open to you depends on local law and eligible regions.
Register questions tend to repeat, so here are the ones we answer most often, phrased the way we would put them across a cashier desk. If yours is not here, the support page takes it. The short answers first: the form accepts either an email address or a mobile number, nothing needs installing, and the account you open today is the one you sign in with tomorrow. What changes between people is usually the detail — a password that will not match, a number already tied to an old account, a wallet route not yet configured. Those cases are worth raising directly rather than working around, because a second account splits your record in two. Read the entry that matches what you are seeing, then follow the route it names.
No. The form accepts either an email address or a mobile number, and whichever you enter becomes your sign-in name. Use one you actually control, because the account pages tie your access to it. If you change numbers later, raise it through the published support route rather than opening a second account.
Read the message under the field it points to — usually a password that does not match, or a contact already in use. Both password boxes must be identical, and a number already tied to an account cannot be entered twice. If nothing is flagged, reload the page and try once more before writing to support.
Yes, and most of you will. The form is one column in a phone browser, with the submit button within thumb reach and no app to install. The same email or phone and password then work on a laptop or tablet, so you can register on the bus and sign in at home.
Your wallet lists what is configured for your account. Nagad and Rocket are the two we hear about most, with bKash and Upay appearing alongside and bank transfer if you fund from a bank account. Open the wallet after your first sign-in and read the route names shown there.
Go back to the sign-in screen and read what the page offers you there. The account area carries the steps that currently apply to your case, so follow the wording on screen rather than a sequence from an older visit. If a step will not complete, send the support page the detail it asks for.
Use the domain you already have and check the address bar on each visit. Links passed around in group chats can point at a copy of the page rather than this site. If the address looks unfamiliar, close the tab and type our domain yourself before entering any login detail.