What is a vLEI? Verifiable Legal Entity Identifier explained

GLEIF describes the vLEI as a decentralized digital identity. ISO 17442-3 standardized the use of vLEIs as digital credentials in 2024.[1] A vLEI can support automated verification in signing, reporting, payments, due diligence, and other organization-to-organization workflows. It does not remove transaction controls, policy checks, or current credential-status verification.

What vLEI means

vLEI means verifiable Legal Entity Identifier.

The underlying LEI identifies the legal entity. The vLEI adds a cryptographically verifiable credential layer that can connect three things:[1]

1. the legal entity's identity, confirmed through its LEI
2. the identity of an individual
3. the official organizational role that the individual holds

This distinction matters. A database field containing an LEI can help identify an organization, but it does not prove that the person presenting it is authorized to act for that organization. A vLEI is designed to make that authority and role machine-verifiable within its trust framework.

vLEI in plain English: an LEI tells a system which legal entity it is dealing with. A vLEI can also help the system verify who is acting for that entity and in what official role.

vLEI definition in one sentence

A vLEI is a verifiable credential that binds a legal entity's LEI to the identity and official role of a person acting for that entity, allowing software to verify the relationship cryptographically.[1]

How the vLEI trust chain works

Global LEI System and GLEIF governance
-> Qualified vLEI Issuer
-> legal entity credential
-> official-role credential for a person
-> signed digital interaction
-> cryptographic verification plus current policy checks

GLEIF describes itself as the root of trust for the vLEI issuance system and says vLEIs are traceable through a cryptographically protected credential chain back to the entity's LEI record in the Global LEI Index.[1]

GLEIF says an organization authorized to issue vLEIs is a vLEI Issuer, also referred to as a Qualified vLEI Issuer or QVI. Issuers perform issuance, verification, and revocation under the vLEI Ecosystem Governance Framework.[2]

A relying system still needs to validate the presented credential, issuer chain, status or revocation information, official role, intended action, and local policy.

What a vLEI can verify

A valid vLEI presentation can support computational verification of:

• the legal entity represented by the credential
• the person presenting a role credential
• the official role associated with that person
• the credential chain back to the governed vLEI ecosystem
• the integrity of the signed presentation

The exact result depends on the credential type, issuer, presentation, verification software, status information, and policy in force.

What a vLEI does not prove by itself

A vLEI does not automatically prove:

• that a payment should be released
• that a transaction is free from fraud
• that an account belongs to the entity
• that sanctions, KYC, KYB, credit, or mandate checks passed
• that the person is authorized for every action
• that a credential is current unless status and revocation checks are performed
• that a reference demo is connected to a live Qualified vLEI Issuer

Use vLEI verification as an identity and authority input to a wider control decision.

Practical vLEI use cases

Corporate signing

A recipient can verify the entity, signer, and organizational role attached to a digitally signed document rather than relying on a name, email domain, or uploaded certificate alone.

Regulatory reporting

A filing workflow can verify that a submission came from a person acting in an official role for the reporting entity.

Business payments

A payment approval or instruction can carry verifiable organizational identity and role evidence. The payment platform still needs mandate, amount, account, fraud, sanctions, segregation-of-duties, and release controls.

Supply-chain and counterparty due diligence

A supplier or counterparty can present verifiable organizational and role credentials during onboarding or a high-risk change request.

Agentic workflows

A software agent can present evidence about the organization and role under which it is acting. That does not grant unlimited autonomy. The relying system must enforce delegation, scope, policy, status, and transaction limits.

LEI vs vLEI

For cross-referencing payment and legal-entity identifiers, see BIC to LEI mapping.

Reference demo boundary

The vLEI Auth Platform project is a reference implementation for exploring credential verification, role evidence, policy checks, and audit receipts. It uses curated or sanitized fixtures and remains non-production.

The project is not a Qualified vLEI Issuer, a GLEIF issuer, a live payment decisioning service, or a claim of compliance readiness. Test credentials are not live ecosystem credentials, and a demonstration verdict does not authorize a real transaction.

The GLEIF vLEI Hackathon 2025 library entry provides additional ecosystem context.

Practitioner takeaway

The vLEI extends legal-entity identification into cryptographically verifiable organizational identity and role evidence. Its value comes from the whole trust and decision chain: issuer qualification, credential integrity, current status, role, presentation, verification software, relying-party policy, and the controls around the intended action.

Sources

[1] GLEIF: The verifiable LEI, accessed August 20, 2026.

[2] GLEIF: Become a vLEI Issuer, accessed August 20, 2026.

[3] GLEIF: vLEI Ecosystem Governance Framework, accessed August 20, 2026.