Reference

Your Login, Three Fields Only

One mobile number, one password, one SMS code — that is the entire 1111bde login, and your session stays tied to your own handset. Access depends on your local law and eligible regions, and we verify the number before any wallet is attached.

Number and passwordSMS code checkSession stays on your devicebKash, Nagad, Rocket inside
1111bde Your Login, Three Fields Only
SAFETY LAYERS

How 1111bde Protects Your Wallet

An account holds money, so the dull parts carry the weight. Passwords are stored hashed rather than in plain text, and pages travel over an encrypted connection. We ask for your mobile number because identity gets checked before a wallet is linked, and no one here will ever ask for your bKash, Nagad or Rocket PIN. Records stay with the account team under local rules — we don't pass your number to outside marketing lists.

Encrypted sessions

Pages load over HTTPS and your session is tied to the device that signed in. Copying a dashboard link into another phone won't open the account.

Name-matched payouts

Withdrawals travel back to the wallet name registered on the account. If the sending name and account name don't line up, we pause the request and ask first.

PINs stay with you

No agent, chat message or email from us will ask for your bKash, Nagad or Rocket PIN, or for a one-time code. Treat any such request as a scam.

Data we actually hold

We keep the number and wallet details you give us to run the account and meet local record-keeping rules. Ask support what's stored against your profile.

What Signing Up Actually Asks

Opening an account takes three answers: a mobile number that can receive SMS, a password you'll actually remember, and the name printed on your bKash, Nagad or Rocket wallet. Type the number, set the password, then enter the one-time code we text you. That's registration done — no queue, no document chase. The wallet name

matters more than people expect, because withdrawals return to a wallet holding the same name. Signing in afterwards is shorter. Number and password first; if the handset is one we already recognise, the lobby loads with your balance in view. A new phone, a new browser or a cleared cache triggers a second code, and

that is deliberate — a password alone should not be enough to move money out of an account wallet. Inside, the game tabs and the cashier share one mobile menu. Open Roulette GlowSpin or the cricket board, drop into the wallet, deposit, and come back to the table without signing in again. If a code

goes missing, wait for the resend timer instead of tapping repeatedly

  • Number-first registration Your mobile number is the account key. We confirm it with an SMS code before any wallet is attached, so a bKash, Nagad or Rocket balance only ever links to a number you control.
  • Device recognition Sign in from a handset we already know and the lobby opens with your balance in view. A new browser or a cleared cache asks for a fresh code instead.
  • One menu, no digging Games, wallet and betting slip share a single bottom bar on mobile. Cricket markets for BPL and international fixtures sit in the sports tab; slots and live tables sit beside them.
  • Help that can see your account Write in through chat or email and the team can check whether a code was sent, whether the number matches, and whether a wallet transfer is still pending on your account.

Account

Opening an account takes three answers: a mobile number that can receive SMS, a password you'll actually remember, and the name printed on your bKash, Nagad or Rocket wallet. Type the number, set the password, then enter the one-time code we text you. That's registration done — no queue, no document chase. The wallet name matters more than people expect, because withdrawals return to a wallet holding the same name. Signing in afterwards is shorter. Number and password first; if the handset is one we already recognise, the lobby loads with your balance in view.

Open Your Account

Your details are encrypted for secure account access.

HELP DESK

When a Login Goes Wrong

Most sign-in trouble traces back to something small: a SIM swapped into another phone, a password typed one time too many, or a code caught in a spam filter. Start with the number you registered, not the number you use now. If the code still won't come, the form side of the page has a resend control that clears on a timer, and the agent on chat can tell you whether a message left our side at all. Keep the wallet reference nearby if a payment is in the background.

Live chat Chat opens from the help widget without signing in. Give the agent the mobile number on your account and they can see whether a code was sent or blocked.
Support email Send the registered number plus a screenshot of the error to our support mailbox. If money is involved, attach the wallet reference — it removes a round of questions.
Password reset The reset option on the sign-in screen sends a code to your registered mobile. Confirm the code, set a new password, then sign in again on the handset you actually use.
WALLET RAILS

Fund the Account From Your Wallet

Paying in isn't a separate app to learn. Open the cashier inside your account, pick bKash, Nagad or Rocket, and we show the receiving number with a reference for that transfer. Send the amount from your own wallet app, confirm with your PIN, then paste the transaction ID back into the field waiting for it. Upay and bank transfer follow the same shape for anyone who prefers them. Which rails you can use depends on your local law and eligible regions.

bKash Choose bKash in the cashier, copy the number we display, send from your own bKash app and confirm with your PIN. Paste the transaction ID back so the credit attaches to your account.
Nagad Nagad follows the same shape: pick it, send, then return with the reference. Keep your Nagad statement handy — support can trace a stalled transfer with the reference in hand.
Rocket Rocket users see the same cashier screen. Send from your Rocket wallet, then type the TxnID into the field we show, so the amount lands against your account instead of sitting unassigned.
Upay and bank transfer Upay and bank transfer sit in the same list with their own reference formats. A larger bank transfer may need the account name to match the sending name before we apply the credit.

Login Questions You Might Have

Sign-in snags tend to repeat: a code that never lands, a password tried once too often, a new handset, or a wallet name that doesn't quite match. These are the ones our team fields most from the login screen. If your case isn't listed, chat puts you with someone who can pull the account up while you talk. Every answer here sticks to the step to take rather than a promise about how quickly a network moves an SMS.

Enter the mobile number registered to your account, then your password. We text a one-time code to that same number, and the lobby loads once the code is confirmed.

Wait for the resend timer to clear, then request a second code. Check that the SIM in your phone is the number on the account — a swapped SIM is the usual reason nothing lands.

Yes. A device we already recognise keeps the session, so you can leave the app, take a bKash transfer and come back without a fresh code. Clearing your browser data ends that.

Because a password alone shouldn't reach an account wallet. A second code proves the person signing in holds the registered SIM, which is why a borrowed phone triggers the extra step.

Use the reset option on the sign-in screen. A code goes to your registered mobile, you confirm it, then set a new password — the old one stops working straight away.

Same number, same password, same code. The layout differs a little — the browser keeps the cashier in a side tab, the app puts it in the bottom bar — but the account and wallet are one.
Reference

1111bde Login

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.