What Is Digital Identity? Components and How It Is Verified

A digital identity is the set of identifiers, attributes, and credentials that represent a person in digital systems. It is not an account, and it is not a document.

What makes one digital identity trustworthy and another worthless is assurance: how rigorously the identity was proven at enrolment, and how strongly it is authenticated afterwards.

NIST separates those into Identity Assurance Level and Authenticator Assurance Level, and treating them as one number is the most common design error in the field.

What Is Digital Identity?

A digital identity is the representation of a person, organisation, or device in a digital system, expressed as data that a system can process.

Two things it is commonly confused with are worth separating immediately. A digital identity is not a login account, and it is not a scanned document. An account is a container that a digital identity may be bound to. A document is one piece of evidence used to establish it.

The distinction that actually matters is between a claimed identity and a proven one. Anyone can assert a name and birth date. A digital identity becomes useful when a system has established, to a defined level of confidence, that the assertion corresponds to a real person who is the one making it.

The Components of a Digital Identity

Component	What it is	Philippine example
Identifier	A value that distinguishes one subject from all others	PhilSys Number, TIN, customer ID
Attribute	A characteristic of the subject	Name, date of birth, address, nationality
Credential	Evidence binding identifiers and attributes to the subject	PhilID, ePhilID, passport, driver’s licence
Authenticator	What the subject uses to prove they are the same person later	Password, passkey, biometric, device
Biometric reference	A stored template used for matching	Face template captured at onboarding

Most confusion in this area comes from collapsing these into each other. A passport is a credential, not an identity. A face template is an authenticator, not an identity. The identity is the whole assembly, and each part fails differently.

Identifiers, Attributes, and Credentials

Identifiers distinguish. Their defining property is uniqueness within a namespace, and a well-designed identifier carries no meaning beyond that. The Philippine system illustrates why this matters: the PhilSys Number and the PhilSys Card Number are different identifiers with different handling rules, covered in our guide to the PSN and PCN. Storing the wrong one creates both a compliance problem and a data reconciliation problem.

Attributes describe. Some are stable across a lifetime, such as date of birth. Others change, such as address and civil status. A digital identity built on attributes that drift, without a refresh mechanism, degrades quietly rather than failing visibly.

Credentials bind. A credential is an assertion by an issuer that a set of attributes belongs to a subject, which is why the issuer’s authority is what gives it weight. A government-issued ID carries more evidentiary force than a club membership card for exactly that reason, not because it is harder to forge.

One consequence follows for anyone designing verification: credentials can be revoked, expire, or be superseded, while the underlying identity persists. A person whose passport expired has not stopped existing. Systems that conflate credential validity with identity validity reject people for the wrong reason.

Digital Identity vs Online Account: Not the Same Thing

An account is a relationship between a service and a subject. A digital identity is what the service believes about who that subject is.

	Online account	Digital identity
Scope	One service	Potentially portable across services
Created by	Registration	Identity proofing
Requires proof of who you are?	Not necessarily	By definition
Can be pseudonymous?	Yes	Only where the design allows it
Fails by	Being taken over	Being wrongly established

That last row is the useful one, because the two failure modes need different defences. An account that gets taken over was correctly established and then compromised. An identity that was wrongly established was never correct, and every control built on top of it inherits the error.

Assurance Levels: Why Not All Digital Identities Are Equal

This is the framework worth knowing, because it turns a vague question about trustworthiness into two separate design decisions.

NIST Special Publication 800-63 is the reference suite, and although it was written for US federal agencies it functions as the de facto global benchmark, cited by banks, government portals, and technology platforms well outside that context. The suite decomposes assurance into three independent dimensions.

Identity Assurance Level (IAL), governed by SP 800-63A, measures how rigorously identity was proven at enrolment. IAL1 requires no proofing and accepts self-asserted attributes. IAL2 introduces proofing of validated identity evidence, remotely or in person. IAL3 requires physical presence, in person or supervised remote, with biometric comparison of the applicant to the strongest piece of identity evidence.

Authenticator Assurance Level (AAL), governed by SP 800-63B, measures the strength of authentication at each subsequent login. AAL1 permits single-factor methods. AAL2 requires multi-factor. AAL3 requires hardware-based authenticators.

Federation Assurance Level (FAL), governed by SP 800-63C, applies where one system asserts an identity to another.

The decision rule that makes this practical

The levels are deliberately decoupled, and the selection logic for each is different.

Choose IAL based on the harm that results if a false identity is successfully enrolled. Choose AAL based on the harm that results if a legitimate account is taken over after enrolment.

Those are two different risks with two different owners, which is why a system can legitimately require high IAL and moderate AAL, or the reverse. A lending platform where enrolment fraud is the dominant threat weights IAL. A wallet holding balances where takeover is the dominant threat weights AAL. Treating assurance as a single dial forces one of them to be wrong.

SP 800-63-4, released in final form in 2025, moved further in that direction with a risk-based Digital Identity Risk Management approach, retiring the older idea of a single overall level of assurance. It also brought phishing-resistant authenticators such as FIDO passkeys explicitly into AAL2 and AAL3, and recognised mobile driver’s licences and verifiable credentials as valid identity evidence.

Philippine institutions arrived at the same conclusion on the authentication side through a different route. BSP Circular 1213 required a move away from interceptable authentication for high-risk transactions by 30 June 2026, which is the same problem NIST addressed by pushing phishing resistance. Our guide to account takeover covers what that changed in practice.

How a Digital Identity Is Proven at Onboarding

