The NOC Regulations 2025: Citation, Commencement and Scope

Pakistan’s virtual asset framework runs on more than one document. The Virtual Assets Act sets the statutory backbone; the PVARA No Objection Certificate Regulations 2025 (the “Regulations”) are the subordinate instrument that turns Section 15 of the Act into a working application process. Regulations 1 and 2 — the opening provisions — settle three questions before anything else in the document can apply: what the Regulations are called, when they took effect, and who they bind.

This piece works through those opening provisions in order, then sets out exactly what an NOC permits once PVARA issues one.

When did the PVARA No Objection Certificate Regulations 2025 come into force?

The Regulations state their own commencement rule directly: they take effect on publication. Regulation 1.2 provides that the Regulations “come into force upon their publication on the official website of the Pakistan Virtual Asset Regulatory Authority.” The document header records an effective date of 2 December 2025, which is the date that publication occurred.

There is no separate transition period or phase-in window written into Regulation 1. An applicant preparing a submission after that date is working under the full text of the Regulations from day one, not a partial or interim version of them.

What is the official name of the Regulations?

Regulation 1.1 gives the citation: “These Regulations may be cited as the PVARA No Objection Certificate Regulations 2025 (the ‘Regulations’).” That is the name to use when referencing the instrument in a submission, a board resolution, or a compliance policy — not an informal shorthand like “the NOC rules,” which does not appear anywhere in the operative text.

The document is issued under code PVARA/REG/AML-REG/2025-1, version 1.0 (Final), by PVARA’s Licensing & Supervision Division. Precision on the citation matters in practice: Form A4, the AML/CFT framework submission statement, requires the Applicant’s board to confirm compliance with “the PVARA No Objection Certificate Regulations” by that exact name, and a document that cites the wrong instrument invites an easy rejection on a technicality that had nothing to do with the substance of the application.

Who do the Regulations apply to?

Regulation 2.1 is narrow and specific: “These Regulations apply to all Virtual Asset Service Providers (‘VASPs’) seeking No Objection Certificate under the Virtual Assets Ordinance 2025 (the ‘Ordinance’).” Two things follow from that wording.

• The Regulations bind VASPs specifically — the defined category of businesses providing virtual asset services as set out in the wider Act — not every company that happens to touch crypto in some incidental way.
• The trigger is seeking an NOC. A VASP that has no plan to apply for an NOC, or that intends to operate entirely outside Pakistan’s territorial reach, does not fall within the Regulations’ stated scope on this wording alone.

Regulation 2.1 also introduces a defined term that recurs throughout the rest of the document: “For the purposes of these Regulations, any VASP applying for an NOC shall be referred to as the ‘Applicant.’” Every later obligation in the Regulations — governance, fit and proper standards, AML/CFT framework requirements, ongoing reporting — is written against that single defined term, so reading “Applicant” correctly from the outset avoids misapplying a later clause to the wrong entity.

What does an NOC actually authorise once granted?

Regulation 2.2 is the operative definition, and it grants two distinct permissions in one instrument. It states that PVARA’s issuance of an NOC “required under Section 15 of the Ordinance shall constitute (i) approval for the Applicant’s AML Registration on the goAML portal; and (ii) permission for the Applicant to proceed with incorporation of its local entity in Pakistan.”

What the NOC grants	What it means in practice
Approval for AML Registration on goAML	The Applicant may register as a reporting entity with the Financial Monitoring Unit’s goAML system
Permission to incorporate locally	The Applicant may proceed with SECP incorporation of a Pakistani entity

Neither element is optional or symbolic. AML Registration is the gateway to the four AML-Registered Services described later in the Regulations — broker-dealer, custody, exchange and derivative services — which an Applicant may begin providing before it holds a full VASP licence. Incorporation, in turn, is a precondition Section 15(1) of the Ordinance separately requires before an Applicant can apply for that full licence. In practice, an NOC is best understood as a single decision that unlocks two parallel workstreams rather than one linear step.

Why does the scope of Regulation 2.1 matter for a foreign exchange entering Pakistan?

