IP Library Granted Patent US 12,541,758
Granted Patent B2
US 12,541,758 · App. 18/063,284 · Granted Feb 3, 2026

Systems and methods for transacting over a network

Inventors: Drummond Reed (Seattle, WA); Brent Zundel (American Fork, UT); Martin Mesršmíd (Prague, CZ); Allan Thomson (Pleasanton, CA)
Assignee: Avast Software s.r.o.
G06Q20/3825G06Q20/3821G06Q20/401G06Q2220/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,541,758
App. No.
18/063,284
Granted
Feb 3, 2026
Kind
B2
Abstract

Systems and methods for transacting over a network. A first agent and a second agent are provided. The second agent is operable to transact with a third agent for use of a network-enabled service based on a first transaction policy from a fourth agent, the third agent enabled to communicate with a fifth agent. The first agent is operable to communicate with the second agent to facilitate the transacting by the second agent with the third agent for the use of the network-enabled service based on the first transaction policy and communicate with the fifth agent to facilitate the transacting by the second agent with the third agent for the use of the network-enabled service.

Claims (70)

1 . A method for transacting over a network to initiate a use of a network-enabled service, the method comprising:

receiving by a third agent from a second agent executed by a computing device a request via the network to initiate the use of the network-enabled service;

transmitting by the third agent to the second agent a request for at least one data point that supports verification of an entity to initiate the use of the network-enabled service;

receiving by the third agent from the second agent at least one requirement for fulfilling the at least one data point, the at least one requirement comprising a first transaction policy, the first transaction policy received by the second agent from a fourth agent;

transmitting by the third agent to the second agent a digitally signed transaction comprising a digital signature;

receiving by a first agent the digitally signed transaction from the second agent;

cryptographically verifying by the first agent the digitally signed transaction;

receiving by the first agent the first transaction policy from the second agent;

receiving by the third agent from the second agent a first cryptographically verifiable proof comprising the at least one data point;

receiving by the first agent from a fifth agent based on the first transaction policy a first transaction proof;

transmitting by the first agent to a sixth agent the first transaction proof;

receiving by the first agent from the sixth agent a first unlock signature for the first cryptographically verifiable proof;

transmitting by the first agent the first unlock signature to the fifth agent;

receiving by the third agent from the fifth agent the first unlock signature;

cryptographically unlocking by the third agent the first cryptographically verifiable proof using the first unlock signature; and

enabling by the third agent the use of the network-enabled service responsive to the unlocking of the first cryptographically verifiable proof by the third agent.

2 . The method of claim 1 , further comprising updating by the first agent a ledger based on the digitally signed transaction received from the second agent.

3 . The method of claim 1 , further comprising:

transmitting by the second agent a first credential request to the fourth agent responsive to the request for the at least one data point from the third agent;

receiving by the second agent a first cryptographically verifiable credential from the fourth agent;

generating by the second agent a cryptographically verifiable presentation comprising the first cryptographically verifiable proof based on the first cryptographically verifiable credential; and

transmitting by the second agent to the third agent the cryptographically verifiable presentation comprising the first cryptographically verifiable proof.

4 . The method of claim 3 , further comprising:

receiving by the second agent from the fourth agent a request for entity-identifying information;

acquiring by the second agent from a user the entity-identifying information; and

transmitting by the second agent to the fourth agent the entity-identifying information.

5 . The method of claim 4 , wherein the entity-identifying information comprises at least one of a driver license, business license, passport, or social security card.

6 . The method of claim 3 , wherein the first unlock signature is for the first cryptographically verifiable credential, the method further comprising:

receiving by the fifth agent from the third agent the digitally signed transaction, the first transaction policy, and the first cryptographically verifiable proof; and

transmitting by the fifth agent to the third agent the first unlock signature.

7 . The method of claim 6 , further comprising updating by the fifth agent a ledger based on the digitally signed transaction, the first transaction policy, and the first cryptographically verifiable proof.

8 . The method of claim 3 , wherein the first cryptographically verifiable proof comprises the first cryptographically verifiable credential.

9 . The method of claim 1 , wherein the at least one data point comprises at least one of a first name, last name, date of birth, credit card number, social security number, or passport number.

10 . The method of claim 1 , wherein the at least one requirement further comprises at least one of a price or a service level agreement.

11 . The method of claim 1 , wherein the entity comprises at least one of a user of the second agent or an organization associated with the user of the second agent.

12 . The method of claim 1 , wherein the first transaction proof is a cryptographically verifiable payment proof.

13 . The method of claim 1 , further comprising:

cryptographically verifying by the first agent the digital signature; and

receiving by the first agent from the fifth agent the first transaction proof further based on the cryptographically verifying by the first agent the digital signature.

14 . The method of claim 1 , further comprising:

deidentifying by the first agent a source of the first transaction proof; and

transmitting by the first agent the deidentified first transaction proof to the sixth agent.

15 . The method of claim 1 , wherein the at least one data point comprises a plurality of data points comprising at a least a first data point and at least a second data point, the method further comprising:

transmitting by the second agent a first credential request to the fourth agent responsive to the request for the at least one data point from the third agent;

