PVARA's Emergency Powers: The Thirty-Day Suspension Explained

Most of PVARA’s enforcement powers involve process — a warrant, a written report, an opportunity to be heard before a licence is touched. Section 60 of the Virtual Assets Act 2026 is different. It is a single, short provision that lets the Authority act first and explain later, for a narrowly time-boxed window.

This is the Authority’s emergency brake. It exists for situations where waiting for the ordinary licence-variation or administrative-sanction process to run its course would itself be the risk — a live cybersecurity breach, a market manipulation event unfolding in real time, a fraud draining customer assets while a hearing is scheduled.

This article sets out exactly what section 60 says, what it does not say, and how it sits alongside PVARA’s other enforcement tools.

What triggers PVARA’s emergency intervention power?

Section 60 lists four situations that can trigger an emergency order: a systemic threat, market manipulation, fraud, or a cybersecurity breach. It also includes a catch-all — “other serious risk to customers or market integrity” — that is not limited to those four named categories.

“In the event of a systemic threat, market manipulation, fraud, or cybersecurity breach, or other serious risk to customers or market integrity, the Authority may issue an order temporarily suspending specified Virtual Asset Services or freezing related assets for a period not exceeding thirty days.”

Two of the named triggers are separately defined elsewhere in the Act. Market manipulation, or market abuse, is defined in section 3(1)(xvii) as conduct giving false or misleading signals about supply, demand or price, securing prices at an abnormal or artificial level, or using deception to interfere with normal supply and demand — the same conduct prohibited outright under section 52. “Systemic threat” and “cybersecurity breach” are not separately defined in the sections we have reviewed, which leaves PVARA meaningful discretion in deciding when a given incident crosses the threshold into “emergency” territory.

What can PVARA actually do under an emergency order?

The section grants two distinct powers, and the Authority is not required to use both together. It may suspend specified Virtual Asset Services, or it may freeze related assets, or both, depending on what the emergency requires.

“Specified” is doing real work in the drafting. The Authority is not limited to suspending an entire licence — it can target the particular service category implicated in the emergency, leaving a licensee’s other permitted services under Schedule I running. A custody provider facing a live security incident, for example, could in principle have custody services suspended while an unrelated advisory or lending line continues, if the Authority frames the order that narrowly.

“Related assets” is similarly undefined in precise terms — the Act does not specify whether this means only the assets implicated in the specific incident, or extends more broadly to a firm’s customer holdings generally. Given the seriousness of an asset freeze, our reading is that the Authority would be expected to draw the order as narrowly as the emergency allows, consistent with its general duty under section 9(1)(b) to protect customers and market integrity, but the Act does not impose an express proportionality test on the face of section 60 itself.

How long can an emergency suspension or freeze last?

Thirty days, and no longer, on the face of the section. This is the only time limit stated anywhere in section 60, and it applies to the order as issued.

The Act does not say, in the text we have reviewed, what happens at the end of the thirty days. It does not state whether the Authority may issue a fresh emergency order for a further thirty-day period if the underlying risk has not resolved, whether the matter must instead convert into a formal licence suspension under section 23 (which requires written notice and an opportunity to be heard), or whether the emergency measure simply lapses automatically. This is a real gap in the published Act, and it is the single most important practical question for anyone actually subject to a section 60 order. Until PVARA issues Regulations or guidance clarifying the position, we recommend treating the thirty-day figure as a hard ceiling on the emergency measure itself, with no assumption about automatic renewal.

Is an emergency order the same as suspending my licence?

No, and the difference matters. Section 23 governs the ordinary route to suspending or revoking a licence: the Authority must give written notice and provide an opportunity to be heard before acting, and the grounds are tied to specific findings — contravention of the Act, insolvency, ceasing to carry on the licensed service, public interest, or fraud in obtaining the licence in the first place.

Section 60 contains no equivalent hearing requirement on its face. It is built for situations where the ordinary process would be too slow, and the trade-off is that the affected person’s opportunity to be heard, if any, comes after the order rather than before it. This is consistent with how emergency intervention powers typically operate in financial regulation generally, but it is a meaningfully different procedural posture from the rest of the Act’s enforcement architecture, and it is worth building into how a licence application applicant thinks about operational-resilience planning from day one — not as a remote scenario, but as a defined regulatory power that exists on the statute book.

Can I appeal an emergency order?

The general appeal route under the Act should apply. Section 63 allows any Virtual Asset Service Provider, Licensee, or other person aggrieved by an order of the Authority to appeal to the Virtual Assets Appellate Tribunal within thirty days of the order being communicated. Section 60 does not exclude itself from this route, and nothing in our source material suggests emergency orders are carved out of the general appeal mechanism.

In practice, this means the thirty-day appeal window under section 63 and the thirty-day maximum duration of the emergency order itself run roughly in parallel — an appeal against a section 60 order may not even be decided, given the Tribunal’s own three-month disposal target under section 64(2), before the order has expired on its own terms. That timing mismatch is worth flagging for anyone advising a client through a live emergency order: the practical remedy in the moment may be direct engagement with PVARA under the order’s own terms, rather than the Tribunal appeal, given how the timelines line up.

How does this interact with website blocking and administrative sanctions?

Section 60 sits alongside two other rapid-response powers in the Act rather than replacing them. Section 61 lets PVARA block or direct the removal of online material connected to an unlicensed Virtual Asset Service — a power aimed outward, at the public-facing presence of an unlicensed operation, rather than at a licensee’s internal services or asset holdings. Section 59’s administrative sanctions, by contrast, are the Authority’s standard enforcement toolkit for established contraventions, running on the ordinary process rather than the emergency track.

A single incident could, in principle, touch all three. A cybersecurity breach at a licensed exchange might trigger a section 60 suspension of the affected service immediately, a section 59 administrative sanction once the Authority completes its assessment of the underlying contravention, and — if the exchange’s public marketing or app listing itself becomes a vector for further harm — a section 61 blocking direction as well. Recognising which power is which, and which procedural protections attach to each, is the difference between responding to a regulator correctly under pressure and responding to the wrong process.

About this analysis

This analysis was prepared by the CoinConnect research desk from the Virtual Assets Act 2026 as passed by the National Assembly — principally section 60, read together with sections 3(1)(xvii), 9(1)(b), 23, 52, 59, 61, 63 and 64 — as published. Where the Act does not specify a procedure or outcome, that is stated plainly in the text above rather than inferred as settled law.

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.