Written by Malik Abbas, CEO of CoinConnect
TL;DR
- The PVARA Exchange license authorizes operating a trading venue, order book or matching system — and requires the highest capital tier: PKR 1 billion (~$3.6 million).
- It carries the heaviest conduct load of any category: market surveillance, listing standards, conflicts controls, and a 24-hour settlement-finality rule (Exchange Services Handbook).
- You can list assets without prior PVARA product approval — but you own the listing decision and must publish per-asset risk disclosures.
- Holding customer assets pulls in Custody obligations; offering margin or leverage requires a separate license and explicit approval.
- Cautious entrants can start on reduced capital via a restricted license, then graduate to the full exchange license.
Table of Contents
- What is a PVARA Exchange license?
- Capital and eligibility requirements
- Governance and accountability
- Listing standards — and the "no prior approval" rule
- Market surveillance and abuse prevention
- Settlement and the 24-hour finality rule
- Customer assets and the custody interface
- Margin, leverage and derivatives — a separate license
- Technology resilience and trading controls
- Conflicts of interest and proprietary trading
- Ongoing reporting and obligations
- Common mistakes
- FAQ
What is a PVARA Exchange license?
A PVARA Exchange license authorizes a company to operate a virtual asset trading venue in Pakistan — an order book, matching system, swap facility or similar arrangement. Defined in Regulation 4(1)(c) of the Virtual Asset Services Regulations, 2026, it is the most capital-intensive and heavily regulated license category, requiring PKR 1 billion in minimum paid-up capital.
This is the deep dive on that category. For the full set of ten, see our PVARA license categories overview; for the big picture, the complete licensing guide.
Conversions use an indicative rate of PKR 278 = USD 1 (June 2026).
Capital and eligibility requirements
The exchange license sits at the top of the Schedule I table: PKR 1 billion (~$3.6 million) minimum paid-up capital, held "at all times" under Regulation 31(1). This is share capital inside your Pakistani company, not a fee — see the full capital breakdown.
On top of capital, you must satisfy the general eligibility bars: a Pakistani company (Regulation 5), a resident key individual with real authority (Regulation 10(4)), a resident compliance officer (Regulation 23), and fit-and-proper directors, controllers and a qualified CEO (Regulation 8, Schedule III).
If PKR 1 billion is too much to commit before proving demand, the restricted route applies. PVARA can grant a reduced-capital, limited-scope license under Regulation 7(5), with customer and product caps, and you graduate to the full exchange license later.
Governance and accountability
The Exchange Services Handbook requires a governance structure built specifically around market integrity. Under Handbook section 4, the governing body is responsible for "the oversight of exchange operations, market integrity and compliance," and the exchange must maintain "clear segregation and appropriate independence between trading operations, market surveillance, compliance, risk management and technology functions."
The board must approve and periodically review the trading rules, listing and delisting standards, surveillance arrangements, proprietary trading policies, and conflicts controls. Surveillance cannot report into the trading desk — independence is structural, not optional.
Listing standards — and the "no prior approval" rule
This is one of the most commercially important — and misunderstood — features of the regime.
An exchange may list assets without seeking PVARA's prior product approval. Handbook section 10(1) permits an exchange to "admit or list a Virtual Asset without prior product approval by the Authority" — provided the asset is not restricted by law, meets the exchange's own listing due diligence, and is already globally launched and compliant.
But this freedom comes with full responsibility and transparency. Handbook section 10(2) confirms that any listing notification "shall not constitute approval of the Virtual Asset by the Authority, and the Exchange remains fully responsible for its listing decision." You must publish objective, non-discriminatory listing standards (section 9), and for each listed asset disclose a risk summary including its market cap, circulating supply, smart-contract audit status, and "largest reduction in price from high to low" (section 6(1)(h)).
One hard prohibition: under section 53 of the Act, algorithmic tokens are prohibited — your listing standards must screen them out.
Market surveillance and abuse prevention
An exchange is the front line against market manipulation, and the Handbook treats surveillance as a core function. Section 13 requires "effective market surveillance arrangements to detect, deter and escalate Market Abuse, manipulation and other misconduct" — where market abuse expressly includes "wash trading, spoofing, layering, abusive self-trading" and misuse of non-public information (section 2).
Surveillance must be backed by "adequate staffing, systems, escalation protocols and management oversight." Where the exchange suspects abuse, section 13(6) requires it to "notify the Authority without undue delay." For a foreign exchange, this often means localizing or adapting surveillance tooling to PVARA's reporting expectations.
Settlement and the 24-hour finality rule
Here is a specific, hard obligation many operators miss. The Handbook imposes a settlement deadline. Section 16(6) provides:
"Licenses providing Exchange Services shall complete the final settlement of a Virtual Asset transaction within twenty-four (24) hours of the transaction being executed on their trading venues, subject to any factors outside it's control, including … any limitations or malfunctioning of any DLT not controlled by itself or its Group."
You must also disclose your settlement cycle, the point of finality, and the circumstances in which settlement may be delayed or reversed (section 16(2)). Build your post-trade infrastructure to meet the 24-hour standard from day one.
Customer assets and the custody interface
If your exchange holds customer assets — as most integrated exchanges do — you take on custody obligations. Handbook section 15(1) requires compliance with the safeguarding and segregation rules "and, where applicable, the Custody Services Handbook."
Critically, an exchange license alone does not let you use customer assets. Section 15(2) states the exchange "shall not use, lend, pledge, encumber, rehypothecate, stake or otherwise dispose of Client Assets solely by virtue of its Exchange License" — any such use needs the customer's "prior written, explicit and informed consent." In practice, plan to pair the exchange license with a Custody license.
Margin, leverage and derivatives — a separate license
An exchange cannot offer leverage on the strength of its trading-venue license. Handbook section 19(1) prohibits offering "margin trading, leveraged spot products, futures, options, perpetual contracts … or other derivatives or leveraged products unless the Licensee holds the relevant License Category."
Margin trading specifically requires the Authority's approval, with the exchange submitting its margin agreement, methodologies and collateral standards (section 20). PVARA can also order the exchange to suspend margin services, close positions, or raise margin requirements at its discretion. If leverage is part of your model, budget for the separate Derivatives & Leverage license.
Technology resilience and trading controls
Section 17 requires trading systems that are "resilient," have "sufficient capacity to ensure orderly trading under conditions of high uncertainty and extreme volatility," and can reject erroneous or threshold-breaching orders. You must maintain backup and disaster-recovery sites, and documented procedures for outages, trading halts and resumptions. This sits on top of the general technology and cybersecurity framework (Regulations 58–62) and key/wallet management rules (Regulation 61).
Conflicts of interest and proprietary trading
If the exchange or a group entity trades on the venue, the conflict must be tightly controlled. Section 14 requires policies on "related-party or affiliated listings," "proprietary trading by the Exchange or any group entity," and conflicts affecting "surveillance, listing or disciplinary outcomes." Proprietary trading policies must be board-approved, disclosed to PVARA, and designed to prevent misuse of customer order information.
Ongoing reporting and obligations
Beyond launch, an exchange produces regular management information (trading volumes, surveillance alerts, outages, complaints) for board review, and reports to PVARA on "material breaches," "serious or systemic trading, surveillance, technology or settlement failures," and "significant incidents of suspected Market Abuse" (section 22). General licensee duties continue throughout — maintaining capital, safeguarding assets, AML/CFT, and the rest covered in our post-NOC operational playbook.
Common mistakes
- Budgeting only the PKR 1 billion. Forgetting custody integration, surveillance tooling, technology resilience and add-ons.
- Assuming the exchange license covers leverage. It does not — margin and derivatives need a separate license and approval.
- Treating listing freedom as listing without responsibility. No prior approval still means full accountability and per-asset disclosures.
- Underbuilding settlement. Missing the 24-hour finality rule in post-trade design.
- Using customer assets without explicit consent. A direct breach of Handbook section 15(2).
Get the build right from the start, and the exchange license is workable; treat it as a spot-trading permit with light obligations, and you will fail supervision. To map the full requirement against your model, start with our PVARA licensing service or the foreign-entrant playbook.
Frequently asked questions
PKR 1 billion (~$3.6 million) in minimum paid-up capital under Schedule I, held at all times. This is share capital inside your Pakistani company, not a fee. A reduced figure may be available under a restricted license (Regulation 7(5)).
It can list without prior PVARA product approval (Handbook section 10), provided the asset is lawful, globally launched and meets the exchange's own standards. But the exchange remains fully responsible for the decision, must publish per-asset risk disclosures, and cannot list algorithmic tokens (prohibited under section 53 of the Act).
Within 24 hours of execution, under Handbook section 16(6), subject to factors outside the exchange's control such as third-party DLT malfunctions.
No. Margin, leverage and derivatives require the relevant separate license category and explicit PVARA approval under Handbook sections 19–20.
Yes, but it takes on custody obligations and, where applicable, the Custody Services Handbook. It cannot use, lend or stake customer assets without their prior written, explicit and informed consent.
Yes. A restricted, limited-scope license under Regulation 7(5) lets you operate on reduced capital under caps, then graduate to the full exchange license, with your track record counting in your favor.
Planning a crypto exchange in Pakistan? CoinConnect builds the full exchange-license application — capital plan, surveillance and settlement design, listing standards and custody interface — to PVARA's standard. Book a free 30-minute discovery call →
Last reviewed: June 2026. Based on the draft Pakistan Virtual Asset Services Regulations, 2026 and the Exchange Services Handbook, 2026, published for public consultation. Provisions are subject to change pending finalization.
External sources: PVARA · SECP · State Bank of Pakistan · FATF – Pakistan