Pakistan payment entity investigation
Easypaisa Bank is regulated; a casino asking for Easypaisa is not thereby authorised
SBP granted Easypaisa Bank Limited a digital retail bank licence and scheduled-bank status, but that institutional fact does not validate a casino domain, merchant, personal recipient or gambling transaction.
The exact entity finding
State Bank of Pakistan notification BPRD (B&DBD)/000495/2025 states that, after granting a Digital Retail Bank licence, Easypaisa Bank Limited became a scheduled bank with effect from 23 January 2025. The current SBP bank register provides a second institution-level check. This is stronger than relying on an app-store badge, advertisement or copied logo because it identifies the regulated bank in a Pakistan authority record.
The finding is still narrow. It does not name a casino, approve a payment purpose or say that every account displaying an Easypaisa label belongs to the bank. The bank’s status and the recipient’s status are separate propositions. A casino that accepts or requests Easypaisa must still be resolved to its exact domain, legal operator, claimed gambling licence and Pakistan-facing conduct. The initial casino trend list does not provide that chain.
Legal and licensing boundaries
A digital retail bank licence authorises banking within its stated regulatory scope. It is not a gambling licence and cannot be borrowed by a merchant. If a casino page says “licensed because Easypaisa is available,” the reasoning is invalid. The evidence that supports Easypaisa Bank’s status proves no Pakistan casino authorisation. Likewise, a foreign casino licence—if genuinely matched—would answer only the foreign regulator’s scope unless separate Pakistan evidence says more.
Pakistan’s SECP surrogate-company direction warns against business and advertising relationships involving surrogate betting companies. It provides relevant local risk context but is not a finding against Easypaisa Bank. Use it to challenge promotional shortcuts, not to accuse the payment institution. An entity page must keep those lines visible to avoid turning public regulation into an invented complaint.
Recipient checks before a deposit
Do not transfer from a chat instruction alone. Record the full hostname, the payment screen’s beneficiary name, mobile or account identifier, amount, currency and reason given. If the beneficiary is a private person or unrelated business, ask how it connects to the operator. Repeatedly changing recipients, requests to split deposits, instructions to hide the purpose, pressure to pay immediately, or an extra fee to “activate” withdrawals are warning signs. None proves fraud by itself, but together they increase uncertainty and weaken recovery evidence.
Open Easypaisa through a trusted route. Confirm the recipient on the final authorisation screen. Do not follow a shortened payment link sent by an unverified casino representative. Never disclose an OTP, PIN, password, biometric sample or screen-sharing code. Keep the payment receipt and statement; a cropped success image without reference and date is weaker evidence.
Casino withdrawals to Easypaisa
A withdrawal dispute has at least two records. The operator record should show the request amount, request date, destination, status changes and any reason for delay. The bank record should show whether an incoming transfer was credited, rejected, reversed or never presented. Do not treat “processed” or “approved” in a casino interface as proof that Easypaisa Bank received settlement instructions. Ask for a payment reference that the bank can assess.
Do not pay a second transfer merely because someone says the withdrawal needs tax, KYC release, anti-money-laundering clearance, insurance or a larger deposit. Real obligations require a verifiable legal and contractual basis. Preserve the request and ask the bank or appropriate authority through an independently reached channel. This investigation found no sufficiently verified named-player complaint to publish as a factual case study, so it provides a process rather than a complaint count.
KYC and a blocked Easypaisa account
SBP’s consolidated 2026 customer-onboarding framework establishes current identification and biometric-verification context for regulated institutions. A bank may need to verify identity, account ownership, transaction purpose or risk signals. A restriction after a casino-related payment is therefore not self-explanatory. It may concern KYC, security, law, transaction monitoring or another cause. Only Easypaisa Bank can state the reason for a particular account.
Ask for the restriction category, complaint reference, documents required, secure submission method and next review point. Keep dates and copies. Do not upload full identity records to a casino chat in an attempt to unlock a wallet. If an unsolicited caller offers to unblock the account in exchange for an OTP or transfer, end the contact and reach the bank independently.
Complaint and escalation route
SBP consumer-protection guidance starts with the bank. Easypaisa’s current first-party contact record lists complaint categories covering account, fraud, cash withdrawal, transfer, Raast and merchant issues, and it points to the SBP Sunwai portal. Use a trusted copy of the bank’s app or address, not a contact supplied by the disputed recipient. Obtain a complaint number and describe one issue at a time.
If the bank does not resolve the matter, use the current official escalation route that fits a scheduled bank and the type and timing of complaint. Banking Mohtasib jurisdiction and procedural requirements should be checked directly. Suspected cybercrime facts may also be reported to NCCIA; unlawful online content can be reported through PTA’s content system. Those are parallel evidence routes, not guaranteed refund services.
Clone and impersonation checks
“Easy Paisa,” “Easypaisa support” and similar labels can be copied into a domain, social profile, QR image or caller name. The SECP’s unauthorised-activities material has previously shown why similar-looking financial names can cause confusion; a name resembling a regulated institution is not enough. Compare the full hostname, certificate context, app publisher and contact route. Do not install an APK sent through messaging.
Preserve the clone without interacting more than necessary: capture the complete URL, time, payment demand, recipient and profile. Do not publish your full CNIC or receipt. A recovery service that promises guaranteed funds for an advance fee is a new entity and must be checked separately. Never assume it represents Easypaisa Bank, SBP, police or the casino.
Evidence table for an Easypaisa dispute
| Item | Use | Limit |
|---|---|---|
| SBP bank notification and register | Confirms Easypaisa Bank Limited’s Pakistan status | Does not approve a casino recipient |
| Full casino hostname | Fixes the online identity | A brand string alone cannot establish operator identity |
| Beneficiary confirmation and transaction reference | Shows intended recipient, amount and payment event | Does not prove gambling legality |
| Withdrawal request and bank statement | Lets the two payment legs be compared | Neither alone proves where a failure occurred |
| Complaint number and replies | Shows procedural history and timing | Does not guarantee a result |
Store originals privately, prepare a redacted copy, and record any missing evidence. The strongest packet is chronological and distinguishes what you saw from what a casino or caller merely asserted.

