EST · MMXXVI
Home/Insights/Guides/Licence Application Readiness Checklist for Digital-Asset Firms
Licensing & Registration

Licence Application Readiness Checklist for Digital-Asset Firms

Licence Application Readiness Checklist for Digital-Asset Firms. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee e

A digital-asset exchange preparing to file for a Virtual Assets Regulatory Authority licence in Dubai discovers, three weeks before submission, that its anti-money-laundering manual references procedures the firm does not yet operate and that two of its five directors lack the regulatory vetting a VASP licence demands. The application stalls. The legal question is not whether the regulator will eventually issue the licence – it is whether the firm can demonstrate, on the day it files, that every element the regime expects is already in place, documented and ready to audit.

Licensing a digital-asset business is not a paper exercise completed after the platform launches. Regulators in every flagship hub – the Virtual Assets Regulatory Authority, the Malta Financial Services Authority, the Monetary Authority of Singapore, the Securities and Futures Commission in Hong Kong and the national competent authorities under MiCA – require that governance, policies, systems, capital and personnel are operational before authorisation is granted. An incomplete application costs time, burns capital and signals to the regulator that the business does not yet understand the obligations it is asking to assume. This checklist walks through the seven categories a digital-asset firm must pressure-test before it submits a licence application in any major jurisdiction.

Does the entity structure match the business model?

The first readiness question is whether the legal entity applying for the licence can hold it under the applicable regime. A VASP licence, a Crypto-Asset Service Provider authorisation under MiCA or a Digital Payment Token service licence in Singapore attaches to a specific legal person in a specific jurisdiction. If the operating entity sits offshore but the user base, banking or material operations sit elsewhere, the regulator will ask why that structure was chosen and whether it creates enforcement or supervisory gaps.

The structure the firm files with must align to the activity the licence permits. If the business model combines custody, exchange and token issuance, the question is whether one licence in one jurisdiction covers all three, or whether the firm needs parallel authorisations. Under MiCA, for example, a Crypto-Asset Service Provider authorisation may permit custody and exchange operations, but an asset-referenced token or e-money token requires a separate issuer authorisation with its own capital and reserve rules. In the United Arab Emirates, the Virtual Assets Regulatory Authority issues activity-based licences; a firm providing custody and operating an exchange applies for both. A common readiness mistake is designing the structure around tax or convenience and discovering, at the point of application, that the chosen jurisdiction does not license the firm's core activity or that it requires the entity to be locally incorporated rather than registered as a branch.

Ownership transparency is mandatory. Every regulator expects a full corporate chart showing ultimate beneficial owners and any parent, subsidiary or affiliated entity with a role in the business. If an individual or corporate shareholder holds more than a jurisdiction-specific threshold – typically between 10 and 25 per cent – that person or entity goes through the same fitness-and-probity vetting the directors undergo. The firm must be able to explain, in the application narrative, why the structure is designed the way it is, how decisions are escalated between entities and where regulatory accountability sits.

For a scoped assessment of whether your entity structure supports the licence you need, contact OBOLUS at info@oboluslaw.com.

Are the directors and key persons vetted and documented?

Every VASP regime designates certain roles as requiring individual regulatory approval. The specific titles vary – "responsible officer", "designated person", "key function holder" – but the concept is universal: the regulator must be satisfied that the individuals controlling the business are fit and proper, that they have relevant experience and that they will be present in the jurisdiction to the extent the regime expects. An application cannot proceed until those individuals are identified, their CVs and personal declarations are prepared and, in some hubs, their background checks are complete.

The minimum officer count depends on the regime. Some jurisdictions require at least two resident directors; others accept non-resident directors provided a sufficient management presence is maintained locally. The Financial Services Regulatory Authority in the Abu Dhabi Global Market, for example, expects a senior executive physically present in the emirate for a meaningful portion of the year. The Malta Financial Services Authority under the prior Virtual Financial Assets framework required a VFA agent – a locally licensed intermediary – to act as a regulatory bridge for the issuer or service provider. Under MiCA, the competent authority in the home member state will assess whether the management body has the collective knowledge, skills and experience to oversee a Crypto-Asset Service Provider.