Identity proofing runs three checks, and skipping any one of them leaves a specific gap.

Is the evidence genuine? Document verification tests whether the credential presented was actually issued and has not been altered.

Do the attributes correspond to a real person? A perfectly genuine-looking document can describe someone who does not exist, which is the mechanism behind synthetic identity fraud.

Is the person presenting it the subject? Biometric comparison between a live capture and the credential portrait, with liveness confirming physical presence.

Our guide to identity verification covers how businesses run these checks in practice.

PhilSys and the Philippine Digital Identity Landscape

The Philippines has something many markets lack: a foundational identity system designed as digital infrastructure rather than as a card programme.

PhilSys, established under RA 11055, assigns a PhilSys Number as a permanent identifier and issues credentials in three formats, the PhilID card, the printed ePhilID, and the Digital National ID in the eGovPH app, all equally valid under Section 13.

Three design features make it a genuine digital identity rather than a digitised card.

Uniqueness is enforced at enrolment. Biometric deduplication runs before a PSN is generated, so the identifier itself is gated on the person not already existing in the registry.

Verification is available as a service. PhilSys Check authenticates a credential against the registry using the digital signature embedded in the QR code, rather than relying on visual inspection.

Acceptance is mandatory. Under RA 11055 the PhilID is single and sufficient proof of identity, which no other Philippine credential can claim.

What the landscape still lacks is federation. A person proving their identity to one institution cannot currently carry that proof to another, so every institution repeats full proofing from scratch. That is the gap FAL describes, and it is where most of the remaining friction in Philippine onboarding sits.

Digital Identity and the Data Privacy Act

Building a digital identity means accumulating personal data, and Philippine law places real constraints on that.

One point is frequently stated incorrectly. Under RA 10173 biometric data is personal information, not sensitive personal information, because Section 3(l) does not enumerate it. What makes a typical identity record sensitive is the government-issued identifiers inside it, along with age and civil status.

The proportionality principle bites hardest here. A digital identity assembled to the maximum extent the technology allows, rather than to the extent the purpose requires, is difficult to defend. Our guide to the Data Privacy Act covers lawful basis, retention, and the NPC’s position on biometric collection.

Where Digital Identity Fails: Synthetic and Stolen

Two failure modes account for most identity fraud, and they defeat different controls.

Stolen identity. Real attributes belonging to a real person, used by someone else. Document verification passes because the credential is genuine. Attribute checks pass because the person exists. What fails is the binding between the credential and the presenter, which is why biometric comparison with liveness is the control that catches it.

Synthetic identity. Attributes assembled to describe a person who does not exist, sometimes mixing real and fabricated data. Biometric comparison passes, because the face presented genuinely matches the fabricated credential. What fails is the existence check.

Our guide to identity fraud covers both patterns in the Philippine context.

The structural lesson is that no single control covers both. A verification stack strong on document forensics and weak on biometrics catches synthetics and misses impersonation. The reverse configuration does the opposite, and both look like a working system until the specific fraud type they are blind to arrives.

Frequently Asked Questions About Digital Identity

What is digital identity in simple terms?

The set of identifiers, attributes, and credentials that represent a person in digital systems, together with the authenticators they use to prove they are the same person later. It is not the same as an online account, which is a relationship with one service and may require no proof of who you are.

What are the components of a digital identity?

Identifiers that distinguish one subject from others, attributes that describe the subject, credentials that bind attributes to the subject on an issuer’s authority, authenticators used to prove continuity at each later interaction, and where biometrics are used, a stored reference template.

What are examples of digital identity in the Philippines?

PhilSys is the foundational example, combining a permanent PhilSys Number with credentials in three formats and a verification service. Bank and e-wallet customer identities established through eKYC are functional digital identities within those services, and employment or professional identities such as a PRC registration operate in narrower domains.

What is the difference between IAL and AAL?

IAL measures how rigorously identity was proven at enrolment; AAL measures the strength of authentication at each subsequent login. They are selected independently: IAL according to the harm if a false identity is enrolled, and AAL according to the harm if a legitimate account is later taken over.

Is a digital identity the same as a digital ID card?

No. A digital ID such as the Digital National ID in eGovPH is a credential, meaning one piece of evidence within a digital identity. The identity is the wider assembly of identifiers, attributes, credentials, and authenticators, and it persists even when a particular credential expires or is replaced.

Can a digital identity be reused across institutions in the Philippines?

Not currently in any general way. Each institution performs its own identity proofing, even where a customer has already been verified elsewhere. Federation, which NIST addresses through Federation Assurance Level, is the mechanism that would allow reuse, and it is the main structural gap remaining in Philippine onboarding.

Assurance Is Two Decisions, Not One

Most organisations describe their identity posture with a single word: strong, or adequate, or in need of investment. That framing hides the decision that actually matters, because identity systems fail in two independent ways and the defences are unrelated.

An identity wrongly established at enrolment produces a customer who was never real, and every downstream control inherits that error silently. An account compromised after enrolment produces a real customer whose access belongs to someone else. Investment in one does nothing for the other, which is why NIST separates IAL from AAL and why the selection logic differs.

For Philippine institutions the enrolment side has the stronger foundation available, because PhilSys provides a verifiable credential and a verification service that most markets lack. Using it well means proving identity properly once, at the point where the whole relationship is defined.

Verihubs eKYC API handles that proofing layer, verifying government IDs across 15+ Philippine document types with PhilSys authentication, biometric liveness, and deepfake detection.

Talk to the Verihubs team about the identity proofing layer beneath your digital services.