transmitting by the second agent a second credential request to a seventh agent responsive to the request for the at least one data point from the third agent;

receiving by the second agent a first cryptographically verifiable credential from the fourth agent;

receiving by the second agent from the seventh agent a second transaction policy;

receiving by the second agent from the seventh agent a second cryptographically verifiable credential;

transmitting by the second agent to the third agent the second transaction policy;

receiving by the first agent from the second agent the second transaction policy;

transmitting by the second agent to the third agent the first cryptographically verifiable proof comprising the at least the first data point based on the first cryptographically verifiable credential; and

transmitting by the second agent to the third agent a second cryptographically verifiable proof comprising the at least the second data point based on the second cryptographically verifiable credential.

16 . The method of claim 15 , further comprising:

deidentifying by the first agent a source of the first transaction proof;

transmitting by the first agent the deidentified first transaction proof to the sixth agent;

receiving by the first agent a second transaction proof based on the second transaction policy from the fifth agent;

deidentifying by the first agent a source of the second transaction proof; and

transmitting by the first agent the deidentified second transaction proof to an eighth agent.

17 . The method of claim 15 , further comprising:

generating by the second agent a cryptographically verifiable presentation comprising the first cryptographically verifiable proof based on the first cryptographically verifiable credential and the second cryptographically verifiable proof based on the second cryptographically verifiable credential; and

transmitting by the second agent to the third agent the cryptographically verifiable presentation comprising the first cryptographically verifiable proof and the second cryptographically verifiable proof.

18 . The method of claim 15 , further comprising:

receiving by the second agent from the fourth agent a request for first entity-identifying information;

receiving by the second agent from the seventh agent a request for second entity-identifying information;

acquiring by the second agent from a user the first entity-identifying information and the second entity-identifying information;

transmitting by the second agent to the fourth agent the first entity-identifying information to transact for the first cryptographically verifiable credential; and

transmitting by the second agent to the seventh agent the second entity-identifying information to transact for the second cryptographically verifiable credential.

19 . The method of claim 15 , wherein the first unlock signature is for the first cryptographically verifiable credential, the method further comprising:

receiving by the first agent from an eighth agent a second unlock signature for the second cryptographically verifiable credential; and