The most frequent vetting failure is a director with a prior regulatory action, an undisclosed conflict or a gap in the employment or regulatory history that the applicant did not explain in the personal questionnaire. Fitness-and-probity is a proactive standard: if a fact might concern the regulator, the application must surface it, explain the context and demonstrate how the firm has mitigated any residual risk. A second common issue is the "nominee director" – an individual appointed to satisfy a local-presence requirement but who plays no real role in decision-making. Regulators identify this arrangement quickly and will refuse the application or demand that governance is restructured so that accountability is genuine.

Is the required capital in place and auditable?

Most digital-asset licensing regimes impose a minimum initial capital requirement, and many impose ongoing own-funds or net-asset rules that vary by the volume or nature of the activity the firm undertakes. The capital must be unencumbered – available to meet liabilities and regulatory calls – and it must be held in a manner the regulator can verify. An application that states the firm "will" raise the capital or that capital "is committed" but not yet transferred into the applicant entity is incomplete.

The exact threshold is jurisdiction-specific. Under the VASP Act in the British Virgin Islands, for example, the minimum capital depends on whether the service provider is conducting a single activity or multiple activities. The Payment Services Act in Singapore sets thresholds that increase with transaction volume, from the money-changing licence tier up to the major payment institution tier. MiCA's own-funds rules for a Crypto-Asset Service Provider are set by reference to the fixed overheads of the firm, with floors and activity-linked add-ons. The common thread is that the regulator expects the capital to be on the balance sheet, supported by audited or certified financials, at the time the application is submitted.

A related readiness question is the source of funds. If the capital came from token sales, from a loan, from a corporate parent or from individual shareholders, the regulator will ask for evidence of the source and, if the funds moved through a digital-asset exchange or a foreign bank, for the transaction trail that ties the source to the applicant. This is not a suspicion check – it is a verification of financial soundness. If the firm cannot demonstrate that its capital is legitimate, stable and proportionate to the risk it will assume, the application will stall while the regulator waits for satisfactory evidence.

Are the AML, compliance and risk-management policies complete and operation-ready?

A licensing application in any flagship hub requires the firm to submit its anti-money-laundering and countering-the-financing-of-terrorism manual, its compliance and risk-management framework, its cybersecurity and business-continuity policies and, depending on the activity, its custody safeguarding procedures and its customer-onboarding standards. These are not template documents that the firm intends to "finalize after approval." They must describe the controls the firm operates today, with named individuals responsible for each function, defined escalation paths and audit trails that match the firm's actual systems.

The baseline is the Financial Action Task Force Recommendations, including Recommendation 15 on virtual assets and the Travel Rule obligation to transmit originator and beneficiary data with transfers above a jurisdiction-specific threshold. Every major regime incorporates these standards and expects the applicant to demonstrate how it will comply. The anti-money-laundering manual must describe customer due diligence, ongoing monitoring, suspicious-transaction reporting, sanctions screening and record retention. The cybersecurity policy must cover access controls, incident response, third-party vendor risk and penetration testing. The business-continuity plan must explain how the firm will maintain service, protect client assets and report to the regulator if a critical system fails or if a key person is unavailable.

A common application defect is a set of policies written for a different business. If the manual describes fiat onboarding but the firm operates a crypto-only platform, or if it references an outsourced custody provider the firm does not use, the regulator will conclude that the applicant copied a template without tailoring it to the actual operation. Another frequent issue is the absence of a named compliance officer or a money-laundering reporting officer with the authority, independence and resources the role requires. The policies must not only exist – they must be credible, internally consistent and tied to real people and real systems.

If a prior application stalled over policy gaps or if your manual no longer reflects what you operate, write to info@oboluslaw.com for a policy-reconciliation audit.

