Crypto License in Labuan

Regulated Digital Asset Authorisation with Substance, Tax Integrity, and Operating Readiness

A crypto licence in Labuan is not a shortcut jurisdictional badge. It is a regulated operating permission granted on the condition that the business functions as a supervised financial services platform — with demonstrable substance, effective AML controls, secure custody architecture, and governance that holds under inspection.

We provide end-to-end support for obtaining and maintaining a Labuan digital asset authorisation under the framework administered by the Labuan Financial Services Authority within the Labuan International Business and Financial Centre. The engagement is designed for international exchanges, brokerages, and custodial models that require a bankable, regulator-defensible structure — not a nominal licence that becomes fragile after approval.

Our approach treats authorisation as operating infrastructure. We align scope, substance, governance, and controls so that licensing assumptions match real activity. AML, sanctions, safeguarding, technology resilience, and audit readiness are built to operate under volume, not to exist on paper.

The objective is not speed at the expense of credibility. The objective is a Labuan-licensed platform that can sustain supervision, preserve qualifying tax treatment through genuine substance, and scale without constant regulatory renegotiation.


Why Labuan for a Regulated Digital Asset Platform

Labuan operates as a mid-shore financial centre combining international compliance standards with a pragmatic fiscal and substance framework. It is neither a low-oversight offshore zone nor a high-cost onshore regime.

For digital asset businesses, Labuan offers a controlled environment where authorisation, substance, and tax integrity are designed to work together. Licensing success depends on meeting operational expectations rather than exploiting formal loopholes.

The regime is particularly suitable for international-facing VASPs that do not target Malaysian residents and require predictable supervision, stable banking access, and internationally recognisable compliance standards.


What Authorisation Means in Practice

Authorisation in Labuan is activity-based. The regulator evaluates whether the firm’s actual operations match the permissions requested and whether control functions are genuinely exercised from Labuan.

Supervision focuses on behaviour, not declarations. Firms are assessed on how onboarding, monitoring, custody, execution, and incident handling function under real conditions. Where the operating model diverges from the authorised scope, regulatory pressure escalates quickly.

Our role is to prevent that divergence by designing the licence around operational reality from the outset.


Permission Scope and Activity Mapping

We begin by translating your real business model into an authorisable permission perimeter. This includes:

  • trading or brokerage mechanics

  • custody or safeguarding exposure

  • client categories and access logic

  • asset universe and listing governance

  • revenue and fee structures

  • control points and decision authority

Scope precision is critical. Over-broad requests weaken credibility. Over-narrow requests create pressure to operate outside permission. We define a scope that is defensible, scalable, and aligned with supervisory expectations.


Substance and Control Location

Labuan’s preferential tax treatment and regulatory credibility depend on genuine substance. Control must be exercised in Labuan, not merely documented there.

We design substance to support both licensing and ongoing tax integrity, including:

  • staffing logic aligned with core income-generating activities

  • governance cadence and decision trails anchored locally

  • operating expenditure that reflects real activity

  • physical presence proportionate to the business model

Substance is not treated as a compliance checkbox. It is treated as operating reality that can be audited and defended.


Governance and Fit-and-Proper Readiness

Governance is evaluated on accountability and independence, not titles. Regulators assess who makes decisions, who challenges risk, and how conflicts are managed.

We structure governance to demonstrate:

  • clear responsibility for onboarding, asset admission, and incident escalation

  • independence of compliance and risk oversight from revenue functions

  • documented decision-making and meeting evidence

  • realistic staffing proportional to scale and complexity

This governance framework is designed to withstand fit-and-proper review and ongoing supervision.


AML, Sanctions, and Transaction Monitoring Discipline

AML controls are assessed as an operating system. The regulator evaluates whether risk is identified, monitored, and acted upon consistently.

We implement AML and sanctions frameworks that include:

  • risk-based onboarding and client categorisation

  • behavioural monitoring calibrated to transaction patterns

  • sanctions screening integrated across deposits, withdrawals, and asset flows

  • escalation and reporting workflows with evidence discipline

  • governance over enhanced due diligence and high-risk exposure

