EST · MMXXVI
Home/Jurisdictions/Vietnam Digital Asset Pilot: Market Access and Local Requirements
Licensing & Registration

Vietnam Digital Asset Pilot: Market Access and Local Requirements

Vietnam Digital Asset Pilot: Market Access and Local Requirements. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee

An exchange platform considering Vietnam's digital-asset pilot discovers that eligibility turns not only on capital and fit-and-proper credentials but on data localisation, ownership structure and a strict time window. The pilot framework – announced by Vietnam's central bank, the State Bank of Vietnam (SBV), as part of a broader push to regulate virtual-asset service providers – creates a supervised test environment for qualifying businesses. For an operator weighing entry, the question is whether the pilot's constraints and the regime's experimental status align with the business case, the user base and the cross-border banking and payments stack that sit underneath.

This page sets out the pilot's core eligibility criteria, the application and supervision process, the capital and ownership conditions that apply, the data-residency and local-presence obligations and how the pilot interacts with Vietnam's evolving AML and payment-services framework. It also addresses where the pilot sits within broader Southeast Asian regulatory convergence and the practical timeline an inbound operator should plan for.

What is the digital-asset pilot, and who supervises it

Vietnam's digital-asset pilot operates under a regulatory sandbox framework administered by the State Bank of Vietnam. The pilot is designed to allow the SBV to assess the operation of virtual-asset service providers – exchanges, wallet custodians, payment-intermediation platforms – in a controlled environment before committing to a permanent licensing regime. The framework is explicitly time-limited: participants enter for a defined pilot period, at the end of which the SBV decides whether to grant a full licence, extend the pilot or terminate the participant's authority.

The pilot is not an open-door programme. The SBV has set firm eligibility gates around capital, governance, technical systems and local presence, and the number of pilot participants may be capped. Businesses that meet the criteria apply through a multi-stage assessment that includes a technical audit, a fit-and-proper review of key personnel and a financial-standing check. Those admitted operate under close supervision: the SBV receives periodic transaction reports, monitors customer-asset segregation and can suspend or terminate a participant at any stage if compliance lapses or systemic risk emerges.

For an operator used to faster, lighter-touch registration regimes in other ASEAN markets, the pilot represents a material procedural and capital commitment. The trade-off is early-mover advantage in a market with significant retail interest in digital assets and a government actively seeking to channel that activity into a regulated framework. In our cross-border practice, we see operators evaluate Vietnam alongside the Philippines, Thailand and Malaysia, each of which is building out its own virtual-asset regime at varying speeds.

Who qualifies for the pilot – capital, ownership and operational requirements

Eligibility for the pilot requires an applicant to satisfy three core tests: financial standing, governance and fit-and-proper credentials, and local operational presence. The financial-standing test includes a minimum capital requirement – the exact threshold depends on the proposed activity category and is set by the SBV in guidance accompanying the pilot framework. The capital must be held in Vietnam, denominated in Vietnamese dong or in a currency approved by the SBV, and available to meet customer claims and operational liabilities.

The ownership test requires transparency around beneficial ownership and, in some configurations, local participation. If the applicant is a wholly foreign-owned entity, the SBV may require that a portion of the shareholding or board representation be held by Vietnamese nationals or entities, particularly if the business intends to offer services directly to Vietnamese retail customers. Alternatively, an applicant may structure as a joint venture with a licensed Vietnamese financial institution or payment-service provider, a route that can expedite the approval process but introduces partner-alignment and exit complexity.

The operational-presence requirement is firm: the applicant must establish a legal entity in Vietnam, maintain senior management and compliance personnel physically present in the country, and host customer and transaction data on servers located within Vietnam's territory. The data-localisation obligation is driven by the SBV's supervisory mandate and by Vietnam's broader cybersecurity framework, which requires critical data relating to Vietnamese users to be stored domestically. For a regional exchange operating out of Singapore or Hong Kong, this means standing up a dedicated Vietnam subsidiary, hiring local staff and implementing a data-residency architecture that may differ from the group's standard setup.

If your entity structure, capitalisation or data-hosting model does not align with these gates, applying before you address the gaps wastes time and signals unpreparedness. To map the structure, capital injection and data-residency path for your build, contact OBOLUS at info@oboluslaw.com.

The pilot application process and the SBV's assessment phases

