
A crypto exchange can have product-market fit, banking conversations in progress, and investor interest on the table – and still fail at licensing because the legal model does not match the product flow. That is the real starting point for how to get a VASP license: not the application form, but the exact way funds, keys, counterparties, and user access move through your system.
Founders often ask the wrong first question. They ask which jurisdiction is fastest. The better question is whether the business actually falls within a virtual asset service provider framework in the target market, and if so, which regulated activities are triggered. A custody wallet, a fiat on-ramp, a token swap engine, OTC execution, staking with control over client assets, and transfer services can lead to different regulatory outcomes even within the same jurisdiction.
How to get a VASP license without starting in the wrong country
There is no universal VASP license. The term comes from the Financial Action Task Force, or FATF, which sets international AML standards, but each country implements them differently. Some jurisdictions use a registration model with heavy AML supervision. Others require a full licensing process with fit and proper review, local substance, compliance staffing, and technical controls. In Europe, the analysis increasingly overlaps with MiCA and national transition rules. In other markets, the regime may sit with the financial intelligence unit, central bank, or securities regulator.
That is why jurisdiction selection is a legal and operational exercise, not a marketing choice. A founder may prefer a country known as crypto-friendly, but if local law requires resident directors, a physical office, outsourced AML restrictions, or prior banking relationships, the timeline and cost can shift quickly. We have seen projects lose three to six months because they formed an entity first and only later discovered that their custody model or token listing plan created additional licensing exposure.
A practical approach starts with a licensing matrix. You map the product against activities such as exchange between virtual assets and fiat, exchange between one or more forms of virtual assets, transfer of virtual assets, safekeeping or administration, and participation in financial services related to an issuer’s offer or sale of a virtual asset. That language comes from the FATF framework and is reflected, with local differences, in many national regimes.
The real licensing test: what your product actually does
Regulators will not rely on your homepage label. If you call the business a software platform but hold user credentials, route orders, intermediate settlement, or exercise discretion over transfers, the legal characterization may still be regulated.
This is where technical architecture matters. A non-custodial interface may reduce licensing exposure in one country, but not if the company controls key elements of transaction execution or earns fees from matched counterparties. Likewise, white-label infrastructure is not a free pass. If your entity faces the customer, performs onboarding, or controls the commercial relationship, regulators may still treat you as the VASP.
For that reason, the first workstream should be legal scoping. Document user journeys, wallet logic, key management, settlement flows, token sourcing, screening controls, fiat touchpoints, and third-party dependencies. If the project includes staking, lending, or yield features, analyze those separately. In some jurisdictions, they trigger additional financial services regulation beyond VASP status.
How to get a VASP license: the step-by-step path
The application itself is only one part of the process. A workable sequence usually looks different from what founders expect.
1. Scope the regulated activity
Start with a legal memo that matches the product to the local statute, regulator guidance, and AML rules. In many countries, the core legal basis will reflect FATF standards, local anti-money laundering laws, and regulator rulebooks. In the EU context, MiCA, AML directives, national virtual asset statutes, and company law all matter together.
This stage should answer four business-critical questions: whether a license or registration is required, which entity should hold it, whether the current product design increases regulatory burden, and what restrictions will apply after approval.
2. Build the right entity and governance model
Many applications fail before filing because the corporate structure is wrong. Regulators typically review beneficial ownership, source of funds, board composition, internal controls, and local presence. If cap table documents are inconsistent, nominee structures are unclear, or decision-making is concentrated in people who cannot pass fit and proper review, the file becomes weak.
You also need governance that exists beyond paper. Compliance officer, MLRO, risk oversight, incident escalation, and board reporting lines should reflect how the company actually operates.
3. Prepare AML/KYC and risk controls
This is usually the heaviest part of the file. A serious VASP application needs a documented AML framework, customer risk assessment methodology, sanctions screening logic, transaction monitoring rules, suspicious activity escalation, blockchain analytics workflow, record retention, staff training, and independent review procedures.
FATF Recommendation 15 and its interpretive guidance are central here, especially around virtual asset risks and the travel rule. Depending on jurisdiction, you may also need a business-wide risk assessment, product risk scoring, enhanced due diligence policies, and outsourcing controls for KYC vendors or screening providers.
4. Evidence operational readiness
Regulators increasingly want proof that controls are implemented, not merely drafted. That may include screenshots of onboarding flows, sample alerts, customer classification logic, custody arrangements, key management standards, complaint handling procedures, cybersecurity policies, and data protection documentation.
This is where legal and product teams need to work together. If your policy says one thing and your onboarding funnel does another, the inconsistency is easy to spot.
5. File, respond, and refine
After submission, expect questions. Regulators often ask for clarifications on token listings, geographic restrictions, source of liquidity, outsourced development, smart contract dependencies, and how the platform blocks prohibited users. A fast, coherent response process can materially improve timing.
Common mistakes that slow down approval
The most common mistake is treating how to get a VASP license as a document collection exercise. It is a regulatory design project. If the business model is unclear, the policies become generic, and generic policies are easy to challenge.
Another recurring issue is underestimating AML operations. Founders may assume a vendor solves compliance. In practice, vendors support controls, but the regulated entity remains responsible for customer due diligence, alert governance, suspicious activity decisions, and regulator reporting.
We also see problems with cross-border strategy. A company may get licensed in one jurisdiction and then market into another without analyzing local solicitation rules, consumer laws, sanctions exposure, tax presence, or securities implications for listed tokens. A VASP license is not a passport to operate everywhere.
What regulators care about most
In our experience, regulators focus less on slide-deck ambition and more on whether the applicant understands risk concentration. They want to see who controls wallets, how high-risk users are identified, what happens when a transaction is flagged, who can override controls, and whether management can explain the system without hiding behind engineers or vendors.
They also care about consistency. Your legal memo, AML policy, terms of service, product specs, and application answers should describe the same business. If one document says non-custodial, another describes recovery access, and a third implies settlement control, trust drops immediately.
For founders and boards, this has a strategic consequence. Licensing should start before launch architecture is fixed. If legal review comes too late, product redesign becomes expensive.
Timeline, cost, and the “it depends” reality
There is no honest single answer on timing. In a straightforward registration-style regime, a prepared applicant may move relatively quickly. In a fuller licensing environment with substance requirements, the process can take many months. Delays often come not from the regulator but from incomplete shareholder documents, weak AML drafting, vendor gaps, or changes in product scope mid-process.
Cost also depends on what you are building. A plain exchange service with limited jurisdictions is one thing. A custody-heavy, multi-asset platform with fiat rails, institutional onboarding, and travel rule implementation is another. Legal fees, local directors, compliance staffing, office requirements, audits, and technology stack costs should be budgeted together.
If you are structuring a crypto exchange, wallet, OTC desk, or custodial service and need a jurisdiction-by-jurisdiction licensing strategy, our team at Web3.Pro helps founders align product design, AML architecture, filings, and regulator communications so the application matches the business you are actually building.
A practical founder checklist before filing
Before you submit anything, pressure-test five points. First, can you explain in plain English whether you ever control client assets or transaction execution. Second, are your shareholder and source-of-funds documents complete and defensible. Third, does your AML framework reflect actual user journeys. Fourth, have you mapped every outsourced function, including development, KYC, hosting, and analytics. Fifth, have you checked whether your token universe creates securities, sanctions, or consumer-protection issues in target markets.
If one of those answers is shaky, filing early rarely helps. It usually creates more regulator questions and a weaker record.
The strongest applications are not the ones with the most pages. They are the ones where legal, compliance, operations, and engineering tell the same story – clearly, consistently, and with evidence. That is the difference between chasing a license and building a business that can keep it.

