Live / Mobile
qdc88 is a mobile-first platform shaped around one practical goal: getting you back into your preferred game category in the fewest steps possible. Every account feature, payment route, and lobby path we run is designed with a Bangladesh player's phone in hand.
We built qdc88 around a straightforward observation: a returning player on a phone should never have to hunt for their game. The lobby remembers where you left off. Your wallet balance is visible the moment you land on the signed-in home screen — no extra tap required.
Numbers only mean something when they describe something real. The four figures below reflect structural facts about qdc88 — what the platform covers, how many ways you can reach it, and the published routes available when you need help. We do not pad this list with invented session counts or unverifiable popularity claims. What you see here is what you can check yourself by opening the lobby, the account area, or the support page on any device.
5
3
2
3
Account help at qdc88 is reachable through three channels you can find directly on the site — no guessing, no third-party redirects. If your Rocket deposit has not reflected, or you need to confirm a bKash transaction against your wallet record, the live chat widget in the signed-in area is the fastest path. For more detailed account queries — such as document verification or wallet limit questions — email gives you a written record of the conversation.
Open the chat widget from your signed-in account screen. It connects you to the support team directly and is the channel we recommend for wallet queries, including bKash and Rocket transaction checks that need a quick resolution.
Send your query to the email address listed on the Contact page. Email works well for account verification questions, Upay wallet confirmations, and any situation where you want a written record of what was agreed or resolved by the team.
The on-site help centre is searchable and covers account setup, payment method steps, and lobby navigation. Check here first — most common questions about deposit flow, account continuity, and device switching already have a published answer.
Trust at qdc88 comes from consistency, not from claims. We publish our support routes, keep our payment options to the three rails we have actually configured, and let the lobby speak for itself through the studios whose titles we carry. When something changes in your account — a deposit status, a wallet update, a navigation change — the account area reflects it first.
The path from the home screen to any game category has stayed consistent since we launched the current layout. Mobile and desktop follow the same structure, so switching devices mid-session does not mean relearning where things are. Your progress and wallet carry over automatically.
We only name payment methods we have actually configured. bKash, Rocket, and Upay are the three local rails in your deposit flow — we do not list options that are not live. Transaction records are visible in your account wallet so you can cross-check any movement independently.
Every slot, live table, and crash game in the lobby comes from one of five studios: PG Soft, Microgaming, PlayStar, Bigtime Gaming, or Habanero. You can identify the source studio on each title card. We do not carry unnamed or unverified content alongside those publishers.
Our three support routes — live chat, email, and the help centre — are published on the site and accessible from the signed-in area. We do not promise response times we cannot consistently deliver, and we do not list channels that are not operational.
Account continuity is one of the specific things we engineered at qdc88, because a returning player who has to set up their preferences again on a new device is a player who wastes time before they reach the lobby. Your wallet balance, your preferred category order, and your transaction history all travel with your login credentials — not with the device.
Your game category, wallet balance, and deposit history are all visible from the mobile home screen after login. The layout is optimised for thumb navigation, and the category rail sits near the top of the screen so you reach your preferred section without scrolling.
The same account, the same wallet, the same transaction record — just on a wider screen. Desktop is where some players prefer to use live casino tables like Blackjack Livebets or Sylhet Roulette Room, because the larger view shows more of the table layout at once.
If you close the mobile browser and return on desktop, the lobby picks up from the same wallet state. Nothing resets. Your bKash or Rocket deposit that cleared earlier is still reflected in your balance — no need to refresh or re-confirm.
Your account data is stored at the platform level, not on your specific device. Logging in on a borrowed phone or a shared computer gives you full access to your wallet and history, and logging out removes that access cleanly.
These are the four things you can observe and verify yourself from the moment you land on the platform — not abstract values, not marketing language. Each one reflects a deliberate choice we made about how the lobby, the account, and the support flow should behave for someone in Bangladesh using a phone as their primary device.
From the home screen to any game takes two category taps and one title tap. We have kept that path short because an extra step on a slow mobile connection is an extra second a player loses. The category rail is the first interactive element above the fold on mobile.
Crash games like Crash Rocket and sports categories including Live Cricket Stadium sit in the same lobby, accessible from the same navigation bar. You do not switch between separate apps or sections — the categories are tabs, not separate platforms.
Your account wallet shows the current balance and a transaction log that reflects every bKash, Rocket, or Upay movement. You can see deposit status without contacting support. If a transaction shows as pending, the log tells you its current state.
Every title in the lobby is backed by one of the five studios we carry: PG Soft, Microgaming, PlayStar, Bigtime Gaming, or Habanero. The studio name appears on the title card, so you know exactly whose game you are opening before you start.
These are questions that come through support and the help centre frequently. Each answer reflects what is actually visible or actionable on the platform — we have not filled gaps with guesses. If your question is not covered here, the live chat and email routes on the Contact page are where to take it.
Availability depends on your local law and eligible region. The platform is built with Bangladesh players in mind — including bKash, Rocket, and Upay as the configured deposit rails — but you should confirm that access complies with the rules that apply where you are located.
The three configured local payment rails are bKash, Rocket, and Upay. Each connects directly to your account wallet. Deposit records appear in your wallet transaction log immediately after a completed payment, and you can verify the status there without needing to contact support.
Log in with the same credentials on the desktop browser. Your wallet balance, transaction history, and account preferences carry over automatically because they are stored at the account level, not on your device. No additional setup is required when switching.
The five studios in the lobby are PG Soft, Microgaming, PlayStar, Bigtime Gaming, and Habanero. They supply slots, live casino tables, and other game formats. The studio name is shown on each title card inside the lobby so you can identify the source before opening a game.
Three routes are published on the site: live chat from your signed-in account screen, email via the Contact page, and the searchable help centre. Live chat is the fastest path for wallet queries such as a bKash deposit that has not reflected in your balance yet.
The platform runs in your mobile browser — no download needed. The mobile browser version is optimised for thumb navigation, with the game category rail near the top of the screen. Your account and wallet behave the same way in the browser as they would in a native app.