How to answer a regulator's request for information without delaying your licence
A regulator's request for information can feel like a test of your patience, but it is really a test of your processes. Answer it well and your licence application keeps moving; answer it poorly and you add weeks or months to your timeline.
Why regulators ask for information (and why speed matters)
During a licensing review, a regulator such as a national competent authority under MiCA or a financial supervision body in an offshore jurisdiction will often send a request for information. This is not a sign that your application is failing. It is a normal part of the review process. The regulator needs to clarify something in your business plan, verify a document, or test whether your compliance framework is actually operational. The faster and more clearly you respond, the faster the file moves to the next stage.
Many applicants lose time not because the request was difficult, but because the response was slow or incomplete. A delayed answer can push your file to the back of the queue. In some jurisdictions, a regulator may pause the clock on your application until it receives a satisfactory response. That pause can turn a four week review into a three month wait. Treat every request as a priority, even if it looks minor.
First 48 hours: triage the request and assign an owner
When the request arrives, do not forward it to a general inbox. Within the first few hours, read it carefully and list every single question or document the regulator has asked for. Regulators often bundle several points into one paragraph. If you answer only the obvious question and miss the sub-point, you will likely receive a follow-up request, which costs another cycle. Create a checklist and number each item.
Assign one person as the response owner. This person does not need to write every answer, but they must track every item to completion. In a small team, that might be your compliance officer or an external consultant. The owner should confirm receipt with the regulator within one business day if the regulator has not specified a deadline. A short acknowledgement shows you are engaged and gives you a little breathing room to prepare a full answer.
Set an internal deadline that is earlier than the regulator's deadline. If the regulator gives you ten business days, aim to submit in seven. This buffer absorbs internal delays, such as waiting for a director's signature or a translated document. It also leaves time for a quality check before submission.
How to draft answers that reduce follow-up questions
Answer the question that was asked, not the question you wish had been asked. If the regulator asks how you will monitor transactions for suspicious activity, do not send your entire AML policy. Send a concise explanation of the monitoring system, the thresholds you use, and who reviews alerts. Attach the relevant policy section only if it directly supports your answer. Long, unfocused responses create more work for the reviewer and increase the chance of another request.
Use plain language and structure. Number your answers to match the regulator's numbering. For each item, state the answer first, then provide supporting detail. If a question requires a document, attach it with a clear file name, such as 'AML_Policy_2026.pdf' rather than 'document1.pdf'. If a document is in a language other than the regulator's working language, include a certified translation. Missing translations are a common cause of delay.
Where you do not know the answer, say so and explain how you will find out. Regulators generally prefer an honest 'we are confirming this with our banking partner and will provide an update by Friday' over a vague or inaccurate statement. If you need more time, ask for a specific extension before the deadline passes. A polite request for an extension is almost always better than a late, incomplete response.
Common mistakes that delay a licence
One of the most frequent mistakes is sending documents that are inconsistent with earlier submissions. If your business plan says you will serve retail clients in three countries, but your AML risk assessment mentions only one, the regulator will ask why. Before you submit, cross-check your answers against your original application and any previous correspondence. Consistency builds credibility.
Another mistake is copying and pasting generic answers from a template or another jurisdiction. MiCA, for example, has specific requirements for CASPs, including capital tiers of EUR 50,000, 125,000, or 150,000 depending on the services you provide. A generic answer that ignores these specifics signals that you have not read the relevant rules. Regulators notice this and will probe further.
A third mistake is failing to keep a record of what you sent and when. If a follow-up request arrives six weeks later, you need to know exactly what you said previously. Maintain a simple log with the date, the items requested, the documents provided, and the date of submission. This log becomes your defence if there is any dispute about timelines.
When to bring in an external licensing consultant
If the request involves complex areas such as prudential requirements, governance, or cross-border passporting, an external consultant who has handled similar requests can save you time. They know the regulator's typical concerns and can help you frame answers that pre-empt follow-up questions. This is especially useful if your internal team is small or if you are applying in a jurisdiction where you have limited experience.
A consultant can also act as a buffer. They can communicate with the regulator on your behalf, manage deadlines, and ensure that translations and formatting meet expectations. For founders who are also running the business, this delegation reduces the risk of the request sitting unanswered while you focus on product or fundraising.
However, do not hand over the process entirely. You remain responsible for the accuracy of every statement. Review every draft before it is submitted. The consultant's role is to improve speed and clarity, not to replace your judgement.
After you submit: follow up and prepare for the next round
Once you submit your response, confirm receipt with the regulator if you have not received an automatic acknowledgement. Then wait. Do not send daily emails asking for an update. If the regulator gave a timeline for review, respect it. If that timeline passes without word, a single polite follow-up is appropriate. Use that follow-up to reiterate your willingness to provide further information.
In many cases, a request for information is followed by another request. This does not mean you did something wrong. It often means the regulator is working through its checklist. Keep your response owner in place and keep your document log updated. The second request is usually narrower and faster to answer if your first response was well organised.
Finally, treat the entire exchange as part of building a relationship with the regulator. Clear, timely, and honest communication during the application phase sets the tone for how you will interact once licensed. A regulator that trusts your responses is less likely to escalate minor issues later.
How to Choose the Right Jurisdiction
Work the decision in this order: customers first, everything else second:
- Who are your customers? EU retail means you need a MiCA passport (Lithuania, Malta or another EU CASP). US customers mean state-by-state money-transmitter licensing or a FinCEN MSB, so consider a Canada MSB or a US setup. Latin America, Asia or HNW clients mean an offshore or territorial base such as Panama is usually the better fit.
- Do you need a regulator badge? A public-facing exchange chasing institutional partners and fundraising often needs the reputational lift of an EU, Swiss or VARA licence. An OTC desk or token treasury usually does not.
- What is your budget and timeline? Offshore and territorial routes set up in weeks for tens of thousands; premium onshore licences take many months and six figures.
- What about tax? Territorial-tax jurisdictions like Panama charge 0% on foreign-source income; EU jurisdictions apply standard corporate tax. Factor total cost of ownership, not just setup fees.
For many offshore-first founders, Panama lands at the intersection of fast incorporation, low cost and 0% tax on foreign-source income, which is why it features so heavily in our work. But the honest answer is that the “best” jurisdiction is the one that matches the four answers above, and that is a conversation worth having before you spend a cent. See our cost breakdown and application process to ground the decision in real numbers.
Banking and Compliance: Where Most Setups Actually Stall
Incorporation is the easy part of any crypto project. Banking is where timelines slip and where under-prepared founders lose months. Since 2023, banks and payment processors worldwide have tightened their onboarding of crypto-adjacent businesses, and they now expect a genuinely professional application , not a one-page business summary. A thin file is simply rejected, and re-applying with the same bank is far harder than getting it right the first time.
Three documents do the heavy lifting. The first is a written AML/KYC compliance program: your customer-onboarding flow, transaction-monitoring rules, sanctions and PEP screening, a named compliance officer, and record-keeping policies. The second is a clear, evidenced source-of-funds file for both the company and its beneficial owners. The third is a coherent business description that explains who your customers are, how money moves, and what volumes you project. Banks approve businesses they understand; ambiguity reads as risk.
Sequencing matters as much as substance. The correct order is: incorporate the operating entity, build the compliance program, assemble the source-of-funds package, and only then approach banking, ideally through a warm introduction rather than a cold application. Founders who approach banks mid-setup, before their file is complete, create the very delays they are trying to avoid. We make direct introductions to banks and crypto-friendly payment rails as part of every engagement, but the introduction only works if the file behind it is ready.
None of this is optional, and none of it changes much from one jurisdiction to the next, the compliance bar is now broadly global. What changes is the appetite of local banks and the speed of onboarding. Our requirements checklist sets out exactly what you need to assemble before you approach a bank.
Crypto Licensing in 2026: The Bigger Picture
Choosing where to license a crypto business in 2026 is no longer a simple cost calculation. The regulatory map has hardened considerably over the last three years. In the European Union, the Markets in Crypto-Assets Regulation (MiCA) has replaced the patchwork of national VASP registers with a single Crypto-Asset Service Provider (CASP) authorisation that passports across all 27 member states. That passport is powerful, but it comes with capital requirements, governance obligations and a multi-month authorisation process that smaller projects often underestimate.
Outside the EU, the picture is more varied. Offshore and territorial-tax jurisdictions compete on speed, cost and privacy, while major financial centres such as Switzerland, the UAE and Singapore compete on credibility and institutional access. The Financial Action Task Force (FATF) sits over all of them: its “travel rule” and AML standards now apply, in some form, almost everywhere a serious crypto business would consider basing itself. Jurisdictions that ignore FATF expectations end up grey-listed, which quietly closes correspondent-banking doors for every company registered there.
This is why the question behind How to answer a is rarely “which licence is cheapest?” It is “which regime matches my customers, my risk appetite and my banking needs?” An EU-retail exchange and an offshore OTC desk serving high-net-worth clients in Latin America have almost nothing in common in terms of the right base. Getting this decision right at the start saves you from the single most expensive mistake in the industry: licensing in the wrong place and having to re-domicile a live business.
Consulting24 has guided more than 200 crypto company setups across 15+ jurisdictions since 2017, which means we have seen how each of these regimes behaves in practice rather than just on paper. The summary below is the same framework we use with clients, and we are always happy to map it to your specific model. Start with our Panama vs Lithuania comparison to see how the trade-offs play out between an offshore base and an EU-passported one.
Common Mistakes to Avoid
The failures we see when founders research How to answer a on their own are remarkably consistent, and almost all of them are avoidable. The first is licensing to the headline tax rate. A 0% jurisdiction is worthless if your customers legally require a regulated provider you cannot become there, and you will simply have to start again. Decide who you are allowed to serve first, then optimise for tax.
The second is treating the compliance program as paperwork. The AML/KYC program is not a formality to satisfy a regulator; it is the document your bank reads most closely. A generic template downloaded from the internet is transparent to any compliance officer and will sink your banking application. It needs to reflect your actual product, customer base and risk profile.
The third is underestimating banking lead time. Founders routinely budget for incorporation and forget that the bank account, the thing that actually lets the business operate, can take longer than the licence itself. Build banking into your launch timeline from day one, not as an afterthought.
The fourth is ignoring personal tax residency. A company in a low-tax jurisdiction does not erase your obligations where you personally live. Many founders create unexpected liabilities by structuring the company perfectly and ignoring themselves. We introduce qualified tax advisors precisely to close this gap.
The fifth and most expensive is choosing a provider on price alone. The cheapest setup that results in a rejected bank application or a re-domiciliation is far more expensive than doing it properly once. Ask any provider to itemise their fee and explain their banking track record before you commit.
What Happens After You Are Licensed
Getting licensed and banked is the start, not the finish. Every regulated or registered crypto business carries ongoing obligations, and letting them lapse is how companies lose their standing, and their banking. At minimum you will maintain a registered agent or local presence, file annual renewals or supervision fees, keep accounting records, and keep your compliance program live with periodic reviews and updated sanctions and PEP screening lists.
Most jurisdictions also expect you to keep your beneficial-ownership information current and to report material changes, new directors, new shareholders, a pivot in business activity, promptly. Transaction monitoring is not a one-time setup either; screening rules need tuning as your volumes and customer mix evolve. Banks may request periodic refreshes of your KYC and source-of-funds documentation, particularly after a year of trading or a significant change in activity.
This is why we offer ongoing maintenance on an annual retainer rather than treating setup as a one-off transaction. The cost of staying compliant is a fraction of the cost of losing a banking relationship and having to rebuild one from scratch. Plan for it in your year-two budget from the outset, and treat your compliance function as a living part of the business rather than a box you ticked at launch.
It is also worth planning ahead for growth. A structure that suits a pre-revenue startup may not suit the same company once it is processing meaningful volume, adding new product lines, or expanding into new markets. Many of the businesses we work with begin in a fast, low-cost offshore base to validate the model, then add a second regulated entity, an EU CASP, for example, once revenue justifies the cost and the market access genuinely matters. Designing the first structure with that possible second step in mind keeps your options open and avoids a disruptive re-domiciliation later. We map this growth path out with clients during the initial planning stage so the early decisions support, rather than constrain, where the business is heading.
Consulting24 has completed 200+ crypto company setups across 15+ jurisdictions. Talk to our team for a fixed-fee proposal and realistic timeline.
Learn more WhatsApp usEmail mardo@consulting24.co · Phone +372 58155779
About Consulting24 & Mardo Soo
Founder & CEO, Consulting24 · LinkedIn
Consulting24 is an eight-year-old advisory firm that has completed 200+ crypto company setups across 15+ jurisdictions since 2017. Founder and CEO Mardo Soo and the team specialise in crypto, VASP and exchange licensing, from Panama and the EU (MiCA) to Dubai, Canada and the offshore world. We don't push a single “best” jurisdiction; we map your business to the regime that actually fits, then handle incorporation, the AML/KYC compliance program, and banking and payment-processor introductions end to end.
Every engagement begins with an honest conversation about your customers, budget and timeline and ends with a fixed-fee proposal, so you know the all-in number before you commit. We also introduce vetted local lawyers and tax advisors wherever your structure requires them.
Operated by X24Consulting OÜ (Estonian Business Register code 16971898), Põrdi tn 3-63, 10156 Tallinn, Estonia · mardo@consulting24.co · +372 58155779
Frequently Asked Questions
How quickly should I respond to a regulator's request for information?
Acknowledge receipt within one business day. Aim to submit a full response within seven business days if the regulator allows ten, or sooner if the deadline is shorter. Always check the specific deadline in the request and ask for an extension before it passes if you need more time.
What if I do not understand what the regulator is asking?
Do not guess. Ask a clarifying question in writing, referencing the specific item number. A short email that asks for clarification is better than submitting an answer that misses the point. If you have an external consultant, they can often help interpret the request based on experience with that regulator.
Can a request for information delay my licence application?
Yes, if you respond late or incompletely. Many regulators pause the review clock until they receive a satisfactory response. A well-organised, timely answer keeps the file moving. A poor answer can add weeks or months.
Should I send my entire compliance manual or just the relevant sections?
Send only what is asked for. If the regulator requests your AML policy, send the policy. If they ask how you monitor transactions, send a concise explanation with the relevant policy excerpt. Overloading the reviewer with unnecessary documents slows the process.
Do I need to translate documents for the regulator?
If the regulator's working language is not the language of your document, yes. Certified translations are often required. Missing translations are a common cause of delay, so check the requirement early and budget time for translation.
What if my answer changes something in my original application?
Be transparent. Explain the change and why it is necessary. Regulators expect some evolution, but they do not like surprises. If the change is material, such as a shift in target market or services, provide a clear rationale and any supporting documents.
How many follow-up requests should I expect?
It varies by jurisdiction and the complexity of your application. One or two rounds of follow-up questions are common. A well-prepared first response can reduce the number and scope of subsequent requests.
Should I hire a consultant to handle the response?
If the request is complex, or if your team lacks experience with that regulator, a consultant can help. They can draft responses, manage deadlines, and reduce follow-up questions. For straightforward requests, you may handle it internally. For more guidance, see https://www.consulting24.co/es/.
Related reading
More crypto-license guides on this blog
- Crypto License in Panama: Cost, Requirements & Setup (2026)
- Crypto Exchange License: How and Where to Get One in 2026
- Crypto License Cost by Jurisdiction: 2026 Comparison
Related crypto licensing routes
A few relevant guides on consulting24.co, each with real cost, timeline and requirements:
This article reflects 2026 market conditions and is general guidance, not legal or tax advice. Regulations change, so confirm specifics with qualified counsel before acting. Consulting24 (X24Consulting OÜ, Estonian reg. 16971898) introduces vetted local lawyers and tax advisors during every engagement.
Comments
Post a Comment