Eligibility & Fit-and-Proper Standards
MSB licensing is assessed against governance integrity, ownership transparency, operational readiness, and the credibility of AML/CFT controls. This page summarizes typical eligibility elements reviewed during licensing and counterparty onboarding.
Eligibility overview
Eligibility is not only “who you are” but “how you operate.” Assessments typically focus on: (1) the integrity and competence of decision makers, (2) transparency of ownership and control, (3) the existence of an accountable compliance function, and (4) operational capability to execute safely at scale.
Governance integrity
Fit-and-proper leadership with clear accountability and escalation capability.
Ownership transparency
Clear UBO mapping and control relationships; no ambiguity in beneficial ownership.
Operational readiness
Systems, staffing, and workflows capable of managing transaction and compliance risk.
Fit-and-proper assessment pillars (typical)
Governance expectations
Governance is assessed through accountability design: who approves risk decisions, who signs off on controls, who owns compliance outcomes, and how management information is produced and escalated.
Minimum governance indicators
-
Defined management rolesClear decision rights for product, risk, and compliance changes.
-
Independent escalationCompliance function can escalate without operational interference.
-
Documented policiesPolicies mapped to process steps and system controls (not standalone PDFs).
-
Management informationReporting on alerts, investigations, complaints, and corridor exposure.
Common governance failures
-
Single-person controlNo separation of duties across operations, finance, and compliance.
-
Unclear UBO influenceOwners making decisions without formal governance roles or oversight.
-
Compliance as “paper”Policies not implemented through monitoring, evidence, and audit trails.
-
Scope driftLaunching products/corridors without assessing risk and updating controls.
Ownership and control transparency
Ownership transparency reduces impersonation and shell risk. Applicants should expect scrutiny of beneficial ownership (UBO), control rights, and relationships between entities in the operating structure.
UBO clarity is non-negotiable
Banks and payment partners typically reject onboarding files where beneficial ownership is unclear, indirect control is undisclosed, or corporate structures are inconsistent across submissions.
UBO mapping
Shareholding and control paths clearly presented, including indirect ownership where applicable.
Group structure
Entity relationships and roles (operator vs. service company vs. holding) clearly defined.
Control rights
Board rights, veto rights, and decision influence disclosed where relevant.
Compliance function requirements
The compliance function is assessed as a real operating capability, not a named person on a chart. Expectations typically include authority, independence, resources, and a documented monitoring approach aligned to the business model.
Minimum expectations
-
Designated compliance leadClear responsibility for AML programme execution and reporting.
-
Policies + proceduresCDD, monitoring, screening, investigations, STR, recordkeeping.
-
Monitoring planRules, thresholds, sampling, QA, and escalation documented.
-
Training and controlsStaff training and evidence of enforcement for process compliance.
Evidence that matters
-
Alert/investigation logsExamples of how monitoring triggers are handled and documented.
-
Sanctions workflowScreening results, escalation, and disposition trail.
-
Record retentionAbility to retrieve files quickly for supervisory or bank requests.
-
Management reportingPeriodic MI reports to leadership on risk indicators.
Recommended next step
Review AML/CFT expectations and ensure your compliance programme is mapped to your exact transaction flows and corridor risk profile.
Operational readiness
Operational readiness is assessed through systems capability, staffing, and documented workflows. This includes how funds are received, processed, safeguarded, reconciled, and settled—plus how exceptions are handled.
Systems and auditability
Transaction logs, user access controls, and the ability to produce evidence for reviews.
Safeguarding discipline
Reconciliation frequency, segregation controls (where used), and exception handling.
Customer support controls
Complaints handling, dispute workflows, refunds, and communications discipline.