Application Process & Assessment Stages
The MSB licensing process is structured around completeness discipline, risk-based assessment, and supervisory clarity. This page explains the stages, common delays, and what evidence reviewers typically expect at each point.
Process overview
Applications are assessed in stages: intake, completeness, substantive assessment, clarifications (if needed), decision, and register publication. The fastest outcomes occur when scope and flows are coherent and AML controls are demonstrably implemented.
Completeness first
Incomplete packs are paused; processing clocks typically stop until corrected.
Risk-based assessment
Higher-risk corridors and complex models trigger deeper review and evidence requests.
Publication outcomes
Decision outcomes are reflected through register entries and official notices.
Pre-submission advantage
Most delays happen because the scope narrative changes mid-file. If you lock scope early and build the AML programme around real transaction flows, clarifications reduce sharply.
Stages and what reviewers look for
Stages are described below. Timelines vary by complexity, applicant readiness, and responsiveness to clarifications.
Scope selection, funds flow diagrams, AML programme mapping, and onboarding evidence pack readiness.
Registered Agent submission, fee confirmation (where applicable), and file assembly validation.
Checklist-based review: missing documents, inconsistencies, unsigned declarations, scope misalignment.
Governance, ownership transparency, safeguarding logic, AML/CFT effectiveness, systems capability.
Requests for information where gaps exist; processing pauses may apply until responses are received.
Approval, approval with conditions, deferral, or refusal. Conditions may include reporting or scope constraints.
Publication of license number, status, scope, and effective dates through the Public Register.
Periodic reporting, data requests, and supervisory engagement to validate control effectiveness over time.
Common delay drivers
These are the recurring issues that slow processing and create iterative clarification cycles.
Documentation gaps
-
Scope not defined preciselyScope drift across business plan, policies, and disclosures.
-
Weak AML evidencePolicies without monitoring rules, alert logs, or investigation workflows.
-
UBO ambiguityInconsistent ownership mapping or missing control disclosures.
-
Safeguarding unclearNot stating where funds sit and how reconciliation and access controls work.
Operational readiness gaps
-
No systems auditabilityInability to produce logs and evidence quickly.
-
Partner reliance not explainedProcessors/settlement partners not described or due diligence missing.
-
Staffing mismatchCompliance staffing not aligned to proposed volumes and risk exposure.
-
Unclear corridorsHigh-risk jurisdictions without enhanced controls and rationale.
Reduce clarification cycles
The strongest submissions include: scope matrix, funds flow diagram, AML mapping table, reconciliation SOP, and an evidence index that points to logs, dashboards, and governance approvals.
Decision outcomes and next steps
Outcomes are based on evidence and risk. Conditions may apply where controls are adequate but require ongoing monitoring or remediation.
Approval
License issued within defined scope; register publication follows.
Approval with conditions
License issued with restrictions or reporting requirements until controls mature.
Deferral / refusal
File paused or rejected where risk is unmanaged or evidence is insufficient.
After approval
Treat approval as the start, not the finish. Ongoing supervision expects evidence: monitoring, MI reporting, training logs, safeguarding discipline, and prompt responses to data requests.