HOME / BUSINESS SERVICES / VIRTUAL ASSETS / PVARA
VIRTUAL ASSETS / PVARA

VASP Continuing Regulatory Compliance and Reporting

Practical PVARA compliance for licensed VASPs: governance, capital, customer assets, AML/CFT/CPF, reporting and supervisory obligations.

PAKISTAN REGULATORY COMPLIANCE GUIDESPVARA
01

Service overview

Continuing compliance is the operating framework that a Pakistan Virtual Asset Regulatory Authority (PVARA) licensee must maintain after its licence is granted. It is not a fresh NOC or licence application. The scope depends on the exact licence categories, limitations and conditions appearing in the licensee’s own instrument, together with the Virtual Assets Act, 2026 and the two final regulations notified on 21 August 2026.

A preliminary approval or no-objection certificate (NOC), a pending application, or sandbox participation is not by itself a commercial licence. A licensee must stay within the categories expressly authorised. A product that combines exchange, custody, transfer, management, lending, derivatives or issuance features may require more than one category; the general Activity-Specific Regulations prohibit using one category to circumvent another.

This guide addresses the common compliance baseline and the main category-dependent overlays. It does not replace the conditions in a particular licence, a written PVARA direction, or the separate chapter governing the service actually performed.

02

Which entities are subject to the continuing regime?

Licensed Pakistani VASP

A company incorporated in Pakistan and holding a current PVARA licence must comply with every category it is authorised to perform, the general Services Regulations, the General Activity-Specific Regulations and each applicable category chapter.

Multi-category licensee

Each additional category brings its own conduct, prudential, custody, reporting and disclosure duties. A licence for one activity is not a general authorisation for the wider virtual-asset business.

NOC holder or sandbox participant

An NOC is preliminary approval to proceed with incorporation and licensing; it is not authority to operate a licensed service. A successful sandbox participant may apply directly for a licence, but completion of testing creates no entitlement to one.

Legacy operator

The six-month transitional application period under section 70 of the Act expired on 5 September 2026. Only a person that submitted a complete application within that period may rely on the statutory continuation provision, subject to interim directions and the core customer-asset and AML/CFT/CPF obligations. PVARA’s licensing page states that transitional operators that missed the deadline must cease the relevant services.

The Act applies to a VASP carrying on, or holding itself out as carrying on, a virtual-asset service in or from Pakistan. The licensing framework requires a Pakistani-incorporated company. Foreign ownership does not remove the need to use the required local legal entity and obtain the relevant PVARA licence. The Act extends to the whole of Pakistan; there is no separate provincial PVARA licence.

Do not assume that every token, payment product or investment arrangement falls exclusively within PVARA. The Act contains exclusions and preserves the jurisdiction of other regulators for matters such as securities, derivatives, collective investment schemes, banking, payment systems and foreign exchange. A tokenised security, pooled investment product or fiat payment leg should be classified on its legal and economic substance, with SECP or SBP engagement where the perimeter overlaps.

03

Records and documents to keep current

There is no single universal annual-compliance form. The working file should let the Board, Compliance Officer, MLRO, auditor and PVARA reconstruct the licence perimeter, financial position, customer-asset position and effectiveness of controls.

  • Licence and ownership: current licence and conditions, variations, incorporation and registered-office evidence, group chart, controllers and beneficial owners, director/Key Individual fit-and-proper records and PVARA approvals.
  • Governance: Board and committee minutes, delegations, conflicts and related-party registers, personal-dealing controls, training records and approved policies.
  • Prudential and financial: paid-up-capital evidence, source of funds, net-liquid-assets calculations, adjusted operating expenses, bank statements, monthly liquidity/funding disclosures, management accounts, statutory statements and audit reports.
  • AML/CFT/CPF: enterprise-wide risk assessment, CDD/beneficial-owner files, source-of-funds evidence, enhanced due diligence, sanctions screening, transaction/wallet monitoring, STR/CTR decisions and Travel Rule data, subject to statutory confidentiality.
  • Customer assets: client agreements, wallet/account mapping, client-money account records, reconciliations, proof-of-reserves evidence, discrepancy investigations, customer statements and explicit consent for any permitted use of client virtual assets.
  • Technology and outsourcing: system inventory, access/key controls, cyber tests, incident logs, business-continuity tests, outsourcing due diligence, risk assessments, agreements, material-outsourcing register and exit plans.
  • Customer, tax and other compliance: disclosures, complaints, product-risk assessments, audit trails, tax and Companies Act filings, and any applicable SBP, SECP, provincial, site, employment or environmental approvals.

