Corporate Banking for Crypto VASPs in Pakistan: The Banks That Open Accounts in 2026

On 6 April 2018, the State Bank of Pakistan (SBP) issued BPRD Circular No. 03 of 2018, prohibiting banks, payment system operators, and electronic money institutions from facilitating cryptocurrency transactions. For eight years, this circular kept Pakistan's crypto market formally outside the banking system. Pakistani users continued to trade on global exchanges in volumes industry estimates put between USD 21 billion and USD 25 billion annually — but they did so via informal P2P channels, OTC desks, and hawala-adjacent flows that the formal banking system could not see, regulate, or capture for tax.

On 14 April 2026, that eight-year prohibition formally ended. Following the enactment of the Virtual Assets Act 2026 and the establishment of the Pakistan Virtual Assets Regulatory Authority (PVARA), the SBP issued a new circular permitting regulated entities to open bank accounts for PVARA-licensed Virtual Asset Service Providers (VASPs). The framework is permissive in principle and narrow in practice — only a small number of Pakistani banks have established internal frameworks for crypto VASP onboarding by mid-2026, and the documentation standards demanded by those banks materially exceed the regulator's published minimum.

This article is the operational playbook for the new framework. We cover what the SBP circular actually permits, the two account types (operational and Client Money Account), what banks require beyond the regulator's checklist, which Pakistani banks are active in VASP onboarding by mid-2026, and the specific failure modes that cause most VASPs to stall at this stage. Banking is the single largest cause of post-NOC failure — covered in detail at PVARA-Phase-2-Compliance-Failure — and getting it right is the difference between operating in Pakistan and remaining an NOC holder on paper.

Key Takeaway
April 2026 ended the eight-year crypto banking ban. The new SBP framework is permissive but narrow. Industry intelligence suggests only four to five Pakistani banks have meaningful VASP onboarding capability as of mid-2026. Foreign exchanges that approach banking only after NOC face 90 to 180 days of bank-by-bank shopping with material risk of failed applications.

2. The SBP April 2026 Banking Circular — What It Actually Permits

The April 2026 SBP circular sets out the framework under which Regulated Entities (REs) — meaning banks, MFBs, and payment system operators — may engage with VASPs. The framework is constructed around four operating principles, all of which appear in the circular and shape every banking application that follows.

Principle 1 — Banking access for PVARA-licensed VASPs only
REs may open bank accounts only for entities duly licensed by PVARA as VASPs, or holding NOCs from PVARA pending full licensing. Before onboarding, REs must obtain and retain a copy of the VASP's valid licence (or NOC) and independently verify its authenticity directly with PVARA. This requirement closes the loophole that would otherwise have allowed informally-operating crypto businesses to bank as generic technology companies.

Principle 2 — Strict segregation between client money and operational money
VASPs operating customer-facing services must maintain separate Client Money Accounts (CMAs) for the settlement of authorised transactions on behalf of customers, strictly segregated from the VASP's own operational accounts. The circular is explicit: commingling of VASP funds with customer funds is prohibited. CMAs are non-remunerative (no interest paid) and PKR-denominated. Cash deposits and cash withdrawals are not permitted in CMAs.

Principle 3 — Banks may not invest in or hold crypto
REs are explicitly barred from investing, trading, or holding virtual assets using their own funds or customer deposits. The banking system gains access to crypto firms; it does not gain exposure to crypto assets. This distinction is structural — Pakistan has chosen a model that formalises crypto activity through licensed VASPs without exposing the banking system itself to crypto market risk.

Principle 4 — Ongoing AML/CFT monitoring
REs must monitor relationships with VASPs on an ongoing basis and report any suspicious transactions to the Financial Monitoring Unit in accordance with the Anti-Money Laundering Act 2010 and SBP's AML/CFT/CPF Regulations. The bank's compliance team becomes a second-line oversight on the VASP, in addition to the VASP's own MLRO. This is materially different from generic corporate banking — for VASP relationships, the bank's compliance team gets actively involved in the VASP's AML posture, not just at onboarding but throughout the relationship.

3. The Two Account Types — Operational vs Client Money Account
Every VASP operating in Pakistan needs both account types. Conflating them or trying to operate with only one is a structural misunderstanding of the framework that surfaces during onboarding and stops the application.

