Service overview
Regulatory sandbox permission allows time-limited testing of innovative virtual-asset products under PVARA supervision.
PVARA differentiates the initial NOC, incorporation in Pakistan, and final licensing for one or more authorised services. An NOC is not an operating licence, and each chosen licence class has its own safeguarding, capital, competence and activity rules.
Who qualifies for the PVARA regulatory sandbox?
The applicant must propose a testable product, consumer safeguards, clear testing parameters and an exit or licensing pathway.
Applicants need a genuine testable innovation, manageable pilot scope and customer safeguards; sandbox inclusion is discretionary and is not a licence for general VASP operations.
For VASP licences, paid-up capital, eligible company form, director qualifications and actual regulated activity must be tested separately for the chosen licence class. A PVARA NOC does not grant permission to operate.
Documents and information for PVARA Regulatory Sandbox Application
Prepare the following information for pvara regulatory sandbox application. The relevant regulator may require further forms or certified evidence, depending on the applicant and chosen procedure.
- Sandbox proposal
- Product and technology architecture
- Test users and limits
- AML/CFT and custody arrangements
- Risk assessment and exit plan.
How do I apply for the PVARA regulatory sandbox? — step-by-step guide
- 01Identify the appropriate application route and eligibility
First determine whether the proposed applicant and activity fall within this procedure. The applicant must propose a testable product, consumer safeguards, clear testing parameters and an exit or licensing pathway. Review the separate conditions and exclusions in the eligibility section before submitting any form or payment.
- 02Prepare the application documents and evidence
Start with the particulars listed for this service: Sandbox proposal; Product and technology architecture; Test users and limits; AML/CFT and custody arrangements; Risk assessment and exit plan.. Ensure the names, applicant identity and documents are consistent. The authority may require further supporting material under its current checklist.
- 03Check the current regulator instructions before filing
Refer to the regulator resource identified on this page (PVARA published 2026 licensing tracks ↗). Reconfirm the currently prescribed forms, online or physical submission method, supporting evidence, fee and any current amendments. Do not assume that historic processing times or fees remain applicable.
- 04Describe the innovation proposed for sandbox testing
Prepare product features, reason for sandbox, limited user base, technical risks and consumer protection controls.
- 05Apply to PVARA Regulatory Sandbox
Submit the sandbox proposal, ownership, funding, AML/CFT/CPF safeguards and test plan through the designated portal.
- 06Operate only inside approved sandbox limits
Follow PVARA's admission decision, testing scope, reporting, safeguarding and customer limits.
- 07Complete exit assessment and separate licence path
Following successful supervised testing, submit an appropriate VASP licensing application as permitted; sandbox admission itself is not a licence.
- 08Keep the approval record and track ongoing obligations
After the authority has made its decision, retain the acknowledgement, correspondence, evidence of approval and any conditions attached to it. Do not represent sandbox approval as a general right to operate a public VASP service. A participant who successfully completes sandbox testing to PVARA's satisfaction may be eligible to proceed to a licensing application without a separate NOC under Regulation 7(6); a licence is not automatic. Check whether separate approvals, renewals or reporting duties apply to the actual business.
Use the current regulator checklist to confirm that every listed item is still required and that any activity-specific conditions have been met. The items below are drawn from the document requirements identified on this page, not a representation that the checklist is exhaustive.
- Sandbox proposal
- Product and technology architecture
- Test users and limits
- AML/CFT and custody arrangements
- Risk assessment and exit plan.
Before signing or paying, reconcile the particulars across Sandbox proposal and Product and technology architecture; check the applicant and business classification, identify the person authorised to submit, and retain a copy of the final application and official correspondence. Official instructions control if the portal or law has changed.
Regulator resource: PVARA published 2026 licensing tracks
After registration or approval
Do not represent sandbox approval as a general right to operate a public VASP service. A participant who successfully completes sandbox testing to PVARA's satisfaction may be eligible to proceed to a licensing application without a separate NOC under Regulation 7(6); a licence is not automatic.
PVARA sandbox: supervised testing does not itself confer a VASP licence
Primary-source research. The following procedural analysis is based on the identified government or regulator sources. Confirm enacted amendments, applicable forms, fees and filing requirements on the date of submission. A consultation draft is not operative law merely because it has been published. This note does not represent final legal-editor certification of the entire guide.
Choose innovation testing rather than an operating licence
PVARA's licensing portal presents a Regulatory Sandbox route for applicants testing innovative virtual asset products under supervision. A sandbox is not the same as a no-objection certificate or a full commercial VASP licence. The Virtual Assets Act, 2026 and the Pakistan Virtual Asset Services Regulations, 2026 remain the governing framework, with sandbox guidelines and the activity-specific regulations relevant to the proposed test.
Prepare scope and testing design
Describe the actual asset and customer flow, why a sandbox is suitable, proposed test users and transaction limits, technology and custody architecture, AML/CFT screening, risk disclosures, complaints and consumer safeguards. Specify what data will be collected and what results will demonstrate technical and regulatory readiness. Do not assume testing can commence simply after submitting an application.
Operate within admission conditions
PVARA's public licensing roadmap separates application, admission, controlled testing, exit and the later VASP licence. Keep records of testing permissions, activity limits, customer assets, incidents, operational controls and regulator communications. Commercial distribution outside the approved test perimeter should not be represented as authorised by the sandbox admission.
Transition to full licensing
PVARA's FAQ states a sandbox participant completing testing to the Authority's satisfaction may apply directly for a licence without a separate NOC under the current Services Regulations. Successful testing does not create an entitlement to a licence: final Category-specific paid-up capital, fit-and-proper, operational and technology conditions still apply.
Official legal and regulatory sources
Governing law & official references
Virtual Assets Act, 2026; Pakistan Virtual Asset Services Regulations, 2026; and Pakistan Virtual Asset Services Activity Specific Regulations, 2026.
The links below lead to government or official regulatory sources relevant to this service. Use the currently consolidated Act, regulations, statutory checklist and official portal when making an application.
How Chambers can assist
Chambers can review the legal route, identify regulatory constraints, prepare or review the supporting corporate and legal documents, manage the prescribed submission and correspond with the competent authority where instructed. The scope of the engagement will be determined by the applicant’s particular circumstances.
For an initial enquiry, identify the proposed activity, applicant entity and current stage, and provide the available documents indicated above. Please avoid sending confidential or identity-sensitive records through an unencrypted first contact.
Common questions about PVARA Regulatory Sandbox Application
Who is eligible for PVARA Regulatory Sandbox Application in Pakistan?
The applicant must propose a testable product, consumer safeguards, clear testing parameters and an exit or licensing pathway.
What documents are needed for PVARA Regulatory Sandbox Application?
Sandbox proposal; Product and technology architecture; Test users and limits; AML/CFT and custody arrangements. Additional requirements can apply to the actual business or regulator.
How do I apply for the PVARA regulatory sandbox?
Describe the innovation proposed for sandbox testing: Prepare product features, reason for sandbox, limited user base, technical risks and consumer protection controls. Apply to PVARA Regulatory Sandbox: Submit the sandbox proposal, ownership, funding, AML/CFT/CPF safeguards and test plan through the designated portal. Operate only inside approved sandbox limits: Follow PVARA's admission decision, testing scope, reporting, safeguarding and customer limits. Complete exit assessment and separate licence path: Following successful supervised testing, submit an appropriate VASP licensing application as permitted; sandbox admission itself is not a licence.
This guide is general information, not advice on your facts. Check the applicable law, notifications, updated regulator checklists and jurisdiction before acting. The authority alone determines eligibility, acceptance and approval; no outcome or processing period is guaranteed.