Controls are built to function under volume and scrutiny, not as static policies.


Safeguarding, Segregation, and Custody Controls

Protection of client assets is a central supervisory focus. Custody and safeguarding failures are treated as governance failures.

We design safeguarding frameworks covering:

  • legal and operational segregation of client assets

  • access control and key management governance

  • reconciliation ownership and escalation triggers

  • incident response and recovery procedures

  • audit-ready custody evidence

The objective is resilience and traceability, not minimal technical compliance.


Technology, Cyber Resilience, and Operational Continuity

Technology is assessed as a regulatory control environment. Supervisors expect systems to be secure, auditable, and recoverable.

We structure technology governance around:

  • access rights and least-privilege enforcement

  • change management and release discipline

  • logging and audit trail integrity

  • security testing and remediation tracking

  • business continuity and disaster recovery readiness

Operational resilience is treated as a licence-critical capability.


Outsourcing Without Loss of Control

Outsourcing does not transfer regulatory responsibility. Management must retain understanding and control over outsourced functions.

We implement vendor governance that includes:

  • proportional due diligence

  • contractual audit rights and reporting obligations

  • internal monitoring and performance review

  • contingency and exit planning for critical providers

Supervisors test whether vendors enhance resilience or conceal risk. Our framework ensures the former.


Regulatory Engagement and Ongoing Supervision

Authorisation is the start of supervision, not the end of the process. Ongoing compliance depends on how changes are managed and communicated.

We support:

  • structured regulatory dialogue

  • reporting cadence and evidence preparation

  • controlled change management for services, assets, and systems

  • remediation governance when issues arise

Transparent engagement consistently produces more predictable supervisory outcomes than reactive disclosure.


Deliverables

Authorisation Scope and Permission Map
Labuan Entity and Substance Blueprint
Complete Application and Submission Pack
AML, Sanctions, and Monitoring Operating Framework
Safeguarding and Custody Control Architecture
Technology and Cyber Resilience Governance Pack
Regulatory Q&A and Review Support
Post-Approval Compliance and Supervision Playbook

Each deliverable is designed to operate in practice and to be auditable under supervision.


Process

Scoping and Feasibility
We analyse your real model and define an authorisable permission perimeter.

Structure and Substance Design
We align governance, staffing, expenditure, and control location with regulatory and tax expectations.

Control Architecture Build
We implement AML, safeguarding, technology, and vendor governance frameworks.

Application Production
We prepare a coherent submission set designed for iterative regulatory review.

Regulatory Review Support
We manage clarification cycles without introducing scope drift.

Go-Live and Supervision Readiness
We finalise reporting routines, governance cadence, and evidence discipline.

Request a Structured Labuan Authorisation Plan

Operating a Labuan-Licensed Crypto Business After Approval

How the Licence Is Tested in Real Operations

Obtaining a Labuan crypto licence is the point where supervision begins, not where regulatory effort ends. After approval, the regulator’s focus shifts immediately from documentation to behaviour. The decisive question becomes whether the licensed entity operates in a way that reflects the assumptions made during authorisation.

Supervisory assessment concentrates on how decisions are taken, how risks are controlled, and whether substance in Labuan is genuine rather than nominal. Firms that treat post-licensing compliance as a reporting exercise typically encounter escalating scrutiny within the first supervisory cycle.

Our approach is built around this reality. We design the operating model so that daily activity continuously confirms the licensing narrative, rather than undermining it through inconsistencies or shortcuts.


Control Location and Decision Authority

Why “Where Decisions Are Made” Matters More Than Paper Substance

Labuan authorisation presupposes that key operational and risk decisions are anchored in Labuan. This is not evaluated through incorporation documents or board appointment lists, but through observable behaviour and evidence.

Supervisors examine:

  • where onboarding decisions are approved

  • where risk thresholds are set and adjusted

  • where AML escalations are reviewed

  • where incidents are assessed and resolved

  • where strategic changes are authorised

