Verifiable Credentials Presentation and Issuance – Proof Help Center
Verifiable Credentials Presentation and Issuance via Proof's API enables organizations to securely request cryptographically signed, user-consented identity attributes—such as name or age verification—through a single OAuth redirect using OID4VCP and OID4VCI standards, allowing users to selectively disclose only necessary information without exposing their full credentials, while organizations receive a machine-readable verifiable presentation (`vp_token`) for compliance and business logic without managing credential infrastructure.
The short answer: Verifiable Credentials (VC) Presentation & Issuance lets your organization request cryptographically signed proof of a user's identity — like their name or age — through a single API redirect, without ever handling their raw identity data.
What It Does
Using the OpenID for Verifiable Credential Presentation (OID4VCP) and Issuance (OID4VCI) standards, your organization redirects users to Proof, where they authenticate and consent to share specific identity attributes — such as name, date of birth, or age verification. Proof returns a verifiable presentation (a vp_token) confirming the credential was presented, without your organization ever receiving the user's full underlying credential.
- No credential infrastructure for your organization to build or maintain.
- Users practice selective disclosure — sharing only what's needed for your use case (e.g., confirming "over 21" without sharing a full identity record).
- The returned
vp_tokenis machine-readable, enabling downstream compliance and business logic that a PDF identity report can't support.
How It Works
For your organization (the relying party):
- Configure an OAuth application in Proof with valid redirect URIs.
- Use the Identity Protocol API to create an identity transaction, then redirect the user to Proof.
- Once the user authenticates and consents, Proof returns a verifiable presentation (
vp_token) to your redirect URI.
For the end user:
- The experience feels like a standard OAuth login: the user is redirected to Proof, prompted for email and SMS authentication, and — if not previously enrolled — completes identity verification (credential analysis / KBA).
- A consent screen then shows exactly which attributes will be shared.
- Once the user consents, they're returned to your application.
Getting Access
This feature is available via API for eligible Business and Real Estate Premium tier organizations. It's on by default for Business Pro+ and above via API tools, and enabled by your CSM or Sales team.
Roles involved:
- Owners and Admins — configure the OAuth application.
- Signers and Recipients — complete the verification and consent flow.
To get set up, your organization will need:
- The
enable_identity_protocolFlag enabled on your organization. - A configured OAuth application with valid redirect URIs.
Contact Proof Support to get your organization enabled and to configure your OAuth application.
What This Feature Doesn't Do
- Doesn't transfer credentials wallet-to-wallet — the credential stays within Proof's infrastructure; your organization receives a verifiable presentation token, not the underlying credential.
- Doesn't support offline presentation — requires an active Proof session and an internet connection.
- Doesn't offer self-sovereign credential portability — users cannot export or carry their credential to third-party wallets.
- Not available in any portal UI — this is an API integration only, with no Keystone or admin UI for organizations to manage presentations.
Developer Resources
For full technical implementation details, see the Verifiable Credential Presentation developer documentation.
Summary Checklist
- Request a verifiable presentation of user identity attributes through a single API redirect.
- Users share only what's needed via selective disclosure — no full identity handoff.
- Requires the enable_identity_protocol flag and a configured OAuth application — contact your CSM or sales to get set up.
- API integration only — no portal UI for organizations to manage presentations.
If you are still unsure, contact Proof Support for help.
Related
Create an Identify Transaction – Proof Help Center
An Identify transaction in Proof allows you to verify an individual's identity without requiring a signature, using methods like credential analysis, IAL2-compliant verification with fraud agent backup, or knowledge-based authentication, and can be created via API or EasyLink by configuring transaction details, adding recipient info, and optionally notifying colleagues, with each transaction verifying one person at a time and resulting in a detailed identity report for fraud prevention in sensitive processes.
Proof: Our Brand Story
The Proof brand story highlights the launch of a unified platform that secures digital transactions through audited identity verification, fraud prevention, and digital signatures, inspired by the concept of DNA sequencing to emphasize unique individual identity and trust in an increasingly digital world.
Introducing Persistent Identity: The Foundation of Repeatable Trust
Persistent Identity is a secure digital ID system that enables individuals to verify their identity once to a high-assurance standard, store it on the Proof platform, and reuse it across multiple online transactions and organizations via the Identity Authorization Network, thereby reducing inefficiency, abandonment rates, and trust erosion caused by repeated identity verifications in an increasingly digital and threat-prone environment.
Supplemental Terms
The Supplemental Terms document, last modified on June 19, 2026, outlines additional user-, service-, and use case-specific terms applicable to various categories such as Business entities, Notary Users, Subscribers, and specific services like In-House Notary and Real Estate, while also defining incident priority levels ranging from critical to minimal business impact based on the severity of service functionality disruption.
Identity timeline with Proof Defend – Proof Help Center
Proof Defend provides owners and admins with an identity timeline for each transaction, displaying a detailed audit trail of the signer's full identity verification journey—including completed steps, timestamps, provided information, and alerts with explanations—to help businesses monitor and understand the verification process.
Your Fastest Lease Is Only as Fast as Your POA Process
Despite digital advances in leasing workflows, the reliance on manual, paper-based powers of attorney (POAs) significantly delays equipment finance deals by causing operational inefficiencies, increasing risk of fraud, and stalling critical processes like lien releases and asset delivery, even though electronic notarization is legally recognized and could streamline these transactions.