DPO Radio

AesirX ComplianceOne | Decree 69/2024/NĐ-CP on eID and Authentication

Overview Image

Decree 69/2024/NĐ-CP: Scope and Current Status

What the decree does. 

If your organization holds electronic identity accounts, relies on authentication, or runs an electronic authentication service in Vietnam, Decree 69/2024/NĐ-CP on Electronic Identification and Authentication sets your rules. It covers:

  • electronic identity accounts and their lifecycle;
  • the authentication levels that apply to them;
  • eligibility to provide an electronic authentication service.

When it applies. 

The Government issued the decree on 25 June 2024. It took effect on 1 July 2024, the same day as the Identity Law 26/2023/QH15 it implements. It replaced Decree 59/2022/NĐ-CP of 5 September 2022.

The amendment from 28 September 2026. 

Decree 320/2026/NĐ-CP amends and supplements Decree 69 from that date. Decree 69 stays in force: most of the amendment rewrites numbered articles that remain in it, so from that date you read every obligation against both decrees. The amendment changes:

  • who may hold an electronic identification account;
  • how issued documents synchronise from connected databases;
  • the conditions and timetable for connecting a system;
  • the procedure for confirming an electronic authentication service;
  • a new linkage obligation for electronic transaction accounts across twelve sectors.

Confirm how the decree applies to your organization with qualified advisers.

Overview Image

How Decree 69 Relates to the Vietnam Data Law

Decree 69 turns the Vietnam Identity Law 26/2023/QH15 into working procedure for electronic identification. The Law sets the identity baseline: identity information, the identity card and the identity database. It is also the legal basis for electronic identification. Decree 69 is the only instrument in the stack with verified official forms.

Project 06 (Đề án 06), approved by Decision 06/QĐ-TTg of 6 January 2022, sits alongside the decree under the same Law. It is a national programme that shapes population-database and VNeID integration. It prescribes no official forms, and ComplianceOne covers it on the Identity Law page.

Evidence you record for Decree 69 can be linked to related frameworks. Each link keeps the other framework's obligations and legal status as they are.

Technical Provisions and Compliance Obligations

Operational AreaComplianceOne Support
ApplicabilityScope each stage of the e-ID account lifecycle (creation, activation, change, suspension, termination) and the authentication-service eligibility rules, the decree's two requirement categories.
Operational workLog authentication events with method, result, time and relying service, and connect each one to its e-ID account record.
Official formsSeven verified official forms: TK01 (applying for an electronic identity account), TK03 (locking or unlocking an electronic identity account or card) and XT01 to XT05 (applying for authentication-service eligibility, amending it, the issued confirmation, the revocation decision and the activity report).
Trust regimeThe decree's 19 regulated identity attribute types, four ranked authentication levels, ten verification methods and the electronic authentication service, available once Decree 69 is added to your workspace.
Identity recordsHold regulated identity profiles, the attributes each one carries, and the verification and authentication events recorded against them, without storing any attribute value.
Internal recordsSeven lifecycle and evidence templates prepared in ComplianceOne, labelled as internal working documents and kept apart from the official forms.
Audit readinessKeep the TK and XT application, confirmation and revocation trail next to authentication-event evidence.
Amendment from 28 September 2026Decree 320/2026/NĐ-CP revises the procedures behind TK01, XT01, XT02 and XT03 without issuing a new form. It adds the sector account-linkage obligation. Under its Article 20(3), linkage is due before 31 December 2026 for national digital platforms and covered non-banking accounts (the last day is 30 December 2026) and before 30 June 2027 for banking-sector accounts (the last day is 29 June 2027).

What Decree 69 Declares as a Trust Regime

Once Decree 69 is added to your workspace, ComplianceOne gives you the decree's own lists of attributes, methods and levels to record against. When the decree changes, the update reaches your workspace without a product change.

19 regulated identity attribute types. 

They cover both individuals and organizations: from the personal identification number, date of birth, facial image and fingerprint to an organization's name, establishment date, head-office address, tax code and enterprise code. Eight of the 19 are restricted.

Ten verification methods. 

Each attribute type lists the methods the decree permits for it. Your record shows what was verified and by which method.

Four authentication levels. 

Article 20 ranks them from level 01 to level 04 as combinations of authentication factors, with biometric factors entering at the third level. ComplianceOne follows the decree's own ranking, so nothing depends on guessing which way the numbering runs.

One trust service and six submission means. 

The electronic authentication service is a conditional business line; you apply for eligibility on form XT01. The decree also names six submission means. Two are portals it names explicitly: the National Public Service Portal and the Ministry of Public Security's own portal. ComplianceOne lists them separately because the decree does.

Where Decree 69 Evidence Is Recorded

A regulated identity attribute is recorded without its value, and without a hash of one. The register has no field for a personal identification number, a date of birth or a tax reference. These values come from small, structured ranges, so a hash can be reversed by trying candidates until one matches. A stored hash would hold a recoverable identity number under a name that looks safe.

