Reference

m71com App Access on Your Phone

Everything you need sits in the phone browser — slots, live tables and the cricket betslip behind one wallet sign-in — and players in Dhaka reach the lobby without installing a thing.

mobile browserdevice accessbuild availability checkwallet sign-incricket betslip
m71com m71com App Access on Your Phone
m71com What a Native Build Adds to Your Session

What a Native Build Adds to Your Session

Where we have a native build running, it changes the small things that decide how a session feels. Push alerts tell you when a live table you were watching opens a seat, or when a slot's feature round is about to begin, without keeping the page awake on your screen. Fingerprint login replaces the typed wallet number and OTP on every return

visit, so reopening Crash Blitz or Blackjack Ace takes one touch. The betslip keeps building while you're off Wi-Fi — add a cricket market, lock the phone, and it's still there when you come back. Wallet funding opens from the same panel. None of that replaces the browser lobby; it sits alongside it.

  • push alerts for table openings and feature rounds
  • fingerprint sign-in instead of a typed wallet number
  • betslip that survives a locked screen
  • wallet funding from the same panel
m71com Mobile Access in Three Steps

Mobile Access in Three Steps

Access takes three moves on any phone we support. Open our site address in the browser you already use, let the page finish loading, then sign in with the mobile wallet number tied to your account. The lobby remembers your last layout — slots on one screen, live tables on the next. If a native build is live at that moment, a

banner on the home screen says so and links you to it; with no banner, the browser lobby is the version we are running. Never install a file from a link someone forwards you on a messaging app.

  • Open our site address — Type the address yourself or use the bookmark you saved earlier. Skip links forwarded in messaging apps; your browser bar is the only place the address should come from.
  • Check browser support — Chrome, Firefox, Safari and most current Android browsers render the lobby fully. If a page looks broken, update the browser first before deciding the phone is unsupported.
  • Sign in with your wallet number — Enter the mobile wallet number on your account, take the one-time code, and you're in. Save the device so later visits skip that code entirely.
  • Pin the lobby to your home screen — Use your browser's add-to-home-screen option. The shortcut opens straight to the sign-in page and behaves like any other icon sitting on the phone.

Login Speed, Dark Mode and Push Alerts

Speed is the whole point of the phone build. Your session opens with a fingerprint or face check, and dark mode keeps the screen readable when you check a live table late at night. Push alerts run per category — cricket, slots, live casino — so you decide what reaches your lock screen. The offline lobby preview keeps your recent rooms cached, letting you see what's inside before the connection settles. Whatever you save stays on the handset you registered, not on a shared one.

Fingerprint sign-in

Save your account once and the phone holds the wallet number. Coming back means a fingerprint or face scan; the one-time code only returns when you clear app data or move to a new handset.

Dark mode

Lobby, betslip and table views switch to a low-light palette after sunset. Handy when you're following a BPL match in bed and don't want a white screen lighting the whole room.

Push alerts

You pick which categories reach your lock screen — slot feature rounds, live table openings, cricket markets you follow. Everything else stays quiet until you open the lobby yourself.

Offline lobby preview

Rooms you opened recently stay cached, so the lobby still renders while your signal settles on the way into the. Nothing is staked or settled until you are back online

Check Your Device Before You Sign In

Run the short list our support desk uses when someone messages about a phone that won't load. Current Chrome, Firefox or Safari handles the lobby. A screen wide enough for the betslip and the table grid side by side gives the cleanest session; narrower panels simply stack instead. Your account has to be verified with a mobile wallet in your own name before the lobby opens fully. When a handset drops off our tested set, we update that list on site rather than leaving you to guess.

Browser accessChrome, Firefox, Safari and the default Android browser all open the lobby. Keep the browser updated, since an old build is the usual reason a page loads without its buttons.
Screen layoutA screen wide enough for the betslip and the table grid side by side gives the cleanest session. Narrower screens stack the panels, which works fine for slots and crash games.
Account requirementOne verified account and one wallet in your own name. Shared devices work when you sign out afterwards, so a saved login doesn't carry over to the next person using it.
Supported device setWe keep the list of phones we test against on the site and refresh it when a browser changes. A handset that isn't listed usually still runs the browser lobby.
Connection checkSlots tolerate a patchy line; live dealer tables need a connection that holds. If a stream keeps dropping, switch between Wi-Fi and mobile data before blaming the handset.

Questions About the m71com App

These are the phone questions our support desk answers most often, written the way we'd reply to you in chat. If your handset isn't covered here, send us the phone model and the browser name — that pair is what we need to trace a loading problem. One more thing worth knowing: the browser lobby and any native build share the same account and the same wallet, so nothing carries over separately.

Only if a native build is live at the moment you look. Our site shows a banner when one is running, and we never ask you to install a file sent through a messaging app link.

Open our home page on the phone and look for the build banner above the lobby. Nothing showing there means the browser version is what we're running today.

No. Wallet transfers run through the mobile browser exactly as they do anywhere else, and you confirm each one with your PIN inside the bKash, Nagad or Rocket screen.

Current Chrome, Firefox and Safari handle slots, live tables and the betslip. When a page loads without its buttons, updating the browser fixes it more often than changing phones.

Browser access gives you alerts while the tab stays open; lock-screen versions come with a native build. That is the difference you would notice day to day.

Yes, with your wallet number and the one-time code. Skip the save-this-device option and sign out when you finish, so the login doesn't stay behind on it.
Reference

m71com App

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.