Do the technical systems match the activity the licence permits?

The regulator will expect a technical narrative that describes, at a functional level, how the platform works: where customer assets are held, how transactions are recorded, how private keys are generated and stored, how the firm segregates client funds from operating funds and how it protects against unauthorized access or a system breach. If the application is for custody, the regulator will ask whether the firm uses hot wallets, warm wallets or cold storage, what multi-signature arrangements are in place and how it reconciles on-chain balances to its internal ledger. If the application is for an exchange, the question is how orders are matched, how the order book is maintained and how the firm prevents front-running or market manipulation.

The technical description does not need to disclose proprietary code, but it must be detailed enough that the regulator can assess whether the architecture is sound and whether it aligns to the policies the firm has submitted. A mismatch – such as a custody policy that assumes cold storage when the firm in fact uses a third-party hot-wallet service – will delay the application while the firm reconciles the inconsistency. If the firm relies on third-party infrastructure – a cloud provider, a blockchain node service, a liquidity aggregator – the application must name the vendor, describe the contractual and technical controls the firm has over that relationship and explain how it will maintain service if the vendor fails or withdraws.

System readiness also includes testing. Some regimes require evidence that the platform has been penetration-tested or that the firm has conducted a simulated incident-response exercise. Others expect a technical audit from an independent assessor. Even where formal testing is not mandatory at the application stage, the firm should be able to demonstrate that its systems are live, that they have processed test transactions and that they perform as the application describes. A platform that exists only on paper or in a development environment is not ready to file.

Are the banking and fiat on-off ramps confirmed?

Most digital-asset businesses require access to traditional banking to serve customers who deposit or withdraw in fiat currency, to pay operating expenses and to hold the capital the regulator mandates. A licensing application that does not address where the firm will bank, or that assumes a bank account will open once the licence is granted, introduces a dependency that can derail the business even if the regulator approves. In practice, many banks will not open an account for a digital-asset firm until it holds a licence, and many licensing authorities expect evidence of banking arrangements before they issue final authorisation. The result is a sequencing problem the applicant must solve before it files.

The solution depends on the jurisdiction and the risk tolerance of local banks. In some hubs – Dubai under the Virtual Assets Regulatory Authority regime, Malta under its prior framework, Lithuania in the early VASP era – certain banks developed digital-asset banking programmes and would engage with applicants that had reached an advanced stage in the licensing process. In other markets, banking access is tighter, and the firm may need to structure its fiat flows through a licensed payment institution or an e-money provider rather than holding a direct commercial bank account. If the business model includes stablecoin on-ramps, the question shifts to whether the firm can establish accounts with the stablecoin issuer or with exchanges that provide liquidity.

The application should describe the banking plan even if final arrangements are not yet confirmed. If the firm has an account, the application states where and under what terms. If the firm is in discussions with a bank or a payment provider, the application says so and explains the expected timeline. If the firm plans to operate without direct fiat rails – for example, a pure crypto-to-crypto exchange – the application must make that clear and demonstrate that the business model does not create an undisclosed fiat exposure. A regulator reading an application that is silent on banking will assume the firm has not thought it through, and that impression alone can delay approval.

Does the structure account for the cross-border reality?

A digital-asset business is rarely confined to one jurisdiction. The entity may sit in Dubai, the directors may be resident in Europe, the development team may work from a third country, the customer base may be global and the banking may sit in a fourth hub. Every regulator understands this, but the application must explain how the firm will manage regulatory obligations, customer protection and data flows across that footprint without creating gaps or conflicts.

The cross-border questions vary by business model. If the firm holds a Crypto-Asset Service Provider authorisation in one European Union member state and intends to passport into others, the application must describe which services will be provided where and how the firm will handle customer complaints, local-language requirements and data-protection obligations in each target market. If the firm is licensing in Singapore under the Payment Services Act but expects a material portion of its user base to come from jurisdictions with their own VASP regimes, the question is whether those users trigger a local registration requirement in their home markets and, if so, whether the Singapore structure allows the firm to comply. If the platform routes transactions through a foreign exchange or custodian, the regulator will ask whether that counterparty is itself licensed and whether the arrangement exposes the applicant to counterparty or sanctions risk.