Instead, each record holds the evidence that a verification happened:

  • which attribute type, asserted by which issuer;
  • which of the decree's methods was used, when, and with what result;
  • a protected attachment where the underlying document lives.

That is what a supervising authority asks for, and it is enough to answer them.

One timeline per identity. 

Verification and authentication events sit together against the identity they belong to. Each keeps its method, result, time and the assurance level claimed. If a recorded level is higher than the method supports, ComplianceOne flags the gap rather than correcting it silently. Your organization may have a reason, and the record keeps both the claim and the flag.

Filings to the Ministry of Public Security. 

Each dossier you file is recorded as an electronic submission: the channel used, the hash of the payload sent, the receipt that came back and any later amendment. ComplianceOne records that a filing was made; it does not send it.

Overview Image

How ComplianceOne Supports Decree 69 Compliance

ComplianceOne keeps e-ID account lifecycle evidence (creation, activation, change, suspension, termination) apart from authentication-event evidence (method, result, time, relying service). That matches Decree 69's two requirement categories. The official TK and XT forms keep their identifiers, and the seven internal templates stay labelled as working aids.

Where Decree 69 covers a filing, ComplianceOne helps you assemble a package ready for the authority or an audit.

You hold the evidence; the Ministry of Public Security runs the identity system. An electronic identity account, its class and its status are set by the Ministry's own system. ComplianceOne issues none of them and authenticates nobody.

Related Modules

Data MappingData Mapping

Maintains electronic identity data inventories, identity attributes, processing flows, and VNeID integration records across systems.

Explore Data Mapping

Data ClassificationData Classification

Classifies electronic identity and authentication information, with documented handling rules, ownership, and review history.

Explore Data Classification

Program GovernanceProgram Governance

Assigns accountable owners, manages recurring reviews, and tracks governance activities for electronic identity operations.

Explore Program Governance

Compliance FormsCompliance Forms

Supports the seven official Decree 69 forms and keeps internal lifecycle records clearly separate.

Explore Compliance Forms

Audit TrailAudit Trail

Preserves contributor, review, approval, evidence, and change history across electronic identity and authentication records.

Explore Audit Trail

Compliance Readiness Checklist

Confirm that Decree 69 applies to you and check its current status, including the Decree 320 amendment.

Assign accountable owners and reviewers.

Use only official forms verified against the source.

Link supporting evidence and related framework records.

Record human review and approval.

Keep audit history for later inspection.

Background Image

See Decree 69 Compliance in Action

See how ComplianceOne helps structure evidence, ownership, and review for this framework.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Frequently Asked Questions

Yes. Decree 69/2024/NĐ-CP was issued on 25 June 2024, took effect on 1 July 2024 and replaced Decree 59/2022/NĐ-CP. ComplianceOne keeps it apart from draft and neighbouring frameworks.

Yes. Decree 320/2026/NĐ-CP amends and supplements it from 28 September 2026; it is an amendment, not a replacement. The forms stay the same: TK01, TK03 and XT01 to XT05 still apply. What changes is the procedure and timetable behind several of them, who may hold an account, and which accounts must be linked to one.

It implements the Identity Law 26/2023/QH15 through the e-ID account and authentication-eligibility rules behind the TK and XT forms. In ComplianceOne it keeps its own status, evidence and review history.

Seven, all verified against the source: TK01, TK03 and XT01 to XT05. They cover applying for an electronic identity account, locking and unlocking an account or card, and the authentication-service eligibility lifecycle, including amendment, revocation and activity reporting. Decree 320/2026/NĐ-CP adds no form. Its appendix holds two reference lists of integrable document types, not anything a filer completes.

The seven TK and XT forms (TK01, TK03, XT01 to XT05) keep their official identifiers and are labelled as issued by the authority. The seven internal templates are labelled as working documents prepared in ComplianceOne and are never presented as prescribed forms. They cover the attribute inventory, account lifecycle, authentication events, state-data reuse, Project 06 integration, VNeID dependency and the dossier checklist.

No, and it stores no hash of one either. There is no field for a personal identification number, a date of birth, a passport number or a tax reference. A hash protects a secret only when there are too many possible inputs to try, and these values have few. What the register holds is the evidence that a verification took place: the attribute type, the issuer, the verification method, the time, the result and a protected attachment.

No. Only the Ministry of Public Security's electronic identification and authentication system establishes an electronic identity account, its class and its status. ComplianceOne records the evidence your organization holds about the regulated identities it relies on, including authentication events carried out by another system.

No. It is not legal advice, and it does not guarantee compliance, certification or acceptance by an authority. It structures evidence, ownership, workflow and review; your organization remains responsible for legal interpretation.

Yes. E-ID account and authentication evidence can be linked to Electronic Transactions Law and Decree 23 e-signature records, the PDPL, the Data Law and the Electronic Labor Contracts overlay. Each keeps its own framework and audit history.

Next Steps

Icon Image

Start a Compliance Pilot

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

Icon Image

Discuss Your Compliance Needs

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