Feature	Operational Account (OA)	Client Money Account (CMA)
Purpose	VASP's own operating expenses — salaries, rent, professional fees, utilities, taxes	Settlement of authorised customer transactions on behalf of VASP customers
Currency	PKR (foreign-currency operational accounts available where applicable)	PKR-denominated, non-remunerative (no interest paid)
Cash transactions	Standard corporate banking — cash deposits and withdrawals permitted within KYC limits	Cash deposits and cash withdrawals NOT permitted
Segregation	VASP's own funds — no segregation requirement beyond standard corporate accounting	Strictly segregated from operational accounts and from VASP's own funds
Signatory authority	VASP's authorised signatories under board resolutions	VASP's authorised signatories with independent reconciliation duties
Regulator visibility	Standard SBP reporting	Enhanced SBP and PVARA visibility into transaction patterns
Commingling	N/A	Strictly prohibited — categorical breach if violated

VASPs that only require operational banking — small custody-only services or B2B token issuers without retail customer-facing fund flows — may not need a CMA. VASPs that operate exchange or broker-dealer services with retail Pakistani customers categorically require both. The walkthrough of how the CMA framework integrates with Section 285BAA tax reporting is at tax-banking.

4. What Banks Actually Require Beyond the Regulator's Checklist

The SBP circular is the regulatory minimum. What banks actually require to onboard a VASP, as of mid-2026, materially exceeds this minimum. The gap is where most banking applications fail.

The Bank's Own Correspondent-Bank Pressure

Pakistani banks operating internationally maintain correspondent banking relationships with global banks (Citi, JP Morgan, Standard Chartered, HSBC, Deutsche Bank). Correspondent banks have their own crypto policies — typically much stricter than Pakistan's regulator — and Pakistani banks face de-risking pressure if they onboard crypto clients in ways their correspondents view as exposing the correspondent to AML risk. This pressure is invisible to the VASP applicant but shapes everything the bank requires.

Practical impact: the bank's compliance team applies a documentation standard that satisfies its own correspondent. Generic AML/CFT policy documentation that satisfies PVARA may not satisfy the bank's correspondent. VASPs need policy documentation calibrated to bank-grade standards, not regulator-grade minimums.

The Bank's Internal Crypto Policy Committee

Pakistani banks active in VASP onboarding typically run a dedicated internal crypto policy committee that reviews each VASP application case by case. The committee includes the bank's chief compliance officer, head of correspondent banking, and (in some banks) a representative from the international/foreign-exchange operations team. Approval requires consensus across these functions, and any single hard-no from a committee member typically kills the application.

The Five Concrete Requirements That Trip Up Foreign Exchanges

⦁ Pre-existing relationship at the parent group level — banks strongly prefer to onboard VASPs whose foreign parent has had prior commercial relationship with the bank or with a peer Pakistani bank. Walking in cold post-NOC is materially harder

⦁ Pakistan-based authorized signatory with banking signing authority — verifiable Pakistani residence, valid CNIC or passport with current visa, signing authority granted under the company's board resolutions. Discussed in detail at Resident-Director-PVARA-Pakistan

⦁ AML/CFT documentation at bank-correspondent standard — usually 50 to 80 pages of policy documentation covering KYC, transaction monitoring, sanctions screening, STR escalation, Travel Rule compliance, and PEP handling. Most foreign exchanges' regulator submissions need expansion to satisfy banks

⦁ Independent CMA segregation arrangements — the bank's compliance officer expects to be able to audit segregation independently. Typical arrangements: separate IBAN structure, separate signatories on CMA versus operational accounts, separate reconciliation processes with independent verification

⦁ Source of funds documentation for paid-up capital — full audit trail back to the foreign parent and corresponding SBP foreign-exchange filings under Chapter XX of the Foreign Exchange Manual.

Key Takeaway
The SBP circular sets the regulatory floor. Banks set the operational ceiling. The gap between them is what catches foreign exchanges off guard. Build banking documentation to bank-correspondent standard, not regulator standard, from day one

5. The Pakistani Banks Active in VASP Onboarding (Mid-2026)
By industry intelligence as of May 2026, four to five Pakistani banks have demonstrated genuine willingness to onboard PVARA-NOC and PVARA-licensed VASPs. The list is not static — banks' positions shift with correspondent-banking pressure, board-level risk appetite changes, and the volume of applications they have already absorbed. Verify availability with each bank directly before relying on this list.

Tier 1 — Banks With Established VASP Onboarding Capability