Keep records in original or native format where practicable, with a complete audit trail sufficient for supervision, investigations, disputes and regulatory reporting. Apply the longer period where the PVARA rules, AML law, a licence condition or another applicable law requires it.

04

Practical continuing-compliance procedure

  1. 01
    Map products to the licence

    Map each product, customer journey, wallet, fiat leg, outsourcing arrangement and revenue stream to the exact authorised category and conditions. Obtain a variation or additional category before introducing a materially different regulated function.

  2. 02
    Maintain approved governance

    Keep at least three directors and ordinarily one-third independent directors, subject to the express regulatory exceptions. Controllers, sponsors, directors and the Managing Director must satisfy fit-and-proper requirements and obtain required approval before acting. Maintain a registered office, resident Key Individual with operational authority, resident Compliance Officer and competent MLRO with Board access. The regulations describe the Compliance Officer and MLRO separately; confirm with PVARA before combining roles.

  3. 03
    Monitor capital and liquidity

    Maintain the Schedule I paid-up-capital floor for each authorised category and net liquid assets of at least 1.2 times adjusted monthly operating expenses. For multiple categories, PVARA may specify capital methodology and prudential add-ons; the highest applicable liquidity floor generally applies unless an additional non-overlapping risk is identified. Keep current calculations, stress assumptions and evidence of eligible assets, and notify material or anticipated breaches.

  4. 04
    Operate AML/CFT/CPF and Travel Rule controls

    Identify and verify customers and beneficial owners, understand the purpose of the relationship, monitor activity, apply enhanced due diligence to higher-risk relationships and screen for targeted financial sanctions. Review the enterprise-wide AML risk assessment at least annually and after material change. Do not provide services involving privacy-enhancing features where the licensee cannot comply with CDD, monitoring, sanctions and Travel Rule obligations. File STRs promptly when the statutory test is met; do not confuse the CTR threshold with the separate STR duty.

  5. 05
    Safeguard client money and virtual assets

    Segregate client money and place it in designated Client Accounts within the prescribed timeframe. Where client virtual assets are held or controlled, identify and segregate them, reconcile at least daily where daily movements occur, and do not lend, pledge, stake, rehypothecate or otherwise dispose of them except as expressly permitted and with prior explicit written customer consent. Maintain proof-of-reserves and independent validation where the regulations apply.

  6. 06
    Control technology, outsourcing and incidents

    Maintain Board-approved compliance and risk systems, cyber/key-management controls, business continuity and incident response. The licensee remains responsible for outsourced functions. Material outsourcing requires due diligence, risk assessment, written terms, a register, annual review and regulatory notification; prior approval is specifically required for outsourcing a Critical Function. Observe the separate 24-hour cyber-event and 72-hour personal-data incident notification rules.

  7. 07
    File returns and remediate

    Use the form, channel and frequency actually specified by PVARA, the licence and applicable FMU/SBP/SECP requirements. Keep submission acknowledgements and regulator correspondence. Escalate material breaches without delay, submit remedial information within the directed period and update the Board and regulator as required.

05

Reporting calendar and continuing obligations

The notified regulations specify some recurring intervals but leave the frequency and templates for other regulatory returns to PVARA. The following distinctions are important:

