# US 2026/0094151 A1 · Online Decentralized Identity Verification for a Multi-sided Network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0094151 A1
- Document ID: US20260094151A1
- Status: Published application
- Kind: A1
- Application number: 19/394,516
- Filed: 2025-11-19
- Published: 2026-04-02
- Earliest claimed: 2022-02-15
- Assignees: Paypal, Inc.
- Applicants: PayPal, Inc.
- Inventors: Anita Paul Rao; Sargis Dudaklyan; Matt Wyman
- Web page: https://patentgrep.com/patent/US20260094151A1

## CPC

- G06Q 20/3823: {combining multiple encryption tools for a transaction}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/363: {with the personal data of a user}
- G06Q 20/3829: {involving key management}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 50/265: {Personal security, identity or safety}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3247: {involving digital signatures}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques are disclosed relating to facilitating secure communication of private user data between different entities for a verification process conducted during an electronic interaction between the user and a verifier entity. In disclosed embodiments, a verification service executing on a server computer system for a verification session for verifying a holder entity on behalf of a verifier entity receives a verification request from a remote computer system. The verification request includes an attestation proof generated from one or more credentials and the verification service communicates with a holder service that manages an identity storage storing credentials for the holder entity. The verification service transmits, to the verifier service, the attestation proof and then receives, from the verifier service based on the proof, verification results that are usable by the verifier to determine whether to process an action requested by the holder prior to requesting verification.

## Claims

### Claim 1

(canceled)

### Claim 2

A method, comprising:
receiving, by a holder service from a verifier service, a verification request for credentials of a holder entity, the verification request specifying one or more identification requirements;
in response to the verification request, determining, by the holder service, a least amount of user data included in one or more verifiable credentials of the holder entity that satisfies the one or more identification requirements, wherein the one or more verifiable credentials are stored in a wallet of the holder entity;
generating, by the holder service based on the determining, an attestation proof that includes the determined least amount of user data included in the one or more verifiable credentials;
sending, by the holder service to the verifier service, a response to the verification request that includes the attestation proof, a formal description of the one or more verifiable credentials used to generate the attestation proof, and a public key; and
receiving, by the holder service from the verifier service, a confirmation message for the attestation proof, wherein the confirmation message indicates a decentralized identifier (DID) of an issuer entity corresponding to the one or more verifiable credentials is verified, wherein the verifier service verifies the DID on a blockchain based on the formal description and the public key.

### Claim 3 (depends on 2)

The method of claim 2, wherein the attestation proof is a compound attestation proof generated using multiple different credentials stored in the wallet of the holder entity.

### Claim 4 (depends on 2)

The method of claim 2, further comprising, prior to receiving the verification request:
receiving by the holder service from an issuer service, the one or more verifiable credentials of the holder entity, wherein the issue entity writes, to the blockchain for respective credentials, the DID of the issuer entity, a schema of respective ones of the one or more verifiable credentials, and the public key.

### Claim 5 (depends on 2)

The method of claim 2, wherein the one or more verifiable credentials are received from the issuer entity via a scannable code displayed by the holder service at a holder device of the holder entity, and wherein
in response to an issuer device of the issuer entity scanning the scannable code, establishing, by the holder service, a secure connection between the holder device and the issuer device; and
receiving, by the holder service from an issuer service corresponding to the issuer entity and via the secure connection, a transmission of at least one of the one or more verifiable credentials.

### Claim 6 (depends on 5)

The method of claim 5, wherein the one or more verifiable credentials transmitted via the secure connection are encrypted using the DID of the issuer entity.

### Claim 7 (depends on 2)

The method of claim 2, wherein the verification request is received by the holder service via a device of the holder entity scanning a quick response (QR) code displayed via a user interface of a verifier device associated with a verifier entity utilizing the verifier service.

### Claim 8 (depends on 2)

The method of claim 2, wherein the DID of the issuer entity is usable by the verifier service to verify authenticity via the blockchain of one or more verifiable credentials of the holder entity received by the verifier service.

### Claim 9 (depends on 2)

