By CRYPTOVERSE Legal Consultancy
A crypto staking service may require FCA authorisation where a business makes arrangements on behalf of another person for qualifying cryptoassets to be used in blockchain validation.
The assessment depends on the service’s actual features. Operating technical infrastructure, pooling customer assets, managing staking participation and distributing rewards can involve different regulatory considerations.
For management, the starting question is:
What does our business do to enable the customer’s staking, and which responsibilities and controls does it retain?
This article explains how to assess the perimeter and prepare supporting application evidence.
1. Identify the Regulated Staking Activity
Article 9Z6 of the Regulated Activities Order defines the activity as making arrangements on another person’s behalf, whether as principal or agent, for qualifying cryptoasset staking.
PERG 18.10.1G links this to the use of qualifying cryptoassets in blockchain validation. It identifies potentially relevant models including pooled staking, lifecycle management and reward distribution.
The guidance also addresses conditional exclusions for introductions, communications and technical services under articles 9Z7–9Z9.
A product labelled “staking” should therefore be examined to establish what happens to the assets and how returns arise.
A service generating returns through lending or another arrangement needs its own activity analysis.
2. Distinguish Current Operations From the Expanded Regime
The expanded crypto regime commences on 25 October 2027. The FCA gateway opened on 30 September 2026, with the relevant application period currently ending on 28 February 2027.
Existing MLR registration does not automatically convert into FSMA authorisation. Firms already authorised under FSMA need to apply to vary their permissions where appropriate.
Prepare a schedule distinguishing:
- Current services and applicable obligations.
- Proposed authorised services.
- Existing permissions.
- Additional permissions required.
- Implementation dependencies.
- Relevant transitional arrangements.
A future staking permission should not be treated as resolving all current legal requirements.
3. Map the Complete Staking Service
For practical assessment, describe the service from customer instruction to completion.
Identify:
- How the customer selects staking.
- Which assets and networks are supported.
- Who controls the assets.
- How validators are selected.
- How assets enter staking.
- How rewards are calculated and allocated.
- Whether rewards are reinvested.
- How unstaking and return operate.
At each stage, identify the applicant, group entities, validators and providers involved.
A customer-facing button may sit above a complex chain of arrangements. The legal analysis should reflect that chain rather than only the interface.
4. Assess Technical Services Carefully
PERG 18.10.2G–18.10.3G distinguish purely technical participation support from wider arrangements. The technical-services exclusion includes a condition concerning holding out to the public.
Additional participation services can affect reliance on the exclusion. Providing a validator node or software interface does not settle the outcome without examining the full role.
For preparation, examine:
- Customer contracts.
- Marketing descriptions.
- Participation decisions.
- Validator selection.
- Reward handling.
- Asset control.
- Additional services.
Document the facts supporting any exclusion. Reassess when the service expands.
5. Review Custody and Other Activities Separately
Virtual asset lending and borrowing services for Staking analysis should be coordinated with the treatment of asset control.
The FCA’s staking guidance expressly identifies possible additional safeguarding or arranging-safeguarding requirements.
A practical permission review should consider:
| Feature | Further question |
| Customer assets transferred to a provider | Who can control their movement? |
| Assets pooled | How are individual entitlements recorded? |
| Rewards retained or reinvested | Who controls them and under what authority? |
| Tokens issued in connection with staking | What rights do those tokens confer? |
| Tokens bought, sold or transferred | Which dealing or arranging activities arise? |
| Additional yield features | How are returns actually generated? |
Each relevant activity needs assessment. One staking permission should not be assumed to cover the complete product.
6. Assess Liquid Staking on Its Facts
Regulatory compliance advisory services for Liquid staking adds a token or other transferable representation to the staking arrangement.
For practical review, identify:
- The token issuer.
- The holder’s rights.
- The relationship with underlying assets.
- Redemption or exchange mechanics.
- Reward entitlement.
- Transferability.
- Control of the underlying assets.
- Other uses are promoted for the token.
Coordinate token classification with the staking, custody and transaction analyses.
Avoid treating the token as a mere receipt without examining whether controlling it enables the holder to exercise or transfer rights.
7. Check Territorial Scope
An overseas staking provider needs a separate UK territorial assessment.
PERG 18.3 requires ordinary territorial analysis before considering the deeming provisions. FSMA section 418(6E) addresses certain overseas safeguarding and staking arrangements involving UK consumers, with conditions concerning appropriately authorised direction. The assessment depends on the actual instructions and responsibility arrangements.
For application preparation, identify:
- Customer location and status.
- Where the relevant activities occur.
- Which entity receives instructions.
- Which entity directs providers.
- The permissions and role of any intermediary.
An overseas provider relationship should be explained through those facts.
8. Prepare Retail Information and Consent Arrangements
The final rules in CRYPTO 10, published with PS26/11, address information, key terms, consent, notifications and records.
Under CRYPTO 10.3.1R, retail clients must receive key terms and give express prior consent before being bound or receiving the service, with consent records capable of reproduction. Specific provisions address auto-staking and reward reinvestment.
For implementation, map:
- What the customer sees.
- When it is presented.
- How consent is captured.
- Which version is retained.
- How changed terms are communicated.
- How customers obtain their records.
Test the journey as a customer would experience it.
9. Explain Risks and Rewards Accurately
The final framework requires retail information covering relevant staking risks, including slashing and operational disruption.
For practical drafting, review how the service explains:
- Variable rewards.
- Fees.
- Lock-up and withdrawal constraints.
- Validator performance.
- Slashing.
- Network events.
- Provider failure.
- Any loss allocation or reimbursement arrangements.
Projected returns should be supported by a clear methodology and assumptions.
If the firm describes protection against a loss, identify who provides it, its scope and limitations. Customer communications should match the contractual arrangement.
10. Design Validator and Provider Oversight
A suggested assessment should examine:
- Technical capability.
- Operating history.
- Security.
- Availability.
- Slashing exposure.
- Conflicts.
- Reporting.
- Subcontractors.
- Recovery and exit arrangements.
Identify who approves appointments and monitors performance.
For an outsourced model, test whether the applicant can obtain sufficient information to understand rewards, incidents and customer balances.
A provider’s reputation should be supported by documented due diligence relevant to the service.
11. Connect Staking With Financial Resources
Under CRYPTOPRU 4.2.1R, arranging qualifying cryptoasset staking carries a £150,000 permanent minimum capital requirement. The wider own funds assessment compares the permanent minimum, fixed overheads and K-factor requirements.
For management planning, model:
- Staking volumes.
- Fee income.
- Provider costs.
- Staffing.
- Operational losses.
- Funding.
- Adverse scenarios.
Where the firm promises reimbursement or other financial support, incorporate the proposed exposure into its planning and legal review.
The financial model should reflect the commitments described to customers.
12. Prepare the Application Evidence
A practical pack may include:
| Evidence | Purpose |
| Staking perimeter analysis | Explain the activity and any exclusions |
| Permission and territorial assessment | Establish the proposed route |
| Service lifecycle | Map entities, assets and decisions |
| Customer terms and disclosures | Explain rights, risks and fees |
| Consent journey | Demonstrate customer instruction records |
| Validator review | Support selection and oversight |
| Asset and reward records | Explain customer entitlements |
| Governance documents | Allocate decisions and escalation |
| Financial forecasts | Support resources and commitments |
| Testing and remediation | Evidence readiness |
Run simulations involving delayed unstaking, incorrect rewards, validator failure and a customer dispute.
Record the expected response, actual outcome, deficiencies and retesting.
How CRYPTOVERSE Can Support Your Staking Application
CRYPTOVERSE is a specialist legal and regulatory firm for UK FCA cryptoasset authorisation support.
We can help assess staking activities, review exclusions and additional permissions, prepare customer documentation and organise supporting application evidence.
Our approach connects the legal analysis with asset control, provider arrangements, rewards and customer instructions.
Contact CRYPTOVERSE to discuss FCA authorisation support for your crypto staking business.
FAQs
1. Does every staking-related service require authorisation?
No. Assess the activity, business and territorial tests, and applicable exclusions.
2. Is operating a validator automatically excluded?
The technical-services conditions and complete role need examination.
3. Does a staking permission cover custody?
Custody and arranging safeguarding require separate assessment where relevant.
4. Is a yield product necessarily qualifying cryptoasset staking?
No. Establish whether assets are used in blockchain validation and analyse the actual transactions.
5. Can auto-staking rely on a single consent arrangement?
The final rules contain specific provisions. Review the agreed service, disclosures and instruction structure before designing the journey.