The application unfolds in three phases: pre-qualification, technical review and final authorisation. In the pre-qualification phase, the applicant submits a detailed business plan, financial statements covering the prior two years (or, for a new entity, pro-forma financials and capital-commitment letters from shareholders), corporate documents evidencing ownership and control, and résumés and background declarations for proposed directors, senior managers and compliance officers. The SBV screens this package for completeness and preliminary eligibility; incomplete or unclear submissions are returned, and the clock resets.

The technical-review phase is the most resource-intensive. The SBV conducts an audit of the applicant's platform technology, examining wallet-custody architecture, transaction-monitoring systems, customer-onboarding and know-your-customer (KYC) processes, and cybersecurity controls. The audit is typically carried out by SBV-appointed technical assessors and may include on-site inspections of the applicant's Vietnam office and data centre. The applicant must demonstrate that customer assets are segregated from corporate funds, that private keys are held in secure, auditable custody arrangements (cold storage or hardware-security-module setups are generally expected for a significant portion of holdings), and that the platform can generate real-time reporting to the SBV on transaction volumes, user counts and suspicious-activity flags.

In the final-authorisation phase, the SBV's decision committee reviews the technical-audit report, the fit-and-proper findings and any public-comment input (the SBV may publish the applicant's name and seek feedback from industry stakeholders or consumer-protection bodies). If the committee approves, the applicant receives a pilot authorisation letter setting out the permitted activities, the pilot duration, reporting obligations and specific conditions – for example, a cap on the number of retail customers, restrictions on certain high-risk token types or a requirement to maintain insurance covering customer-asset loss.

The timeline from submission to authorisation is not fixed in the pilot framework; guidance from the SBV indicates an assessment period of several months, but the clock depends on the completeness of the application, the complexity of the proposed services and the SBV's workload. In practice, an operator should budget six to nine months from initial submission to go-live, with a buffer for any requests for further information or technical remediation.

Permitted activities under the pilot and what remains prohibited

The pilot framework permits a defined set of virtual-asset services: operation of a trading platform (exchange), custody of virtual assets on behalf of customers, facilitation of virtual-asset transfers (payment intermediation) and issuance or distribution of stablecoins or tokenised assets, subject to additional approval. Activities that remain prohibited or outside the pilot's scope include margin trading or derivatives on virtual assets, lending or staking services that involve pooling customer assets, and any service that links virtual assets to securities or collective-investment products without a separate licence from Vietnam's securities regulator.

An exchange admitted to the pilot can list and facilitate spot trading in approved virtual-asset pairs. The SBV maintains a list of eligible assets, initially expected to cover major cryptocurrencies with established track records and transparent governance; assets deemed high-risk – privacy coins, algorithmically volatile stablecoins, tokens under regulatory challenge in other major markets – are excluded. The exchange must implement listing standards that mirror the SBV's eligibility criteria and must notify the SBV before adding a new asset to the platform.

Custody participants hold customers' virtual assets but do not operate a trading platform; they provide wallet services, secure storage and asset-administration functions. The custody model must be non-custodial in the sense that the customer retains ultimate control (through seed-phrase backup or multi-signature arrangements) or, if fully custodial, the provider must meet enhanced capital and insurance requirements to cover the risk of loss or theft.

Stablecoin issuers face a parallel approval track. A stablecoin denominated in Vietnamese dong or pegged to the dong must be fully reserved in dong-denominated assets held with a licensed Vietnamese bank; the reserves are subject to regular audit and the issuer must publish monthly attestations. Foreign-currency-pegged stablecoins may be approved if the issuer demonstrates equivalent reserve backing and provides the SBV with real-time visibility into issuance, redemption and reserve movements.

AML, KYC and transaction-monitoring obligations during the pilot

Pilot participants are subject to Vietnam's anti-money-laundering and counter-terrorist-financing framework, including customer due diligence, suspicious-transaction reporting and record-keeping obligations. The applicant must establish a compliance function headed by a qualified AML officer, implement risk-based KYC procedures that capture customer identity, source of funds and the purpose of the account, and maintain a transaction-monitoring system capable of detecting patterns consistent with money laundering, terrorist financing or sanctions evasion.

The Travel Rule – the obligation to pass originator and beneficiary information with virtual-asset transfers above a threshold – applies to pilot participants when they interact with other regulated VASPs. Vietnam's implementation follows the Financial Action Task Force (FATF) Recommendation 16; the specific data fields and the technical standard for message exchange are set out in SBV guidance. For transfers below the threshold, simplified information may suffice, but the participant must still screen both parties against sanctions lists and maintain records for the prescribed retention period.