If these functions are effectively exercised offshore, the entity risks being treated as a licensing shell. Over time, this leads to increased reporting requirements, restrictions on scope expansion, or challenges to qualifying tax treatment.

We structure governance and workflows so that decision authority is demonstrably located in Labuan, supported by meeting records, access rights, and escalation logs that can be audited without reconstruction.


Client Lifecycle Governance

From Onboarding to Exit Under Continuous Supervision

Client onboarding is assessed as a lifecycle, not a one-time KYC event. Supervisors evaluate how clients are accepted, monitored, restricted, and, where necessary, exited.

A defensible client lifecycle model demonstrates:

  • clear differentiation between client categories

  • onboarding thresholds aligned with risk profile

  • monitoring intensity that evolves with behaviour

  • escalation logic that results in documented decisions

  • exit procedures that protect both clients and the firm

Weaknesses typically arise where onboarding is strong but monitoring is static, or where client categorisation exists only formally without operational consequences.

We design client lifecycle governance so that controls operate dynamically and leave a clear evidentiary trail, reducing regulatory friction and banking risk.


Transaction Flow Integrity and Economic Purpose

How Regulators Reconstruct Your Business

Labuan supervisors reconstruct transaction flows to assess whether the firm’s activity aligns with its declared business model. This includes fiat inflows, digital asset movements, internal transfers, execution mechanics, and withdrawals.

A robust operating model can demonstrate:

  • economic purpose behind transaction patterns

  • consistency between client profile and activity volume

  • controls that detect anomalies before they escalate

  • preventive measures rather than post-event explanations

High-risk indicators include unexplained pass-through activity, circular flows without commercial rationale, and reliance on manual intervention after anomalies occur.

We structure transaction logic and monitoring so that behaviour is explainable in real time, not rationalised retrospectively.


Custody Operations as a Regulated Environment

Why Key Control Is Treated as Governance, Not Technology

Where custody exposure exists, control over private keys becomes a regulated function. Supervisory assessment focuses on who can initiate, approve, and execute asset transfers, and how those rights are governed.

Acceptable custody frameworks demonstrate:

  • segregation of client and proprietary assets

  • layered access controls and approval thresholds

  • multi-party authorisation for high-risk actions

  • near-real-time reconciliation with escalation triggers

  • tested recovery and incident response procedures

Cold storage ratios, key sharding, and technical architecture are assessed on a risk basis, but governance over these elements is non-negotiable.

Custody failures are treated as systemic governance failures. Our design prioritises auditability and resilience over technical minimalism.


Market Integrity and Execution Oversight

How Trading Activity Is Evaluated in Practice

For exchanges and brokerage models, market integrity is a core supervisory pillar. Regulators assess not only the presence of monitoring tools, but whether they are actively used to manage risk.

Expected controls include:

  • detection of manipulation patterns and abusive trading

  • transparent execution and pricing logic

  • governance over volatility events and suspensions

  • conflict management where proprietary activity exists

Where proprietary trading or market making is permitted, segregation from client execution must be structural and demonstrable. Disclosure alone is insufficient.

We design execution governance so that outcomes are consistent, explainable, and defensible under inspection.


Banking Compatibility as an Operating Outcome

Why Licences Do Not Automatically Open Accounts

Banking access is not granted because a licence exists. Banks evaluate whether the licensed firm behaves in a way that aligns with their own regulatory obligations.

Banks typically examine:

  • coherence between licence scope and transaction flows

  • segregation and safeguarding discipline

  • AML and sanctions effectiveness in practice

  • responsiveness to information requests

  • operational stability under volume

A licence supported by weak operations often fails to deliver sustainable banking. A licence supported by disciplined controls often retains banking even during periods of sector-wide scrutiny.

Our approach treats banking compatibility as a direct output of regulatory discipline.


Technology Governance and Evidence Production

Why Systems Are Evaluated as Control Mechanisms

In a supervised environment, technology is not neutral infrastructure. It is a regulatory control layer that must produce evidence.

Supervisors expect:

  • auditable access controls

  • traceable transaction and decision logs

  • disciplined change management

  • tested continuity and recovery procedures