Dated official evidence
The source set gives priority to SBP status, KYC and complaint records; first-party bank material is labelled and is never used as independent proof of a casino.
| Source | Authority | What it supports | Accessed | Open source |
|---|---|---|---|---|
| PK-S07 Consumer Protection | State Bank of Pakistan | bank complaint handling and Banking Mohtasib escalation | 2026-08-09 | Open source |
| PK-S08 Sunwai Customer Complaint Portal | State Bank of Pakistan | general banking complaint route | 2026-08-09 | Open source |
| PK-S09 Digital banking security FAQs | State Bank of Pakistan | fraud dispute handling and interbank coordination | 2026-08-09 | Open source |
| PK-S16 Commercial Banks and Digital Banks | State Bank of Pakistan | Easypaisa Bank Limited identity and digital-bank status | 2026-08-13 | Open source |
| PK-S17 Collection of digital banking fraud information through call centres | State Bank of Pakistan | urgent channel blocking and institution guidance after suspected fraud | 2026-08-13 | Open source |
| PK-S18 Consolidated Customer Onboarding Framework 2026 | State Bank of Pakistan | current KYC and biometric-verification framework | 2026-08-13 | Open source |
| PK-S24 Easypaisa Bank scheduled-bank notification | State Bank of Pakistan | Easypaisa Bank Limited digital retail bank licence and scheduled-bank status from 23 January 2025 | 2026-08-13 | Open source |
| PK-S25 Easypaisa complaint channels | Easypaisa Bank Limited | institution complaint categories contact channels and Sunwai escalation | 2026-08-13 | Local source record |
| PK-S26 Easypaisa account and transfer FAQs | Easypaisa Bank Limited | account transfer and institution-help scope | 2026-08-13 | Local source record |
Frequently asked questions
Is Easypaisa Bank licensed in Pakistan?
Yes. The reviewed SBP notification records a digital retail bank licence and scheduled-bank status effective 23 January 2025.
Does that make an Easypaisa casino payment legal?
No. Bank authorisation and a casino recipient’s legal status are separate questions.
How do I investigate a missing casino withdrawal?
Preserve the casino request and Easypaisa statement, request a traceable transfer reference and avoid any extra release or recovery fee.
Why did Easypaisa block or restrict my account?
KYC, security, legal or transaction controls may be involved. Only the bank can provide the individual reason and required next step.
Where does an Easypaisa complaint start?
Start with Easypaisa Bank through a trusted channel, get a complaint number, then check the current official escalation route if unresolved.
How do I spot fake Easypaisa support?
Check the complete hostname and app publisher independently, reject unsolicited OTP or PIN requests, and do not install messaging-app APK files.
Found a factual error or have first-party evidence? Use the documented correction and response route.