RequirementFrequency or triggerWho receives it / qualification
Sources of liquidity and fundingMonthlyDisclose to PVARA under Services Regulations 10(9).
Material related-party transactionsQuarterlyNotify PVARA under regulation 30(3), with supporting documents on request.
Risk reportingAt least quarterlyReport to the Board under regulation 84; more frequently where risk or a material event warrants.
External audit and segregation verificationAnnualExternal audit of financial statements and annual operational audit, including verification of customer-asset segregation.
AML/CFT/CPF risk assessmentAt least annually and after material changeReview enterprise-wide assessment and adjust controls, resourcing and monitoring.
Material cyber event or BCDR activationInitial notice within 24 hours of detection; interim update within 5 Working Days; final report within 30 calendar daysNotify PVARA under regulation 67. The Authority may specify follow-up intervals.
Personal-data incidentWithin 72 hours of awarenessNotify PVARA under regulation 71; staged notice is permitted and a longer period must be justified after an initial notice.
Customer-money statementsAt least monthly for retail clientsApplies where the licensee holds or controls client money.
Client virtual-asset reconciliationAt least daily where daily movements are processedApplies where the licensee holds, controls, safeguards or administers client virtual assets.
Proof of reserves and independent validationSix-monthly; validation report within 30 days after each six-month periodApplies where the licensee holds, controls, safeguards or administers client virtual assets, subject to any earlier PVARA direction.
Material regulatory eventWithout delay or within the specific period directedIncludes material breach, insolvency proceedings, material enforcement matters, cyber/data incident, threats to financial soundness or customer assets.

These intervals are not a complete list of every licence-specific return. Regulation 88 permits PVARA to require financial statements, prudential returns, customer-asset reconciliations, risk and compliance reports and other information in a form, manner and frequency calibrated to the licensee’s scale, complexity and risk profile. It does not create one universal quarterly or annual PVARA return for every category.

For record retention, the final Services Regulations require at least seven years or a longer period required by applicable law. The AML Act separately prescribes five years for transaction and CDD records under section 7C and ten years after reporting for STR/CTR records under section 7(4). PVARA’s public regulatory-framework webpage currently describes a ten-year minimum in general terms; because that webpage is not itself a regulation, the exact legal periods should be applied by record class. A conservative records policy may retain the complete compliance file for ten years pending written PVARA clarification.

R

Fees, forms, portal and regulator-specific reporting

Fees and forms

Services Regulations 11 requires processing, licensing, annual supervisory, renewal and other fees as published in Rules. The notified regulations and the public PVARA regulatory library reviewed for this guide do not provide a verified numerical fee schedule for continuing compliance. Forms I and II contain PKR [x] placeholders for application-stage fees. No fee, challan, PSID, renewal amount or payment channel is invented here. Obtain the current written fee instruction from PVARA before payment.

Form I and Form II are NOC/licensing application forms, not universal periodic-compliance returns. The regulations do not publish one standard annual compliance form for every VASP. Use any category-specific template, return, direction or licence condition actually issued to the licensee.

Portal workflow

PVARA’s public application page confirms online applications, applicant accounts, saved drafts and application tracking for the sandbox, NOC and licence routes. It does not expose the authenticated reporting interface, continuing-return upload sequence, file-size limits, accepted formats or payment screens. Do not assume that the application portal’s public workflow is the reporting workflow. Follow the licensee’s authenticated instructions and obtain written confirmation of the channel, template, signatory and filing deadline for each return.

FMU reporting and the current CTR threshold notice

VASPs are treated as financial institutions for AML Act purposes. STRs must be filed promptly when the statutory suspicion test is met; the CTR threshold does not limit the separate STR obligation. PVARA’s Travel Rule regulation requires originator and beneficiary information for virtual-asset transfers meeting or exceeding the PKR equivalent of USD 1,000, with separate pre-transfer obligations for the ordering VASP and pre-release obligations for the beneficiary VASP.

FMU Circular No. 03 of 2026, dated 11 November 2026, announces PKR 3,000,000 as the minimum CTR reporting threshold with immediate effect. The linked Ministry notification still states that it is “to be published” in the Gazette and displays no SRO number. The circular is the latest official FMU instruction located, but the Gazette publication status was not independently confirmed in the materials reviewed. Treat the circular as the current FMU operational announcement and confirm the Gazette reference with FMU before relying on it as the final statutory notification. A CTR threshold is not a safe harbour for suspicious transactions.

