What the PVARA regulatory sandbox does
The Pakistan Virtual Assets Regulatory Authority (PVARA) describes its regulatory sandbox as a route for testing an innovative virtual-asset product or service under supervision before the applicant seeks a full VASP licence. The legal foundation is section 35 of the Virtual Assets Act, 2026. It authorises PVARA to establish a controlled testing environment for innovative virtual-asset products or services and contemplates rules for eligibility, application procedure, supervision, risk limits, duration and exit.
A sandbox admission is not a general operating licence. PVARA's published licensing pathway separates application, admission, controlled testing within agreed scope and customer limits, exit assessment, and a later VASP licence. The permission is confined to the test that PVARA approves. It does not authorise an applicant to offer unrelated virtual-asset services, expand to unrestricted customers or treat a pilot as a commercial launch.
The Act commenced on 5 March 2026. PVARA subsequently notified the Pakistan Virtual Asset Services Regulations, 2026 (S.R.O. 1419(I)/2026) and the Pakistan Virtual Asset Services Activity-Specific Regulations, 2026 (S.R.O. 1420(I)/2026) on 21 August 2026. These are final Gazette instruments, not consultation drafts. The Act and notified regulations prevail over inconsistent guidance.
Choose the correct regulatory route
Consider the sandbox where the proposal is genuinely innovative and the objective is to test a defined product or service under PVARA's supervision. The public licensing page identifies the sandbox as Track A.
The ordinary route is NOC, Pakistani incorporation and a licence for each required category. Section 19 of the Act and regulations 6–7 of S.R.O. 1419 govern this route. A sandbox participant that successfully completes testing may use the direct-licence route in regulation 7(6).
Do not assume a sandbox application replaces a licence variation. Regulation 12 of S.R.O. 1419 addresses adding or removing categories and varying licence conditions. Obtain PVARA's written classification where the proposed test changes the approved business or product scope.
Section 70 and regulation 5A contain transitional rules. PVARA currently states that transitional persons had to submit an NOC application by 5 September 2026 or cease operations. That date has passed. A later sandbox application should not be treated as retrospective permission or a cure for missed transitional requirements; obtain written PVARA directions before any activity.
Foreign and non-local applicants. Section 35 does not itself set out a complete applicant-form eligibility test. The detailed criteria are left to the regulatory framework and PVARA's sandbox guidance. Do not assume that a foreign company, individual, offshore affiliate or local subsidiary is automatically eligible. Confirm the applicant entity and ownership structure with PVARA before incurring incorporation or pilot costs. For a full VASP licence, section 50 of the Act and regulation 5(1) of S.R.O. 1419 require a company incorporated in Pakistan.
Test the regulatory perimeter before preparing the application
Describe the product by what it does, not by its marketing label. The Act applies to VASPs carrying on, or holding themselves out as carrying on, virtual-asset services in or from Pakistan and to issuers offering, originating or distributing virtual assets in or from Pakistan. Schedule I includes advisory, broker-dealer, custody, exchange, lending and borrowing, derivatives, management and investment, transfer and settlement, issuance and mining-related categories.
Some products may fall outside the Virtual Assets Act or within another regulator's mandate. Section 2(2) excludes, subject to its stated conditions, closed-loop tokens, traditional securities and other financial instruments falling within SBP or SECP jurisdiction, certain central-bank digital currency representations and specified NFTs or digital collectibles. The closed-loop exclusion is conditional: the token must remain within the restricted ecosystem and satisfy all statutory conditions. It is not enough that the issuer calls a token a loyalty point.
Where the product represents a security, derivative, collective investment scheme, depositary receipt, payment instrument or regulated financial asset, obtain a reasoned perimeter assessment and engage the relevant regulator. Sections 9 and 17 provide for PVARA's classification and inter-agency cooperation. A PVARA sandbox letter should not be represented as an SBP, SECP, exchange, payment-system, foreign-exchange or other statutory approval unless the relevant authority has separately granted it.
The Services Regulations also restrict virtual assets from being used as a means of payment for domestic commercial transactions unless SBP specifically approves under section 9(1)(f) of the Act. A proposed remittance, merchant-payment, stablecoin or fiat on/off-ramp test therefore needs a clear description of the fiat leg, participating banks, payment rails and foreign-exchange flow. PVARA's Advisory PVARA/ADV/001/2026 says that pilots or agreements that result in, or directly enable, virtual-asset services require prior PVARA authorisation.
Eligibility, documents and the working application dossier
Section 35(2) of the Act leaves detailed eligibility, application procedure, supervisory arrangements, risk limits, duration and exit requirements to regulations. The public PVARA regulatory library links an official document titled Incubation Guidelines for Participating in PVARA's Regulatory Sandbox Program. The Services Regulations also contain a saving provision for earlier sandbox guidelines and permissions, but only to the extent they are consistent with the Act and the current regulations. The Act's general savings clause must be read in the same way: it does not allow a guideline to override a later Act or Gazette regulation.
The detailed sandbox form, annexures, documentary checklist and any eligibility exclusions should be taken from the current official guideline and the applicant's written instructions from PVARA. They are not reproduced as a complete sandbox checklist in S.R.O. 1419 or S.R.O. 1420. In particular, the Form I attached to regulation 6 of S.R.O. 1419 is the NOC application for incorporation; Form II is used for the subsequent VASP licence application. Neither should be substituted for a sandbox form unless PVARA's current sandbox guidance expressly directs that result.
As a practical preparation exercise, assemble a controlled testing dossier that explains:
- the product, service, target users, jurisdictions and the specific regulatory question that the test is intended to answer;
- the end-to-end flow of virtual assets, fiat funds, wallets, private keys, counterparties, banks, custodians and technology providers;
- the proposed test population, duration requested, transaction and exposure limits, and the controls that will prevent activity outside the approved perimeter;
- ownership, governance, funding, responsible officers, conflicts, outsourced functions and the persons accountable for the test;
- customer eligibility, disclosures, consent, complaints, safeguarding, reconciliation, withdrawal and loss-management arrangements;
- AML/CFT/CPF, sanctions screening, transaction monitoring, recordkeeping, incident response, cybersecurity, data protection and business continuity; and
- success measures, reporting data, exit criteria, customer communications and an orderly wind-down or transition plan.
This is a recommended working dossier, not a representation that every item is a prescribed form field or that the list is exhaustive. The current PVARA guideline, the live application instructions and the written approval determine the mandatory submission requirements for the particular applicant.
Submission and PVARA portal workflow
- Obtain the current primary material. Start with PVARA's Regulatory Guidelines library and download the sandbox guideline directly from the Authority. Check the document version, any amendments, notices or written directions, and whether the document is consistent with the 2026 Act and S.R.O. 1419.
- Seek early perimeter confirmation. Send PVARA a concise description of the product, customer and funds flow, proposed test, other regulators involved and the reason the sandbox is appropriate. The Authority's April 2026 advisory expressly encourages early engagement for virtual-asset pilots, stablecoin use cases, allied blockchain solutions and tokenisation structures.
- Create an applicant account. The official PVARA application portal says applicants can submit and track applications online, create an applicant account, save a draft and return later. The public page does not expose the authenticated sandbox fields, upload sequence, file limits or payment screens.
- Use the current sandbox application material. Complete the form and annexures specified by the current sandbox guideline and portal. Do not copy a third-party form, use an old Ordinance-era template without checking it, or treat the NOC Form I as the sandbox application merely because both processes concern virtual-asset regulation.
- Retain the submission record. Keep the submitted version, attachments, acknowledgement, correspondence, requests for information, fee evidence (if applicable), and every revised version. Record which entity and persons are responsible for responding to PVARA.
- Wait for written admission and conditions. Filing an application, receiving an acknowledgement or discussing the proposal with PVARA does not authorise testing. Commence only after the Authority issues the written approval or other permission that identifies the approved test and its conditions.
PVARA's public licensing page describes the sequence as Sandbox Application, Admission, Controlled Testing, Sandbox Exit and then VASP Licence. It does not publish the authenticated application screens or a universal checklist on the public page. Confirm those details through the live portal and PVARA before filing.
Operate only within the approved test and complete the exit process
The written sandbox approval should be treated as the boundary of the permission. Map every approved feature to the product build, users, counterparties, wallets, transaction flows and controls. PVARA's public pathway says testing is confined to the agreed scope, duration and customer limits and that participants must meet reporting, safeguarding and disclosure requirements throughout the test. A change in asset, customer group, geography, transaction type, custody model, payment rail or third-party provider should be escalated to PVARA before implementation where it may exceed the approved perimeter.
Maintain evidence that the test remained controlled: customer onboarding and consent records, test transactions, wallet and fiat reconciliations, security testing, incident logs, complaints, control exceptions, monitoring outputs, regulator reports and decisions to pause or restrict activity. Do not assume that a sandbox participant is exempt from generally applicable Pakistani law. Section 5 of the Act preserves the operation of other laws; the applicable AML, sanctions, tax, foreign-exchange, data, consumer, company and payment-system requirements must be assessed for the actual test.
The Act and the final Services Regulations do not state a universal customer cap, transaction limit, sandbox duration or standard reporting frequency for every participant. Those parameters must be checked in the current official guideline and, critically, in the participant's written approval. Do not import a number from a news article, an earlier draft or another participant's letter.
At exit, follow the written criteria and timetable in the approval. PVARA's public pathway contemplates completion of testing, an exit assessment and either a move to full licensing or cessation of the test. A successful test is not itself a licence. Under regulation 7(6) of S.R.O. 1419, a participant that completes testing to PVARA's satisfaction may apply directly for a VASP licence without a separate NOC. The Authority may consider test outcomes and compliance history, but the applicant must still meet every applicable licence-category requirement. The provision creates a route to apply, not an entitlement to approval.
Fees, timelines and points requiring written confirmation
The Act recognises that PVARA's Fund may receive charges for services including sandbox participation (section 14(2)(j)), but that provision does not state a fee amount. No numeric sandbox application or participation fee is quoted here. Obtain the current fee, payment reference and payment method from the Authority or the authenticated portal before filing. Do not assume that sandbox participation is free.
Section 35 and the two final Gazette SROs do not state a universal sandbox decision period or test duration. The 60-day period in regulation 6(3) concerns a complete NOC application; the 90-day period in regulation 7(3), with a possible 60-day extension, concerns a complete licence application. Neither is a sandbox processing deadline. If the current sandbox guideline states a target period, confirm the operative version and the event from which its clock runs before planning a launch.
Before submission, obtain written confirmation of the applicant's eligibility and legal form, the current form and annexures, the required documents, fee and payment route, assessment timetable, any permitted resubmissions, the proposed test limits and duration, reporting frequency, incident-notification rules, extension procedure and exit deliverables. These are not treated as verified merely because a third-party article or an earlier draft describes them.
Official primary sources
- Virtual Assets Act, 2026 (Act XIII of 2026) — sections 1, 2, 5, 9, 14, 17, 19, 35, 50, 70 and 74.
- Pakistan Virtual Asset Services Regulations, 2026 (S.R.O. 1419(I)/2026) — regulations 3, 5, 5A, 6, 7 and 10.
- Pakistan Virtual Asset Services Activity-Specific Regulations, 2026 (S.R.O. 1420(I)/2026) — general activity perimeter and cross-category controls. The instrument does not contain a separate sandbox application chapter.
- PVARA Regulatory Guidelines library and the official Sandbox Guidelines DOCX.
- PVARA licensing framework and sandbox pathway; PVARA application portal; and PVARA FAQ.
- PVARA/ADV/001/2026, Advisory on Virtual Asset-Related Announcements and Activities.
The Act and Gazette regulations control in the event of inconsistency. The public guideline and portal should be checked again immediately before filing because PVARA may update its operational instructions or issue applicant-specific conditions.
Frequently asked questions
Does sandbox admission permit a commercial launch?
No. It permits only the controlled test described in PVARA's written approval. Commercial VASP activity requires the relevant licence or other express authorisation. Section 50 of the Act prohibits unlicensed virtual-asset services.
Does a successful sandbox participant need a separate NOC?
No separate NOC is required where the participant has successfully completed testing to PVARA's satisfaction. Regulation 7(6) allows a direct licence application, but the participant must still satisfy all applicable licence requirements and PVARA may refuse the application.
What is the sandbox fee and how long does approval take?
The Act recognises charges for sandbox participation but does not set a numeric amount. The Act and final Services Regulations do not set a universal sandbox decision period. Confirm the current fee and any target period in the official guideline, portal or written PVARA instructions.
Can a foreign company apply without incorporating in Pakistan?
The detailed sandbox eligibility test must be checked in the current PVARA guideline and confirmed with the Authority. The full VASP licence route requires a company incorporated in Pakistan under section 50 of the Act and regulation 5(1) of the Services Regulations. Do not assume sandbox eligibility settles the later incorporation requirement.
Can an existing operator use the sandbox to regularise past unlicensed activity?
Do not assume so. Existing providers are subject to the transitional provisions in section 70 and regulation 5A. PVARA states the transitional NOC deadline was 5 September 2026. Obtain written directions from PVARA before continuing or restarting any activity.
This guide is general information, not advice on a particular product or applicant. It deliberately does not state unverified sandbox eligibility criteria, forms, resubmission limits, testing periods, customer caps, reporting deadlines or fee amounts. Obtain the current official Sandbox Guidelines and written PVARA conditions before filing or commencing any test. No approval or processing time is guaranteed.