A frequent oversight is the assumption that a single licence – particularly an offshore licence in a permissive jurisdiction – is sufficient to operate globally. That assumption no longer holds. Most flagship hubs now apply their VASP regimes on the basis of where the customer sits, not where the entity is incorporated. If a platform incorporated in the British Virgin Islands actively markets to users in the European Union, MiCA's authorisation requirement may apply. If it onboards customers in Hong Kong, the Securities and Futures Commission's licensing regime may be triggered. The readiness checklist must include a jurisdiction-mapping exercise: where are the users, where are the service providers, where is the material infrastructure and what licensing, tax or data obligations follow from that map.

To pressure-test your structure against the actual user and banking footprint before you commit, write to OBOLUS at info@oboluslaw.com.

What is the realistic timeline and cost to authorisation?

Licensing timelines in the digital-asset space vary widely by jurisdiction, by the complexity of the business model and by how complete the application is when submitted. A straightforward registration under the Money Laundering Regulations in the United Kingdom may be a matter of weeks if the firm is already operating and the policies are in place. A full Virtual Assets Regulatory Authority licence in Dubai or a Crypto-Asset Service Provider authorisation under MiCA can take months, particularly if the regulator issues information requests or requires the firm to amend its governance or capital structure.

The application fees, supervision fees and any third-party costs – legal, compliance, audit, technical assessment – must be budgeted in advance. Some regimes publish fixed application fees; others scale the fee to the activity or the size of the firm. Ongoing supervision fees are typically annual and are calculated by reference to the firm's turnover, its asset base or a flat rate set by licence type. These figures vary by jurisdiction and by the specifics of the application, and they are not included in this checklist because they change as regimes mature. The firm should obtain current fee schedules from the relevant regulator or from counsel before it begins the application process.

The realistic timeline includes not just the formal review period but the time required to prepare the application, to gather the supporting evidence, to vet and onboard the key persons and to respond to any regulator queries. In our cross-border practice, we see firms underestimate this preparation phase and file prematurely, only to face delays when the regulator identifies gaps that could have been addressed before submission. A better approach is to treat the application as the final step in a readiness process, not the starting gun.

What are the most common readiness mistakes?

The first mistake is treating the application as a compliance formality rather than a business-readiness audit. The regulator is not simply checking boxes – it is assessing whether the firm can operate safely, whether it understands the risks it will assume and whether it has the resources, systems and people to meet its obligations over time. An application that reads like a template, that contains policies the firm does not yet operate or that lacks substance in the technical or financial narrative signals to the regulator that the business is not ready, even if every formal requirement is nominally met.

The second mistake is underestimating the cross-border dimension. A firm that applies for a licence in one hub but ignores the regulatory implications of its user base, its banking or its service providers in other jurisdictions creates latent risk. That risk may not prevent the initial licence from being granted, but it will surface when the firm attempts to scale, when a bank closes the account because it discovers unlicensed cross-border activity or when a foreign regulator issues an enforcement notice for operating without local authorisation.

The third mistake is filing before the capital, the banking and the key persons are confirmed. Some applicants assume these elements can be finalized in parallel with the regulatory review. In practice, a regulator that sees unresolved dependencies will either refuse the application outright or issue a conditional approval that cannot be activated until the gaps are closed. The result is wasted time and, in some cases, a negative regulatory record that complicates future applications in other jurisdictions.

A fourth mistake, less obvious but increasingly important, is the failure to document the rationale for the structure. If the business sits in Jurisdiction A but the users are in Jurisdiction B and the banking is in Jurisdiction C, the application must explain why. A structure that appears designed to avoid regulation, rather than to facilitate compliance, will attract scrutiny and may lead the regulator to conclude that the firm is not committed to operating transparently within the regime it is asking to join.

