DPO Radio

Since 28 September 2026, Decree 320/2026/NĐ-CP has changed how organizations in Vietnam deal with electronic identification:
Legal status. The Government issued Decree 320 on 13 August 2026, on the proposal of the Minister of Public Security. It has been in force since 28 September 2026. It was issued on the basis of the Law on Identification, as amended by Law 118/2025/QH15, and the Law on Data.
An amendment, not a replacement. Decree 320 amends and supplements Decree 69/2024/NĐ-CP on electronic identification and authentication. Most of its twenty articles rewrite numbered articles that stay in Decree 69, so you read the two decrees together and cite each obligation to both.
Not the draft law. Decree 320 is separate from the 2026 draft law on electronic identification and authentication, which is still a draft.

Decree 69/2024/NĐ-CP is still the operative decree on electronic identification and authentication. Project 06 is the population-data programme that the application and databases sit within. Decree 320 is the amendment to Decree 69.
To act on the amendment, you need both the amending article and the article it changes, because the rest of Decree 69 still applies unchanged. For example:
The amendment also reaches outside the identity stack. It amends Decree 77/2020/NĐ-CP on automated border-control gates, as already amended by Decree 67/2024/NĐ-CP, and repeals Article 11 of Decree 77.
| Decree 320 article | Decree 69 article changed | What it requires | What to do |
|---|---|---|---|
| Article 2 | Amends Article 4(4) | Agencies and organizations may not require an original or copy of a document already integrated into the National Identification Application. Fees and charges for online public services through the application are reduced or waived | List the integrated document types in your intake procedure, so staff do not decide at the counter |
| Article 3 | Amends Article 7 | Foreigners lawfully entering or residing in Vietnam, and organizations established or registered in Vietnam, may hold accounts, with no distinction by level | Foreign-invested entities and their staff become eligible. Record which category each subject falls into |
| Article 4 | Amends Article 8 | Documents that are not state secrets synchronise automatically from connected databases. Updates happen immediately on change, within 24 hours where objectively delayed, and within 5 minutes on a citizen's request in the application | Set up the update path so you can measure the elapsed time |
| Article 4 | Amends Article 8(6) | Looking up another person's integrated information needs that person's consent. Where they lack capacity, are under 14, are declared missing or have died, a lawful representative or heir consents | Record the consent basis with every third-party lookup |
| Article 10 | Amends Article 18 | Connecting a system needs a cybersecurity plan meeting information-system security level 3 or above, a written request stating scope and purpose, and a security inspection. Access history is kept and shown to the subject. Extracted information may not be shared onward | Hold the level 3 evidence before you request a connection. Log documents, purpose, count, time and accessor |
| Article 19 | Adds Article 40(9) | Electronic transaction accounts on digital platforms in twelve named sectors must be linked and authenticated with an electronic identification account | Inventory accounts by sector and by creation date |
| Article 19 | Adds Article 40(10) | For other sectors, the relevant minister issues the specific list of online transactions in scope | Watch for ministerial lists. Assume nothing about a sector until its list is issued |
| Article 15 | Adds Article 34(13) | The Ministry of Public Security inspects, periodically or ad hoc, whether platform accounts were linked and authenticated before use | Keep a linkage record for each account |
Accounts on platforms serving national defence, security or cross-border services are linked and authenticated before use, once the platform meets the conditions and is connected. That is a trigger, not a date, and it should not be planned as one.
| Obligation | Timeline | Reference |
|---|---|---|
| Decree takes effect | 28 September 2026 | Article 20(3) |
| National digital platforms integrate electronic identification for authentication, login and transactions | 30 December 2026 | Article 20(3) |
| Covered non-banking accounts created before the effective date are linked and authenticated | 30 December 2026 | Article 20(3) |
| Banking-sector accounts created before the effective date are linked and authenticated | 29 June 2027 | Article 20(3) |
| Update a changed document where an immediate update is not possible | 24 hours | Article 4 |
| Update on a citizen's request in the application | 5 minutes | Article 4 |
| Process an integration request where the issuer has no database | 5 working days | Article 4 |
| Issue a foreigner's account where biometrics are already held | 2 working days | Article 7 |
| Issue a foreigner's account where they are not | 5 working days | Article 7 |
| Issue an organization's account that needs verification | 10 working days | Article 7 |
| Connect a system after the security inspection is complete | 5 working days | Article 10 |
| Notify that an authentication-service dossier is incomplete | 2 working days | Article 11 |
| Seek ministry opinions on a complete dossier | 2 working days | Article 11 |
| Ministries examine, appraise and reply | 7 working days | Article 11 |
| Appraise, inspect on site and issue the confirmation | 20 working days | Article 11 |
Decree 320 prescribes no new form. The Decree 69 forms for application, amendment, confirmation, revocation and reporting still apply, and the Ministry of Public Security still issues the eligibility confirmation on form XT03. What changed is the procedure behind them.
The appendix holds two official reference lists, not forms:
Each row names the managing ministry, the field, the document and the document type. Nothing on either list is filled in or submitted.

Once Decree 320 is added to your workspace, it sits beneath Decree 69 with its own effective date and active status. Each of its twenty requirements names the amending article and the Decree 69 article it changes, so you can trace any obligation to the text that now governs it.
The two dates cover different accounts, and treating them as one is the likeliest planning error:
The defence, security and cross-border case is tracked as a trigger, with no invented date.
List 1 and List 2 are browsable reference lists with their row counts, not 197 form records. A list of document types is not something you fill in, and ComplianceOne does not present it as one.
The Decree 69 forms were annotated, not duplicated. TK01, XT01, XT02 and XT03 each carry a note on the revised procedure and timetable, so you see the form and the new clock in one place.
Runs the linkage applicability assessment and tracks each deadline against the accounts it covers.
Explore Program GovernanceHolds the per-account linkage records and the account lifecycle events.
Explore Access and AccountabilityRecords which integrated document types your intake process may no longer demand.
Explore Data MappingKeeps the Decree 69 forms current with the revised procedure, and keeps the appendix lists apart from them.
Explore Compliance FormsKeeps the access history that is retained and shown back to the identity subject.
Explore Audit TrailOrganizations operating under Decree 320 should confirm:
See how ComplianceOne helps structure evidence, ownership, and review for this framework.

No. It amends and supplements Decree 69, which remains the operative decree. Most of Decree 320's articles rewrite articles that stay in Decree 69, so cite every obligation to both the amending article and the article it changes.
No. The 2026 draft law on electronic identification and authentication is a separate instrument and is still a draft. Decree 320 is a government decree amending an existing decree. Keep the two apart in planning material.
Electronic transaction accounts on digital platforms in twelve named sectors. Non-banking accounts created before 28 September 2026 must be linked by 30 December 2026. National digital platforms must integrate electronic identification for authentication and login by the same date. Banking-sector accounts created before the effective date have until 29 June 2027. Accounts created after the decree takes effect are linked before use.
Not yet. For other sectors, the relevant minister must first issue the specific list of online transactions that must be linked. Until that list exists, assume nothing about the sector's obligations.
No. They are official reference lists of document types integrated on the National Identification Application: 57 rows for individuals and 140 for agencies and organizations. Use them to tell your intake process which documents it may no longer demand on paper.
Generally no. State agencies and political and socio-political organizations paying from the state budget must disburse through the social welfare account. A private organization is reached only where it operates payment, banking, wallet or welfare-disbursement systems.

Test scoped workflows, evidence, and review with your compliance team.

Review applicability, evidence sources, and operating-model requirements.