The method of claim 2, wherein the confirmation message for the attestation proof is further received based on the verifier service determining, via the blockchain, whether the issuer entity has revoked one or more of the one or more verifiable credentials used to generate the attestation proof.

### Claim 10

A non-transitory computer-readable medium having program instructions stored thereon that are executable by a holder service executing on a server computer system to perform operations comprising:
receiving, from a verifier service, a verification request for credentials of a holder entity, wherein the verification request specifies one or more identification requirements;
in response to the verification request, determining a subset of holder data included in a set of holder data of the holder entity that satisfies the identification requirements of the verification request, wherein the set of holder data is stored in a wallet of the holder entity;
generating, based on the determining, an attestation proof that includes the subset of the set of holder data;
sending, to the verifier service, a response to the verification request that includes the attestation proof, a formal description of the subset of the set of holder data used to generate the attestation proof, and a public key; and
receiving, from the verifier service, a confirmation message for the attestation proof, wherein the confirmation message is received in response to the verifier service verifying, via a blockchain and based on the formal description and the public key, a DID of an issuer entity corresponding to the subset of the set of holder data.

### Claim 11 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the attestation proof is a compound attestation proof generated using multiple different verifiable credentials stored in the wallet of the holder entity.

### Claim 12 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the attestation proof is generated by:
calculating, based on the holder data, an age of a user associated with the holder data; and
determining whether the calculated age satisfies a minimum age requirement specified in the verification request received from the verifier service for the holder entity.

### Claim 13 (depends on 10)

The non-transitory computer-readable medium of claim 10, further comprising after the determining and prior to generating the attestation proof:
transmitting, by the holder service to a device of the holder entity, a request for approval specifying one or more portions of user data included in one or more verifiable credentials stored in the wallet of the holder entity to be used in generating the attestation proof to be shared with the verifier service for the verification request.

### Claim 14 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the identification requirements of the verification request include an age requirement.

### Claim 15 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the verification request is received by the holder service via a device of the holder entity scanning a QR code displayed via a user interface of a verifier device associated with a verifier entity utilizing the verifier service.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the DID of the issuer entity is usable by the verifier service to verify authenticity via the blockchain of one or more verifiable credentials of the holder entity received by the verifier service.

### Claim 17

A system, comprising at least one processor; and
a memory having instructions stored thereon that are executable by the at least one processor to implement a holder service; wherein the holder service interfaces with a blockchain to:
receive, from a verifier service, a verification request for a holder entity, wherein the verification request specifies one or more identification requirements;
in response to the verification request, determine one or more portions of user data included in one or more verifiable credentials of the holder entity that satisfy the one or more identification requirements of the verification request, wherein the one or more verifiable credentials are stored in a wallet of the holder entity;
generate, based on the determining, an attestation proof that does not include an entirety of the one or more verifiable credentials;
send, to the verifier service, a response to the verification request that includes the attestation proof, a formal description of the one or more verifiable credentials used to generate the attestation proof, and a public key; and
receive, from the verifier service, a confirmation message for the attestation proof, wherein the confirmation message indicates that the verifier service has verified, via the blockchain and based on the formal description and the public key, a decentralized identifier (DID) of an issuer entity corresponding to the one or more verifiable credentials.

### Claim 18 (depends on 17)

The system of claim 17, wherein the identification requirements of the verification request specify a minimum age requirement.

### Claim 19 (depends on 17)

The system of claim 17, wherein the verification request is received by the holder service via a device of the holder entity scanning a QR code displayed via a user interface of a verifier device associated with a verifier entity utilizing the verifier service.

### Claim 20 (depends on 19)

The system of claim 19, wherein the one or more verifiable credentials are transmitted via a secure connection between the issuer entity and the holder entity, and wherein the one or more verifiable credentials are encrypted using a DID of the holder entity.

### Claim 21 (depends on 17)

The system of claim 17, wherein the attestation proof is further generated by the holder service based on determining, via the blockchain, whether the issuer entity has revoked the one or more verifiable credentials used to generate the attestation proof.
