Do you need FCA crypto authorisation?
That depends on the activity your firm performs, not whether it describes itself as a wallet, API, trading firm or DeFi business. The FCA’s new cryptoasset perimeter guidance is still in draft: the exclusions discussed below are proposals for guidance, not a final answer on any firm’s permissions. Firms should assess each activity against the legislation and the FCA’s proposed interpretation before deciding whether to apply.
The new UK regime brings cryptoasset activities into the FCA perimeter from 25 October 2027. Firms preparing for that change can review their activities with crypto licensing and authorisation support. An exclusion from one regulated activity does not necessarily exclude another activity carried on by the same business.
What did the FCA publish on 21 October 2026?
The FCA published CP26/36, proposing amendments to its perimeter guidance in PERG 18 and financial promotions guidance in PERG 8. It also published GC26/7, draft non-Handbook guidance on decentralised finance. Both are consultations, not final guidance. Comments close on 18 November 2026, and the FCA aims to publish final guidance in January 2027.
The Financial Services and Markets Act 2000 (Cryptoassets) Regulations 2026 bring new activities into the perimeter from 25 October 2027. The FCA published perimeter guidance in PS26/18 in September 2026. The day before that publication, the government laid a second statutory instrument adding further exclusions. CP26/36 addresses how those exclusions apply, including to technical providers and firms trading on their own account.
Firms can respond to CP26/36 through the FCA’s online form or at cp26-36@fca.org.uk. Comments on GC26/7 can be sent to gc26-7@fca.org.uk. The consultation is an opportunity to raise a specific uncertainty rather than wait for the final guidance to resolve it.
Who is outside the perimeter under the proposed guidance?
The following table is a starting point, not a list of business models that are automatically unregulated. Each exclusion has a defined scope; the activity that remains in scope may be performed by the same firm or another party in the transaction.
| Exclusion | Who it may help | Key condition | Who may stay in scope |
|---|---|---|---|
| Temporary settlement arrangements | Firms temporarily safeguarding cryptoassets for settlement | The temporary holding facilitates settlement of a transaction | Firms safeguarding outside that exclusion |
| Temporary payment holding | Firms holding a UK qualifying stablecoin to execute a payment | The holding is temporary and connected with executing the payment transaction | Firms holding other cryptoassets or operating beyond the exclusion |
| Stablecoin backing assets | Participants in arrangements involving backing assets | The assets back a UK qualifying stablecoin | Arrangements for other stablecoins; relevant backing-asset safeguarding obligations still apply |
| Own-account trading or QCATP market making | Proprietary traders and qualifying market makers | Trading is on own account without providing another person a service, or the firm acts as a market maker on a QCATP | Dealing businesses serving users outside those conditions |
| Technical services | Certain wallet, interface and API providers | The article 9Z2A conditions are met for access to another provider or a decentralised protocol | Firms substantively arranging deals or carrying on another regulated activity |
| Recognised CSD arrangements | Recognised central securities depositories, including certain third-country CSDs | The arrangement falls within the specific new exclusion | Arrangements outside its terms |
When does the FCA technical service provider exclusion apply?
Article 9Z2A concerns arranging deals in qualifying cryptoassets under article 9Y. It is not a general exemption for software, automated systems or anything connected with DeFi, and it does not extend to other activities such as dealing. CP26/36 sets out four conditions:
- The provider, A, is neither an authorised person nor a payment service provider.
- A merely provides a technical service.
- That service allows customer C to access the services of a third person or a decentralised protocol, V.
- V either carries on the regulated activity for those services and is authorised or exempt for that activity, or V is a decentralised protocol.
For access to an authorised firm, its authorisation must cover the specific regulated activity in question. A cannot be both the technical provider A and the provider or protocol V. Those details matter when a front end presents access to a third-party service but also controls how a transaction is executed.
The FCA gives six indicators that A’s role is merely technical:
- The service responds to C’s instructions.
- A transmits those instructions without qualitative judgement about their content or destination.
- C chooses the provider or protocol.
- A does not select, recommend or rank counterparties, providers, protocols, liquidity sources or execution routes.
- A does not negotiate or determine material transaction terms.
- A does not otherwise substantively participate in whether, where or how the transaction happens.
An interface that selects, shapes, directs, negotiates or routes transactions may therefore fall outside the exclusion even if its decisions are automated. Charging a fee or specialising in cryptoassets does not, by itself, prevent a service from being technical. The practical question is what the system and its operator actually do at each decision point.
Are proprietary traders and market makers excluded?
Article 9UA addresses dealing as principal under article 9T. Trading only on a firm’s own account, for its own purposes and using its own or borrowed funds may be excluded where it is not providing a service to another person. Merely labelling a desk proprietary does not resolve the question.
The FCA says it will generally see a service being provided where one of four features is present:
- The counterparty is a retail customer.
- The firm charges a fee or commission.
- The trade forms part of ongoing arrangements offered to a counterparty.
- The firm holds itself out as a liquidity provider or offers dealing or execution services.
For example, an operator of a dealing app that trades with its users is in scope; it should not treat those trades as excluded simply because it acts as principal. Separately, article 9UA excludes acting as a market maker on a qualifying cryptoasset trading platform, or QCATP, where the relevant conditions are met.
For this purpose, a market maker holds itself out as able and willing to buy and sell qualifying cryptoassets admitted to a QCATP, at prices it determines generally and continuously rather than transaction by transaction. Responding to requests for quotes on a QCATP can qualify. A QCATP may be operated by an authorised or an unauthorised person; the platform’s status alone does not settle the market maker’s position.
Which stablecoin and safeguarding arrangements are excluded?
The revised article 9Q exclusion concerns cryptoassets safeguarded temporarily to facilitate settlement of a transaction. Article 9QA concerns temporary holding of a UK qualifying stablecoin in connection with executing a payment transaction; it does not cover other cryptoassets. Firms combining payments and custody should identify which asset is held, why it is held and whether each holding fits the relevant exclusion.
Articles 9QB and 43A address backing assets of UK qualifying stablecoins only, not other stablecoins. The FCA’s safeguarding rules for those backing assets still apply. There is also a new exclusion for certain arrangements by recognised central securities depositories, including third-country CSDs.
A UK qualifying stablecoin is a qualifying stablecoin issued within article 9M by a person with Part 4A permission. Do not apply an exclusion expressly limited to that category to another stablecoin. CP26/36 also discusses the distinction between stablecoins and e-money in PERG 18.4.5B, and issuing qualifying stablecoins becomes a controlled activity under the Financial Promotion Order. Firms assessing existing tokens may also find the stablecoin action plan for CASPs useful, while treating the UK tests separately.
What does GC26/7 mean for DeFi firms?
GC26/7 is draft, non-Handbook guidance for FCA-regulated firms providing financial services using DeFi where SYSC 15A on operational resilience, SYSC 6 on compliance and financial crime, or the Money Laundering Regulations apply. It covers the risk landscape and illustrative measures concerning operational resilience and financial crime.
It should be read alongside CP26/36, not used as a substitute for a perimeter assessment. Calling a service decentralised does not answer whether its operator arranges a transaction, deals, or merely supplies technical access to a protocol. Firms should document both the activity analysis and how applicable resilience and financial crime obligations are addressed.
What are the consultation and application dates?
| Date | What it means |
|---|---|
| 30 September 2026 | The application period opened for firms with existing UK cryptoasset business that want to carry on new regulated activities. |
| 18 November 2026 | Both CP26/36 and GC26/7 consultations close. |
| January 2027 | The FCA aims to publish final guidance; this is an aim, not guidance already in force. |
| 28 February 2027 | The application period closes. Firms seeking the savings provision must apply within the window. |
| 25 October 2027 | The new cryptoasset activities enter the FCA perimeter. |
The FCA recognises that the timing of the second statutory instrument caused uncertainty. Where uncertainty about the technical services exclusion materially affected a firm’s ability to submit a complete application, the FCA will allow extra time to address incomplete aspects relating to arranging permission, provided it submits an otherwise complete application within the window. This is not a general extension of the application deadline. Affected firms should use the FCA’s pre-application support service.
How should your firm assess its position now?
- Map activities, not labels. List what each legal entity and product does when customers place, route, execute, settle or hold cryptoasset transactions.
- Trace transaction decisions. Record who chooses the provider, protocol, counterparty, price and execution route. Test technical-service claims against all four conditions and the FCA’s six indicators.
- Separate trading models. Identify own-purpose trades, customer-facing dealing and any QCATP market-making activity. Check the FCA’s service indicators rather than relying on a proprietary-trading description.
- Classify assets and holdings. Distinguish UK qualifying stablecoins from other assets, and record the purpose of temporary settlement or payment holdings.
- Decide what to submit. If an existing UK business needs permission and wants the savings provision, work to the application window. Escalate material uncertainty about arranging permission through FCA pre-application support.
Keep an evidence trail of the assumptions behind each conclusion and revisit it when the FCA publishes final guidance. A draft exclusion may clarify a permission analysis, but it cannot replace one.
FAQ
Do I need FCA crypto authorisation if my product is an API?
Possibly. Under draft CP26/36 guidance, an API may meet the technical services exclusion if it satisfies all article 9Z2A conditions; selecting routes or substantively shaping transactions points the other way. The final guidance is not yet settled.
Does charging for a wallet interface prevent the technical exclusion?
No. The FCA says charging a fee does not by itself prevent a service from being merely technical. What matters is the provider’s actual role and whether all the exclusion’s conditions are met.
Is a crypto market maker excluded if its platform is unauthorised?
A QCATP can be operated by an authorised or unauthorised person. The firm must still assess whether its activity meets the market-maker description and the relevant article 9UA exclusion; platform status alone is not decisive.
Do the UK qualifying stablecoin exclusions cover every stablecoin?
No. The payment-holding and backing-asset exclusions described here are limited to UK qualifying stablecoins where stated. Other stablecoins require their own activity and asset assessment.
Can a firm wait for final guidance before applying?
Firms seeking the savings provision must apply between 30 September 2026 and 28 February 2027. The FCA aims to publish final guidance in January 2027, but CP26/36 and GC26/7 remain under consultation until 18 November 2026; firms should not assume the final guidance or their permissions position is settled now.
If your firm already holds a UK registration, the FCA has also opened CP26/38 on financial crime controls: see FCA unhosted wallet checks: what CP26/38 expects.
How VMGlobals can help
VMGlobals can help map cryptoasset activities, test proposed exclusions against the operating model and prepare an authorisation assessment without assuming approval. For firms planning an application, the FCA authorisation gateway and application window provides a starting point for the next steps.