Suspicious-activity reporting is mandatory and immediate. If a transaction or a pattern of transactions raises a red flag – unusual volume, rapid movement of funds through multiple wallets, transactions involving jurisdictions under enhanced scrutiny – the participant must file a report with Vietnam's Financial Intelligence Unit within a defined window, typically 24 to 48 hours. The participant is prohibited from notifying the customer that a report has been filed (the "tipping-off" prohibition common to AML regimes worldwide).

A compliance miss during the pilot – a missed STR, a KYC gap discovered during an SBV inspection – can result in suspension or termination of the pilot authorisation. Operators moving from lighter-touch regimes underestimate the AML intensity Vietnam's framework demands. If a prior application in another ASEAN market stalled on compliance design, a second read can surface the structural reason and the route forward. Contact info@oboluslaw.com for a pre-submission compliance audit.

Data-localisation and cybersecurity requirements

Vietnam's cybersecurity law requires that personal data and transaction data relating to Vietnamese users be stored on servers physically located in Vietnam. For a pilot participant, this means that customer records, transaction logs, wallet addresses and KYC documentation must reside on Vietnam-domiciled infrastructure. The participant may replicate this data to offshore systems for disaster recovery or group reporting, but the primary data store must be in-country and accessible to the SBV on request.

The data-localisation rule creates architectural and cost implications. A regional platform running on cloud infrastructure in Singapore or AWS Tokyo must provision Vietnam-specific instances or co-locate servers in a Vietnam data centre. The participant must ensure that data flows between the Vietnam instance and the group's global systems comply with Vietnam's cross-border data-transfer rules, which generally require that any outbound transfer be logged, that the receiving jurisdiction offer equivalent data-protection standards, and that the participant obtain SBV clearance for certain categories of sensitive data.

Cybersecurity controls are audited as part of the technical-review phase. The SBV expects the participant to implement multi-factor authentication for all administrative access, encryption at rest and in transit for customer data, intrusion-detection and incident-response procedures, and regular penetration testing by an independent third party. Cybersecurity incidents – a data breach, a wallet compromise, a distributed-denial-of-service attack that disrupts service – must be reported to the SBV within hours, and the participant must demonstrate that it has contained the incident, notified affected customers and taken remedial action.

Banking, payments and the cross-border money flow

A Vietnam pilot participant needs a local bank account to hold customer fiat deposits and to facilitate dong-crypto conversions. Vietnamese banks have historically been cautious about opening accounts for virtual-asset businesses, and the SBV's pilot framework does not compel banks to provide service. An applicant's banking strategy is therefore a critical path item: securing a bank willing to hold customer funds, process inbound deposits and execute outbound withdrawals is often more time-consuming than the regulatory application itself.

The participant's corporate account structure must segregate customer funds from operating funds. Customer deposits are held in a trust or escrow account (or an equivalent segregated arrangement recognised under Vietnamese banking law), and the participant may not use those funds for operational expenses, capital expenditures or lending. The bank providing the customer-funds account is expected to cooperate with SBV supervision, providing the regulator with account statements and transaction records on request.

For an operator serving customers outside Vietnam, the question becomes whether the pilot authorisation permits cross-border flows. The pilot framework does not prohibit a participant from facilitating transfers to or from foreign wallets or exchanges, but the participant must apply Vietnam's AML and sanctions controls to those transactions and must comply with any foreign-exchange restrictions that apply to dong conversions. If the participant allows users to deposit or withdraw in foreign fiat currency (USD, EUR), it may need a separate foreign-exchange or payment-services licence, depending on how the transaction is structured and whether it involves conversion to dong at any stage.

Pilot duration, transition to full licence and exit scenarios

The pilot authorisation is granted for a defined period, typically one to two years, during which the participant operates under enhanced supervision. At the end of the pilot period, the SBV assesses the participant's compliance record, operational stability, customer-complaint history and the overall performance of the pilot cohort. If the assessment is favourable, the participant may apply for a full virtual-asset service provider licence under whatever permanent regime Vietnam enacts following the pilot's conclusion.

Transition to a full licence is not automatic. The participant must submit a fresh application, demonstrate that it meets any additional requirements introduced in the final framework (capital, governance, systems) and undergo a further review. The advantage is that the SBV already has visibility into the participant's operations, and the track record built during the pilot weighs in the participant's favour.