Because it decides whether a foreign group’s Pakistan entry needs to go through this instrument at all, and in what order. A foreign exchange whose group is “already providing” AML-Registered Services in Pakistan — the language used later in Regulations 11.4 and 17.1(a)(i) — is treated by the Regulations as the entity to be registered on goAML, with the local Pakistani entity only assuming the reporting-entity role once it is incorporated and separately licensed. Regulation 2.1’s application clause is what puts that foreign group inside the Regulations’ reach in the first place, ahead of any local corporate presence existing.

Our reading is that this sequencing — NOC first, AML Registration and incorporation next, full licensing after that — is the “phased regulatory pathway” the Regulations describe as one of their objectives. A foreign applicant planning a Pakistan launch should treat Regulation 2 as the starting gate: nothing else in the document applies until an entity fits the description in Regulation 2.1, and nothing an entity does under the NOC extends further than the two permissions Regulation 2.2 actually grants.

How does an Applicant confirm it falls within scope before submitting?

Regulation 15.1 requires an Applicant to submit its NOC application “using Form A1, as prescribed in Annex A, together with all required documentation.” Section 1 of Form A1 asks for the applicant’s legal name, incorporation details, country of incorporation, and group membership — the information PVARA uses to confirm the entity applying is in fact a VASP seeking an NOC within the meaning of Regulation 2.1, before any assessment of the substance of the application begins.

Confirming scope early matters because Regulation 2.1’s definition of “Applicant” then governs every later reference in the document. An entity that misreads its own status — for example, a group entity that is not itself providing virtual asset services but sits above the operating VASP in a corporate structure — risks submitting a Form A1 in the wrong entity’s name, which Section 4 of the same form would then need to unwind through the Controllers and beneficial-ownership disclosures rather than through the applicant details in Section 1.

This is precisely why Section 1.9 of Form A1 asks a direct threshold question before any substantive assessment begins: “Is the Applicant part of a group of companies?” Where the answer is yes, the form requires the name of the parent entity, its country of incorporation, a brief description of the group’s structure and main business activities, and a Group Structure Chart showing every entity and jurisdiction involved. For a multi-entity group weighing which company within the structure should be the one seeking an NOC, that question is where the scope analysis in Regulation 2.1 gets tested against the group’s actual corporate map, not left as an abstract exercise.

Does an existing VASP relationship with another regulator change how Regulation 2.1 applies?

No — Regulation 2.1 does not carve out an exception for an entity already licensed or registered elsewhere. Section 9 of Form A1 asks separately whether the Applicant or its group entities hold any licence from the State Bank of Pakistan, the Securities and Exchange Commission of Pakistan, or any other Pakistani authority, and whether the Applicant holds any foreign regulatory licence or registration such as a VASP, electronic money institution, securities broker, bank, or money services business licence abroad. Those disclosures inform PVARA’s assessment once an application is under review, but nothing in Regulation 2.1’s wording suggests that holding a foreign VASP licence, or an unrelated Pakistani licence, removes an entity from the scope the Regulation sets. A VASP already licensed in another jurisdiction still falls within Regulation 2.1 the moment it seeks an NOC to operate in or from Pakistan, and still becomes the “Applicant” the rest of the Regulations refer to.

What is not covered by Regulations 1 and 2?

The commencement and scope provisions do not themselves set out fees, forms, assessment timelines or the substantive AML/CFT obligations an Applicant must meet — those appear in later parts of the Regulations, principally Parts 4 through 6 and the accompanying Annex A forms. Regulation 2 also does not define “Virtual Asset Service Provider” itself; that definition sits in the underlying Virtual Assets Act, and the Regulations rely on it rather than restating it. Where a reader needs the precise boundary of what counts as a VASP, the Act — not the NOC Regulations — is the correct source to check.

About this analysis

This analysis was prepared by the CoinConnect research desk from the PVARA No Objection Certificate Regulations 2025, principally Regulations 1.1, 1.2, 2.1 and 2.2, read as published. Where a term or threshold is defined in the wider Virtual Assets Act rather than in this instrument, that is stated in the text above rather than assumed.

Regulatory positions change and specific requirements should be verified against the current position published by the relevant authority before you act on them. This is information and analysis, not legal advice, and it does not create an advisory relationship. Take professional advice on your own circumstances.