Shared Definitions
Words such as account, wallet and settlement mean the same thing on every policy page we publish, so you never have to guess whether a term shifts meaning between them.
Every account on ace555 runs on written terms you can read in full before you register. Open your account, then keep these pages close — they set out...
ace555 publishes policy wording that applies where local law permits, and we adjust individual clauses for supported regions. Nothing on this page overrides the terms you accept when you open an account. Where a rule differs between markets, the version shown at registration governs your JazzCash, Easypaisa, SadaPay or Raast activity. We keep the wording plain: what you can expect from us,
what we expect from you, and how a disagreement gets settled. If a clause changes, the updated text replaces the old one from the date printed in the header strip. You can always ask our desk to explain a clause in simpler words before you accept it. Pakistani account holders reading this in Urdu or English hold the same protections either way.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
When a clause reads oddly, ask us before you act on it. Our desk answers policy questions in English and Urdu, explains which rule applies to your account, and tells you what happens next. Keep your ticket number — it links every reply to the same case.
Chat opens from the help button inside your account and routes straight to a policy agent. First replies land within minutes during Pakistani evening hours, and the transcript is emailed to you.
Send longer questions about terms, closures or contested play to our support inbox. Attach screenshots of the transaction, and we reply with the clause we applied and why.
If a first reply does not settle the matter, ask for escalation. A senior assessor re-reads the clause, your account history and any evidence, then writes back with a final position.
These pages are written and kept by the same desk that runs account operations, so the wording matches what actually happens on the platform. We date each revision, log what changed, and...
Policy pages carry the internal desk that drafted them rather than a generic byline. That desk answers for the wording, handles your follow-ups and signs off every revision before it goes live.
Every clause block shows the date it took effect. Older versions stay archived so you can compare what you accepted at registration against the wording that applies to your account today.
Before publication each section is rewritten until a reader with no legal training can follow it. Where a technical term is unavoidable, we define it in the same paragraph.
Wording is checked against how JazzCash, Easypaisa, SadaPay and Raast actually settle transactions in Pakistan. If a banking rule shifts, the clause about it is edited to match.
We do not change a clause and pretend it always read that way. Substantive edits are listed with dates, and anything that alters your obligations is flagged in the header strip.
Spot an inconsistency between two sections? Write to the desk and we reconcile them. Corrections are published, and the reader who raised the issue gets the credit.
Our policy pages are meant to be read together. The terms page, the privacy page and this legal page share definitions, revision dates and a dispute route, so a term you learn...
Words such as account, wallet and settlement mean the same thing on every policy page we publish, so you never have to guess whether a term shifts meaning between them.
Policy pages update on a single schedule. When a release goes out, the dates in each page header move together, so you can tell whether the wording you are reading is current.
Complaints follow one path whichever page raised them. Chat, email and escalation land on the same case file, and replies quote the clause you questioned by its section heading.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are named and described the same way wherever they appear, so clearing times quoted on one page match what the next page states.
Support hours, channels and response windows are written once and reused everywhere. If those numbers change, every page carrying them is republished together rather than left to drift apart.
Access wording uses the same test across pages: what we offer where local law permits, and what stays restricted in supported regions. No page contradicts another on eligibility for your account.
Where one policy depends on another, we link the exact section instead of repeating it. That keeps a single source of truth and stops two versions of one rule sitting side by side.
This page keeps its structure predictable on purpose. Headings sit in a fixed order, clause numbers stay stable between releases, and a short strip in the...
A fixed index follows you down the page on desktop and rests under the header on mobile, so you can jump to account rules, play rules or dispute steps without scrolling back.
Revisions appear in a short strip in the header. It names the clause that moved and the date it took effect, so you can skip straight to what affects your account.
Each dense clause opens with a two-line summary in ordinary English. Read the summary first, then drop into the full wording only when you need the precise obligation spelled out.
Clauses that apply in only some markets carry a visible region tag. You can see at once whether a rule about JazzCash or Raast settlement touches the account you hold.
A print view strips the navigation and keeps clause numbering intact, useful when you want to save the wording you accepted at registration alongside your own records.
The toggle switches the page between English and Urdu without losing your place. Both versions carry matching clause numbers, so you can compare them line by line.