Surrender of a permission: what the decision maker looks at
Surrender of a permission is the voluntary return of an authorisation to the body that granted it. The decision maker checks that client assets are protected, outstanding obligations are settled, and the register can be updated without gaps. Nothing is finalised until every open item on that checklist is closed. This page sets out the stages, the documents usually asked for, and the point after which the surrender cannot be reversed.
It is written for a team that already holds a permission and wants to close it in an orderly way, not for someone applying for one. It does not cover a permission being revoked or suspended by the authority on its own initiative — that is a different process, with a different starting point and a different tone.
What surrender means in practice
Surrender differs from a licence being revoked or suspended. It starts with the holder, not the authority, and it only succeeds if the wind-down behind it is orderly. A request that arrives with open client positions or missing safeguarding evidence is not refused outright; it is usually returned with questions, which adds time rather than closing the file.
The authority's internal procedure sets out the checklist for this kind of request. This overview follows that checklist without naming a specific provision, because the exact requirements depend on the type of permission held and are confirmed case by case with the case handler assigned to the file.
What changes once the file is closed
Once surrender is accepted, the entity loses the right to provide the service the permission covered. Client relationships tied to that permission must be wound down, transferred, or completed before the change takes effect; none of them can simply be left open. The public register is updated to reflect the closure, and the former holder cannot rely on that permission for any new activity from the effective date onward.
Records built up while the permission was active should still be kept for a reasonable period afterwards. Supervisory correspondence, client files, and the wind-down summary itself are the documents most likely to be asked for if a question comes up later.
What to do
- Confirm internally that no client obligation under the permission remains open, and put that confirmation in writing.
- Notify the authority that you intend to surrender the permission, stating the effective date you propose and the reason in brief.
- Prepare a wind-down summary covering every open client position: how each one is being closed, transferred, or protected in the meantime.
- Submit the notice and the summary through the authority's usual supervisory correspondence channel, not as a general enquiry.
- Respond to any follow-up questions from the assigned case handler within the deadline given in that specific request.
- Keep evidence of every closing step until the authority confirms the register has actually been updated.
A file that skips the wind-down summary is the single most common reason a surrender request stalls. The authority is not being difficult; it simply cannot close a register entry while a client position behind it is still open.
Who decides and how long it takes
One case handler is usually assigned once the notice is received, and that person stays the point of contact until the file closes. The final decision to accept surrender and update the register sits with the authority, not with the case handler alone.
| Stage | Who acts | Typical timing |
|---|---|---|
| Internal check and notice | The holder | Before the file is submitted |
| Case review | Supervisory case handler | Begins on receipt of the file |
| Follow-up questions, if any | Case handler and holder | Set separately for each request |
| Decision and register update | The authority | After the file is complete |
A file with no open client positions and clear evidence moves through this sequence with fewer questions. A file that still has loose ends attracts more of them, and each round of questions resets the clock on that particular point.
Branches worth checking before you file
If a supervisory inspection is already open when you file for surrender, the two files typically run in parallel until the inspection closes. See Supervisory inspection step by step for what that separate file needs.
If the permission covers a tokenised collection whose branding is shared with another party, an unresolved trade mark question can slow the surrender review as well. The same weighing test that applies here governs Coexistence negotiation step by step.
If the underlying technology was built by a co-founder who has since left the team, incomplete technical records can hold up the wind-down summary. The same documentation gap is described in Biotech and life sciences — when a founder leaves.
What this page does not cover
This page describes the surrender procedure only. It does not set out safeguarding rules for client assets, the tax treatment of a wind-down, or the criteria the authority applies when it revokes a permission on its own initiative instead of accepting a voluntary surrender.
Those are separate questions, each with its own answer and its own timing. Treat this page as the map of the process, not as the full rulebook behind it.
Verified
This is a general procedural outline, not a substitute for direct contact with the authority. The primary source for a live filing is the authority's own published supervisory guidance, confirmed with the case handler assigned to your specific file. In keeping with the procedural scope of this article, no specific provision or numbered act is cited above.
Related reading
For the stage before authorisation, see Pre-application meeting step by step, which sets out what to bring to that first meeting.
Next steps
If you are preparing a surrender file and want a second opinion on the wind-down summary before it goes in, that is a reasonable point to bring in outside support.
If the same portfolio also involves a tokenised collection built on artwork you do not own, start with When a collection uses third-party artwork.
If the offer behind the permission is aimed at several countries at once, see how The offer targets several countries token issuance is scoped before you file for surrender.
FAQ
How long does surrender of a permission take in practice?
Timing depends on how complete the wind-down summary is when it reaches the case handler. A file with no open client positions and clear safeguarding evidence moves through review faster than one with loose ends. Build in time for at least one round of follow-up questions.
Which documents are needed to start?
At minimum: a written notice of intent to surrender, a wind-down summary covering every open client position, and evidence of how client assets are protected until each position closes. Internal sign-off that no obligation remains open should sit behind that file, even if it is not sent separately.
What happens if the other side does not respond?
If a client or counterparty whose confirmation you need does not respond, that point in the wind-down summary stays open. The case handler will normally ask how you propose to protect that position anyway, rather than let the whole file wait indefinitely for one reply.