Casino / Live
Everything you would normally message us to ask about access, the lobby and the wallet is written down on this 889fb FAQ page, in the order your session runs. Each block points at a route you can open yourself, so you are not waiting on a reply to get moving.
An FAQ page is only worth reading if it answers the question you actually typed. So we ordered this one the way a session usually runs: access first, then the lobby, then the wallet, then the awkward thing that went wrong at the end.
Nothing on this page is padded to look bigger than it is, so the same rule applies to how we describe the page itself. The figures below are structural: what the lobby holds, what the layout renders on, which language you are reading, and how many routes sit in the support block further down. We are not counting visits or accounts, because those numbers move and they are not yours to verify.
6
2
1
3
The FAQ stops where your own account begins. Three routes on this site take over from there, and each starts from a fact you can already see, which keeps the exchange short.
When a block does not match what you see, open the support link from your signed-in account menu and quote the heading you were reading. Paste the wallet reference and the route you followed. That keeps it to one message, because we can look at the same screen.
Some questions are settled by wording rather than explanation. Our terms page carries the binding text on access, eligibility and account use, and it sits on this same site. If a block here reads differently, follow the terms page and tell support where the gap sits.
Most money questions end at the record, not at a message. Open your account wallet, pick the transaction, and read the reference and status printed there. bKash, Nagad, Rocket, Upay and Bank Transfer entries each carry their own line, so quote it.
A page like this only earns its place if you can audit it. So we keep every claim tied to something on screen: a tab you can open, a name printed in the lobby, a line in your wallet row. Where we have no figure to point at, we leave the gap open and say so.
Nobody hands us a script. These answers come from the team that keeps the lobby and the account routes running, which is why they name real screens instead of describing a mood. If a block cannot point at something you can open, we cut it.
RTP varies by title and by studio, so we print no percentage nobody published. Where a game shows that figure in its own panel, the block tells you where to look. Where it does not, we say so and stop.
Studio and game names appear here exactly as the lobby prints them, from Pragmatic Play through JDB, Bigtime Gaming, Habanero and PG Soft, so a search lands on the same tile. A misspelled provider costs you time and costs us credibility.
The page is in plain English for readers in Bangladesh, with local wallet names left as they are. No translated sentences, no phrasing borrowed from another market. If a line needs a second read, that is our editing problem, not yours to decode.
Answers and screens drift apart for ordinary reasons: a label changes, a field moves, a tile gets recategorised. When that happens the live screen carries it and the block needs editing. Here is how the four comparisons usually land.
Where a block describes a step, you should be able to repeat it on your own account and see the same fields. If the screen shows something the block leaves out, follow the screen: it reflects your state, while the block describes the general route.
Terms wording is fixed and specific, FAQ wording is explanatory, and the two should never disagree on substance. When you find a difference, the terms page carries it, and we want the heading you were reading so the block gets corrected.
A title named in an answer should appear in the lobby under that same spelling, in that same category. Slot Extreme, Football FastGoal or Live Cricket Odds, you can open each one and look. If a tile moved, the lobby label is current.
What support tells you and what this page says should match, because both start from the same routes. A reply that contradicts a block is a signal that the block needs rewriting, so send the heading back with your message and we will look.
What makes this page recognisable is not decoration. It is the order of the blocks, the plainness of the questions, and the way each answer hands you a route instead of a promise. Those three habits repeat on every block, whether you read on a phone or on a desktop.
Every heading is phrased the way it gets typed into a search box, not the way a policy gets titled. That is deliberate. You should be able to skim the headings on a phone, recognise your own situation, and stop there.
Answers here end by pointing somewhere: the account menu, the wallet record, the terms page, a named tile in the lobby. We do not close a block with a request to contact us when a screen already exists. That habit is why the page runs long.
The layout starts at mobile width. Headings stack, answers open where you tap, and nothing pushes you sideways. Moving between the lobby and this page on one device does not reset which block you were reading.
Payment names read as your wallet row shows them, and studio names sit with the tiles they belong to. Consistent naming is what lets a short answer stay checkable months later, when the lobby around it has changed.
Below are the six questions we get asked about this page itself: where to start, who writes it, what to do when a screen disagrees with a block. If yours is not here, the support link in your account menu is the next stop.
Start at the block that matches where you are stuck, not at the top. Access questions come first because they come first in a session, then lobby browsing, then wallet routes, then support. The headings are written to be skimmed, so one glance should tell you which block to open.
We write them as the operator of this lobby, which is why each one names a screen or a name you can open. You can match a payment name against your wallet row, a title against its lobby tile, and terms wording against the published page. None of it rests on taking our word.
Your account screen reflects your own state, so follow that and treat the block as the general route. Then send us the heading and what you saw instead. A mismatch usually means a field or a label moved and the block was not rewritten alongside it.
Yes. The page renders for a phone first: headings stack, answers expand where you tap, and no table drags you sideways. On desktop the same blocks sit wider. Moving between the lobby and this page on one device does not reset the block you were reading.
It explains routes; it does not replace the published terms, and it does not quote live figures such as odds or current lobby contents. Anything that turns on your region or your local law belongs on the terms page, because that wording binds both sides in a way a block here cannot.
Open the support link inside your signed-in account menu, name the block you already read, and paste your wallet reference or the route you followed. One message usually settles it. If what is missing is a block rather than a personal case, send the heading and we will write it.