Account terms
The account terms and this page share one definition of an open account, so nothing here contradicts what you agreed to when you registered your details with us.
LEGAL REFERENCE
The Terms That Sit Behind Your Account
One set of written terms covers every account we run: what you agree to when you open an account, how we hold your details, and how withdrawals are...
Account termsJurisdiction rulesData handlingSupport hours
How We Apply These Rules Where Local Law Permits
Our stance is straightforward: we operate in supported regions, and where local law permits, your account runs under the terms published on this page. Access depends on where you are when you sign in, so the same account can behave differently across borders, and we check that at login rather than assume it. If a rule changes in your province, we update
the wording here first and the lobby second. Deposits made with JazzCash, Easypaisa, SadaPay or Raast settle through the banking channels that carry them, and we keep a record of each one. Nothing here changes how your bank treats a transfer; we only set out what we do with the funds once they arrive. That is the whole posture.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
EDITORIAL STANDARDS
How This Page Is Written And Kept Current
Every clause here is drafted by the team that operates the platform, checked against the payment partners we work with, and dated so you can see when it last changed. We don't...
Drafted in-house
Our own staff write these clauses rather than an outside agency, and each version carries the date it went live so you can trace what changed and when.
Matched to real settlement
Before any line about transfers appears, we confirm it against how JazzCash, Easypaisa, SadaPay and Raast actually settle, so the wording on the page reflects live behaviour rather than assumption.
Version history kept
Earlier drafts stay on file after a rewrite, so if a clause you relied on shifts you can open the previous wording and see exactly which line moved.
Plain language pass
Each update gets rewritten into everyday English before it goes live, because a term you cannot follow is a term you cannot hold us to. Short sentences beat sub-clauses.
No invented credentials
You will not find award claims, licence numbers or start dates on this page that we cannot point to a document for on request, and that restraint is deliberate.
Yours to question
If a clause reads wrongly to you, say so before you act on it and we will either explain the intent or correct the wording in the next update.
ACROSS OUR PAGES
How This Page Lines Up With Our Other Policies
Our policy set is built as one group, so the wording here has to agree with the account terms, the privacy page and the cashier rules. Where two pages touch the same...
Privacy page
Data wording on the privacy page matches the handling described here, covering what we store, how long we keep it and who can reach it inside the platform.
Verification steps
Identity checks are described the same way on both pages, including the documents we accept and how long a manual check usually takes to clear during a busy week.
Cashier rules
Withdrawal wording lines up with the cashier pages for JazzCash, Easypaisa, SadaPay and Raast, so the timing you read in one place holds in the other as well.
Fair use clauses
Rules about shared networks and duplicate accounts appear in identical form across the set, so you are not asked to read two competing versions of the same rule.
Complaints path
If a dispute moves between pages, the escalation steps stay the same, and the address you write to is the one published on every policy page we run.
Change notices
When one page is updated, the others that depend on it are checked in the same pass, so definitions cannot drift apart after a single edit goes live.
What Sits On This Policy Page
The layout is deliberate: clause headings you can scan, dates on every revision, and a plain summary before the formal wording begins. Local currency figures sit...
Dated revisions
Every revision carries the date it went live and a one-line reason, so you can tell at a glance whether the clause you read last month still stands.
Plain-language summary
The opening block on each page restates the formal wording in short everyday sentences, which helps when you want the gist before sitting down with the full clause.
Rupee-denominated limits
Thresholds that affect you are shown in rupees first, in figures that match the wording on our cashier pages, so no mental conversion is needed before you compare anything.
Scannable clause indexing
Sections are numbered and linked, meaning you can jump straight to the paragraph a support agent quoted instead of hunting through the whole document on your phone or desktop.
Local timing tables
Each schedule lists Pakistan Standard Time alongside the window it refers to, so you know whether a step lands the same day or the next working morning in your region.
Readable on mobile
Type sizes and tables reflow on a handset, so a clause you open on the commute reads the same way it does on a desktop screen at home.
Questions We Get About Our Terms
Access follows where you are when you sign in, not where you opened the account, so the rules of that supported region govern the session for its duration.
Transaction records are retained for the period our banking partners require, and you can request a summary of your own history from inside your account at any time.
The new wording applies from the date it goes live, and the earlier version stays on file so you can compare exactly what moved before you act on it.
They do. Money sent through JazzCash, Easypaisa, SadaPay or Raast settles under the same account terms, and the cashier wording matches what this page states about timing and records.
You can close an account at any time from your profile. We then stop using your details for anything beyond the record-keeping our partners require us to hold.
Write to our policy desk with the section heading included, and an agent will answer against that wording or correct it in the next revision we publish here.