These banks have publicly committed to crypto banking under the new framework, have onboarded at least one PVARA-NOC holder, and have established internal crypto policy committees with documented procedures. Foreign exchanges with strong parent profiles and bank-grade documentation are likely to clear onboarding here in the 90 to 120 day range.

⦁ HBL (Habib Bank Limited) — Pakistan's largest bank by assets, with established correspondent banking relationships and internal crypto policy framework. Selective onboarding — focused on global exchanges with strong compliance histories

⦁ UBL (United Bank Limited) — second-tier large commercial bank with active VASP onboarding posture. Documentation standards aligned with international correspondent banking norms

⦁ Bank Alfalah — mid-tier private bank with strong technology and fintech orientation; among the earlier movers post the April 2026 framework

⦁ Bank Al Habib — conservative-conservative onboarding posture with high documentation bar but stable approval rate for properly prepared applications

Tier 2 — Banks Observing The Framework

These banks have not publicly committed to active VASP onboarding but are not categorically declining. They are observing the first wave of VASP relationships through Tier 1 banks before deciding whether to participate. Foreign exchanges may be able to onboard here as a second-bank relationship after Tier 1 onboarding succeeds.

⦁ Meezan Bank — Pakistan's largest Islamic bank. Sharia-compliant VASP products are a natural fit; Sharia incompatibility flags can stop onboarding for margin/futures-heavy VASPs

⦁ MCB Bank — large commercial bank in observer mode; expected to enter active onboarding once first-cohort experience matures

⦁ Standard Chartered Pakistan — international-affiliate bank with global crypto-banking precedents but cautious Pakistan-specific posture

Tier 3 — banks not currently active

Smaller commercial banks, microfinance banks, and Islamic banks beyond Meezan are largely not active in VASP onboarding as of mid-2026. The compliance overhead, correspondent-bank pressure, and reputational considerations exceed the commercial opportunity at smaller bank scale.

Practical Advice
Apply to Tier 1 banks in parallel — typically 3 of the 4 simultaneously — rather than sequentially. Sequential applications mean each rejection adds 4 to 8 weeks before the next application starts. Parallel applications compress total wall-clock time and provide useful comparative feedback on documentation gaps. Verify each bank's current onboarding posture directly with their corporate banking team before applying — published positions can shift.

6. The 90–180 Day Onboarding Timeline
Realistic VASP banking onboarding timeline is 90 to 180 days from first formal application to fully operational accounts. The variance depends on documentation quality, the bank's current onboarding queue, and the absence of any compliance flags that trigger enhanced due diligence.

Stage	Duration	What Happens
Pre-application discovery	2–4 weeks	Bank corporate banking team meeting, indicative discussion, documentation requirements list
Application submission	1 week	Formal application with full documentation stack (50–80 page AML policy + corporate documents + Source of Funds + Fit & Proper)
First-line review	3–6 weeks	Bank's corporate banking team initial review, identification of gaps, request for supplementary documentation
Compliance committee review	4–8 weeks	Internal crypto policy committee review with cross-functional approval. May involve interview of authorised signatory
Correspondent-bank consultation (where required)	2–6 weeks	For VASPs above certain volume thresholds, the bank consults its correspondent. Material delays possible
Account opening + activation	2–3 weeks	KYC of authorised signatory, mandate letter, account opening, activation of segregation arrangements for CMA
Full operational status	Total 90–180 days from start	Both operational and CMA accounts active and reconciling correctly

Foreign exchanges that compress this timeline below 90 days typically miss steps. Compressing below 60 days is structurally not possible at any well-run Pakistani bank. The 90 to 180 day range is realistic; 120 to 150 days is typical for well-prepared applications.

7. Limited-Purpose Accounts at NOC Stage

The SBP circular includes a useful provision for VASPs at the NOC-but-pre-license stage: banks may open limited-purpose accounts of entities holding NOCs issued by PVARA, enabling them to complete formalities for obtaining a license from PVARA. This is a narrow account type designed for a specific purpose.

What Limited-Purpose Accounts Permit

⦁ Receiving paid-up capital from the foreign parent — supporting SECP incorporation requirements
⦁ Paying SECP filing fees, FBR registration fees, and other government charges
⦁ Paying professional fees to legal counsel, audit firms, and consultants supporting the licensing journey
⦁ Paying salaries to Pakistan-based Key Individuals during the pre-licensing phase

