Our FAQ hub collects the questions Pakistani account holders send us most: account access, JazzCash and Easypaisa steps, live table behaviour and policy. Every answer is written by...
Each answer starts as a real ticket from an account holder in Pakistan, then gets checked by the team that owns that flow — payments, live tables, account access or policy. We rewrite in plain English, date-stamp every page and refresh it whenever a step changes, so you are never following last year's instructions.
We sort the hub into three question sets so you can skip to yours: lobby and game behaviour, payment and account funding, and the policy questions that decide how you use your...
Some questions are yours alone — a stuck transaction, a locked account, a live table that behaved oddly. Every answer page carries a route to a human, so you never hit a dead end.
Open chat from any answer page and an agent picks up with your account already in view. Payment questions usually need your transaction reference, so keep it nearby.
Send a written request when you want a record of the reply. Attach screenshots and the exact time, and we answer using the same wording the hub uses.
Messages inside your account cover follow-ups on a case you already opened. We keep the history attached so you do not explain the situation twice.
Answers are written by the operations team that handles the same flows daily, not by a separate marketing desk. Each page names the team behind it and the...
The people who process JazzCash and Easypaisa requests write the payment answers. Our live dealer team writes the table questions...
Every answer shows when it last changed. If a step looks different from the screen in front of you, check...
We write in the English you use for banking and mobile apps in Pakistan, with local payment names spelled the...
We do not publish player counts, awards or claims we cannot show you. Where a figure appears, it comes from...
When an answer turns out wrong, we fix it and say what changed. You can tell us through chat or...
Where access depends on local rules, our answers say 'where local law permits' or name the supported regions instead of...
An answer only helps if it matches what you are told elsewhere. Our hub, chat agents and in-app messages read from the same source document, so a payment...
Our answer pages share one layout so you always know where to look: the category chip, a dated change line, numbered steps and a route to...
A single chip above the heading tells you which question set the page belongs to, so you can jump sideways to a neighbouring answer without returning to the index.
One line records the last time the answer changed and which team signed it off. It is the quickest way to judge whether the page still reflects your screen.
Local payment steps appear as a numbered list in the order you perform them, starting from the screen you are actually on rather than an abstract first step.
One field scans every answer, including local spellings of JazzCash, Easypaisa, SadaPay and Raast, so a mistyped product name still lands you on the right page.
Three or four related answers sit under each page. They follow the flow you are in, so a payment question leads to timing questions rather than unrelated lobby subjects.
Every page ends with a direct route to chat or email, carrying the page headline so the agent knows exactly which answer you were reading.