Sandbox Vocabulary: Applicant, Participant, Exit, No-Action Relief

The Sandbox Guidelines 2026 open with a short definitions section, and it is easy to skim past it on the way to the eligibility criteria and the application form. That is a mistake. Several of the operative rules in the Guidelines only make sense once the defined terms are read precisely — in particular, the distinction between an Applicant and a Participant, which marks the exact point at which PVARA’s supervisory powers over a sandbox entrant begin.

This article works through each defined term in the Guidelines, in the order PVARA lists them, and explains what turns on the wording.

Who is an “Applicant” under the Sandbox Guidelines?

An Applicant is “any person applying for participation in the Sandbox in accordance with Section 43 of the Ordinance.” Nothing more is required to acquire the label — submitting an application is enough. An Applicant has not yet been assessed, has no supervisory agreement with the Authority, and has none of the operating permissions a Participant holds.

The practical significance of this term is that every obligation attached to “Applicant” in the Guidelines — completing Form I, submitting the Annexure-A self-assessment, meeting the eligibility criteria — applies before any approval decision is made. A person remains an Applicant through initial screening, through the evaluation phase, and up to the point PVARA issues a Letter of Approval (LoA).

Who is a “Participant,” and how does that differ from an Applicant?

A Participant is defined as “an applicant that has been approved to operate within the Sandbox under a supervisory agreement with the Authority.” The word “approved” is the hinge. An Applicant becomes a Participant only once PVARA has completed its evaluation, issued the Letter of Approval, and the applicant has executed the Annexure-B undertaking that formalises the supervisory relationship.

This distinction is not academic. The obligations that apply specifically to testing — reporting to PVARA on an agreed format and frequency, the one-hour incident notification clock, the 48-hour detailed incident report, the seven-year record retention requirement in the undertaking — all attach to Participant status, not Applicant status. A firm still in the assessment queue is not yet bound by the testing-stage obligations, but it is also not yet permitted to operate.

What does “Exit” mean, and what are the three possible outcomes?

Exit is defined as “the process, at the conclusion of Sandbox testing, through which a participant either transitions to full licensing, discontinues the Virtual Asset service, or takes other steps as directed by the Authority under Section 44(3) of the Ordinance.” The definition names exactly three possible destinations for a Participant once testing ends.

• Transition to full licensing — the product is judged successful and the Participant proceeds to a full VASP licence application.
• Discontinuation of the service — the Participant winds the tested product down, whether because it failed, was withdrawn, or PVARA directed an orderly close.
• Other steps as directed by the Authority — a residual category that gives PVARA discretion to prescribe an outcome not covered by the first two, on a case-by-case basis.

The Guidelines elsewhere require every Applicant to submit “a sandbox exit plan specifying transition to full authorization or orderly wind-down” as part of demonstrating operational readiness — so the exit route is meant to be planned for at the application stage, not improvised once testing ends.

What is “No-Action Relief,” and how does the definition limit it?

No-Action Relief is defined as “a no-action letter issued by the Authority under Section 45 of the Ordinance, indicating that the Authority does not intend to take enforcement action in respect of specified conduct for a defined period.” Three words in that definition do the limiting work: “specified,” “defined period,” and “does not intend.”

“Specified” means the letter covers named conduct, not blanket protection for everything a Participant does. “Defined period” ties the relief to the test window, not an open-ended grant. “Does not intend” is a statement of present enforcement posture, not a binding waiver — and the body of the Guidelines confirms this reading directly elsewhere, stating that a no-action letter “shall not constitute a legal immunity” and that PVARA “reserves the right to withdraw such a letter at any time by providing written notice.”

What do “Agile Approach” and “Sandbox” mean in the Guidelines?

Agile Approach is defined narrowly as “a process under which Applicants may submit applications at any time during the year for consideration by the Authority.” It describes a submission timetable, not a lighter assessment standard — the same 60-working-day evaluation clock and the same eligibility bar apply regardless of when in the year an application lands.

Sandbox itself is defined as “the controlled environment established and operated by the Authority under Section 42 of the Ordinance for the purpose of fostering responsible innovation in Virtual Asset products and services.” The words “controlled environment” recur throughout the rest of the Guidelines, in the Authority’s power to impose limits on transaction volumes, user numbers, or exposure on a case-to-case basis.

Who or what are “Authority,” “Board,” and “Ordinance” in this context?

The Guidelines define Authority as PVARA, “established under the Section 6, sub-section 1 of the Ordinance.” Board is defined as PVARA’s governing body, “established under section 8 the Ordinance, and vested with the powers and functions set out therein, including the authority to constitute committees, approve membership changes, and oversee the overall operations of the Authority.” Ordinance is defined simply as “the Virtual Assets Ordinance, 2025.”

As with the sandbox’s statutory basis generally, these Ordinance section references have not been updated to match the Virtual Assets Act, 2026, which now governs PVARA directly — the Act establishes the Authority at section 6 and sets its composition at section 7, and a saving provision at section 74 preserves actions taken under the lapsed Ordinance as if done under the Act’s corresponding provisions. Readers relying on a specific numbered cross-reference inside the Guidelines should treat it as pointing to the Act’s current equivalent section rather than a live Ordinance citation.

Why does the Applicant-to-Participant distinction matter most?

Of the nine terms defined in the Guidelines, the Applicant-to-Participant boundary is the one with the most legal consequence, because it marks the exact moment PVARA’s supervisory agreement — and every obligation that comes with it — takes effect. Everything before that boundary is a screening and evaluation process governed by the eligibility criteria; everything after it is governed by the Annexure-B undertaking and the testing-stage reporting regime.

For a firm preparing to apply, this has a practical implication: the readiness demonstrated in Form I is being assessed against the standard a Participant will be held to, not a lighter Applicant-only standard. Building the testing plan, governance structure and exit plan required to become a Participant is, in effect, the same work required to survive as one.

Related reading

• PVARA Exchange License: Capital, Rules & Obligations 2026
• PVARA Transfer & Settlement License: Crypto Payments 2026
• PVARA Licensing Process: NOC to Full Licence, Step by Step
• The PVARA Licensing Gold Rush: Pakistan’s Crypto Frontier
• PVARA Custody License: Safeguard Customer Crypto 2026

About this analysis

This analysis was prepared by the CoinConnect research desk from the Virtual Assets Act, 2026 and 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.