FMU Circular No. 03 of 2025 and its attached Suspicious Transaction and Currency Transaction Reporting Regulations describe goAML reporting, prompt STR filing and a CTR deadline of no later than seven working days. The covering circular says Gazette publication through an SRO was to follow, while the attached copy still shows a blank SRO number. The attachment is an official FMU-issued reporting document, but its final Gazette citation was not located. Confirm the current notified form and deadline with FMU; do not misdescribe the blank-SRO attachment as a Gazette SRO.

SBP banking and cross-regulatory boundary

SBP BPRD Circular Letter No. 10 of 2026 replaced the 2018 prohibition circular. SBP-regulated entities may open accounts for duly PVARA-licensed VASPs subject to verification and due diligence. Where applicable, Client Money Accounts must be separate, PKR-denominated and non-remunerative; cash deposits and withdrawals are not permitted, and CMA balances cannot be used as collateral or security for VASP financing. Banks may open limited-purpose accounts for PVARA NOC holders to complete licensing formalities, but virtual-asset transactional activity is not authorised until the PVARA licence is granted. SBP-regulated entities remain subject to foreign-exchange and other SBP requirements and may not invest, trade or hold virtual assets using their own funds or customer deposits.

The PVARA licence does not itself confer a banking, electronic-money, payment-system, securities, collective-investment or foreign-exchange authorisation. A business that also operates a regulated payment system, deals in securities or offers a pooled investment product must assess the separate SBP/SECP perimeter. Provincial sales tax, labour, environmental, land, building, electricity and local permissions depend on the actual premises, employees, infrastructure and transaction model; there is no single provincial VASP filing.

07

How Chambers can assist

Chambers can map the licence perimeter, prepare a category-specific compliance register, review Board and approved-person arrangements, test capital and liquidity calculations, review AML/CFT/CPF and Travel Rule controls, assess customer-asset segregation, review outsourcing and technology arrangements, and prepare or respond to PVARA, FMU, SBP, SECP and FBR submissions where instructed.

For an initial review, identify the legal entity, each licence category, licence conditions, customer types, custody and fiat-flow model, current reporting calendar and any open regulator correspondence. Do not send private keys, credentials, unredacted identity documents or confidential STR material through an ordinary first-contact channel.

Common questions about VASP continuing compliance

Does an NOC allow a VASP to start commercial operations?

No. An NOC is preliminary approval for incorporation and licensing. It is not a licence to provide virtual-asset services. Only the transitional provision for a person that submitted a complete application within the statutory six-month period may permit continuation of existing services, subject to interim directions and the Act.

Is there one annual PVARA return for every VASP?

The regulations require returns and information in the form, manner and frequency specified by PVARA, with risk-based variation. They do not establish one universal annual return or one standard calendar for every licence category. Follow the actual licence conditions and written reporting instructions.

What is the minimum capital and liquidity requirement?

Minimum paid-up capital ranges from PKR 15 million for Advisory Services to PKR 500 million for Exchange, Lending and Borrowing, Derivatives and Mining-related services. The net-liquid-assets requirement is at least 1.2 times adjusted monthly operating expenses. Multi-category capital methodology and any add-ons must be checked against the licence and PVARA direction.

How long must a VASP keep records?

The final PVARA Services Regulations prescribe a seven-year baseline or a longer period required by applicable law. The AML Act separately requires ten years for records relating to STRs and CTRs, and five years for specified transaction and CDD records. PVARA’s general webpage uses a ten-year summary; the licensee should apply the longer relevant period and seek written clarification where the record class is uncertain.

Are the PVARA fees and online reporting forms publicly available?

The regulations require processing, licensing, annual supervisory and renewal fees as published in Rules, but the current public materials reviewed do not provide a verified numerical fee schedule. The public portal confirms application accounts and tracking, not the authenticated continuing-reporting workflow. Obtain the current fee and reporting instructions from PVARA before filing.

This guide is general information, not advice on a particular VASP, product or transaction. Apply the current Act, notified regulations, licence conditions, regulator directions and applicable federal and provincial laws to the facts. Confirm unpublished forms, fees, portal instructions and case-specific requirements with the competent authority. No regulatory outcome or processing period is guaranteed.