Scope
Here we stay with access, verification, and account use. Other policy pages may focus on data handling or platform conduct, but this one stays tied to the rules that shape your legal relationship with us.
We keep this page focused on the legal side of isb 7 so you can see how access, privacy, payments, and account use are handled in supported Pakistan...
Our legal position is simple: access depends on the laws that apply where you are, the details you enter, and the payment route you choose. Before any account action moves ahead, we may ask you to confirm your name, mobile number, and transaction route so our records stay aligned with the rules that apply in supported regions. JazzCash, Easypaisa, SadaPay, and Raast
can each move at a different pace, so the timing you see in your account can vary by rail and by verification step. If local law changes, we adjust the page and the account flow to match what is allowed. That is why we ask you to read the terms each time you return. We do this to keep access and record
handling aligned for you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you want to discuss legal access, account records, or a wording point on this page, we give you direct paths instead of sending you through a maze. Use the contact route that matches your request, share the mobile number on your account if it relates to a record check, and we will route it to the right team. We keep these channels simple so you can reach us from mobile or desktop without extra steps.
Send a written legal query when you need a record trail, a terms question, or a correction request. We use the account details you provide to match the message with the right profile before we reply.
Use the form inside your account when your issue touches verification, access, or a change to the details on file. It keeps the request attached to your profile and speeds up the handoff.
Open chat when you want a quick read on access rules, payment status, or a page wording point. We keep the chat team ready to direct you to the right step without sending you in circles.
Legal pages need more than tidy copy, so we built this one with checks that tie the words to how the account actually works. We keep a clear change trail, use account-level...
We write in short, direct English so you can read the rule once and understand what it means for your account, your region, and the route you use to move money.
When a legal line changes, we keep the prior wording in our internal record and update the live page together with the account step that it affects, so the rule stays consistent.
If a rule depends on your profile, we check the name, mobile number, and route on file before we apply it, which helps prevent mixed messages across support and the page.
JazzCash, Easypaisa, SadaPay, and Raast are treated as separate routes, so any timing or limit wording is tied to the rail you actually choose, not to a blanket assumption.
We only apply access wording where local law permits, and we keep the language broad enough to cover supported regions without pretending that every area has the same rule set.
Each contact path leaves a record that our team can check later, which helps us answer the same legal point the same way whether you ask by chat, form, or email.
This page follows the same legal voice as our other policy pages, but it stays anchored to access rules, account checks, and the way local payment routes affect timing. We keep the...
Here we stay with access, verification, and account use. Other policy pages may focus on data handling or platform conduct, but this one stays tied to the rules that shape your legal relationship with us.
The phrasing is plain and direct across the set, so you do not have to decode different styles on different pages. That makes it easier to match one rule with another when you compare them.
We keep the same supported-region language wherever access depends on local law, so the legal meaning stays aligned even if the practical steps change by country or payment route.
When a page mentions JazzCash, Easypaisa, SadaPay, or Raast, it does so as a legal processing context, not as a separate product pitch. That keeps the rules attached to the right route.
The contact options stay consistent with our other policy pages: short path, clear subject, and a route to the right team. You should not need extra steps to ask a legal question.
If we change a rule here, we change the matching account step and any linked policy text around the same time, so the live flow and the written page do not drift apart.
We keep a record of the version you saw and the request you made, which helps us answer later questions with the same wording instead of relying on memory.
This page is built to read fast on mobile and still stay clear on desktop. You get a stable section order, compact paragraphs, chips for local context, and...