Firms that cannot demonstrate how systems enforce controls, or how logs are reviewed and acted upon, face supervisory skepticism.

We design technology governance to support both compliance and operational efficiency, reducing remediation cost and supervisory friction.


Outsourcing Without “Black Box” Risk

Maintaining Accountability When Using Third Parties

Outsourcing is permitted, but accountability remains with the licensed entity. Supervisors test whether management understands outsourced processes or treats them as opaque solutions.

A defensible outsourcing framework includes:

  • pre-engagement due diligence

  • contractual audit and information rights

  • performance monitoring and escalation logic

  • contingency and exit planning

Supervisory reviews often probe vendor dependency indirectly by asking management to explain how a control operates. “The provider handles it” is rarely an acceptable answer.


Incident Handling and Regulatory Confidence

Why Response Quality Matters More Than Incident Frequency

Operational incidents are inevitable. Regulatory judgment is shaped by how incidents are handled rather than by their mere occurrence.

Effective incident frameworks define:

  • detection thresholds

  • escalation authority

  • notification timelines

  • client communication logic

  • root cause analysis and remediation ownership

Delayed disclosure or fragmented responses often trigger intensified supervision. Transparent handling, even of serious incidents, tends to strengthen regulatory confidence.

We build incident governance so that response is structured, timely, and evidence-based.


Audit, Assurance, and Remediation Discipline

How Supervisors Assess Control Maturity

Annual audits are not treated as formalities. Supervisors evaluate whether findings result in real remediation.

Key expectations include:

  • ownership of audit findings

  • realistic remediation timelines

  • evidence that controls improve over time

  • governance oversight of recurring issues

Firms that treat audits as box-ticking exercises often experience repeated supervisory intervention. Firms that use audits as control tools gain credibility.


Change Management and Scope Discipline

Preventing Licence Drift During Growth

Growth introduces regulatory risk when changes are implemented without assessment. New assets, services, systems, or client segments can all affect licensing assumptions.

A defensible change management framework ensures:

  • regulatory impact assessment before implementation

  • documented approvals and rationale

  • timely regulatory notifications where required

  • evidence that controls scale with activity

Reactive disclosure undermines trust. Proactive engagement supports predictable supervisory outcomes.


Wind-Down Planning and Client Protection

Why Exit Capability Is a Governance Requirement

Regulators expect licensed entities to demonstrate the ability to exit the market without harming clients.

Credible wind-down planning covers:

  • client asset return procedures

  • custody key transfer or destruction

  • client communication

  • record retention

  • regulatory notifications

Absence of credible exit planning is treated as a governance weakness, particularly for custodial models.


Using Labuan as a Regional Operating Hub

Scaling Without Regulatory Fragmentation

Labuan can function as a central operating hub for regional activity, but only where jurisdictional boundaries are respected.

We structure hub-and-spoke models that:

  • centralise core controls in Labuan

  • adapt distribution to local regulatory constraints

  • prevent unauthorised market access

  • maintain coherence across jurisdictions

This approach reduces duplication, supports institutional credibility, and enables controlled growth.

Supervisory Expectations in Practice

How Labuan Tests Credibility Over Time

Labuan supervision is not episodic. It is cumulative. The regulator forms a view of the licensed entity over time, based on patterns of behaviour rather than isolated events. Early-stage operators often underestimate this dynamic and assume that compliance is assessed transaction by transaction. In practice, supervision is holistic.

Regulatory confidence is built through consistency: consistency of scope, consistency of reporting quality, consistency of governance behaviour, and consistency in how issues are escalated and resolved. Once a supervisory narrative is formed, it influences the intensity and tone of future engagement.

Our operating model is designed to shape that narrative proactively. The objective is not merely to “pass inspections,” but to establish a predictable supervisory relationship that allows the business to evolve without disproportionate friction.


Reporting Discipline and Regulatory Signalling

Why the Quality of Reporting Shapes Supervision

Reporting to the Labuan regulator is not a neutral administrative task. Reports function as signals. They indicate whether management understands its own risk profile, whether controls are effective, and whether issues are identified internally or only when discovered externally.