If the SBV decides not to extend a participant's authorisation – because of compliance failures, financial instability or a strategic decision to limit the number of licensed providers – the participant must wind down its Vietnam operations in an orderly manner. This means returning customer assets, closing accounts, deleting or archiving data in compliance with Vietnam's data-retention rules, and notifying customers of the cessation. The pilot authorisation may include a wind-down protocol specifying the timeline, the customer-notification requirements and the SBV's oversight role during the exit phase.

How Vietnam's pilot compares to neighbouring ASEAN regimes

Vietnam's pilot sits within a broader Southeast Asian regulatory picture that includes Singapore's Payment Services Act, Thailand's SEC licensing for digital-asset exchanges, the Philippines' BSP registration for virtual-asset service providers and Malaysia's emerging framework. Each market has chosen a different entry model – Singapore uses tiered licensing with significant capital and governance requirements, Thailand requires exchange operators to be licensed by the securities regulator, the Philippines combines central-bank registration with securities oversight for token offerings, and Malaysia is moving toward a dedicated digital-asset framework under its central bank and securities commission.

For an operator choosing between these markets, the decision matrix turns on capital availability, tolerance for local-ownership requirements, data-residency flexibility and the target user base. Singapore offers the strongest passporting potential (under bilateral and ASEAN frameworks), but the capital and compliance burden is high. Thailand's regime is well-established but exchange licensing is tightly controlled and new licences are issued sparingly. The Philippines offers faster registration but weaker legal certainty around token classification and tax treatment. Vietnam's pilot is experimental, which means regulatory risk (the framework may change or the pilot may not convert to a permanent licence), but it offers access to a large domestic market with significant retail interest in digital assets.

An operator building a regional hub typically chooses Singapore or Hong Kong for the holding company and booking, then layers in local licences or representative offices in target markets. Vietnam's data-localisation and ownership rules make it difficult to serve the market from offshore, so a Vietnam play generally requires a dedicated subsidiary and a local team – a heavier lift than a cross-border marketing or partnership model.

Related at OBOLUS

FAQ

How long does a crypto licence take to obtain?

Timelines vary by jurisdiction and licence type. In well-established regimes with clear application procedures, an operator can move from submission to authorisation in three to six months if the application is complete and the technical systems are ready for audit. Regimes that require local ownership, data residency or enhanced capital – or that process applications in limited windows – may take nine months to over a year. Pilot frameworks like Vietnam's introduce additional variability because the regulator is assessing not only the applicant but also the design of the framework itself. Planning a realistic timeline means understanding the specific steps – pre-qualification, technical audit, fit-and-proper review, public comment – and the regulator's current processing speed, which changes as the regime matures.

Which jurisdiction suits my crypto business?

The right jurisdiction depends on where your customers are, where you can bank, where your team can work and where the regulatory regime matches your risk appetite. If you serve institutional or high-net-worth clients globally and need strong legal certainty, a Tier 1 financial centre – Switzerland, Singapore, certain UAE free zones – is the natural choice. If you target retail in a specific region, you may need a licence in that market regardless of where the business is headquartered. If speed and cost are paramount and the business model is simple (a single service, a defined token set, no lending or derivatives), a mid-tier regime with faster licensing may work, provided you can bank there. The cross-border analysis – where the entity, the licence, the bank accounts and the substance sit, and how they interact – is more important than the headline licensing process, because every piece affects the others.

Do I need a separate custody licence?

It depends on the jurisdiction and how custody is embedded in your service. Some regimes treat custody as a standalone regulated activity requiring its own licence or registration; others fold custody into the exchange or payment-service licence. In the EU under MiCA, custody is a distinct CASP service, so a custodian-only operator applies for authorisation covering that service alone. In Singapore, digital-payment-token custody falls under the Payment Services Act and requires a licence unless the operator qualifies for an exemption (for example, custody incidental to another licensed activity). In several offshore centres, custody is unregulated or lightly regulated, but the operator still faces AML registration and, increasingly, requirements to segregate customer assets and maintain insurance. The custody question also implicates insurance, capital requirements and liability – if the platform holds customer keys, a loss or hack creates direct legal and financial exposure, and the regulator will expect the operator to have addressed that risk through a combination of capital, cold storage and third-party coverage.

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 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. We map the licence stack across operating, custody and payment layers before you commit, and we coordinate freezing relief and on-chain tracing across leading common-law forums when recovery speed is critical. To discuss your situation, contact info@oboluslaw.com.

By Aisha Tan, Licensing & Jurisdictions Analyst – advising on cross-border digital-asset licensing, regulatory strategy and multi-jurisdiction compliance for exchanges and issuers expanding into emerging and frontier markets.

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