Account Terms
The rules on this page match the ones you accept during registration, word for word, so nothing new appears after you have already opened your account.
Every rule that governs your account sits on this page — how we verify who you are, which regions we serve, and what happens when a withdrawal needs...
We publish these terms so you know the ground you stand on before you send a rupee. Access is offered only where local law permits, and supported regions are listed plainly rather than hidden behind a signup wall. Eligibility follows the age and identity rules of the province you register from, and we ask for matching documents when an account opens, not
months later. Money moves through JazzCash, Easypaisa, SadaPay, NayaPay and Raast, so every line on your statement traces back to a rail you already recognise. When a rule changes we update this page and stamp the revision date instead of quietly editing the text. If a clause conflicts with a mandatory local requirement, that requirement applies to your region. Read it once
properly now; it saves an argument later.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Legal questions move faster when they reach the right desk, so we route them deliberately. Chat handles quick clause questions during staffed hours, email creates the dated record you may need later, and document handling stays inside your account area where every upload is logged.
Chat opens from your account dashboard whenever our desk is staffed, and the agent sees your ticket history straight away, so a query about a clause rarely needs repeating.
Send formal notices to our compliance inbox and you get a reference number back, which creates a dated record you can keep for your own files and for any later dispute.
Identity or address documents are uploaded inside your account area rather than by email, so verification files never sit in an inbox. Upload once and the same file covers every later check.
Policy text is only worth reading if you can tell who wrote it and why it changed. We name the team behind each clause, publish a change log...
Each clause carries an owner inside our compliance team, so when you ask why a rule exists, someone can answer...
We keep a visible change log at the foot of the page, listing what moved and when, so a returning...
Clauses are drafted in plain English first and legal phrasing second, with short sentences and no chains of cross-references that...
Before any revision goes live, a Pakistani lawyer checks it against provincial requirements, and conflicting wording is corrected on our...
Our compliance desk answers between 9am and 11pm Pakistan time, seven days a week, with Urdu-speaking agents available when you...
Documents you upload are stored encrypted and shared only with the verification staff handling your file, then archived under a...
This page is not written in isolation. Clause wording is pulled from the same drafting standards used for account terms, cash movement commitments, privacy promises and dispute handling, so a reader moving...
The rules on this page match the ones you accept during registration, word for word, so nothing new appears after you have already opened your account.
Our cash movement wording and this legal page use the same settlement windows, so a withdrawal timeline quoted at signup still holds when you read it here.
Data clauses point to the same retention periods described in our privacy commitments, which means you can cross-check one page against the other without finding a contradiction.
Region eligibility is stated once and reused everywhere, so a supported area listed during signup shows the same status on this page and in support replies.
Account security wording is lifted from the same drafting standards as our security commitments, keeping device rules, login checks and document handling consistent across the site.
Complaint stages run in the same order here as in our service commitments, from an agent reply through to a written escalation, with the same response targets.
English and Urdu wording sit side by side, and both versions follow the same clause numbering, so switching language never changes which rule you are reading at all.
The layout does the quiet work here. Dates sit above the fold, region eligibility reads in a plain panel, and payment rails appear as chips rather...
A revision bar sits under the headline and shows the last date the wording changed, so you can tell at a glance whether anything moved since you last opened this page.
The region panel lists supported areas in plain text, without forcing you through a signup wall, and it is the same list support agents read from.
A chip row names JazzCash, Easypaisa, SadaPay, NayaPay and Raast so you can see which rails the clauses refer to before you read the detail underneath.
Every clause carries a stable number, so when you write to us you can quote one figure and the agent opens the exact paragraph you mean.
A contact block closes the page with the same channels listed higher up, and it repeats our compliance desk hours so you are not left guessing when a reply arrives.
A language switch sits in the corner and reloads the page in Urdu with identical clause numbers, useful when you want a relative to read the same rule.