Supervisors assess:

  • accuracy and internal consistency of reports

  • timeliness of submission

  • clarity of explanations and assumptions

  • alignment between reported data and observed behaviour

Late, incomplete, or inconsistent reporting is interpreted as a governance weakness, even if no underlying breach exists. Conversely, clear and structured reporting — including voluntary context where appropriate — often reduces follow-up queries and supervisory pressure.

We design reporting processes so that data is produced from operational systems, reviewed by accountable owners, and contextualised before submission. This reduces reactive engagement and strengthens supervisory confidence.


Evidence Hierarchy and Audit Readiness

How Supervisors and Auditors Reconstruct Decisions

In supervised environments, evidence is hierarchical. Policies sit at the top, but they carry limited weight unless supported by operational proof. What matters is whether the firm can reconstruct how and why decisions were made.

Regulators and auditors typically request:

  • records of onboarding and risk assessments

  • logs of monitoring alerts and escalation actions

  • minutes from governance meetings

  • incident reports and remediation tracking

  • change approvals and implementation evidence

Firms that rely on informal communication or undocumented decisions struggle under review, even if controls exist in practice. We design evidence discipline so that decision-making can be reconstructed without reliance on individual memory or ad hoc explanations.

This approach reduces disruption during audits and inspections, and it lowers internal stress by making compliance predictable rather than investigative.


Managing Supervisory Change Requests

How to Respond Without Creating New Obligations

During supervision, regulators may request changes, enhancements, or clarifications. These requests are often framed as questions or recommendations, but they can evolve into de facto obligations if handled incorrectly.

A common failure pattern is over-commitment: firms respond quickly but promise changes that are broader than required, creating unnecessary future constraints. Another failure is defensive minimalism, which undermines trust.

We manage supervisory change requests by:

  • clarifying the precise regulatory concern

  • assessing impact on scope, controls, and resources

  • proposing proportionate responses

  • documenting agreed interpretations

The objective is to address the concern without unintentionally expanding the regulatory perimeter or creating obligations that are difficult to sustain.


Relationship Between Tax Integrity and Supervision

Why Substance Failures Trigger Regulatory Attention

In Labuan, regulatory supervision and tax substance are interconnected. Failure to demonstrate genuine economic substance does not only affect tax treatment; it also raises questions about control location and governance integrity.

Supervisors may examine:

  • whether key personnel are genuinely engaged in Labuan

  • whether operating expenditure reflects real activity

  • whether board and management decisions are taken locally

  • whether CIGA functions are executed by qualified staff

Substance weaknesses often surface during routine supervision rather than tax audits. Once identified, they can lead to heightened scrutiny across multiple dimensions, including AML effectiveness and outsourcing dependence.

We design substance models that support both regulatory and tax expectations simultaneously, reducing the risk of cascading issues.


Human Capital as a Regulated Risk

Why Staffing Decisions Attract Supervisory Attention

People risk is increasingly recognised as a core operational risk. Regulators evaluate not only whether roles exist, but whether individuals are capable, empowered, and stable in their positions.

Supervisory concerns often arise from:

  • high turnover in compliance or security roles

  • excessive reliance on a single individual

  • unclear segregation of duties

  • incentives that prioritise growth over control

We structure staffing and role design so that responsibilities are distributed, escalation paths are clear, and succession risk is mitigated. Training, access control, and performance evaluation are aligned with control ownership rather than purely commercial outcomes.

This reduces key-person dependency and strengthens institutional resilience.


Remuneration and Incentive Alignment

How Pay Structures Affect Regulatory Risk

Compensation is not a purely commercial matter in regulated environments. Incentive structures influence behaviour, and regulators increasingly examine whether remuneration encourages excessive risk-taking or weakens compliance.

Supervisory focus includes:

  • whether bonuses are tied solely to volume or revenue

  • whether control functions have independent remuneration

  • whether clawback or adjustment mechanisms exist

  • whether performance metrics include compliance outcomes