transmitting by the first agent the second unlock signature for the second cryptographically verifiable credential to the fifth agent.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2025
From: GEN DIGITAL AMERICAS S.R.O.
To: GEN DIGITAL INC.
Reel/Frame 071771/0767 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2025
From: AVAST SOFTWARE S.R.O.
To: GEN DIGITAL AMERICAS S.R.O.
Reel/Frame 071777/0341 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2023
From: REED, DRUMMOND; ZUNDEL, BRENT; THOMSON, ALLAN; MESRSMID, MARTIN
To: AVAST SOFTWARE S.R.O.
Reel/Frame 062549/0014 →
Continuity (1)
Related Publication 20240193592A1 · Jun 13, 2024
References Cited (73)
US 4910693A · Sperling et al. · 1990 [cited by applicant]
US 5825880A · Sudia et al. · 1998 [cited by applicant]
US 5862325A · Reed et al. · 1999 [cited by applicant]
US 6044205A · Reed et al. · 2000 [cited by applicant]
US 6088717A · Reed et al. · 2000 [cited by applicant]
US 6327578B1 · Linehan · 2001 [cited by examiner]
US 6345288B1 · Reed et al. · 2002 [cited by applicant]
US 6757710B2 · Reed · 2004 [cited by applicant]
US 7341177B2 · Shepley et al. · 2008 [cited by applicant]
US 7425795B2 · Anderson et al. · 2008 [cited by applicant]
US 7490762B2 · Shepley et al. · 2009 [cited by applicant]
US 7934644B2 · Shepley et al. · 2011 [cited by applicant]
US 8316237B1 · Felsher · 2012 [cited by examiner]
US 10373158B1 · James · 2019 [cited by examiner]
US 11139955B1 · So · 2021 [cited by examiner]
US 11184395B1 · Novotny et al. · 2021 [cited by applicant]
US 20020188490A1 · Kruse · 2002 [cited by applicant]
US 20030158820A1 · Mathur et al. · 2003 [cited by applicant]
US 20090300747A1 · Ahn · 2009 [cited by examiner]
US 20140281491A1 · Zaverucha et al. · 2014 [cited by applicant]
US 20150095999A1 · Toth · 2015 [cited by examiner]
US 20190097812A1 · Toth · 2019 [cited by applicant]
US 20200127845A1 · Yang et al. · 2020 [cited by applicant]
US 20200136921A1 · Doshi et al. · 2020 [cited by applicant]
US 20200302441A1 · Collinge et al. · 2020 [cited by applicant]
US 20210014060A1 · Giorgiadis et al. · 2021 [cited by applicant]
US 20210287770A1 · Anderson · 2021 [cited by examiner]
US 20220272085A1 · Novotny et al. · 2022 [cited by applicant]
US 20220329653A1 · Govindarajan et al. · 2022 [cited by applicant]
US 20230259922A1 · Rao · 2023 [cited by examiner]
US 20240187238A1 · Pourtabatabaie et al. · 2024 [cited by applicant]
EP 4254234A1 · 2023 [cited by applicant]
WO 2018031856 · 2018 [cited by applicant]
WO WO2019191213 · 2019 [cited by applicant]
WO WO2020233236 · 2020 [cited by applicant]
WO WO2022096126 · 2022 [cited by applicant]
International Search Report dated Oct. 24, 2023 for International Patent Application No. PCTUS2370319. [cited by applicant]
U.S. Appl. No. 17/872,250, filed Jul. 25, 2022. [cited by applicant]
International Patent Application No. PCTUS2370319 filed Jul. 17, 2023. [cited by applicant]
U.S. Appl. No. 18/052,752, filed Nov. 4, 2022. [cited by applicant]
Aries RFC 0046: Mediators and Relays, Daniel Hardman, Dec. 1, 2018 through Feb. 1, 2019, GitHub, https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0046-mediators-and-relays/README.md, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0478: Coprotocols, Daniel Hardman, Feb. 3, 2020 through May 19, 2020, GitHub, https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0478-coprotocols/README.md, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0075: Payment Decorators, Sam Curren et al., Apr. 22, 2019 through Jun. 11, 2019,GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/features/0075-payment-decorators, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0453: Issue Credential Protocol 2.0, Nikita Khateev et al., Mar. 23, 2020 through Apr. 15, 2021, GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/features/0453-issue-credential-v2, accessed Sep. 28,… [cited by applicant]
Aries RFC 0454: Present Proof Protocol 2.0, Nikita Khateev et al., May 27, 2020 through Apr. 15, 2021, GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/features/0454-present-proof-v2, accessed Sep. 14, 2023. [cited by applicant]
Aries RFC 0004: Agents, Daniel Hardman, Nov. 1, 2017 “(approx, backdated)” through Jan. 15, 2019, GitHub, https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0004-agents, accessed Sep. 14, 2023. [cited by applicant]
DIDComm Messaging v2.x Editor's Draft, Sam Curren et al., The Decentralized Identity Foundation, https://identity.foundation/didcomm-messaging/spec/, accessed Sep. 14, 2023. [cited by applicant]
Credential.md, Dmitry Khovratoavich et al., GitHub, https://github.com/sovrin-foundation/protocol/blob/master/themis/credential.md, accessed Sep. 14, 2023. [cited by applicant]
Alex Preukschat; Drummond Reed, Self-Sovereign Identity: Decentralized digital identity and verifiable credentials, Manning, 2021. [cited by applicant]
Machine Translation of EP 4254234 A1 (Year: 2023). [cited by applicant]
Machine Translation of WO 2020233236 A1 (Year 2020). [cited by applicant]
Dmitry Khovratovich; Jason Law, Sovrin: Digital Identities in the Blockchain Era, Dec. 2016, Sovrin. org. [cited by applicant]
“Decentralized Identity and Verifiable Credentials”, Microsoft Security, Sep. 28, 2022 pp. 1-11. [cited by applicant]
Daniel Hardman, How DIDs, Keys, Credentials, and Agents Work in Sovrin, Apr. 2018, Sovrin. org. [cited by applicant]
Phillip J. Windley, How Sovrin Works, Oct. 3, 2016, Sovrin.org. [cited by applicant]
Office Action dated Nov. 14, 2024 for U.S. Appl. No. 18/052,752. [cited by applicant]
Updated Office Action dated Dec. 3, 2024 for U.S. Appl. No. 18/052,752. [cited by applicant]
Reply dated Jan. 22, 2025 for U.S. Appl. No. 18/052,752. [cited by applicant]
Notice of Allowance dated May 14, 2025 for U.S. Appl. No. 18/052,752. [cited by applicant]
Office Action dated Feb. 13, 2025 for U.S. Appl. No. 18/066,213. [cited by applicant]
Reply dated Apr. 9, 2025 for U.S. Appl. No. 18/066,213. [cited by applicant]
Notice of Allowance dated May 30, 2025 for U.S. Appl. No. 18/066,213. [cited by applicant]
Office Action dated Nov. 27, 2024 for U.S. Appl. No. 17/872,250. [cited by applicant]
Reply dated Jan. 22, 2025 for U.S. Appl. No. 17/872,250. [cited by applicant]
Office Action dated May 16, 2025 for U.S. Appl. No. 17/872,250. [cited by applicant]
Reply dated Aug. 4, 2025 for U.S. Appl. No. 17/872,250. [cited by applicant]
Notice of Allowance dated Mar. 6, 2025 for U.S. Appl. No. 18/446,068. [cited by applicant]
Notice of Allowance dated Jun. 25, 2025 for U.S. Appl. No. 18/446,068. [cited by applicant]
Japanese Office Action dated Jul. 8, 2025 for Japanese Patent Application No. 2025-504595 including English translation of Office Action. [cited by applicant]
Machine translation of JP2019525645. [cited by applicant]
Machine translation of WO2022102930. [cited by applicant]
Machine translation of JP2021111412. [cited by applicant]
Machine translation of CN109716373A. [cited by applicant]