Suspension of an offer: what the decision maker looks at
When a decision maker suspends a token offer, it looks at three things: whether the disclosure document is complete, whether the issuer can be reached without delay, and whether letting the offer continue risks harm to subscribers. It weighs these against the stage the offer has reached. Our Counterparty reports overview shows how we track distribution partners through a file, and suspension is usually the point where that tracking starts to matter. A suspension issued before any tokens change hands is a different event from one issued after distribution has begun.
What actually changes once suspension lands
Marketing stops the moment the order takes effect. The subscription page must come down, not slow down. No new commitments can be accepted, and any commitments taken in the hours before the order was issued need to be reviewed rather than processed automatically. The issuer usually receives a short window to respond with the missing information or the correction requested. That window is the real deadline on the file, not the suspension order itself.
Existing subscribers are left in an uncertain position: their funds or commitments are neither confirmed nor returned until the decision maker rules on whether the offer resumes or is withdrawn. This is the period where most disputes with counterparties start, because nobody has a clear instruction yet.
What to do, in order
- Freeze the subscription channel immediately. The platform operator, not the legal team, is usually the one who can pull the page down within minutes.
- Notify distribution partners the same business day. This includes any Subprocessors, including local delivery partners explained handling onboarding or payment collection on the issuer's behalf.
- Assemble the file the decision maker is likely to request. White paper drafts, marketing communications sent to date, and subscriber records are the usual first ask.
- Name one contact person authorised to respond without delay. A committee cannot answer a regulator inside a short window; one named person can.
- Track every deadline set by the decision maker. A missed deadline extends the suspension automatically in most procedures we have seen.
- Prepare the request to lift the suspension once the gap is closed. This should be ready before the response is even filed, not drafted afterwards.
Who decides, and on what timeline
| Stage | Who acts | Typical timing |
|---|---|---|
| Preliminary review of the offer | National competent authority | Before or shortly after the offer opens |
| Suspension order issued | Same authority | Takes effect immediately on notice |
| Issuer response window | Issuer, coordinated with counsel | Short, set by the authority case by case |
| Decision to lift or extend | Same authority | After the response is reviewed |
| Review of the decision, where available | Authority's own review panel or a court | Runs on a separate, longer timeline |
The table describes the sequence, not fixed day counts. The length of each stage depends on how complete the issuer's response is and on the workload of the authority handling the file.
Three forks, three different outcomes
If the suspension arrives before any tokens have been transferred, the issuer amends the disclosure document and resumes once the authority is satisfied. Nothing irreversible has happened yet.
If tokens have already been distributed to subscribers when the order lands, suspension stops further offering activity but does not undo transfers already completed. This is the point of no return: a decision maker can halt what happens next, not what has already settled.
If the issuer does not respond inside the window, the suspension typically extends on its own and can convert into a full withdrawal order. At that stage the file moves from a pause to a closure, and the options narrow sharply.
What this page does not resolve
This page describes the procedure, not the outcome of any specific file. It does not set out statutory deadlines or cite the provisions a particular authority relies on, because a procedural page does not carry legal citations in our approach — the national detail behind each register is tracked separately, and citing a rule we cannot verify against that register would be worse than leaving it out.
Sources and limits
The detail that decides how fast a suspension moves depends on the register the offer actually uses. For issuers working through Estonia, the underlying registers and their limits are catalogued in Document in Estonia. Where the offer touches Latvia instead, the equivalent route and its limits sit in Jurisdiction in Latvia. Neither report replaces a case-specific read of the suspension order itself; both explain where the boundaries of what we can check actually sit.
Last reviewed: 4 February 2025. This page draws on our own file experience and on procedural guidance published by the relevant authorities; it does not rely on statute citations, for the reason set out above.
Related publications
The stage after suspension is lifted brings its own obligations. Post-issue reporting step by step covers what the decision maker checks once an offer has actually gone ahead.
FAQ
How long does suspension of an offer take in practice?
There is no fixed run-time. It runs as long as it takes the issuer to close the gap the authority identified, inside the window the authority sets. A complete response inside that window is what shortens the process; nothing else does.
Which documents are needed to start?
The file the decision maker is likely to request first: every version of the disclosure document circulated, the marketing communications sent to date, and the subscriber or commitment records held at the moment the order took effect.
What happens if the other side does not respond?
The suspension usually extends automatically. In our experience, a prolonged silence from the issuer tends to move the file from a pause towards a formal withdrawal order rather than resolving on its own.