Shared definitions
Words such as account, verified, supported region and settlement day carry one meaning across every rule page, so a term learned here still applies on the privacy and payments pages too.
LEGAL REFERENCE
The Rules Behind Your salma bet Account
Every clause that governs your salma bet account sits on this page, from how funds move through JazzCash, Easypaisa, SadaPay and Raast to the point where a withdrawal...
Account access rulesJurisdiction wordingJazzCash & EasypaisaRaast payoutsVerification steps
How These Terms Apply Where You Live
salma bet is built for people in Pakistan, yet the clauses on this page do not read identically everywhere. Where local law permits, you can open an account, place wagers and withdraw through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. In supported regions outside Pakistan the same account work applies, though a few details shift: the currency you settle in, the documents we
ask for when you verify, and the timescale we quote for a payout. You are responsible for knowing what your own province or country allows before you register. If one clause cannot be enforced where you live, that clause alone drops away and the remainder of the agreement still stands. We date every change, so you always know which version is current.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
EDITORIAL STANDARDS
Who Writes and Checks This Page
Our compliance and settlements teams draft these clauses together, then a second reader checks the wording against how the platform genuinely behaves: the payout windows we hold to...
Plain wording check
Any clause that needs a legal dictionary gets rewritten, so you can follow the terms without paying someone to interpret...
Dated revisions
Each change on this page carries a date and a short line saying what moved: a payout window, a document...
Behaviour match
Before anything goes live we compare the clause with what our systems actually do, so the page never promises a...
Separate sign-off
A second reader who does not work on the marketing side approves the final text, which keeps promotional pressure out...
Local route awareness
Every payment clause is tested against JazzCash, Easypaisa, SadaPay, NayaPay and Raast thresholds, because a rule that suits one route...
Reader questions
Points that reach support often get folded back into this page, so the wording improves from real queries instead of...
POLICY CONSISTENCY
How This Page Matches Our Other Policies
Nothing on this page should contradict the documents that sit beside it. This one carries access and jurisdiction wording, the privacy page covers your data, and the payments pages handle route-specific rules...
Jurisdiction clause
The where-local-law-permits wording appears in the same form on each document, so a clause lifted for your region is lifted consistently rather than in one place only.
Route naming
JazzCash, Easypaisa, SadaPay, NayaPay and Raast are written the same way wherever they appear, so searching any page lands on the same description of that route.
Contact routing
Support addresses printed here match the ones on the complaints and privacy pages, so you never have to guess which inbox holds a question about your records.
Version dates
Each policy page shows its own revision date, and when a shared definition changes we update every affected document on the same day rather than leaving one behind.
Eligibility wording
Eligibility lines stay identical across the set, so if you cannot hold an account under the rules that apply to you, that answer does not change between pages.
Escalation ladder
A complaint raised under this page follows the same steps described in our complaints terms, so the route from chat to a senior reply never shifts depending on where you started.
Design Choices Behind This Rule Page
We laid this page out for reading on a phone between other things, so the clauses sit in short blocks with the numbers pulled clear of...
Jump anchors
Section links near the heading move you straight to jurisdiction wording, payout windows or support routes, which helps when you are checking a single clause mid-session.
Group tags
Small tags label each group of clauses, so you can see at a glance which block covers access, which covers records, and which covers the dispute route.
Readable figures
Timescales and thresholds are printed as numerals inside the sentence rather than hidden in a table, so a payout window is obvious the moment you reach it.
Phone spacing
Blocks are spaced for a handset screen, which means no sideways scrolling and no zooming to read a clause while you are away from your desk.
Steady order
Sections keep the same sequence every time you return, so the clause you needed last week sits exactly where you left it on the next visit.
Contrast and size
Type runs at a size that stays legible on even the cheaper handsets, and the headings carry enough contrast for the structure to survive bright daylight outdoors.
Answers to Rule Page Questions
In supported regions they do, where local law permits. The account rules work the same, though the currency you settle in and the paperwork we request may differ.
JazzCash, Easypaisa, SadaPay, NayaPay and Raast each appear in the clause that governs settlement on that route, with the timescale we hold to for your account.
If a clause cannot be enforced where you live, that clause alone falls away. The remaining terms still bind your account and still bind us.
We revise it when a payment route shifts, when access rules change, or when a question from support shows a sentence is being misread. Each revision is dated.
We usually write to your registered email first and give you a chance to put things right. Serious or repeated breaches can lead to the account being closed.
Chat from your dashboard is quickest for a short answer, while email suits anything you want in writing. Both routes sit in the support block above.
No. Shared definitions carry the same meaning across documents, so a term explained here keeps that meaning on the privacy and payments pages as well.