The Sandbox Self-Assessment: Eight Questions to Answer First

Before a firm files Form I with PVARA, the Sandbox Guidelines 2026 hand it a diagnostic tool to run on itself first. Annexure-A is a self-assessment checklist of eight questions, each paired with the specific signals PVARA treats as positive and the specific signals it treats as negative.

This piece works through all eight questions in the order Annexure-A lists them, with the exact indicators attached to each.

What is Annexure-A, and when is it used?

Annexure-A is a self-assessment checklist that must be submitted alongside a sandbox application. The Application submission process section of the Sandbox Guidelines states the requirement directly: “Applicant shall submit the self-assessment along with application as provided in Annexure-A.” It is not a separate optional exercise — it is a mandatory companion document to Form I, and its eight questions map closely onto the Key Evaluation Criteria the Authority applies during the formal assessment phase. Working through it honestly before submission is, in effect, a preview of how PVARA will read the application.

Question 1 — Is the proposed business model within scope, and is it beneficial for Pakistan?

This is a two-part gate: scope and benefit. Annexure-A’s positive indicator is that “your project involves virtual assets and virtual asset services, or related infrastructure relevant to Pakistan’s financial system.” The negative indicator is blunt — the project is “not related to Virtual Asset Services or the related eco-system.” A proposition that does not touch Virtual Asset Services as defined under Schedule I of the Virtual Assets Act 2026 fails this gate before any of the other seven questions are relevant.

Question 2 — Does the business have real demand and room to scale?

The positive indicator here is a “target market identified with expansion potential (local, regional, global).” The negative indicators are two distinct failure modes worth separating: “weak or stagnant user adoption” describes a product that has not found traction, while “reliance on niche or unsustainable demand (e.g., speculative hype only)” describes a product that has found traction of the wrong kind — demand that will not survive the testing period. A business plan that cannot show which of these two risks it avoids is not ready for this question.

Question 3 — Is the technology secure and resilient?

Positive indicators are concrete and testable: “robust IT infrastructure, cybersecurity safeguards, smart contract audits, disaster recovery plans,” together with “independent third-party security testing performed.” Negative indicators are equally specific — “weak cybersecurity indicators, no audits, or reliance on unverified smart contracts,” and, separately, a “lack of safeguards to ensure custody of consumer’s funds in case of cyber intrusions.” That last point is a distinct requirement from general cybersecurity: PVARA is asking specifically whether customer assets are protected if the security controls fail, not only whether the controls exist. This overlaps directly with the custody standards applied to full licensees.

Question 4 — Is the innovation genuine?

The positive indicators describe two acceptable routes to genuine innovation: introducing “a new use-case for virtual assets not yet tested locally,” or an “adaptation of proven international solutions to Pakistan’s market with significant improvements.” Note the word “significant” in the second route — an unmodified copy of an existing foreign product does not qualify under this indicator, only one that has been meaningfully improved for the local market. The negative indicators mirror this precisely: “numerous similar models already exist in Pakistan,” or “minor tweaks to an existing product/services or business model related to virtual assets.” A sandbox slot is not available simply for launching a variant of something PVARA has already seen.

Question 5 — Does the project benefit consumers, markets and the national exchequer?

This question has the widest set of positive indicators in Annexure-A: increased transparency, lower costs or improved efficiency for users; enhanced financial inclusion or access to digital financial services; and — critically — the applicant must “identify and propose mitigation for risks (ML/TF, volatility, fraud, cyber)” rather than simply assert that risks exist. The negative indicators are the mirror image: “limited transparency, cost inefficient,” a project that “poses high risks of consumer loss or market instability,” and, most commonly the deciding factor, “no clear risk mitigation strategies (e.g., for hacks, price manipulation, or data privacy).” Identifying a risk without a mitigation plan attached to it reads as a negative under this question, not a neutral disclosure.

Question 6 — Are you actually ready to test?

Readiness here is assessed across four positive indicators: understanding of applicable laws, cybersecurity and data protection requirements; a clear business model, technology architecture and compliance plan; a testing plan with “objectives, success criteria, timelines, and risk controls” already prepared; and adequate financial and human resources to run the pilot. The negative indicators describe the same gaps from the other side — no clarity on ML/TF, KYC, cybersecurity or custody rules; a lack of technical or financial readiness; no consumer protection measures in place; and the sharpest of the four, a project that is “concept only on paper yet.” That last phrase is Annexure-A’s own wording, and it is worth taking literally: an idea without an operating testing plan behind it is not sandbox-ready, whatever its underlying merit.

Question 7 — Do you actually need the sandbox, or could you answer this another way?

This question tests necessity, not just quality. The positive indicator is that the proposition “requires regulatory flexibility to test novel mechanisms (token issuance, DeFi protocols, smart contracts, custodial services)” — in other words, the product cannot be validated under the ordinary licensing framework because the framework does not yet accommodate what it does. The negative indicator is correspondingly narrow: “live testing not necessary to answer regulatory or market questions.” A well-built, low-risk product that could simply apply for a standard VASP licence may not need — or qualify for — sandbox treatment at all; the sandbox exists for propositions the current framework cannot yet directly license.

Question 8 — How will you meet AML/CFT/PF and FATF obligations?

The positive indicators are “strong KYC/AML processes integrated into platform design” and “alignment with FATF and Pakistan’s AML laws” — note the word “integrated,” which points to compliance built into the product architecture rather than bolted on afterward. The negative indicators are stated as a spectrum of the same failure: “weak or no AML/KYC framework,” creating a “high risk of misuse for money laundering, terrorism financing, or fraud.” This question connects directly to the FMU goAML reporting infrastructure that applies across the wider licensing framework, not only inside the sandbox.

How do the eight questions map onto the Guidelines’ Key Evaluation Criteria?

Annexure-A question	Corresponding Key Evaluation Criteria heading
1. Scope	Innovation and Market Impact (inclusion)
2. Business Scalability	Innovation and Market Impact (novelty, differentiation)
3. Technology & Security	Risk Management and Compliance (cybersecurity)
4. Genuine Innovation	Innovation and Market Impact (novelty, differentiation)
5. Consumer & Investor Benefit	Risk Management and Compliance; Financial Strength
6. Readiness	Feasibility and Exit Strategy
7. Genuine Need for Sandbox	Feasibility and Exit Strategy
8. ML/TF & Compliance Preparedness	Risk Management and Compliance

The overlap is not a coincidence. Annexure-A is best read as a self-scored preview of the same criteria the regulatory sandbox evaluation team applies formally after submission. A founder who cannot honestly tick the positive indicator on any one of the eight questions is looking at the specific weakness an evaluator is trained to find. Our companion piece on what makes a sandbox application fail works through the same negative indicators from the rejection side, alongside the procedural limits on resubmission.

About this analysis

This analysis was prepared by the CoinConnect research desk from Annexure-A and the Key Evaluation Criteria and Application submission process sections of the PVARA Sandbox Guidelines 2026, read as published. Where practice is not yet settled or guidance has not been issued, that is stated in the text above.

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.