What Limited-Purpose Accounts Do Not Permit

⦁ Customer-facing transactions — limited-purpose accounts cannot operate as Client Money Accounts
⦁ Virtual asset transactions of any kind — the entity remains pre-operational under this account type
⦁ Operational scaling beyond licensing-related expenses

The limited-purpose account provision is structurally important: it gives NOC holders a banking relationship to fund Phase 2 operations without waiting for full licensing. Once full licensing is granted, the bank can extend additional services (including virtual-asset-related transactional activity) subject to strict compliance with the broader VASP banking framework.

Strategic Application
Limited-purpose accounts shorten the practical banking timeline for NOC holders. Apply for a limited-purpose account immediately after NOC grant — the documentation standard is lower than for full VASP banking, and the account establishes the bank relationship before the harder full-onboarding application. Many banks treat the limited-purpose relationship as the runway for the full VASP onboarding decision later.

8. Why Banking Stalls Cause Silent VASP Failures

Banking is the single largest cause of silent VASP failure in Pakistan, and the failure pattern is structurally specific. Unlike incorporation failure (visible immediately) or Fit & Proper failure (PVARA notifies the applicant), banking failures often manifest as slow timelines that gradually consume budget without ever triggering an explicit rejection. This is the silent-failure pattern.

The Slow-No Failure Mode

Banks rarely formally reject VASP applications. Instead, applications stall in compliance committee review for months at a time, with periodic requests for supplementary documentation that never quite close the application. The VASP burns 6 to 9 months and significant operational budget without a definitive answer. By the time the foreign parent realises the bank is effectively saying no without saying so, the Pakistan operation is structurally impaired and the budget overrun is significant.

The Cascade Failure Mode

Without operational banking, the VASP cannot pay salaries to Pakistan-based Key Individuals, cannot pay regulatory fees, cannot fund the entity's working capital. Without a CMA, the VASP cannot transact with customers. Both effects cascade: the absence of banking forces the VASP to operate cross-border (typically through the foreign parent paying Pakistani vendors directly), which itself creates SBP foreign exchange compliance issues and weakens the case for the bank that the entity has genuine local operations.

The Reputational Lock-Out

Once a VASP has been informally declined by a Tier 1 bank, the news travels through Pakistan's compliance community quickly. Other Tier 1 banks become more reluctant to onboard, perceiving correlated risk. A second formal rejection compounds this — the third bank's compliance committee starts from a more cautious posture. Foreign exchanges that approach banking poorly the first time can find their entire Pakistan banking universe effectively closed within 9 to 12 months.

9. The Application Documentation Stack

Successful VASP banking applications require a comprehensive documentation stack. Banks evaluate completeness as much as substance — an application with all sections present and well-structured clears review faster than an application with the same substance presented incompletely.

Corporate Documents

⦁ SECP Certificate of Incorporation
⦁ Memorandum of Association and Articles of Association
⦁ Form 28 (Particulars of Directors and Officers) and Form 29 (Particulars of Charge)
⦁ Board resolutions authorizing the account opening and signatories
⦁ National Tax Number (NTN) certificate
⦁ Registered office address proof (rental agreement plus utility bill)
⦁ Sales tax registration where applicable

Regulatory Clearances

⦁ PVARA NOC certificate (or full VASP license when granted)
⦁ FMU goAML registration confirmation
⦁ SBP foreign exchange repatriable share registration confirmation (where applicable)
⦁ Ministry of Interior security clearance for foreign directors

AML/CFT Policy Documentation (The Longest and Most Scrutinized Section)

⦁ Customer Due Diligence (CDD) policy covering KYC, EDD for high-risk customers, and ongoing monitoring procedures
⦁ Transaction monitoring policy covering rule-based and behavioral monitoring with calibrated thresholds for the Pakistan PKR market
⦁ Sanctions screening procedures covering OFAC, UN, EU, UK, and Pakistan TFS list with documented vendor relationships
⦁ Suspicious Transaction Report (STR) escalation procedures with named MLRO and statutory timelines under AMLA 2010
⦁ Travel Rule implementation procedures with PKR 1 million threshold and originator/beneficiary information capture
⦁ PEP and beneficial ownership procedures including domestic, foreign, and international organization PEPs
⦁ Record retention procedures for the statutory 7-year period
⦁ Internal audit and compliance review schedule

Fit & Proper Supporting Documentation

