Contact & Application Intake
This page is intended for structured enquiries relating to MSB licensing, application readiness, document coordination, and administrative intake. The fastest responses usually come from enquiries that clearly state the proposed business model, requested scope, current stage of preparation, and whether a Registered Agent has already been appointed.
Purpose of the intake channel
The intake function is not just a generic contact inbox. It is intended to triage whether an enquiry is informational, application-stage, clarification-stage, or administrative in nature so that communication remains structured from the start.
Pre-application enquiries
Used for questions on scope, documentation readiness, and whether the model fits the MSB category.
Application-stage coordination
Used where a file is being assembled and clarification is needed on structure, sequencing, or intake expectations.
Administrative contact
Used for file references, payment-reference follow-up, register-related guidance, and official communication routing.
Best way to avoid back-and-forth
State the business model plainly, identify the requested scope, explain where funds move and where they sit, and list what documents are already prepared. Vague enquiries create vague replies. Clean inputs get cleaner handling.
What to prepare before making contact
The contact process works better when the enquiry arrives with a coherent outline rather than a broad “how do we get licensed?” message. At minimum, the intake team should be able to tell what the applicant wants to do and whether the requested activity appears to align with the licensing category.
Describe in plain language what the business does, who the customers are, and how money moves through the model.
State whether the proposed activity relates to remittance, FX services, payment processing, stored value, agent distribution, or related MSB functions.
Identify where customers are located, where funds originate, and where they are intended to be sent or settled.
Indicate whether the business plan, AML/CFT programme, ownership chart, funds-flow narrative, and safeguarding explanation already exist.
Typical enquiry categories
Not every message is the same. Categorizing the enquiry correctly from the beginning reduces delays and limits pointless follow-up.
Informational enquiries
-
Scope interpretationQuestions about whether a business model fits within MSB activity boundaries.
-
Document expectationsQuestions about what materials are generally expected at submission stage.
-
Register verificationQuestions regarding status checks, register fields, and formal confirmation pathways.
Application-stage enquiries
-
Intake sequencingQuestions about when to submit, whether the file is ready, and how to reduce clarification cycles.
-
Administrative coordinationQuestions related to file references, payment allocation, and Registered Agent routing.
-
Supplemental document handlingQuestions about how clarifications, corrections, or replacement documents should be routed.
Communication standards
Enquiries should be clear, concise, and tied to an identifiable subject. The intake process is administrative, not mystical. Messages that bury the real question under sales copy, generic marketing language, or half-explained ambition waste time for everyone.
Use exact entity names
Legal names, proposed names, and file references should be stated consistently.
Use one coherent narrative
Do not describe one business model in the email and a different one in the attachment set.
Use the right supporting detail
Enough information to classify the enquiry is useful; random document dumping is not.
Fastest route to a useful reply
One subject line, one entity name, one requested scope, one short model summary, and one note on document readiness. That usually beats a wall of text trying to sound impressive.
Contact points and routing logic
Exact communication channels and operational handling may vary. As a general rule, the enquiry should be routed to the function most closely tied to the real issue, not the most dramatic-sounding one.
Application intake
Used where a prospective applicant needs to determine readiness, file structure, or whether a proposed model is appropriately framed for submission.
Administrative follow-up
Used where there is an existing file reference, payment issue, register-related query, or official communication that needs routing or clarification.
Final practical note
If you are not yet ready to explain the business clearly, you are probably not ready to submit. Use the intake stage to clarify the model before the file becomes a mess.