We design remuneration frameworks that balance commercial objectives with control quality. This alignment supports long-term stability and reduces the likelihood of behavioural breaches that trigger enforcement.


Data Governance and Confidentiality

Managing Information as a Regulatory Asset

Digital asset businesses process large volumes of sensitive data. Regulators assess whether data is protected, controlled, and accessible for supervisory purposes.

Key expectations include:

  • clear data ownership and access rights

  • encryption and secure storage practices

  • documented data flows and retention policies

  • ability to produce records promptly upon request

Data governance failures often surface during incident investigations or cross-border information requests. We design data frameworks that balance confidentiality, operational efficiency, and regulatory access.


Cross-Border Exposure and Marketing Controls

Preventing Unintended Jurisdictional Reach

Even when a Labuan licence targets non-Malaysian clients, marketing and distribution activities can inadvertently create exposure in restricted jurisdictions.

Supervisors assess:

  • website content and language targeting

  • onboarding flows and geo-restrictions

  • affiliate and referral arrangements

  • customer support interactions

We implement distribution and marketing controls that align with the authorised client perimeter. This reduces the risk of regulatory action arising from unintended jurisdictional reach.


Handling External Pressure Events

Market Stress, Media, and Law Enforcement Requests

External events can test governance under pressure. These include market volatility, negative media coverage, or requests from law enforcement agencies.

Supervisors evaluate:

  • whether management responds calmly and transparently

  • whether communications are coordinated and accurate

  • whether client interests are protected

  • whether regulatory notifications are timely

We design crisis communication and response frameworks so that the firm can act decisively without creating conflicting narratives or regulatory exposure.


Enforcement Risk and Early Warning Signals

How Issues Escalate — and How to Stop Them Early

Enforcement actions rarely occur without warning. They are usually preceded by patterns: repeated reporting deficiencies, unresolved audit findings, delayed responses, or inconsistent explanations.

Early warning signals include:

  • recurring audit issues

  • frequent staff changes in control roles

  • increasing volume of supervisory queries

  • informal requests becoming formal notices

Our approach focuses on identifying and addressing these signals early. Proactive remediation often prevents formal enforcement and preserves regulatory trust.


Preparing for Thematic Reviews

Why Sector-Wide Inspections Matter

Regulators periodically conduct thematic reviews focusing on specific risks, such as custody resilience, AML effectiveness, or technology security.

Participation in thematic reviews requires:

  • rapid production of structured evidence

  • clear explanations of control logic

  • consistency across teams and documentation

Firms that maintain organised records and tested controls experience less disruption. Those that rely on ad hoc explanations often face extended scrutiny.

We design operating models with thematic reviews in mind, reducing disruption when sector-wide inspections occur.


Long-Term Regulatory Adaptability

Why Static Compliance Models Fail

Regulation evolves. Firms that design compliance as a static set of rules struggle to adapt when standards change.

Supervisors increasingly expect:

  • ongoing regulatory monitoring

  • structured change impact assessments

  • governance oversight of regulatory updates

  • timely implementation of new requirements

We build adaptability into governance and control design, allowing the firm to respond to change without repeated structural overhauls.


Institutional Credibility as a Strategic Asset

How Regulation Enables, Rather Than Restricts, Growth

For serious operators, regulatory credibility is not a cost centre. It is a strategic asset that enables partnerships, banking access, and institutional clients.

A Labuan licence supported by disciplined operations allows the firm to:

  • negotiate from a position of strength with banks

  • onboard institutional counterparties more efficiently

  • expand scope with predictable regulatory outcomes

  • withstand market stress without reputational collapse

This is the commercial payoff of treating authorisation as operating infrastructure rather than as a formal hurdle.


Positioning the Labuan Licence Within a Global Structure

Using Regulation as a Coordinating Layer

Many international groups use Labuan as part of a broader structure. The licence can serve as a coordinating layer for regional operations, liquidity management, or compliance infrastructure.

We design structures that:

  • respect jurisdictional boundaries

  • avoid regulatory arbitrage narratives

  • centralise control without over-concentration of risk

  • support transparent group governance