⦁ Form A3 submissions for Key Individuals, particularly the authorised signatory and MLRO. Detailed walkthrough at Fit-And-Proper-Test-PVARA-Form-A3
Source of funds and capital
⦁ Audited financial statements of the foreign parent (typically last 3 years)
⦁ Capital flow documentation from foreign parent to Pakistani entity
⦁ SBP foreign exchange filings
⦁ Bank confirmations of capital deposit

10. The Five Most Common Banking Application Failures

1. Generic AML/CFT documentation that satisfies PVARA but not the bank's correspondent. Banks reject for inadequate calibration to Pakistan-specific patterns (PKR thresholds, CNIC ingestion, domestic TFS list).

2. Authorized signatory who isn't Pakistan-resident. Banks require KYC of a physically-present signatory. Foreign-only signatory structures stall at the first KYC step.

3. Source of funds documentation that doesn't reach far enough back. Capital flows funded through multi-jurisdiction holding company chains require explanation back to the original capital event, not just the most recent transfer.

4. Customer base profile that triggers correspondent-bank concerns. VASPs with significant exposure to high-risk jurisdictions (sanctioned-country users, multiple jurisdictions with limited AML supervision) face elevated correspondent-bank scrutiny.

5. Sequential application strategy. Approaching one bank at a time, then moving to the next after rejection, creates an 18 to 24 month banking quest. Parallel applications across 3 of the 4 Tier 1 banks compress this materially.

11. Strategies for Multi-Bank Parallel Applications

Multi-bank parallel applications are the single most effective strategy for compressing the banking timeline. Done well, parallel applications convert a 12 to 18 month sequential bank-shopping process into a 4 to 6 month focused effort. Done poorly, parallel applications trigger correlated rejections and reputational damage.

How To Structure Parallel Applications

⦁ Apply to 3 of the 4 Tier 1 banks simultaneously — HBL, UBL, Bank Alfalah, and Bank Al Habib. Reserve the fourth as a fallback if the first three fail

⦁ Use the same documentation stack across all three — banks compare notes informally and inconsistent documentation across applications creates suspicion

⦁ Disclose the parallel applications in advance to each bank — banks expect VASPs to compare options, and proactive disclosure builds credibility

⦁ Engage a Pakistani banking-relationship advisor to coordinate across banks. Foreign exchanges that try to coordinate this themselves often miss subtle cross-bank signals

⦁ Be prepared to commit primary banking to whichever bank approves first — banks expect the relationship not just the formal account. Walking away from an approval that took 4 months damages the relationship for future expansion

What CoinConnect Adds

CoinConnect maintains active relationships with corporate banking teams at all four Tier 1 banks. Parallel applications run through CoinConnect typically clear in 90 to 120 days versus 150 to 180 days for self-managed applications, primarily because the documentation stack is calibrated to each bank's known preferences from the outset rather than discovered during review. Engagement options at services.


Sources Cited
⦁ State Bank of Pakistan VASP Banking Circular, April 2026 (Client Money Account framework). sbp.org.pk.
⦁ SBP Foreign Exchange Manual, Chapter XX (repatriable share registration). sbp.org.pk.
⦁ SBP BPRD Circular No. 03 of 2018 (the original prohibition, formally superseded April 2026). sbp.org.pk.
⦁ Virtual Assets Ordinance 2025 / Virtual Assets Act 2026 (Sections 6, 8, 17). pakistancode.gov.pk.
⦁ PVARA No Objection Certificate Regulations 2025. pvara.gov.pk.
⦁ Anti-Money Laundering Act 2010 and SBP AML/CFT/CPF Regulations. fmu.gov.pk.
⦁ Companies Act 2017 (Sections 153, 154, 460). secp.gov.pk.
⦁ Dawn editorial on the SBP April 2026 circular, April 2026 (cited as commentary). dawn.com.
⦁ Industry intelligence on Pakistani bank onboarding posture as of May 2026 (qualitative assessment based on conversations with corporate banking teams; verify each bank's current posture directly before applying).


Article prepared by CoinConnect's regulatory advisory team. Specific bank names referenced are based on industry intelligence as of May 2026; bank onboarding posture changes over time and direct verification with each bank is recommended before relying on availability for any particular onboarding. Last reviewed against published SBP, PVARA, SECP sources as of 8 May 2026. This article is general analysis and not legal, regulatory, or banking advice.