Terms & Conditions
How you open the account, what you agree to keep accurate, and when we may suspend or close it. Every other policy on this shelf inherits from this parent clause.
Every account you open here runs on one plain set of rules, and this page sets them out. You will see how we confirm who you are, what...
These terms cover every account you hold with us and sit alongside the rules of wherever you are. Access is offered where local law permits, so eligibility turns on your region and on the documents you can produce. Before a first withdrawal we ask for a government-issued ID, a selfie check and proof of address, and we match that name to the
one on your JazzCash, Easypaisa, SadaPay or Raast wallet. Verified payout requests are handled in the order they arrive, and we tell you when a request moves on. If a Pakistani rail is briefly unavailable, your balance is untouched. Nothing here changes what you can already do; it puts the arrangement in writing, in the wording our support team uses.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This page is written by the same team that operates your account, not an outside agency. When a clause changes, the person who edited it signs the wording you read here, and...
The clauses come from the people who run the lobby, the wallet routes and the tables. Nobody outside the business drafts them, so the wording matches how the account behaves.
We settle through names you already use here, JazzCash, Easypaisa, SadaPay and Raast, so your statement stays readable and your bank sees a familiar merchant in supported regions.
Clauses stay short, headings describe what follows, and definitions sit beside the rules that use them. You should settle most questions on one screen without jumping between paragraphs.
Every revision carries the day it took effect and a one-line summary of what moved. Earlier versions stay available on request when a payout you began was governed by them.
Disagree with a decision and you can escalate inside your account, then receive a written outcome with the reasoning attached, naming the rule applied and the date the case closed.
Identity files are encrypted at rest, opened only by the verification staff handling your case, and kept for the period local record-keeping rules require. You may request a copy.
Wording only works when every page agrees with the rest, so we keep the same definitions, payment names and escalation route across the whole shelf. Read the privacy page after this one...
How you open the account, what you agree to keep accurate, and when we may suspend or close it. Every other policy on this shelf inherits from this parent clause.
Which details we collect at sign-up and during payouts, why we hold them, and how long they stay on file. Same definitions, and nothing redefines a term elsewhere.
Timing per rail, minimum amounts, and how we match the wallet name to your registered ID. We list each option in the order most Pakistan accounts clear it.
What counts as one account per person, how shared devices are treated, and the evidence we weigh when a pattern looks automated. Check it before opening a second profile.
Which cookies keep you signed in, which remember your language and currency, and how to clear a session on a shop-counter phone. Settings live in your profile, not a separate tool.
The path from a support message to a formal escalation, with the response windows we hold ourselves to at every stage. Keep the reference number; it follows your case.
Optional caps you set yourself, reminders that flag how long you have been signed in, and a cooling-off period you can switch on without contacting support. All three sit in your profile.
Each policy page follows the same shape so you always know where to look. Headings come first, definitions follow, then the rules themselves, and chips for...
The page title stays pinned as you scroll, so you never lose track of which policy you are reading halfway down a long clause list. A back-to-start tap sits beside it.
Words with a specific meaning get their own bordered block, and those blocks repeat across every policy so one term never carries two meanings. Tap a term to find it again.
Where a rule touches money, the relevant rail appears as a chip: JazzCash, Easypaisa, SadaPay or Raast. Chips are context markers, not extra clauses, and they show which route is meant.
A narrow strip at the foot of each page shows the revision date and one sentence on what moved, so returning readers can spot edits without rereading everything.
Open a query from any policy page and a reference number appears in your profile, linking the clause you were reading to the answer our team sends back.
On a phone the sections collapse into tappable panels, and the body text reflows without side scrolling, which helps when you check a payout rule away from a desk.