One clause skeleton
Our privacy and cookie pages share this structure, so a term you learn here keeps the same meaning when you read about data handling or stored preferences.
Every account at parimatch pk runs on the terms set out on this page, and they apply from the moment you register. We keep the wording plain so...
These terms are written for Pakistan and are applied where local law permits. That wording matters: if a clause conflicts with a rule that applies in your province or city, the local rule takes over and the rest of the page still stands. We describe payment handling around JazzCash, Easypaisa, SadaPay, NayaPay and Raast, since those are the rails you will use
to load and withdraw, and each one carries its own settlement window that we cannot shorten. Age, identity and location checks sit inside the registration flow rather than after it. Where a term depends on a regulator, a bank or a mobile wallet provider, we say so instead of hiding it in a footnote. Anything we change is dated, and the version
on this page governs your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a clause reads oddly, ask us before you agree to it rather than after. Our live chat runs every day from 09:00 to 02:00 Pakistan time, and email tickets are answered within one working day. When you write in, quote the paragraph number from this page so we can point you to the exact wording and explain it in plain English.
Chat runs daily from 09:00 to 02:00 Pakistan time. Keep your account email handy and name the paragraph you want explained; the agent will walk you through the wording.
Write to our policy desk and put the paragraph number in the subject line. We reply within one working day and send older wording alongside any clause we have since revised.
If you cannot sign in, use the login screen reset or ask chat to verify your details. Access questions follow the account rules section, and we never ask for your wallet PIN.
These terms are reviewed by the people who run the platform, not by an outside agency, and that shows in the level of detail: wallet names, support hours and settlement windows appear...
These clauses are drafted and maintained by our own operations and payments teams in Pakistan rather than copied from a template, so the wording matches how the platform behaves day to day.
Timeframes, wallet names and support hours are given in Pakistan terms from the opening line, so you will not find foreign bank references buried inside a clause.
Each policy area names the team responsible for it, so a payment question reaches the payments desk and an access question reaches the security desk instead of one general queue.
A dated log at the foot of the page records what changed and when, so you can trace a revision instead of discovering an obligation that appeared without explanation.
We set out which details we hold, why we keep them and how long they stay on file, and security questions are answered in writing so you can refer back later.
If you disagree with a decision taken under these terms, the page shows where to send it, which team reads it and how long a reply normally takes.
Every policy page on parimatch pk shares one skeleton: the same headings, the same definitions and the same version stamp. That consistency is deliberate. It means a term you understood while reading...
Our privacy and cookie pages share this structure, so a term you learn here keeps the same meaning when you read about data handling or stored preferences.
Definitions are written once and reused across every policy page, which stops a word like balance or withdrawal from changing meaning between two documents.
When one policy page is revised, the related pages are stamped the same day, so the footer dates show the set moved together rather than drifting apart.
Balance and withdrawal clauses carry the same wording here as on the payments page, so the window you read in one place applies in the other.
Contact routes named in these terms point to the same channels shown across the site, so you are never sent to an inbox that has been retired.
Each sibling page opens with a short summary before the strict wording, which keeps the reading experience steady whether you check this document or another policy area.
A single version number covers the whole set, so quoting it in a support message tells the agent exactly which edition of every policy page you are reading.
Legal pages are usually walls of text, so we laid this one out for reading on a phone as well as a desktop. A side index...
A side index follows you as you scroll, so you can jump to account rules, withdrawals or closure in one tap instead of hunting through paragraphs on a phone.
Each heading keeps a fixed number across revisions, so mentioning a specific paragraph in a chat message opens exactly the section you are reading.
Dense paragraphs sit beside a short summary in everyday language; the summary orients you quickly while the numbered clause underneath governs your account.
You can save the document as a file and keep your own copy, giving you a record of the wording that applied when you opened your account.
The page prints without menus or banner images, so a paper copy reads like a contract you can file rather than a screenshot of a busy website.
Every revision shows the date it took effect at the top of its section, so you can tell whether the wording you quoted last month still stands.