One identity for the entire digital journey

Customers shouldn't have to prove their identity at every touchpoint with a business. When digital identity is properly connected, a single authentication can unlock an entire service journey—while also placing higher demands on security and data governance.

From September 28, 2026, Decree 320/2026/ND-CP will come into effect. The new regulations expand the scope of eligibility for electronic identification accounts to include foreigners legally entering or residing in Vietnam who require them, and no longer categorize accounts by level. (Government document)

This account can help users access public services and conduct electronic transactions in areas such as credit, telecommunications, transportation, e-commerce, and import/export. However, the new policy only creates a legal framework. The actual experience depends on how each organization integrates electronic identification into its system. (Tuoi Tre News)

DUDI Software's Perspective

What's noteworthy isn't just that foreigners now have an additional account on VNeID. The bigger change is the potential for creating a shared identity layer between users and digital services.

From a system development perspective, businesses shouldn't view this as simply adding a login button to a website. Electronic identification only creates value when the authentication results are linked to applications, CRM, contracts, orders, and back-end service processes.

If these systems remain separate, even verified customers will have to re-enter their information, resubmit documents, and wait for staff to manually check them. New technology may appear in the interface, but the old operating methods remain virtually unchanged.

Websites and applications must change from the very first step.

In banking, tourism, telecommunications, logistics, or e-commerce, foreign customers often face more verification steps than domestic customers. Language differences, paperwork, and name formatting can easily lead to inconsistent data.

By integrating electronic identification, websites and applications can shorten the registration process. Verified information no longer needs to be requested through multiple different forms.

However, businesses shouldn't simply copy all identifying data to their system just because they can. A proper design should require only the necessary information for each transaction, clearly explain its purpose, and provide a way to handle situations where electronic authentication fails.

A good digital experience isn't about eliminating every step. It's about retaining only the essential steps and making users understand why they exist.

CRM needs to correctly identify a customer.

An international customer can use the website to register for services, contact via the app, visit a physical store, and call customer support. If each channel creates a separate profile, the business will see multiple accounts but won't realize they belong to the same person.

Electronic identification can help CRM consolidate interactions into a single customer profile. This allows employees to understand which services a customer has subscribed to, what stage their application is currently in, and how they were verified.

However, identity verification does not mean that customers have consented to receive advertisements. Businesses must still keep identifying information, transaction data, and consent separate for marketing purposes.

This is a crucial line between personalizing services and using data beyond its original purpose.

ERP and new internal processes determine efficiency.

Once the customer is authenticated, the data can proceed to the contract signing process, order creation, invoice generation, or service delivery. If employees still have to download information from the website and re-enter it into the ERP system, the business is not truly automated.

The system needs to clearly define which data sources are considered official, which departments have access, and which changes must be saved. When an identity account is locked or information is updated, the relevant systems also need to have corresponding handling mechanisms.

Businesses don't necessarily need to store all identifying data in every software application. In many cases, the system only needs to store the authentication result, the authentication time, and the necessary reference code. This approach helps limit the amount of sensitive data copied to too many locations.

AI should only use the necessary portion of the data.

With a unified identity, AI can assist in classifying requests, guiding procedures in multiple languages, or forwarding files to the correct department. However, AI should not automatically have access to all of a customer's identifying information.

Each task requires the right data scope. A procedure assistant may need to know the language and type of service, but doesn't necessarily need to see fingerprints, documents, or financial history.

As AI becomes more deeply involved in processes, businesses increasingly need to implement access control, mask sensitive data, and record access history.

Where should a business begin?

  • Recreate the journey of a foreign customer from registration and verification to service usage.
  • Determine which data actually needs to be stored in the website, CRM, and ERP systems.
  • Design a mechanism for access control, consent management, and handling of authentication failures.

A digital identity account doesn't automatically create a seamless experience. Value only emerges when websites, applications, and operating systems all utilize that identity within a unified, controlled architecture that serves the intended business purpose.