A licensed exchange books its core trading engine with a cloud provider in one jurisdiction, custody wallets with a specialist vendor in another, and customer-verification checks with a third-party KYC platform. Six months into operation the regulator writes: "Provide your outsourcing register, evidence of audit rights in each contract, and a continuity plan if any vendor fails." The business discovers that two contracts lack regulator-notification clauses, one has no exit provision, and the register was never created. What was a routine supervision inquiry becomes a breach notice and a remediation timeline that freezes product launches. Outsourcing and cloud arrangements sit at the centre of every licensed digital-asset business, yet the regulatory framework governing them is rarely priced into vendor selection until the licence is already at risk.
Across the flagship licensing regimes – MiCA, VARA, the MAS Payment Services Act, the SFC's VASP framework – regulators expect a firm to retain full accountability for every material function, whether performed in-house or delegated to a third party. That expectation translates into a defined set of contractual, operational and notification obligations that apply from the moment a service provider touches customer data, holds private keys, performs a compliance check or runs any component of the platform's critical path. This guide sets out the regime requirements, the contract mechanics and the common mistakes operators make when structuring vendor relationships under a crypto licence.
What counts as outsourcing under a crypto licence?
Outsourcing, in the licensing context, means the delegation of a material operational function to a third-party service provider. The regulator's definition typically turns on whether the function is critical to the delivery of the licensed activity or to compliance with regulatory obligations, not on whether the contract is called "outsourcing" or "cloud services." A cloud infrastructure provider hosting the order-matching engine is outsourcing. A specialist custody vendor holding private keys on behalf of clients is outsourcing. A third-party KYC platform performing customer due diligence under the firm's AML obligations is outsourcing. A generic office-support service – payroll, office cleaning – generally is not, because it does not sit in the critical path of the licensed business.
Under MiCA, a CASP must notify its competent authority before materially outsourcing a critical or important function and must ensure that the arrangement does not impair the quality of its internal control or the regulator's ability to supervise. VARA in Dubai requires prior written approval for outsourcing material functions and mandates that the arrangement include audit rights, business-continuity provisions and the regulator's right to access the service provider's records. The MAS framework expects a major payment institution to notify the Authority of material outsourcing arrangements and to maintain a register of all such contracts, with periodic attestation that each arrangement meets the operational resilience and risk-management standards set out in MAS Notice 644.
The practical boundary is drawn at **materiality**: does failure of this vendor prevent the firm from meeting a regulatory obligation or from delivering a core licensed service? If the answer is yes, the contract and the governance around it fall within the outsourcing regime. The common error is to treat cloud infrastructure as a commodity purchase outside regulatory scope. It is not. The moment a cloud provider hosts customer data, transaction records or the platform's trade-execution logic, the arrangement is material outsourcing and the full framework applies.
The outsourcing register and notification timeline
Every licensing regime that addresses outsourcing expects the firm to maintain a register of material arrangements. The register is not a static document filed once at authorisation; it is a live operational record that must be updated whenever a new vendor is onboarded, a contract scope changes, or an arrangement is terminated. The regulator's supervision team uses the register to assess concentration risk (multiple critical functions with a single vendor), jurisdictional risk (vendors in high-risk or uncooperative territories) and continuity risk (whether exit and substitution plans exist).
Notification timelines vary. Under MiCA, the competent authority must be notified in advance of a material outsourcing decision, and the firm may not proceed until it has assessed and documented how the arrangement preserves its control environment and the regulator's supervisory access. VARA requires prior written approval for outsourcing material functions; an operator that proceeds without approval risks a breach notice. MAS does not require prior approval for every arrangement but expects notification and expects the firm to self-assess materiality using the criteria in the relevant Notice. The Hong Kong SFC's conduct requirements for licensed VATPs include governance expectations around outsourcing that align with the broader conduct standards for licensed corporations under the Securities and Futures Ordinance.
In practice, the register should record, for each arrangement: the vendor's name and jurisdiction, the function being outsourced, the contract term and termination provisions, whether the vendor itself sub-contracts any part of the service, the audit and access rights the firm holds, the business-continuity and exit arrangements, and the date the regulator was notified (or the exemption basis if notification was not required). Operators we advise typically discover the register requirement during the licence-application process and scramble to document contracts that were signed without regulatory input. The cleaner path is to build the register discipline into procurement from the outset, treating every vendor decision above a materiality threshold as a regulatory event that requires advance documentation.
Contractual requirements: audit, access and exit
Regulators do not prescribe a standard contract, but they do mandate a minimum set of provisions that must appear in every material outsourcing arrangement. Three clauses are universal: **audit rights**, **regulator access** and **termination with continuity**.
Audit rights. The licensed firm must retain the right to audit the service provider's performance of the outsourced function, either directly or through an independent third party. The audit right typically includes access to the vendor's systems, records and staff to the extent necessary to verify that the service is being delivered in accordance with the contract, that data is being handled securely, and that the vendor's own controls meet the standards the regulator expects of the licensed firm. Under MiCA, audit rights are explicit: the CASP must be able to instruct audits and the vendor must cooperate. VARA's rulebooks include similar language. A vendor that resists audit-rights language on confidentiality or IP grounds creates a regulatory problem before the contract is signed; the usual resolution is a bounded audit right (advance notice, frequency limits, IP safeguards) that meets the regulatory standard without giving the firm unrestricted access to the vendor's entire operation.
Regulator access. The contract must allow the regulator, on request or as part of its supervisory powers, to access the vendor's records and systems related to the outsourced function. This does not require the regulator to contract directly with the vendor, but it does require the vendor to acknowledge that the licensed firm's regulator may, in the course of supervision or investigation, require information or access that the firm itself cannot provide without the vendor's cooperation. The clause is often drafted as an obligation on the vendor to cooperate with regulatory requests made through the licensed firm, with the firm indemnifying the vendor for reasonable compliance costs. Vendors operating in multiple jurisdictions may push back on open-ended regulator-access language; the negotiated version typically specifies that access is subject to the vendor's own legal and regulatory obligations and that conflicts (e.g., data-protection restrictions) will be resolved in good faith.
Termination and exit planning. The contract must include a termination right that allows the firm to exit the arrangement without material disruption to the licensed service, and it must provide for an orderly wind-down or transition period during which the vendor continues to perform while the firm migrates to an alternative provider or brings the function in-house. Under MiCA and VARA, the firm must demonstrate, before outsourcing a critical function, that it has an exit plan: how will the function be performed if this vendor becomes unavailable? The contract's termination clause feeds directly into that plan. A vendor lock-in – where the contract term is multi-year, auto-renewing, with exit fees that exceed the firm's capital buffer – is a regulatory red flag. Regulators expect the firm to retain the ability to substitute the vendor within a reasonable period (typically the notice period for material changes to a licensed business, which varies by regime but is often measured in months, not years).
The practical difficulty is that many cloud and SaaS vendors operate on standard terms that do not contemplate these provisions. A hyperscale cloud provider will rarely agree to bespoke audit-rights language in an SME customer's contract. The resolution in those cases is a **framework compliance opinion**: the firm's counsel reviews the vendor's standard terms, the vendor's published security and compliance certifications (SOC 2, ISO 27001), and the data-processing agreement, and produces a short memo confirming that the arrangement, taken as a whole, meets the regulatory standard for audit and access. The regulator will not approve a vendor on that basis alone, but it will accept that the firm has made a reasonable assessment within the constraints of a non-negotiable vendor contract.
Sub-contracting and concentration risk
A material outsourcing arrangement often involves sub-contractors: the custody vendor uses a key-management specialist; the cloud provider uses third-party data centres; the KYC platform routes certain checks to a fourth-party sanctions-screening service. Under the licensing frameworks, the firm remains fully accountable for every link in that chain, and the regulator expects the firm to know and approve material sub-contracting decisions before they occur.
MiCA requires that a CASP, when outsourcing a critical function, ensure that the service provider does not further outsource that function without the CASP's prior written consent. VARA's guidance on outsourcing includes a similar expectation: the licensed firm must track sub-contractors and must confirm that each sub-contractor is subject to equivalent standards of data security, operational resilience and regulatory access. The contract with the primary vendor should therefore include a **sub-contracting register obligation** – the vendor must notify the firm of any material sub-contractor, provide equivalent audit and access rights down the chain, and obtain the firm's consent before engaging a new sub-contractor for a material part of the service.
Concentration risk is the regulator's second concern. If a firm's custody, cloud infrastructure, KYC checks and customer-support ticketing all sit with vendors in the same jurisdiction or under the same ultimate parent, a single political, operational or credit event can disable the entire platform. Regulators do not ban concentration – it is often unavoidable for small firms in niche markets – but they expect the firm to assess and document the risk and to explain how business continuity would be maintained if the concentrated vendor became unavailable. In a recent licensing engagement, an operator initially proposed to use a single vendor group for exchange infrastructure, wallet custody and compliance checks; the regulator's preliminary feedback was that the concentration was acceptable only if the firm held contractual rights to migrate each function independently (i.e., not bundled under a single master agreement) and maintained off-site backups of all customer data and private-key material sufficient to reconstitute the service with an alternative provider.
Data location and cross-border transfers
A crypto firm licensed in the EU but using cloud infrastructure in Singapore, with customer data replicated to US-based availability zones, sits at the intersection of MiCA's outsourcing requirements, the GDPR's cross-border transfer rules, and any data-localisation expectations in the customers' home jurisdictions. Regulators in most flagship hubs do not mandate that data stay within the licensing jurisdiction, but they do expect the firm to demonstrate that cross-border data flows comply with applicable data-protection law and that the firm retains the ability to produce records to the regulator on demand, regardless of where the data physically sits.
Under MiCA, a CASP may outsource data processing and storage to a provider in a third country, but the arrangement must not impair the firm's or the regulator's access to data, and it must comply with the GDPR where personal data is involved. The GDPR's transfer mechanisms (adequacy decisions, standard contractual clauses, binding corporate rules) apply in full; the licensing authority will not approve an outsourcing arrangement if it would put the firm in breach of its data-protection obligations. VARA does not impose blanket data-residency requirements but expects the firm to assess and document jurisdictional risk where customer data or transaction records are held offshore, particularly in jurisdictions with weak legal frameworks for data access or with a history of non-cooperation with UAE authorities.
The practical workflow is to **tier vendors by data sensitivity**. A cloud provider that hosts only anonymised platform telemetry sits in a different risk category from a custody vendor that holds customer personal data alongside private keys. For high-sensitivity vendors, the contract should specify the data's physical location, the applicable data-protection regime, the transfer mechanism (if cross-border), the encryption and access-logging standards, and the process for responding to law-enforcement or regulatory requests for data. Where a vendor operates in a jurisdiction with mandatory data-disclosure laws that conflict with the firm's home-jurisdiction protections (a recurring issue for EU-licensed firms using US cloud providers post-Schrems II), the resolution is typically a hybrid model: sensitive data stays in-region with a provider that offers contractual commitments not to respond to third-country requests without notice, while non-sensitive infrastructure is placed where operational resilience and cost considerations dictate.
Business continuity and disaster recovery
The regulator's question is simple: if this vendor disappears overnight, how long before your licensed service stops working, and what is your plan to restore it? Every material outsourcing arrangement must be backed by a **business-continuity scenario** that explains how the firm would continue to meet its regulatory obligations and serve its customers during a vendor failure and what steps would be taken to migrate to an alternative provider or to bring the function in-house.
For infrastructure outsourcing (cloud compute, data storage, network services), the continuity plan typically involves multi-region redundancy, off-site backups, and contracts with alternative providers that can be activated within the restoration time objective (RTO) the regulator expects. Under MiCA, a CASP's ICT and security risk-management framework must address third-party dependencies and must include contingency arrangements for critical outsourced functions. VARA's operational resilience guidance expects a licensed firm to test its continuity plans at least annually and to demonstrate that recovery procedures work as documented. MAS Notice 644 sets specific RTOs and recovery-point objectives (RPOs) for major payment institutions, and those standards apply to outsourced components of the service just as they apply to in-house systems.
For custody outsourcing – where a third-party vendor holds customer private keys – the continuity plan must explain how key material would be recovered if the vendor becomes insolvent, loses its own licence, or suffers a security breach that compromises its ability to sign transactions. The standard model is **escrow or dual control**: key shards or encrypted key material are held by the firm or by a neutral escrow agent, separate from the vendor's operational environment, such that the firm can reconstitute signing capability without the vendor's cooperation. The vendor resists this model because it reduces lock-in; the regulator insists on it because a licensed custodian that cannot recover customer assets from a failed vendor is in breach of its safeguarding obligations.
In a recovery matter last year, an exchange lost access to a white-label custody provider after that provider's own licence was suspended. The exchange held no backup of the key material and no escrow arrangement. Customer withdrawals were frozen for three weeks while the provider negotiated a lift of the suspension. The regulatory outcome was a finding that the exchange had outsourced a critical function without adequate continuity planning, and a requirement to unwind the custody arrangement and bring key management in-house within ninety days. The lesson: continuity planning for custody outsourcing must assume vendor failure as the base case, not an edge scenario.
Cost allocation and fee transparency
Outsourcing introduces a recurring cost line into the licensed business, and regulators expect the firm to demonstrate that it has priced those costs into its financial projections and capital adequacy calculations. A firm that burns through its minimum capital buffer because vendor fees exceeded budget is at risk of breaching its licence conditions even if the service itself is performing well.
Under MiCA, a CASP's own-funds requirement is calculated to cover operational risk, and that includes the risk of vendor cost overruns or unexpected termination fees. VARA expects the firm's financial model, submitted with the licence application, to reflect all material outsourcing costs on a going-concern basis, including costs that would be incurred on exit (migration, dual-running, data extraction). The model should also account for **concentration premium**: if a single vendor becomes indispensable, that vendor gains pricing power, and the firm's future cost base becomes unpredictable. Regulators do not prescribe a maximum share of operating costs that may be allocated to vendors, but they do challenge applications where vendor dependency erodes the firm's financial resilience or its ability to exit an arrangement without breaching capital requirements.
For operators on tight budgets, the resolution is to **tier outsourcing by criticality** and to bring lower-risk functions in-house or onto open-source infrastructure where the capital/talent trade-off favours internal build. Transaction monitoring and AML screening, for example, are often better outsourced (because specialist vendors maintain up-to-date sanctions lists and behavior-detection models that a small in-house team cannot match), while front-end user interfaces and non-critical middleware can be built internally to reduce recurring fees and vendor lock-in. The licensing authority will accept that trade-off provided the firm can demonstrate that in-house functions meet the same control and resilience standards that would apply to an outsourced equivalent.
When to notify changes to an existing arrangement
A licensed firm that signed a cloud contract at application and then, two years later, migrates from the vendor's European region to its Asia-Pacific region to reduce latency has materially changed the outsourcing arrangement. The data's physical location has moved; the applicable data-protection regime has changed; the vendor's sub-contractors in the new region may be different from those in the original region. Under most frameworks, this is a notifiable event.
MiCA expects a CASP to notify its competent authority of any material change to an outsourcing arrangement that affects the firm's ability to meet its obligations or the regulator's ability to supervise. VARA's guidance is more explicit: any change to a material function, including changes to vendors, contract scope, or data location, requires prior notification and, in some cases, fresh approval. MAS expects ongoing compliance with the outsourcing standards in Notice 644, which means that a change triggering a fresh materiality assessment (a new sub-contractor, a shift to a higher-risk jurisdiction, a significant fee increase that affects capital adequacy) should be notified and documented in the register update.
Operators routinely underestimate this requirement. A vendor upgrade (moving from a legacy custody API to the vendor's new multi-chain platform) is treated as a technical migration with no regulatory implications, when in fact the change introduces new sub-contractors (the vendor's new blockchain-node provider), new jurisdictions (the nodes may be hosted in different territories), and new operational dependencies (the firm now relies on the vendor's interoperability layer, not just its key-management module). The safe rule: **any change that would have required disclosure if the arrangement were being proposed fresh should be notified as a change to an existing arrangement**. The regulator will not penalise over-notification; it will penalise operating a changed arrangement without disclosure.
Common mistakes and how to avoid them
The error pattern is consistent across jurisdictions. First mistake: signing a vendor contract before considering the regulatory obligations. The firm selects a cloud provider on cost and features, signs a standard SaaS agreement, and only later discovers that the contract lacks audit rights, has auto-renewal terms incompatible with the licensing regime's exit expectations, and places data in a jurisdiction that creates GDPR transfer issues. The contract cannot be unwound without business disruption, so the firm proceeds and tries to obtain a regulatory waiver. Waivers are rare. The correct sequence is to treat every vendor decision above the materiality threshold as a licensing decision first: draft the regulatory requirements (audit, access, exit, sub-contracting, data location), issue them as part of the procurement RFP, and disqualify vendors that cannot meet them.
Second mistake: building the outsourcing register only when the regulator requests it. The register is a supervision tool, and regulators expect it to be current at all times. An operator that scrambles to compile the register during an on-site inspection will produce an incomplete document, miss contracts that have expired or changed, and struggle to demonstrate that the governance process around vendor decisions was followed. The operational discipline is simple: every vendor onboarding goes through a short approval workflow (legal reviews the contract for regulatory clauses, compliance assesses materiality, finance confirms budget, and the COO updates the register), and the register is reviewed quarterly to confirm that it reflects the current state.
Third mistake: treating open-source software or decentralised infrastructure as outside the outsourcing framework. If the firm's platform relies on a specific open-source library for cryptographic key generation, and that library is maintained by a single volunteer or a small project team with no service-level commitment, the regulator will ask: what happens if the library is abandoned or if a critical security patch is not released? The fact that the software is open-source does not remove the dependency risk. The answer is not to avoid open-source (which is often the best technical solution) but to document the dependency, assess whether the firm could maintain or fork the library itself if necessary, and include that assessment in the business-continuity plan. Where the firm lacks that capability, the open-source dependency should be wrapped in a commercial support contract with a vendor that can provide the continuity commitment the regulator expects.
Fourth mistake: assuming that a vendor's SOC 2 or ISO certification eliminates the need for contractual audit rights. Certifications are evidence that the vendor has controls in place, but they do not give the licensed firm or its regulator access to verify that those controls are being applied to the specific service the firm is receiving. The contract must still grant audit rights. The certification reduces the frequency with which the firm needs to exercise those rights (an annual attestation review may suffice if the vendor's SOC 2 report is current and scoped to cover the outsourced function), but it does not eliminate the regulatory requirement to hold the right in the first place.
For a scoped assessment of your vendor contracts and outsourcing register before a supervision review, contact OBOLUS at info@oboluslaw.com. If an audit or compliance gap has surfaced and the clock is running, we map the remediation path and negotiate with vendors to bring arrangements into line with the applicable framework.
Self-assessment: outsourcing readiness checklist
Before onboarding a new vendor or before a licensing-authority review, run this self-assessment against each material outsourcing arrangement:
- Register – Is the arrangement recorded in the outsourcing register with all required fields (vendor name/jurisdiction, function, contract term, termination rights, sub-contractors, audit provisions, notification date)?
- Materiality – Has the firm applied its materiality assessment framework to confirm that this arrangement meets the threshold requiring notification/approval?
- Notification – Was the regulator notified in advance (or, if the regime does not require advance approval, is there a record of the materiality determination and the date the arrangement went live)?
- Audit rights – Does the contract grant the firm (and, where required, the regulator) the right to audit the vendor's performance and controls?
- Regulator access – Does the contract allow the regulator to access the vendor's records on request, or does it obligate the vendor to cooperate with regulatory inquiries made through the firm?
- Exit and continuity – Does the contract include a termination right with a reasonable notice period, and does the firm have a documented continuity plan explaining how the function would be performed if the vendor exited?
- Sub-contracting – Does the contract require the vendor to disclose material sub-contractors and obtain the firm's consent before engaging new ones?
- Data location – Is the physical location of customer data and transaction records documented, and does the arrangement comply with applicable data-protection and cross-border transfer rules?
- Cost and capital – Are the vendor's fees and any exit costs reflected in the firm's financial projections and capital-adequacy calculations?
- Change protocol – Is there a documented process for assessing and notifying material changes to the arrangement (scope, sub-contractors, data location, fee structure)?
If any line fails, the arrangement is not fully compliant with the regulatory framework, and the gap should be closed before the next supervision cycle or before the regulator's next on-site review.
Related at OBOLUS
- Licensing & Registration for Digital-Asset Businesses – the full service line for VASP, CASP and payment-institution licensing across the flagship hubs
- Winding Down a Digital-Asset Business: Orderly Exit Planning – continuity planning for voluntary and forced exits, including vendor wind-down obligations
- Economic Substance for Licensed VASPs (Established Operators) – ensuring that the outsourcing footprint does not undermine substance tests in the licensing jurisdiction
FAQ
How long does a crypto licence take to obtain?
Application timelines vary by jurisdiction and by the complexity of the business model. In the EU under MiCA, a CASP authorisation typically takes several months from submission of a complete application, assuming the competent authority does not request material supplementary information. In Dubai under VARA, the process involves a pre-application consultation phase followed by formal review, and the total timeline depends on the firm's readiness and the completeness of its operating procedures and vendor documentation. In Singapore, a Digital Payment Token service licence under the MAS Payment Services Act involves a thorough assessment of the applicant's AML/CFT controls, technology risk management, and outsourcing governance, with timelines measured in months for a well-prepared submission. For a scoped timeline estimate based on your operating model and target jurisdictions, contact info@oboluslaw.com.
Which jurisdiction suits my crypto business?
The right jurisdiction depends on where your customers are, where you can establish banking relationships, where your team and technology sit, and what your growth plan looks like. An exchange targeting European retail users will need MiCA compliance and a CASP authorisation in a member state with a path to euro banking. A custody business serving institutional clients across Asia may prioritise Singapore or Hong Kong for regulatory credibility and cross-border legal enforceability. A token issuer preparing a public offering may choose a jurisdiction with a mature securities framework and clear guidance on when a token constitutes a financial instrument. There is no universal best jurisdiction; the analysis turns on your facts. We map the licence, tax, banking and substance stack for operators across more than seventy jurisdictions and provide a comparative recommendation before you commit. Write to us at info@oboluslaw.com to discuss your build.
Do I need a separate custody licence?
It depends on the jurisdiction and on whether you are holding customer assets on your own balance sheet or as a custodian. Under MiCA, custody and administration of crypto-assets on behalf of clients is a distinct service under the CASP regime and requires specific authorisation. VARA in Dubai treats custody as a regulated activity requiring its own licence category. In Singapore, safeguarding and holding a customer's digital payment tokens is a licensable activity under the Payment Services Act. In some jurisdictions, an exchange licence or a broader VASP registration covers custody as part of the service bundle, but the prudential and safeguarding obligations are higher for firms that hold customer keys. If your business model involves taking control of customer private keys (even if only as part of the deposit-to-trade flow), you should assume custody regulation applies and structure accordingly. For a custody-licensing assessment and a structure that minimises key-holding risk while preserving operational flexibility, contact OBOLUS at info@oboluslaw.com.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across more than seventy jurisdictions, on disputes and on-chain asset recovery across twenty-five forums, and on the tax, banking and compliance frameworks that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we pressure-test vendor arrangements and outsourcing governance against the supervision standards regulators actually enforce. To discuss your situation, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – Aisha specialises in VASP and CASP licensing processes, outsourcing governance, and cross-border regulatory compliance for digital-asset platforms.
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.