By CRYPTOVERSE Legal Consultancy
FCA crypto applications encounter problems when the applicant cannot clearly explain its business, demonstrate appropriate arrangements or support its statements with reliable evidence. Missing information, inconsistent documents and unresolved operational dependencies can prevent meaningful assessment.
The FCA warns that poor-quality crypto applications may be rejected if they lack minimum information, delayed during assessment or ultimately refused. For existing businesses, application deficiencies can also affect continuity when the expanded regime begins. www.fca.org.uk
These outcomes are not interchangeable. Understanding the problem—and its legal and practical consequences—is the first step towards resolving it.
This article draws on published FCA expectations and identifies preparation weaknesses firms should test before submission. It does not present historical MLR application outcomes as a prediction of future FSMA authorisation results.
Rejection Withdrawal and Refusal Mean Different Things
The FCA identifies approval, rejection, withdrawal and refusal as possible outcomes for MLR cryptoasset registration applications. FCA
| Outcome or situation | Practical distinction |
| Rejection for insufficient information | The submission does not contain the information needed for assessment |
| Further information requests | The FCA requires clarification or supporting evidence |
| Withdrawal | The applicant ends the application |
| Refusal | The regulator determines that the relevant standards are not met |
| Approval | The applicable registration or permission is granted |
The precise process and procedural rights depend on the application route.
A remediation strategy should begin with the actual correspondence. Do not describe every unsuccessful application as “rejected” or assume that withdrawal removes the underlying issues.
1. The Application Route or Permission Scope Is Unclear
A company may begin drafting before determining whether it needs MLR registration, new FSMA authorisation or a variation of permission.
Within the chosen route, the requested activities may also fail to match the operating model.
For example, a business may describe itself as an intermediary while its contracts and wallet arrangements indicate additional asset-control functions.
How to Resolve It
Complete an activity, token and territorial assessment. Then produce a permissions matrix linking each business function to the relevant entity and legal analysis.
The FCA’s PS26/18 provides final perimeter guidance, while its broader application observations identify legal analysis and references to PERG as useful preparation practices. www.fca.org.uk
Completion evidence: A settled scope reflected consistently across the forms and supporting documents.
2. The Business Plan Describes Ambition Without Operations
Statements about market opportunity do not explain how the regulated business functions.
Weak descriptions leave unanswered questions about customer contracts, execution, settlement, custody, revenue and accountability.
How to Resolve It
Describe the actual service step by step. Identify who performs each function, where it occurs and which agreement governs it.
The FCA’s sample business plan guidance outlines the subjects it typically expects an RBP to address, including services and compliance arrangements. It should be adapted to the applicant’s route and model. FCA
Use customer journeys and transaction diagrams where they clarify the explanation.
Completion evidence: A plan that management can explain and reconcile with contracts, procedures and forecasts.
3. Policies Are Generic or Do Not Match the Business
A template can provide structure, but it may describe controls the firm does not use or risks it does not face.
An illustrative problem would be an AML policy describing manual review while the application claims automated monitoring, without explaining how the two interact.
How to Resolve It
Review each policy against:
- Actual products and customers;
- Selected systems;
- Responsible personnel;
- Escalation arrangements;
- Geographic risks; and
- Recordkeeping procedures.
For MLR registration, the FCA expects the framework to be tailored to the cryptoasset business. www.fca.org.uk
Completion evidence: Approved procedures matching the operating model, supported by relevant implementation records.
4. Implementation Claims Lack Evidence
The application says a control is operational, but the firm cannot demonstrate configuration, testing or use.
This can affect financial crime monitoring, reconciliations, supplier oversight and recovery arrangements.
How to Resolve It
Distinguish clearly between:
Documented · Approved · Implemented · Tested · Verified
For each material statement, identify its supporting record.
| Claim | Evidence to consider |
| Monitoring is operational | Configuration and testing records |
| Alerts are investigated | Anonymised case records |
| Recovery arrangements work | Exercises and remediation results |
| Governance oversight operates | Reports and decision records |
| Funding is available | Financial records and commitments |
Do not manufacture historical evidence for a new business. Use accurate testing and readiness records, explaining their scope and limitations.
5. Personnel Arrangements Are Unconvincing
An organisation chart may name people without demonstrating relevant competence, authority or availability.
For MLR applications, the FCA expects the MLRO to be heavily involved in preparation and explains its expectations concerning experience and continuity of appointment. FCA
How to Resolve It
Review appointment status, responsibilities, time commitments and competing roles. Confirm access to information and escalation authority.
Where recruitment remains outstanding, disclose it accurately and assess its effect on readiness.
Completion evidence: Appropriate appointment materials, responsibility descriptions and a credible staffing plan.
6. Financial Information Does Not Support the Applicant
Forecasts may omit material costs, rely on unexplained assumptions or describe only part of the applicant’s business.
The FCA states that financial information must align with the legal entity seeking authorisation, rather than represent only a portion of it. It also requests supporting assumptions. FCA
How to Resolve It
Reconcile forecasts with the business plan, staffing and supplier arrangements.
Distinguish available funding from expected investment. Review downside scenarios and the applicable financial resource requirements.
For relevant cryptoasset firms, assess COREPRU and CRYPTOPRU. www.fca.org.uk
Completion evidence: Explainable forecasts, funding records and applicable resource calculations.
7. Group and Outsourcing Responsibilities Are Unclear
An applicant may depend on overseas affiliates or providers while failing to explain oversight and contractual responsibilities.
The issue is particularly significant where another entity controls assets, technology or customer decisions.
How to Resolve It
Create an entity and supplier responsibility map. Review agreements against the arrangements described in the application.
For international firms, assess the proposed model against the FCA’s FG26/7 guidance. www.fca.org.uk
Identify information access, incident responsibilities, monitoring and exit arrangements.
Completion evidence: A consistent narrative supported by contracts and oversight procedures.
8. Customer Documents Contradict Operational Arrangements
Customer terms may promise services the operating model cannot deliver.
Examples include immediate withdrawals despite lock-up periods, ambiguous asset ownership or fees inconsistent with the forecasts.
How to Resolve It
Review contracts alongside product workflows and activity-specific controls.
For custody, the FCA distinguishes the initial treatment of qualifying cryptoassets and relevant specified investment cryptoassets under different client asset provisions. www.fca.org.uk
Completion evidence: Customer rights, procedures and disclosures describing the same service.
9. The Applicant Treats FCA Questions as a Drafting Exercise
A regulator’s question may expose an unresolved operational or governance issue. Rewording the response will not resolve the underlying deficiency.
How to Resolve It
For each request, record:
- The question asked;
- The underlying concern;
- The information or action needed;
- The accountable owner;
- Supporting evidence; and
- Affected documents.
The FCA expects proactive, open engagement and warns against submitting a poor application on the assumption that willingness to improve it later is sufficient. www.fca.org.uk
Where a correction is needed, explain it plainly and update related materials.
10. Deadline Pressure Overrides Submission Quality
Rushing an incomplete pack can create continuity consequences.
The FCA explains that a rejected submission lacking minimum information, without a subsequent valid application, may be treated as no application for the relevant transitional purposes. www.fca.org.uk
How to Resolve It
Plan backwards from the submission target. Identify blockers early and obtain resources to resolve them.
The application period closes on 28 February 2027, ahead of commencement on 25 October 2027. www.fca.org.uk
Assess timing, application quality and business continuity together. A nominal submission date is insufficient.
A Practical Remediation Method
Use a controlled gap register.
| Issue | Required action | Owner | Closure evidence |
| Unsettled permission scope | Complete perimeter review | [Owner] | Approved matrix |
| Inconsistent documents | Reconcile operating descriptions | [Owner] | Reviewed final versions |
| Control not tested | Complete testing and remediation | [Owner] | Verified results |
| Funding unclear | Confirm resources and assumptions | [Owner] | Supporting records |
Prioritise issues that prevent meaningful assessment. Verify closure rather than accepting a statement that work is complete.
The final review should confirm that the application presents one supportable business model.
What If an Application Has Already Encountered Problems?
Begin with the latest regulatory correspondence and the exact submitted pack.
Assess whether the problem concerns missing information, unmet standards, changed facts or another issue. Consider procedural deadlines and continuity implications before deciding to withdraw, amend or resubmit.
For MLR registration, the FCA notes that pre-application engagement may be particularly useful following rejection or withdrawal. FCA
Resubmission should address the underlying deficiencies with evidence. Repackaging the same materials is unlikely to resolve them.
How CRYPTOVERSE Can Help
CRYPTOVERSE provides specialist legal and regulatory support for UK FCA cryptoasset authorisation.
Our support can include application diagnostics, regulatory scope reviews, remediation plans, document consistency checks and preparation of agreed responses to FCA information requests.
If your application is incomplete, delayed or facing material questions, request an application assessment from CRYPTOVERSE.
FAQs
1. Why do FCA crypto applications encounter problems?
FCA crypto applications may encounter problems because of missing information, unclear business activities, generic compliance policies, insufficient evidence, inconsistent documents, or inadequate financial and operational arrangements.
2. What is the difference between FCA application rejection and refusal?
Rejection may occur when an application lacks the minimum information required for assessment. Refusal means the regulator determines that the applicable standards have not been met. The exact process depends on the application route.
3. How can a business resolve FCA crypto application deficiencies?
A business should review the FCA’s correspondence, identify the underlying issues, update relevant policies and documents, gather supporting evidence, assign responsibility for remediation, and verify that the issues have been resolved before resubmission.
4. What documents and evidence should support an FCA crypto application?
Depending on the application route and business model, supporting materials may include a business plan, compliance policies, financial forecasts, governance records, customer agreements, supplier contracts, and evidence of control implementation and testing.
5. Can a business resubmit an FCA crypto application after rejection or withdrawal?
A business may be able to pursue a further application, depending on the circumstances and applicable requirements. Before resubmission, it should review the regulator’s feedback, address the underlying deficiencies, and consider relevant deadlines and business continuity implications.