Account Opening
The registration page and the eligibility clause both require one account per person, a correct date of birth and a verifiable mobile number. Neither location accepts a correction the other rejects.
LEGAL REFERENCE
Legal Terms Behind Your cg777 Account
Every cg777 account in Pakistan runs on one written rulebook, and this page is where we publish it. Below you will find how we word account terms, how...
Account TermsMarket RulesPolicy Desk
How We State Our Legal Position
cg777 writes its legal position for Pakistan on one principle: you should be able to read the terms before you move money, not after. Where local law permits, we accept accounts from supported regions and apply the same written clauses to each: identity checks, single-account rules, and how a disputed transaction is handled. Where local law does not permit access, we block
registration rather than leave the wording vague. Every amended clause is versioned and dated here, so the copy you agreed to stays reachable. JazzCash, Easypaisa, SadaPay and Raast transfers fall under the payment clause on this page, which also states what happens when a rail is briefly unavailable. If a term reads unclearly, the policy desk answers directly and we amend the
clause rather than lean on the ambiguity.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
EDITORIAL CARE
Who Writes And Checks These Clauses
The terms here are drafted by the team that operates the platform, then read again by people who handle account disputes, payments and customer contact. Nothing is written to fill space: each...
Operator-Written Terms
Clause text is drafted in-house by the people who run cg777 day to day, so the wording reflects how the platform actually behaves rather than how a template says it should.
Independent Clause Checks
Before publication a separate reader tests each clause against real account scenarios: a payment dispute, a failed verification, a dormant account. A sentence that cannot be applied gets rewritten.
Dated Version History
Every amendment carries a revision date and the clause it replaced, so you can see which version applied on the day you accepted the terms and compare it with the current wording.
Payment Rail Accuracy
We check the payment clauses against current JazzCash, Easypaisa, SadaPay and Raast behaviour and correct the wording whenever a rail changes its settlement window or reference format.
Plain English First
Clauses are written in clear English for Pakistan readers, with the binding meaning stated once and the practical outcome spelled out directly underneath so you are not left guessing.
Correction Path
If you find a clause that misstates how the platform works, write to the policy desk. Confirmed errors are corrected, dated, and the change becomes visible on this page.
CLAUSE CONSISTENCY
Where These Terms Match Other Pages
Legal wording only works if it echoes what the rest of the site already tells you. Our account, payments and security pages each describe the same behaviour in their own words, and...
Identity Checks
The security page explains when documents are requested; this clause states that withdrawals may pause until checks complete, and that no document is ever requested through a third-party link.
Payment Rails
JazzCash, Easypaisa, SadaPay and Raast are named identically in both places, with the same accepted-rail list and the same rule that transfers must come from an account in your name.
Withdrawal Wording
The payments page quotes the same processing windows that appear in the settlement clause, including the extra step where a bank or wallet provider adds its own delay outside our control.
Account Security
Two-step sign-in, device confirmation and session timeouts appear as features on the security page and as obligations in the access clause, so the two versions cannot contradict each other.
Closure And Dormancy
If an account stays unused, both pages describe the same sequence: we make contact first, keep the record intact, and only restrict access under the inactivity clause once notice has been given.
Language And Content
Everything published for Pakistan appears in English, and the language clause commits us to telling you before any future change to the languages we support, including which version binds.
What You See On This Clause Page
This page is built to be read, not skimmed past. Each clause sits under a dated heading, chip rows name the local rails a clause refers...
Dated Clause Headings
Each numbered clause carries the day it took effect and a short line explaining what changed, so you can follow one clause across versions without reading the whole page again.
Local Rail Chips
Chip rows name JazzCash, Easypaisa, SadaPay and Raast wherever a clause depends on one of those rails, showing at a glance which part of the page applies to your wallet.
Plain-English Summaries
Longer clauses open with a short summary in ordinary English followed by the binding wording. The summary never replaces the clause, and we state that in the first line.
Amendment Log
A dated list at the foot of the page records every change, the reason for it and the clause affected. Older versions stay readable so a past agreement can still be checked.
Question Thread
The questions below come from queries the policy desk actually received, and each answer is kept to a similar length so no point is quietly played down.
Support Route
Every clause page ends with the same contact paths, so a question raised from any part of the terms reaches the desk that owns that clause rather than a general inbox.
Questions We Get About Our Terms
The clause set is published here with revision dates. Where a clause changed after you accepted it, the earlier version stays readable so you can compare your agreement with the current wording.
We accept accounts from supported regions where local law permits online play. Registration is blocked where it is not permitted, and the eligibility clause says so plainly rather than leaving it to a support reply.
The payment clause states that a transfer must come from an account held in your own name, that the reference is recorded against your account, and that timing depends partly on the provider's window.
Write to the policy desk with the clause number. If the wording is genuinely ambiguous, we amend it and record the change in the amendment log rather than rely on one reading during a dispute.
The termination clause lists the limited grounds we use, including breach of the single-account rule, failed identity checks and use from a region where access is not permitted. Notice is given in writing.
Clauses change when payment rails, regional rules or platform behaviour change. Every amendment is dated on this page, and material changes are also sent to the contact address attached to your account.