This approach reduces fragmentation and supports coherent global operations.

FAQ

The minimum paid-up capital required for the Labuan Money Broking License (the license commonly used by VASPs) is RM 500,000 (approximately USD 110,000). This sum must be fully paid, deposited into a bank account in Labuan or Malaysia, and remain unimpaired throughout the operation. It's important to note that the Labuan FSA may require a higher capital amount if the applicant's projected transaction volumes or the complexity of the services (such as derivatives trading) present a higher systemic risk. The capital serves as a stability reserve, not operational funding.

Licensed digital financial service providers in Labuan benefit from a preferential 3% corporate tax rate on audited net profits derived from qualifying trading activities. As an alternative, the entity may elect to pay a fixed annual tax fee of RM 20,000. This low rate applies because Labuan is classified as a midshore jurisdiction, provided the company meets the strict Substance Requirements under the LBATA (Labuan Business Activity Tax Act 1990). No withholding tax, capital gains tax, or indirect taxes (like Sales and Service Tax) apply to international business income.

The licensing process, from filing the application with the Labuan FSA to final approval, generally takes between 3 to 6 months. This timeframe is heavily influenced by the quality of initial submissions. Delays often occur due to deficiencies in the AML/CFT Compliance Manual, slow execution of the required background checks (the "fit and proper" test) for directors and shareholders, or failure to quickly establish the physical office and local staffing requirements. A pre-application consultation with the LFSA is highly recommended to clarify expectations.

To maintain the license and benefit from the low tax regime, the entity must demonstrate genuine economic substance in Labuan. This includes three non-negotiable requirements:

  1. Maintaining an operational physical office in Labuan.

  2. Employing a minimum of two full-time employees locally. These staff must be qualified and dedicated to performing the Core Income-Generating Activities (CIGA), such as platform decision-making and compliance oversight.

  3. Incurring a minimum annual operating expenditure of RM 100,000 in Labuan. Failure to meet these annually audited requirements can lead to loss of the preferential 3% tax rate.

Yes. All Labuan-licensed VASPs are subject to international Anti-Money Laundering (AML) standards, as guided by the Financial Action Task Force (FATF). The Travel Rule mandates that VASPs collect and transmit specific originator and beneficiary information for all crypto transfers above a designated threshold. Compliance requires integrating technological solutions for transaction monitoring and information sharing between different VASP entities.

No. The Labuan license is explicitly granted for international business activities. License holders are strictly prohibited from actively marketing services to or accepting clients who are Malaysian residents (including individuals and entities). All transactions must be conducted in foreign currencies. Serving the domestic Malaysian market requires a separate and much more stringent license from the Securities Commission Malaysia (SC), with different tax implications.

Yes. By law, the entire application process, the incorporation of the Labuan International Company, and the initial submission of documents to the Labuan FSA must be facilitated and managed by a licensed Labuan Trust Company (LTC). The LTC acts as the legal and corporate services intermediary, ensuring all filings and corporate maintenance adhere to the Labuan Companies Act 1990 and LFSA regulations.

The application must include a comprehensive set of operational and compliance manuals. The two most critical documents are:

  1. AML/CFT Compliance Manual: Detailing the Risk-Based Approach (RBA), Customer Due Diligence (CDD), Enhanced Due Diligence (EDD) procedures, and the process for submitting Suspicious Transaction Reports (STRs) to the authorities.

  2. IT Governance and Cybersecurity Policy: Outlining infrastructure security, client asset segregation protocols (cold vs. hot storage), multi-signature key management, and a robust Business Continuity and Disaster Recovery (BCDR) plan, including the 14-day mandatory incident reporting rule to the LFSA.

The core Money Broking VASP license covers the custody of client assets that are directly related to the exchange services (i.e., holding assets on behalf of trading clients). However, if the company plans to offer specialized, standalone Digital Asset Custody Services as a primary business, the LFSA may require a specific endorsement or a separate license. This triggers heightened requirements concerning external security audits, cold storage protocols, and mandatory insurance coverage for digital assets under custody.

Get in touch with our experts