When should a firm engage licensing counsel?

The optimal point to engage counsel is before the entity is incorporated and before material commitments are made to the structure, the banking or the technical architecture. Early advice allows the firm to design the setup with the licensing requirements in view, rather than retrofitting compliance onto a structure that was built for other reasons. In a recent licensing matter, a payments company engaged us at the planning stage; we mapped the multi-hub licence stack, aligned the entity structure to the activity mix and coordinated local counsel in the banking jurisdiction. The firm filed complete applications in two hubs within six months and received authorisation without additional information requests.

If the firm has already launched and is now seeking to regularize its position, counsel can conduct a gap analysis – comparing what the business operates today to what the target regime expects – and prepare a roadmap that prioritizes the remediation steps. That roadmap may include restructuring the entity, onboarding new directors, rewriting the policies, conducting the AML and technical audits the regulator will require and engaging the banking and service-provider relationships that the licence presupposes. The cost of this remediation is typically lower if the firm acts before it receives a regulatory inquiry, because the work can proceed at a measured pace rather than under enforcement pressure.

For firms expanding into new jurisdictions, counsel's role includes the cross-border analysis this guide emphasizes: which activities trigger licensing where, whether an existing authorisation allows passporting or recognition, how customer data and transaction records move between jurisdictions under the applicable data-protection rules and whether the expansion creates tax nexus or permanent-establishment risk. These questions cut across licensing, tax, data and commercial law, and resolving them before the firm files prevents the situation where authorisation is granted in one hub but the business discovers it cannot operate because a second jurisdiction's rules were not considered.

Related at OBOLUS

FAQ

How long does a crypto licence take to obtain?

The timeline varies by jurisdiction and by the completeness of the application. A registration under the United Kingdom's Money Laundering Regulations may take a matter of weeks if policies and governance are already in place. A full Virtual Assets Regulatory Authority licence in Dubai or a Crypto-Asset Service Provider authorisation under MiCA typically ranges from several months to over a year, particularly if the regulator issues information requests or requires structural amendments. The preparation phase – entity setup, director vetting, policy drafting, capital confirmation and banking – often takes as long as the formal review.

Which jurisdiction suits my crypto business?

The choice depends on where your users sit, where you can secure banking, the activity mix you offer and your tolerance for ongoing compliance cost. A pure crypto-to-crypto exchange with no fiat rails and a global user base may prioritize a hub with streamlined VASP registration and low capital requirements. A stablecoin issuer or a custodian serving institutional clients will need a jurisdiction with robust reserve rules and access to correspondent banking. The question is not which hub is "easiest" but which regime aligns to your business model, your risk appetite and the markets you intend to serve. OBOLUS maps that stack before you incorporate.

Do I need a separate custody licence?

It depends on the regime and on how your custody function is structured. Under MiCA, custody of crypto-assets on behalf of clients is a regulated service covered by the Crypto-Asset Service Provider authorisation. In Singapore, custody falls within the Digital Payment Token service licensing framework under the Payment Services Act. In some jurisdictions, such as Hong Kong under the Securities and Futures Commission regime, custody of virtual assets that are "securities" requires a Type 1 or Type 9 licence, while custody of non-security tokens may fall under the virtual asset trading platform regime. If you outsource custody to a third-party provider, the question shifts to whether that provider is licensed and whether your arrangement exposes you to counterparty or regulatory risk in your home jurisdiction.

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. In recent applications across the European Union, Dubai and the Channel Islands, we have worked with operators at the readiness stage – mapping the licence stack, aligning governance and policies to the regime and coordinating the entity, banking and tax structure before filing. To map your readiness position and identify the gaps before you commit to a jurisdiction, write to info@oboluslaw.com.

By Aisha Tan, Licensing & Jurisdictions Analyst – advising digital-asset firms on regulatory authorisation, entity structuring and cross-border licensing strategy across the major hubs.

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours