vLEI: The Verifiable LEI, Explained
The vLEI is the cryptographically verifiable version of the Legal Entity Identifier. Here is what it is, how role credentials and the ecosystem work, why it matters for payments and digital identity, and how to approach an implementation.
What is the vLEI?
The vLEI (verifiable LEI) is GLEIF's verifiable credential form of the Legal Entity Identifier. Where a plain LEI is a number in a registry, a vLEI is a cryptographically verifiable credential that proves an organization's identity, and the authority of the people acting for it, without a phone call or a manual check.
It is built on verifiable credential technology (KERI and ACDC), which lets a relying party verify a credential's authenticity and chain of authority directly.
How the vLEI works
The vLEI ecosystem issues credentials in a chain of trust that starts at GLEIF and flows down to an organization and its representatives.
- Qualified vLEI Issuers (QVIs): organizations authorized to issue vLEI credentials to legal entities.
- Legal entity credential: proves the organization's identity, anchored to its LEI.
- Role credentials (OOR and ECR): prove that a named person holds an official or engagement role for the entity.
- Verification: a relying party checks the credential and its chain of authority cryptographically.
Why vLEI matters for payments and identity
Payments are moving toward richer identity and stronger authorization. The vLEI gives a payment or compliance workflow a verifiable answer to who an organization is and whether a given actor is authorized to act for it.
That is directly relevant to Verification of Payee, to authorization and audit evidence in payment operations, and to the emerging world of agentic workflows where machine actors need verifiable authority. It also connects to reference data: the vLEI is anchored to the LEI, so clean LEI data is the foundation.
vLEI in practice: a reference build
The vLEI Auth Platform is a reference build that demonstrates identity proof, policy decision, verdict, evidence, and audit flow end to end. It is a proof-of-work reference pattern, not a production service and not a Qualified vLEI Issuer.
The public demo uses curated, sanitized fixtures. It is the right place to see how a credential-driven authorization flow can be structured before committing to an implementation.
Frequently Asked Questions
- What is the difference between an LEI and a vLEI?
- An LEI is a 20-character identifier in a public registry. A vLEI is a cryptographically verifiable credential form of that identity, so a relying party can verify an organization and the authority of its representatives directly.
- What is a Qualified vLEI Issuer (QVI)?
- A QVI is an organization authorized within the GLEIF ecosystem to issue vLEI credentials to legal entities. The vLEI Auth Platform reference build is not a QVI.
- Is the vLEI Auth Platform a production service?
- No. It is a reference build that demonstrates the identity, policy, verdict, evidence, and audit flow using curated, sanitized fixtures. It is proof-of-work, not production financial infrastructure.
- Why does vLEI matter for payments?
- It provides verifiable answers to organizational identity and actor authorization, which supports Verification of Payee, authorization and audit evidence, and emerging agentic workflows. It is anchored to the LEI, so clean LEI data is the foundation.